Avast! 5 Pro and Floppy Drive Seek!?!?!?!?! (SOLVED:D:D:D:D)

[steveoderocker]

Hey,

To whom this may concern (someone with the answer I hope):

All/most of the people on this thread have had this problem. Most of the posts are just people describing that they have this problem. Does anyone have the answer to this problem or can the developers try and figure it out before the release of the next build??

It really is an annoying problem. And  as other people have mentioned, I shouldn't have to disable my working hardware for bugged software.

If someone could come up with a working solution for everyone here, that would be great!


Thanx All!

[Hermite15]

keep rocking steve

[steveoderocker]

keep rocking steve

Thanx Logos

[Vlk]

Guys,

while we're still unable to reproduce the issue, it strikes me that all the people who're experiencing this are using either the Pro AV or the IS. This can't be a coincidence.

I think that one of the modules that may be possibly responsible for this behavior is the Virtualization component (aka sandbox). Therefore, I'd like to ask you to uninstall this component for a while and see if that makes any difference. If it does, we can take it from there and dig a bit deeper.

To remove the component, please go to Control Panel -> Add/Remove Programs -> avast! -> Change/Remove -> Change and uncheck the box that says (surprise surprise ) "Virtualization component".


Thanks much
Vlk

[Savoir]

Bingo !!!
Worked for me ..... and cured the longer than usual boot times I've been experiencing as a side benefit !!

Thanks Vlk ......  but, be aware that I also had the P2P and the IM modules disabled previousily as I never engage in those types of activity. Just for your knowledge.

[steveoderocker]

Hey All!

I am very happy today as MY PROBLEM HAS BEEN SOLVED!!!!!!!! ::D:D:D:D:D:D:DXDXDXDXD

Although, i do still have some followup questions:

A: After uninstalling the sandbox component, why do the settings for it still remain in the main UI allowing to be changed, and it still saying "run a process virtualized"
B: I have noticed that this problem still happens when Skype (4.X) is opened. Although, Skype has no delay while opening, so it is not really much of an issue.

Also, please correct me if I am wrong by making this assumption, though, it seems (nearly) everyone having this problem is using an Asus motherboard (anyone with it in their sig). I also use an Asus M2N-MX American Megatrends MoBo. Could that have any affect of Avast!?

Thank you for all your help users of the avast forums!!!!!!!!!! :D:D:D:D:D:D:D:D:D:D:D:DXD

[Asyn]

Also, please correct me if I am wrong by making this assumption, though, it seems (nearly) everyone having this problem is using an Asus motherboard (anyone with it in their sig). I also use an Asus M2N-MX American Megatrends MoBo. Could that have any affect of Avast!?

If it is related to Asus Motherboards, you can check for driver updates for your board...
http://support.asus.com/download/
asyn

[Savoir]

@steveoderocker

I'm making an assumption here but, here goes anyway:
Since you started this thread, I'm assuming that you have the option somehow\somewhere to change the title of it.
If you change the topic title to something like "Avast! 5 Pro and Floppy Drive Seek!?!?!?!?! SOLVED" then others, with a similar problem, will most likely read it and be able to remedy their own situation and hopefully 'chime in' with their results.

You might also add something like "Stay tuned for further developments from the devs".

Just a thought !!

[steveoderocker]

@steveoderocker

I'm making an assumption here but, here goes anyway:
Since you started this thread, I'm assuming that you have the option somehow\somewhere to change the title of it.
If you change the topic title to something like "Avast! 5 Pro and Floppy Drive Seek!?!?!?!?! SOLVED" then others, with a similar problem, will most likely read it and be able to remedy their own situation and hopefully 'chime in' with their results.

You might also add something like "Stay tuned for further developments from the devs".

Just a thought !!

Hey

@ Saviour: Do you know how  i can do this? I cannot find an option for it. Does anyone know how to do this?


Thanx!

[YoKenny]

@ steveoderocker

Go to the first post:
http://forum.avast.com/index.php?topic=57244.0

There you can change the topic title as you will see MODIFY over on the right.

Please go to PROFILE then Modify Profile then Forum Profile Information then update your Signature: with information like my signature as this helps the helpers offer pertinent advice.

[Savoir]

After uninstalling the sandbox component, why do the settings for it still remain in the main UI allowing to be changed, and it still saying "run a process virtualized"

I can't help with this ... after I uninstalled the Virtualization component ..... I no longer have the option to run a process virtualized nor any sandbox references in UI at all.
Maybe a reboot was needed??  I suspect so, as you haven't followed up for a couple of days.

[doktornotor]

I can't help with this ... after I uninstalled the Virtualization component ..... I no longer have the option to run a process virtualized nor any sandbox references in UI at all.
Maybe a reboot was needed??  I suspect so, as you haven't followed up for a couple of days.

There's a bug making it necessary for some people to uninstall virtualization component two times. Uninstall, reboot, uninstall.

[steveoderocker]

Hey,


Thanx for the replies. It was just a query that was bugging at me (about the UI) - I don't really mind - as long as my problem is solved! :D:D

Anyways,


Thanx everyone for all of your help on this matter. And  i can officially say that this is the only thread on all of the avast forums that actually has a fix for this problem! :D:D:D:D:D:D:D:D:D:D:D:D

Thanx!

steveoderocker XDXDXDXD

[isamuelson]

So when will there be a fix to the virtualization component so that it doesn't do this?

[pk]

So when will there be a fix to the virtualization component so that it doesn't do this?

it's already fixed in avast source code, please wait for the next beta refresh...