Hello,
just wanted to let you know about a major flaw that the most recent update brought for me:
I run Windows 7 Pro x64 SP1 on a Samsung 840 EVO, basis system is a Dell Vostro 3350 (no hardware issues).
Upon updating and restarting, my OS gave me a bluescreen shortly after the Windows 7 logo is shown the first time - with error code 0x0000007B, no system file or other error description mentioned.
Luckily, I had a 2-month old backup on another hdd. So by changing disks and booting from the backup I was sure, there was no other hardware failure. I connected the original disk via USB and ran chkdsk /f several times - either no issues found or something about the Volumebitmap - but chkdsk seemed to have repaired it. Switching disks again and trying once more, still bluescreen unfortunately.
Ok, so using the error code: apparently it refers to a problem with booting, e.g. the OS cannot initialize properly. duckduckgo-ing brought a lot about the issue of ahci and ide drivers - I checked:
started Win7 in Secure Mode and ran regedit: for the msahci value was 0 as necessary but for iastorv it was now "3" - changed it but still bluescreen.
Again, in secure mode I ran msconfig and disabled the autostart-services and program for avast - et voilá, original OS came back to life.
Thought, it might have been the update, so to be sure; I removed avast completely and downloaded the most recent installer to have a fresh and clean version - it led to the same bluescreen again!
So, it seems to me that this version changes something in its autostart behaviour or in one of its services that at least my OS does not like. Anyone having the same/similar issues? Maybe you (as in avast-team) could investigate and suggest what might be responsible for the different behaviour?! My OS is up and running again but without avast and I'd like of course to continue using it ;-)
Thx in advance!
Best regards,