Windows BSOD Error 0x00000060 — PROCESS_INITIALIZATION_FAILED Fix

What Does This Error Mean?

The 0x00000060 blue screen is called PROCESS_INITIALIZATION_FAILED. It means Windows could not start a critical system process during startup. This is most often caused by corrupted Windows system files, a damaged user profile, or a bad software installation.

Affected Models

Windows 10
Windows 11
Windows 8.1
Windows 7

Common Causes

Corrupted Windows system files are preventing a required process from starting
A recently installed program replaced or damaged a core Windows file
The Windows registry has become corrupted or has invalid entries
Faulty RAM is causing memory errors during process initialization
A virus or malware has damaged system startup files

How to Fix It

Boot into Safe Mode. Hold Shift while clicking Restart, then choose Troubleshoot > Advanced Options > Startup Settings > Restart, then press F4 for Safe Mode.

If Windows starts in Safe Mode, the problem is caused by a driver or program that loads at startup, not a core system issue.
Run the System File Checker in Safe Mode. Open Command Prompt as Administrator and type: sfc /scannow

Running this in Safe Mode is more effective because fewer files are locked by running processes.
Run DISM to repair the Windows image. Type in an elevated Command Prompt: DISM /Online /Cleanup-Image /RestoreHealth

This downloads replacement files from Microsoft's servers, so you need an internet connection. It can take 20 to 45 minutes.
Use System Restore to roll back to a time before the error started. Search 'Create a restore point' in the Start menu and click System Restore.

Choose a restore point dated before you first saw the blue screen. Your personal files will not be deleted.
Scan for malware using Windows Defender or a trusted tool like Malwarebytes. A virus that modifies startup files can easily cause this error.

Run the full scan, not a quick scan. If malware is found and removed, run sfc /scannow again to repair any files the malware damaged.

When to Call a Professional

If your computer will not boot into Windows at all and Startup Repair does not fix it, a technician can run repairs from external media. This is worth doing before a full reinstall, as it may save your files and settings.

Frequently Asked Questions

Why does this happen right at startup?

Windows loads dozens of processes automatically when it starts up. If any of those critical processes fail to initialize — because of a missing file, bad memory, or corrupted code — Windows cannot continue and issues a blue screen. This is Windows protecting itself from running in a broken state.

Can I recover my files if I cannot boot into Windows?

Yes. Boot from a Windows installation USB drive and choose Repair Your Computer instead of Install. From there you can access Startup Repair and Command Prompt tools. If you need to pull your files off, a Linux live USB can read NTFS drives and let you copy your files.

Is this error related to a virus?

It can be. Some malware specifically targets Windows startup files to make itself harder to remove. If your antivirus was recently disabled or you downloaded something suspicious before the crashes started, run a full malware scan from Safe Mode as your first step.