Vista hangs on boot after 120404-1

I have Avast Free 7.0.1426 on Vista Home Basic SP2. Everything went OK untill I got the 120404-1 update that came yesterday in the morning. I shut down my notebook and tried to boot some time later. But I couldn’t - everything stopped just after the desctop appeared on the screen. I did a reboot but everything stopped again. Then I booted in the safe mode, removed Avast and successfully rebooted in the normal mood. After that I cleaned my system and re-installed Avast. The database was updated to 120405-0 and I continued my internet-surfing untill I went to bed.

Today I couldn’t boot normally again! I repeated all the procedure and now I have the 120406-0 update. But, sorry, I am not sure that won’t have to repeat everything once more. :frowning: And one more user has the same problem: http://forum.avast.com/index.php?topic=69524.msg772434#msg772434 The user re-installed Avast too but says that after the 120406-0 update booting isn’t stable.

Can anybody explain what has happened and when the problem will be fixed?

That is rather weird… would you be willing/able to create&upload a full system dump (https://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=71) if that happens again?
(i.e. prepare for the possibility by inserting that special registry key, and use the magical shortcut if it happens again?)

Sorry but I can’t make the dump because I have no SCROLL-LOCK key on my notebook’s keyboard.

I tried to reboot with the 120406-0 update and now even the desktop appeared - I could only a black screen with a lonely mouse pointer on it. So I re-installed my Avast again.

I guess you added something new or special since the 120404-1 update. Maybe you tried to improve the rootkit scanning? Please, remove that “improvement” as soon as possible.

BTW, when I tried to reboot for the first time (with the 120404-1 update), I was prompted that TaskEng hangs and prevents from the shutting down.

The rootkit scan is started later, not that soon (and can be disabled in the Troubleshooting options).
I’m not aware of any changes or “improvements”, other than the usual adding of ordinary detections.

As for me, I didn’t install any new program or a program update before and after the 120404-1 update. The problem started just after that update.

Today I decided to get rid from USB Disc Security and TrendMicro RUBotted. I don’t know why but after that I could boot with Avast on my notebook.

To make it short, I resolved my issue. Something has been damaged in my registry and only the restoration from the registry backup helped me.