Windows 10: Microsoft-Windows-CodeIntegrity Code Integrity determined ...

Anyone out there who can tell me what to do to prevent Event Log errors reading as follows:


They all start with the same:

Microsoft-Windows-CodeIntegrity Code Integrity determined that a process (\Device\HarddiskVolume2\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorsvw.exe) attempted to load \Device\HarddiskVolume2\Windows\assembly\GAC\

then followed with:

.....\GAC\Microsoft.StdFormat\7.0.3300.0__b03f5f7f11d50a3a\Microsoft.stdformat.dll that did not meet the 8 signing level requirements.

.....\GAC\ADODB\7.0.3300.0__b03f5f7f11d50a3a\adodb.dll that did not meet the 8 signing level requirements.

.....\GAC\MSDATASRC\7.0.3300.0__b03f5f7f11d50a3a\msdatasrc.dll that did not meet the 8 signing level requirements.

.....\GAC\Microsoft.StdFormat\7.0.3300.0__b03f5f7f11d50a3a\Microsoft.stdformat.dll that did not meet the 8 signing level requirements.

.....\GAC\ADODB\7.0.3300.0__b03f5f7f11d50a3a\adodb.dll that did not meet the 8 signing level requirements.

.....\GAC\MSDATASRC\7.0.3300.0__b03f5f7f11d50a3a\msdatasrc.dll that did not meet the 8 signing level requirements.

.....\GAC\stdole\7.0.3300.0__b03f5f7f11d50a3a\stdole.dll that did not meet the 8 signing level requirements.

All are Event-ID 3033

==

Thanks
-
Windows 10 x64
=
Attachment 31018

=

:)

 

All System32 drivers are suddenly unsigned in Windows 10

I received an error while signing in that Windows defender could not load. After rebooting the system failed multiple times and went to the advanced recovery options screen. After disabling device driver signature enforcement I was able to log in again.
Following instructions at Troubleshooting Boot Issues due to missing Driver signature (x64) I used the sigcheck tool to check the drivers listed in the CodeIntegrity log and they all appear to be unsigned.

These are all drivers inside System32. Why did all my windows drivers suddenly become unsigned and is there a way to fix this without reinstalling windows? If I disable signature enforcement I can get into my machine and everything works except for Defender
which still won't startup.

Example errors in log:

Code Integrity was unable to load the Microsoft-Windows-Common-Drivers-minkernel-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cat catalog. Status 0xC0000034.

Code Integrity determined an unsigned kernel module \Device\HarddiskVolume4\Windows\System32\drivers\cdrom.sys is loaded into the system. Check with the publisher to see if a signed version of the kernel module is available.

 

Code Integrity and Cryptographic problems

I have no Idea about this, but am advised it needs to be fixed.

(Hoping I'm posting under the correct topic.)

Additional scan result of Farbar Recovery Scan Tool

...

CodeIntegrity:

===================================

Date: 2015-12-10 10:57:17.760

Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume5\Windows\System32\efswrt.dll because the set of per-page image hashes could not be found on the system.

Date: 2015-12-10 10:21:45.332

Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume5\Windows\System32\efswrt.dll because the set of per-page image hashes could not be found on the system.

Date: 2015-12-10 09:54:30.551

Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume5\Windows\System32\efswrt.dll because the set of per-page image hashes could not be found on the system.

Etc., etc..

There was also reported "Error: (12/12/2015 11:50:09 AM) (Source: Microsoft-Windows-CAPI2) (EventID: 513) (User: ) Description:
Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.", but I don't yet know the source. Likely Farbar, at a guess.

This is from the nice people on MBAM forum.

I have recently repaired what I can with DISM and SFC, but the Code Integrity problem still exists. I can't tell if the cryptography issue does or or not. I'll report further when I know more.

Help always appreciated. Thank you.