Recovering from Windows 10 boot Blue Screen, Critical Service Failed, Disable drivers signature enforcement, Unsigned Drivers

In case it helps someone, worked for me in a recent very annoying BSOD in my Windows 10
(instead of a full refresh or fresh install, don’t settle easily for that, usually try to dig a little bit and see what I can find…).

*update 2017-05-19, found this thread on reddit with a safer fix/workaround: seems installing the new Windows creators update fixes the issue, so would advise for that first!*

*update 2017-05-19, please read the part II for additional info and possible issue with Disk Cleanup tool: Disk Cleanup and Windows 10 boot Blue Screen / Critical Service Failed – Disable drivers signature enforcement, Unsigned Drivers *

Please note: It’s been stable and no problem with restarts for a few days now, but not saying it’s a permanent fix or better than a clean install. Will update if something changes. (probably something on my system is triggering this and will happen again)

My advice also before testing any kind of changes or emergency repairs, keep calm, don’t make it worst, backup the data you want safe before anything else.

My setup

  • Dual boot, default Win10 enterprise and an old Win81 legacy boot partition I still use occasionally
    (ex: when I get a recurring Blue Screen on boot !), no bitlocker
  • Separated Data drive, with bitlocker
  • Win10 Build 14393.1066 Version 1607
  • Single SSD, 3 main partitions


  • On restart and before my dual boot selection screen I get the Blue Screen,
    detail message is Critical Service Failed
  • Image result for critical service failed windows 10
  • Suspect this usually happens after major updates, I have the bad habit of never restart and always hibernate…
  • The system is bootable if you choose the “Disable drivers signature enforcement” on the troubleshoot / AdvancedOptions / Startup settings screens (usually option 7 when you restart)
  • Image result for Disable drivers signature enforcement
  • After restart with “Disable drivers signature enforcement” windows works pretty much as normal
  • But every restart you will get the same Blue Screen as this option is not permanent (nor advised), and I end up having to do two restarts to enable the option again, better than nothing but annoying
  • Running sigverif  tool (after booting with  “Disable drivers signature enforcement” to get Windows working) showed a huge number of “not signed” drivers??
  • image
  • in Event log (Application and Services Logs > Microsoft > Windows > CodeIntegrity > Operational I see a lot of errors when windows tries to load driver signature files needed, seems suddenly all drivers are being marked as not signed and Windows won’t allow it, except for enabling the “Disable drivers signature enforcement” boot option, also errors pointing to files I don’t have in C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
  • image
  • Drivers then get marked as not signed! not good…
  • image
  • When compared to similar setup from another win10 same build, the number of files on my C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} is very low (~1600 vs ~6000 files in the working win10), only two files starting with M… on my folder?
  • image

What worked for me (use as is, as a last resource, no guarantees whatsoever, do your backups!):

After checking my win 10 build, got a zip with all the files in C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} from a “healthy and compatible donor” Smile (thx António) and pasted the missing ones on my system. Being cautious not to overwrite any file just in case and doing a backup of my folder (obviously!).

check the build numbers, *probably* they should match your win build version, ex 14393


Restart, now the boot selection appears, choose win10, everything working. sigverif tool now only complains about few files that seem not critical, previous Eventlog CodeIntegrity errors also clear.

Now, what I really have a hard time to accept is why do we contribute with so much data, diagnostic & logging information these days, and still no sign of minor “windows data intelligence” suggestions to help with a problem that for sure I’m not the only to experience…

Thx also to Pedro Sousa and José António Silva and our Help Desk for their tips & guidance.

Yet again I skipped that clean install! Winking smile 

Some references with similar problems

Critical_service_failed BSOD restart loop windows 10

All System32 drivers are suddenly unsigned in Windows 10

(Which reminds that one of these days I probably should share some thoughts on bitlocker, efs and …backups, do your backups! and be sure to test them!)



About Rui Quintino
Developer & Software Architect @ DevScope

11 Responses to Recovering from Windows 10 boot Blue Screen, Critical Service Failed, Disable drivers signature enforcement, Unsigned Drivers

  1. Simon Locke says:

    You’re a life saver!!

    I had exactly the same problem and your suggested fix worked a treat!

    Like you I rarely reboot, preferring to hibernate. So I couldn’t be sure whether it’s due to a previous update, but highly suspect it is.

    I tend to disable the Windows Update service unless I actually need an update, due to being plagued with update related issues in the past, including forced reboots at inopportune times.
    This experience being another case in point. Microsoft really need to do something about this!

    I don’t know how you worked it out, but I’m very grateful to you :-)

  2. Simon Locke says:

    No didn’t run that! Unless some update service (Windows update maybe) runs it automatically without telling you.
    But interestingly it reports 51.5GB in Temporary files which I find hard to believe. My two logins total around 3.5GB in their TEMP folders.
    I’m reluctant to try it given the experience you describe in your referenced article!
    But thanks for the heads-up.

    • Rui Quintino says:

      Great feedback, thank you Simon, adding that tested the creators update this weekend, like some mention it can be another way of fixing the issue, would say because it pretty much install/refreshes windows folders again (old files remain in windows.old) and a new set of signature files in that folder are installed (different build numbers for creators update)
      Thx again!

  3. pito says:

    I seem to have the exact same issue, same build number, I also did the disk cleanup tool and I remember it saying something ridiculous for Temporary files (over 500GB), so I thought that was strange at the time but forgot about it until the next time I restarted and the BSODs began.
    Sorry if I missed it but can you provide a link for the files that need to be pasted ?

    • pito says:

      Nevermind, managed to install creator’s update via usb (internet was not working while booted in the no-driver-signing mode) and the ‘fresh’ install has resolved the issue.

      • Rui Quintino says:

        Hi, great you solved it, I was just about suggesting the creators update as it also seems to fix the issue, tested myself (fresh signature folder also). Just in case I’ve saved a copy of the new catroot folder, but haven’t tried cleanup again yet. :) thx for the feedback! Awesome

      • Simon Locke says:

        Just to add, I went for the ‘catroot’ fix initially (see earlier posts). Everything seemed to be working ok until I tried to use IIS and found it wasn’t working (sorry didn’t note specific errors). The admin console gave error 80020007 and refused to connect to IIS so I couldn’t even reconfigure.
        What resolved it was installing the Creators update.

  4. salzali says:

    Thanx dude.. İt’ s working!!

Leave a Reply

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

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

Google photo

You are commenting using your Google 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 )

Connecting to %s

%d bloggers like this: