Windows 10 Code Integrity and Cryptographic problems, EventID: 513

Description: Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object

The Code Integrity component of Windows enforces the requirement that kernel-mode drivers be signed in order to load. Windows always generate Code Integrity operational events and optionally will generate additional system audit events and verbose diagnostic events that provide information about the status of driver signing.
The Code Integrity operational log includes warning events that indicate that a kernel-mode driver failed to load because the driver signature could not be verified. Signature verification can fail for the following reasons:
An administrator preinstalled an unsigned driver, but Code Integrity subsequently blocked loading the unsigned driver.
The driver is signed, but the signature is invalid because the driver file has been altered.
The system disk device might have device errors when reading the file for the driver from bad disk sectors.
For more information: https://msdn.microsoft.com/en-us/library/windows/hardware/ff539911(v=vs.85).aspx

Solution:
Run In Elevated Command Prompt:

dism /online /cleanup-image /restorehealth
sfc /scannow
powershell
Get-AppXPackage -AllUsers |Where-Object {$_.InstallLocation -like "*SystemApps*"} | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s