How To How to fix Windows 10 error Kernel Security Check Failure

Status
Not open for further replies.

JamieKavanagh

Commendable
Apr 19, 2016
318
0
1,780
0

The Windows 10 error Kernel Security Check Failure usually results in a BSOD. While the blue screen in Windows 10 is friendlier than before, it still isn’t something we want to see while working on our computer. So if you want to fix Windows 10 error Kernel Security Check Failure, this tutorial is for you!

Kernel Security Check Failure means a file has failed a compatibility or integrity check and needs to be updated or replaced. This can be caused by outdated drivers, inherited drivers from Windows 7 or 8 that aren’t fully compatible with Windows 10 or a drive or core file that got corrupted somehow.

Fix Windows 10 error Kernel Security Check Failure
There are a few things we can do to fix this error. First let’s perform a Windows update to make sure you’re running the latest version.

1. Navigate to Settings, Update & Security and Windows Update.
2. Click ‘Check for updates’.
3. Update everything as required.

Then:

1. Type or paste ‘verifier’ into the Search Windows box.
2. Select ‘Create standard settings’ and click Next.
3. Select ‘Automatically select unsigned drivers’ and click Next.
4. Update any or all drivers in the list.
5. If you have just upgraded to Windows 10, also try ‘Automatically select drivers built for older versions of Windows’ and click Next. Update those too if they don’t overlap with step 4.

Then:

1. Open a CMD window as an administrator.
2. Type or paste ‘sfc /scannow’ and press Enter.
3. Let the process complete and make any repairs as necessary.

In the vast majority of cases, one or all of these procedures fixes the Windows 10 Kernel Security Check Failure. If you know of any other methods, let us know below!

More Windows 10 tutorials you may find useful:
How to change your computer’s name in Windows 10
How to set up a minidump for BSOD troubleshooting in Windows 10
How to add a show desktop shortcut to Windows 10



 
Sep 28, 2019
1
0
10
0
Ok, I have to respond to this because something glaringly obvious had been completely overlooked.

People come to this article because they are seeing this error code and their system won't start. Your solution is to do things that can only be done on a system that's started.

How the heck does that make sense?!?!

If these solutions can/should be done in safe mode, that would be step number one but you don't mention that.

Clarification needed please.
 
Status
Not open for further replies.

ASK THE COMMUNITY

TRENDING THREADS