Jump to content

Emsisoft did not meet the N signing level requirements


emwul64
 Share

Recommended Posts

The Windows 10 x64  (18363.1082) event log is showing the following entries

(\Device\HarddiskVolume4\Program Files (x86)\Microsoft\Edge\Application\msedge.exe) attempted to load \Device\HarddiskVolume4\Program Files\Emsisoft Anti-Malware\a2hooks64.dll that did not meet the 8 signing level requirements.

(\Device\HarddiskVolume4\Program Files\Emsisoft Anti-Malware\eppwsc.exe) attempted to load \Device\HarddiskVolume4\Program Files\Emsisoft Anti-Malware\eppcom64.dll that did not meet the 7 signing level requirements.

Emsisoft v2020.11.

At one point the protection was 'Off',  but the 'Fix Now' didn't work. Had to shut down and restart.
Any suggestions?
BTW it almost always involves harddiskvolume4 which is in fact a Samsung 850 Pro SSD C:-drive with Windows.

Thanks.

 

=

w2w2wbF.png

=


2RAyiWl.png

Link to comment
Share on other sites

16 hours ago, emwul64 said:

(\Device\HarddiskVolume4\Program Files (x86)\Microsoft\Edge\Application\msedge.exe) attempted to load \Device\HarddiskVolume4\Program Files\Emsisoft Anti-Malware\a2hooks64.dll that did not meet the 8 signing level requirements.

Such errors are completely normal. Certain Windows System Files have higher code signing requirements than other software, so when Emsisoft Anti-Malware injects a2hooks64.dll into them to open hooks to those processes it shows this error in the event logs.

 

16 hours ago, emwul64 said:

BTW it almost always involves harddiskvolume4 which is in fact a Samsung 850 Pro SSD C:-drive with Windows.

That's just how Windows internally tracks the drive and partition that are mapped as C:/

 

16 hours ago, emwul64 said:

At one point the protection was 'Off',  but the 'Fix Now' didn't work. Had to shut down and restart.

This is completely unrelated to the code integrity errors that you're seeing in the event logs. It could mean that a2service.exe had crashed, failed to start, or had hung/frozen at some point. It could also mean there was an issue with the Emsisoft Protection Platform (EPP) driver. If this happens again we can try getting debug logs, and see if they show us the cause.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...