Digital signature of aswVmm.sys in windows 10

[REDACTED]

I bought a new windows 10 computer last night - no choice to have 8.1, so I bit the bullet. I have an MSI Apache Pro running windows 10 64-bit on a 5th gen intel i7 processor.

Here's what's going on:

- Installed avast, next reboot, I got a blue recovery screen and the message that my PC/Device needed to be repaired. (Error code: 0xc0000225)

- I used the function that was prompted to choose a boot option, and choose safe mode with command prompt.

- This reboot produced the following error:
The operating system couldn't be loaded because the digital signature of a file couldn't be verified.
File: \Windows\System32\Drivers\aswVmm.sys
Error code: 0xc0000428

- I attempted to repair avast twice. I could still only load my OS if I chose the option that made it ignore digital signatures during the boot check process. I went in to the file, viewed the digital signature, which showed a current date, and manually downloaded it following the prompts in windows - both to my local machine and user. Rebooted - still had error.

At this point, I uninstalled avast, rebooted, and everything loaded fine.

Downloaded avast again so I had a fresh file. Installed it, rebooted, and was right back to the original error. So I uninstalled it, and my computer is working fine again now.

I've used avast for at least 5 years. I don't want to have to replace it, but I don't know what else to do at this point.


If there is a solution I'd love to hear it. I know the exact file, and confirmed that it's not a corrupted installation or a different program.

Help?

[Asyn]

- Which Avast..? (Free/Pro/IS/Premier)
- Which version..?
- Other security related software installed..?
- Which AV(s) did you use before Avast..?

[REDACTED]

- Which Avast..? (Free/Pro/IS/Premier)
- Which version..?
- Other security related software installed..?
- Which AV(s) did you use before Avast..?

Avast Free, newest version (it was downloaded yesterday, so whatever current version is.)
Norton was installed on computer at the factory. I uninstalled it and rebooted prior to installing Avast.
There was nothing other than standard Windows programs installed when I put avast on. It's always the first thing I do after removing factory antivirus software.

I read a lot of reports in the forums about people having troubles with loading their computers or loading avast when re-starting on windows 10. My suspicion is that the digital signature isn't being read properly by windows 10.

[Asyn]

Regarding W10, which build..?

[bob3160]

- Which Avast..? (Free/Pro/IS/Premier)
- Which version..?
- Other security related software installed..?
- Which AV(s) did you use before Avast..?

Avast Free, newest version (it was downloaded yesterday, so whatever current version is.)
Norton was installed on computer at the factory. I uninstalled it and rebooted prior to installing Avast.
There was nothing other than standard Windows programs installed when I put avast on. It's always the first thing I do after removing factory antivirus software.

I read a lot of reports in the forums about people having troubles with loading their computers or loading avast when re-starting on windows 10. My suspicion is that the digital signature isn't being read properly by windows 10.

How was Norton removed

[REDACTED]

I have the same problem on the same computer. It's the latest Windows 10 build and I uninstalled Factory Norton using Windows 10 uninstall in control panel. The difference is that I installed another internet security (AVG) program, which worked fine for 2 days and started doing the exact same thing. I managed to do a complete uninstall today and after several reboots I installed Avast Pro. It installed with no problem and I rebooted 3 times to check it. Then I created a recovery flash drive using MSI recovery. I tried to shut down the Laptop and it got hung up shutting down for over an hour. The next boot up I have the same problem again. The only difference is this time I can boot up if I ignore the digital signature.

[davexnet]

If you're installing the insider builds, then anything is possible.  But if you're on the retail build (build 10240),
this is the  build avast has been tested in and is supposed to work.

I have not seen an official statement on this, but I believe this is the state of affairs.

I'm running the insider builds and have not attempted anything beyond the in-built Windows Defender.

[bob3160]

I have the same problem on the same computer. It's the latest Windows 10 build and I uninstalled Factory Norton using Windows 10 uninstall in control panel. The difference is that I installed another internet security (AVG) program, which worked fine for 2 days and started doing the exact same thing. I managed to do a complete uninstall today and after several reboots I installed Avast Pro. It installed with no problem and I rebooted 3 times to check it. Then I created a recovery flash drive using MSI recovery. I tried to shut down the Laptop and it got hung up shutting down for over an hour. The next boot up I have the same problem again. The only difference is this time I can boot up if I ignore the digital signature.

Removing Norton through the programs and Features section only removes a portion of the program.
The same would apply for removing AVG. See my signature for successfully installing Avast which includes
the use of the removal tools supplied by both Symantec and AVG.

[REDACTED]

Hi all,

I also encountered a problem with Avast Internet Security (latest version - direct from Avast website).  I had done a fresh, clean install of Windows 10 -- then immediately installed Avast.  Upon reboot, the system cannot boot -- and I have to select "Disable driver signature enforcement" in startup options in order to get the system to boot.

As soon as I uninstall Avast -- then it goes back to normal -- no issue at all. 

Clearly there is an issue with driver signing and/or the install process.  I called Support - they essentially said since the software finishes its install that the problem is with Windows and that they cannot help. 

I'll be looking for another product -- but wanted to update this thread for others.

-m

[bob3160]

If this was truly an Avast problem, this forum would be flooded with reports.
I personally have Avast Free and Avast IS running on several computers 32 and 64 bit.
This includes several computers running the latest build without any problems.

[igor]

Well, the driver certainly is signed.
It could be useful to see the file (as copied from the system having booted without driver signature enforcement) to check if it didn't get corrupted somehow. It could also be interesting to check what the particular system says about the file signature on the file's Properties page.

[REDACTED]

I also had this problem (doesn't boot without ignoring driver signature).
I uninstalled Avast since

[REDACTED]

I got burned by the exact same problem. Here are my specs:

1. OS: Windows 10 Enterprise 64bit
2. Tablet: Samsung Slate 700T series (modified XE700T1A-A04US received at Microsoft Build Conference on 2011)
3. BIOS/UEFI: UEFI WIN_05WJ
4. Avast Version: Latest and greatest as of October 22, downloaded from Avast site and installed
5. Secure Boot / TPM / BitLocker: Turned ON

After I installed Avast, on the next boot, I got the exact same error message. For me the problem was, I was lax in saving the Bitlocker recovery key. So I was not able to repair Windows. Also I was not able to boot from USB at that time (I was not aware that for that particular tablet, I needed to have a FAT32 formatted USB with no more than 4GB in primary partition in order to be able to boot). So I had to temporarily stand up PXE/TFTP server to do network boot. After some long arduous hours, I finally got Windows reinstalled.

I am not going to install Avast on any Windows 10 box until I am assured that the root cause is found and resolved. I am now depending on Windows Defender. God save me!

[REDACTED]

If this was truly an Avast problem, this forum would be flooded with reports.
I personally have Avast Free and Avast IS running on several computers 32 and 64 bit.
This includes several computers running the latest build without any problems.

Just because the forum is not flooded with reports, does not mean that it's not an Avast problem. Here is why:

1. The problem started appearing immediately after installing Avast
2. The problem disappeared immediately after uninstalling Avast
3. The boot error specifically mentions aswVmm.sys as the culprit

The error might be because of some very specific hardware/software combination that we have and none of the majority users have.

[bob3160]

It could also have been a corrupted install or, a corrupted download.