Author Topic: Can't Boot - aswVmm.sys is corrupt or missing  (Read 29103 times)

0 Members and 1 Guest are viewing this topic.

Offline devnullius

  • Newbie
  • *
  • Posts: 5
Re: Can't Boot - aswVmm.sys is corrupt or missing
« Reply #15 on: September 03, 2019, 02:52:33 PM »
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?

Online bob3160

  • Avast √úberevangelist
  • Probably Bot
  • *****
  • Posts: 45671
  • 61 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: Can't Boot - aswVmm.sys is corrupt or missing
« Reply #16 on: September 03, 2019, 03:15:45 PM »
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?
Posting in a 6 year old topic doesn't make sense.
I suggest you start your own topic and explain your problem in detail.
Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v21H2 64bit, 16 Gig Ram, 1TB SSD, AvastOmni 21.6, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq

Offline devnullius

  • Newbie
  • *
  • Posts: 5
Re: Can't Boot - aswVmm.sys is corrupt or missing
« Reply #17 on: September 03, 2019, 08:36:42 PM »
It does make sense, it's the top Google result and the exact same problem. Thank you

Offline devnullius

  • Newbie
  • *
  • Posts: 5
Re: Can't Boot - aswVmm.sys is corrupt or missing
« Reply #18 on: September 03, 2019, 09:28:03 PM »
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)
« Last Edit: September 03, 2019, 09:40:52 PM by devnullius »