A friend’s Win 7 x64 Laptop won’t boot because the aswVmm.sys file is either missing or corrupted.
What I know so far:
Avast program version is unknown but it is a free version.
He can’t boot into safe mode.
He can’t use the restore to last known good configuration option.
He does not have a Win 7 x64 disc.
He only wants to use a factory restore as a last resort.
Any other ideas? Also, is it possible that a rootkit could have damaged the aswVmm.sys file?
I can’t help him “hands-on” because he lives in another state.
did he uninstall the previous used AV before installing avast?
did he run removal tool to make sure all conflicting files are gone before installing avast?
tools found here. http://singularlabs.com/uninstallers/security-software/
Did he do a system image backup as Windows instructs you too? If so he can mount that image. He can also use a Windows Emergency boot disk with will allow him to repair his system even though it will not boot. He can boot off the disk.
Insert the USB into the sick computer and start the computer. First ensuring that the system is set to boot from USB
Note: If you are not sure how to do that follow the instructions Here
When you reboot you will see this although yours will say windows 7. Click repair my computer
notepad and press Enter.
The notepad opens. Under File menu select Open.
Select “Computer” and find your flash drive letter and close the notepad.
In the command window type e:\frst64.exe and press Enter Note: Replace letter e with the drive letter of your flash drive.
The tool will start to run.
When the tool opens click Yes to disclaimer.
Press Scan button.
It will make a log (FRST.txt) on the flash drive. Please copy and paste it to your reply.
The first time the tool is run, it makes also another log (Addition.txt). Please attach it to your reply.
Wow… and thank you very much essexboy for taking so much time and effort to respond to my (friend’s) issue. That is really a beautiful tutorial but I must ask one more question before I point him to this thread. “Will this procedure preserve his important files that have been created by other installed programs?” Again, thank you so much!
Thank you for responding; however, I’m not sure of a way to instruct him on how to get to the recovery console when he can’t even boot into safe mode and/or he doesn’t have a Win 7 disc. So, as you can see, I’m not expert in this area. Any hints on how that might be accomplished would be greatly appreciated.
Thank you for all your help but I have stopped trying to assist my friend because he wants a “magic button” solution that will make his PC “all better” so I told him where the nearest magic store was located (in his area) and he is now “in-transit” to buy a magic wand. Thank you for all of your efforts!
Tell your friend the next time buy an external hard drive and keep a clean disk image handy. Anything happens such as this or a bad malware infection just mount the stored image and your up and running like nothing ever happened. But he needs to be sure he makes a bootable recovery disk. Easeus Todo Backup is a great free product.
Microsoft does offer a bootable Windows disk which can be downloaded onto another PC and burned.
I’m having similar issues and would like to know how to uninstall Avast before I resort to reinstallation of Windows7. Could you assist me in that essexboy?
Boot from Hiren’s Boot CD or a live Linux distro.
Delete c:\Windows\system32\drivers\avw*.*
Delete the Avast! directories in c:\Program Files and c:\ProgramData
Problem solved.
(Replying to this thread because it was the top Google search result for aswvmm.sys)
I’m stuck in the same repair bootloop. I renamed all offending files but while the boot seems to work for a while, in the end it still gives a bsod. Any chances I can simply replace the corrupted aswvmm.sys?
After renaming / moving the files, I get, after a longer wait period, the following (new) error: inaccessible boot device. I’ll check my BIOS next to see what my disk settings are.
I also did ‘Sfc /Scannow /OFFBOOTDIR=D:\ /OFFWINDIR=D:\Windows’. It found a few problems and corrected it. A second run did not find any problems (same for chkdsk).
…\system32\logfiles\srt\srttrail.txt is clean now, aswvmm.sys isn’t mentioned any longer. I’ll move and rename all asw*.* files and folders back to their original location, hopefully triggering the aswvmm.sys log entry again, and see if I can fix Windows another way. And I am still wondering… Can’t the file simply be replaced?
Post-edit: putting all avast files back in its place did not repeat the original problem (which is the srt-log reference of aswvmm.sys)