So just for others and Avast’s Team info - System is a biostar TZ77B G2140 plenty of ram, booting win7 home prem 32 bit, non eufi mbr serv pak 1.
Yesterday, Avast updated according to the user during usual Live Mail usage.
The system had the big Avast screen up - the user reset the system. Windows would not boot again, it boot looped.
After lengthy troubleshooting I noticed the drive config in the bios was set to IDE mode instead of AHCI.
Switched to AHCI and she finally booted into win 7 32bit home premium again.
Bios had not lost time/clock and no other settings appeared to be changed though it is possible some had. Bios CR2302 battery is fine.
When it booted into win 7 the avast has been updated screen appeared (for the 1st time).
I suspect some Avast coding is to blame… so there’s a heads up for the coders - or users SWITCH IT BACK FROM IDE TO AHCI
Well, I certainly got lucky (I’ll include 50% experience) finding the issue, but as for Avast interference, that would be for the experts to say.
You probably well know an antivirus engine likes to hook the drive channels to prevent a virus, and with
the newer bios, settings are accessible to a degree from windows, so it’s an easy conclusion to make.
The drive configuration page is not the default bios entry thus blaming the user for an errant key strike at boot
, panic and exit makes less sense.
Perhaps Avast was setting itself (through the update) on the drive hook when it locked the system and the three finger salute was issued,
thus the bios setting was specifically in play.
Whatever the nitty gritty details, the info on what occurred is there for the coders and users.
Yes, I do not think I am incorrect - but of course it could be a more complex combination of the software and reset / more an MSFT issue.
Bios is American Megatrands