How to Fix PROCESS1_INITIALIZATION_FAILED (0x0000006B) in Windows 11, 10 and 7

PROCESS1_INITIALIZATION_FAILED has the bug-check value 0x0000006B. It appears when Windows cannot complete an important early initialization process. The computer may restart repeatedly, remain stuck on the blue screen, or fail before the sign-in screen appears.

The stop code does not identify one single damaged file. Possible causes include protected Windows files that are missing or corrupted, file-system errors, a failed or interrupted Windows update, an unavailable boot partition, a damaged registry hive, a boot-start storage driver problem, a failed clone or restore, or a hard disk or SSD that is no longer reading data reliably.

Before You Start

You need either a Lazesoft Recovery Suite bootable USB, Windows installation media, or access to Windows Recovery Environment. Confirm that BIOS/UEFI detects the internal Windows drive. If the disk is absent from firmware, repair commands will not solve the underlying hardware or controller problem.

Drive letters often change inside Windows PE or Windows Recovery Environment. The installed Windows system may appear as D: or E: even though it normally uses C:. Identify the correct volume before running commands:

diskpart
list volume
exit

dir C:\Windows
dir D:\Windows
dir E:\Windows

Use the drive that contains the Windows, Program Files, and Users folders. The manual examples below assume the offline Windows installation is on C:. Replace that letter when necessary. If BitLocker protects the Windows volume, unlock it before running offline repairs.

Method 1: Use Lazesoft Windows Recovery and SFC Fix

This method is useful when Windows cannot start and you prefer a graphical tool. Lazesoft runs System File Checker against the selected offline installation instead of the temporary Windows PE system on the recovery USB.

Step 1: Boot from the Lazesoft recovery USB or CD

Create Lazesoft bootable recovery media on a working Windows computer. Connect it to the affected PC, open the one-time boot menu, and select the USB or optical drive. When using a CD or DVD, press a key when prompted.

Step 2: Select Lazesoft Live CD

At Windows Boot Manager, highlight Lazesoft Live CD and press Enter. Wait for the Windows PE recovery environment to load.

Step 3: Open Windows Recovery

When Lazesoft Recovery Suite Home Edition opens, select Windows Recovery.

Step 4: Select the Windows installation

Lazesoft scans the connected disks and lists the Windows installations it can access. Select the affected Windows 11, Windows 10, or Windows 7 installation and click OK. Verify the Windows version, boot volume, disk size, and system volume so you do not select the temporary recovery environment.

Step 5: Open LoadingCrash and select SFC Fix

In Lazesoft Windows Recovery, open the LoadingCrash tab and select SFC Fix from the left panel.

Step 6: Click Run SFC Repair

Click Run SFC Repair. Lazesoft starts Microsoft System File Checker with the selected offline Windows directory. The underlying command is similar to:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Step 7: Wait for the offline SFC scan

The scan may take several minutes or longer, depending on the disk speed, file-system condition, and amount of corruption. Do not shut down the computer while the repair is running.

Step 8: Review the result and restart

The example result says that Windows Resource Protection found corrupt files but could not repair all of them. This does not necessarily mean the repair was useless. Files required for startup may have become accessible even if some noncritical corruption remains.

Close Lazesoft, remove the recovery media, and restart the computer. In this test, Windows reached the lock screen after the offline SFC operation.

Method 2: Run Offline SFC Manually

Boot from Windows installation media and choose Repair your computer → Troubleshoot → Advanced options → Command Prompt. Identify the correct Windows drive letter, then run:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

To save a separate offline log, use:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows /offlogfile=C:\sfc-offline.log

Replace C: with the actual offline Windows volume. When the scan finishes, restart the computer. If SFC reports that it could not repair all files on Windows 10 or Windows 11, repair the component store with DISM and run SFC again.

Method 3: Check the Windows Partition with CHKDSK

Windows may fail during initialization when it cannot reliably read system files, registry hives, or drivers. From the recovery Command Prompt, run:

chkdsk C: /f

The /f option repairs logical file-system errors. For a deeper scan that also checks for unreadable sectors, use:

chkdsk C: /f /r

The /r scan can take a long time, especially on a large mechanical hard disk. Do not interrupt it. After CHKDSK completes, run offline SFC again. If CHKDSK repeatedly reports bad sectors or the drive continues to disappear, treat the issue as possible hardware failure and back up data as soon as possible.

Method 4: Repair Windows 10 or 11 with DISM

On Windows 10 and Windows 11, DISM can repair the offline Windows component store used by servicing operations and System File Checker. From Windows Recovery Environment, run:

dism /image:C:\ /cleanup-image /checkhealth
dism /image:C:\ /cleanup-image /scanhealth
dism /image:C:\ /cleanup-image /restorehealth

If DISM cannot find the source files, use a matching Windows installation image. The source should match the installed Windows release, architecture, language, and edition. One approach is to mount the correct image and specify its Windows directory:

dism /image:C:\ /cleanup-image /restorehealth /source:D:\Mount\Windows /limitaccess

After DISM reports success, run offline SFC again:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Revert an Incomplete Windows Update

If PROCESS1_INITIALIZATION_FAILED appeared immediately after Windows Update, an interrupted pending operation may be blocking startup. On Windows 10 or Windows 11, run:

dism /image:C:\ /cleanup-image /revertpendingactions

Restart after the command completes. Use this only when Windows became unbootable during or directly after an update. It should not be used as a routine maintenance command.

Rebuild Windows Boot Files

If the system files are readable but Windows Boot Manager or the OS loader is damaged, use BCDBoot to recreate boot files and the BCD store from the installed Windows directory.

UEFI/GPT computer

Use DiskPart to locate the small FAT32 EFI System Partition and assign it a temporary drive letter:

diskpart
list volume
select volume X
assign letter=S
exit

bcdboot C:\Windows /s S: /f UEFI

Replace X with the EFI System Partition volume number. On a UEFI installation, the BCD store is normally located at \EFI\Microsoft\Boot\BCD.

Legacy BIOS/MBR computer

For an older BIOS/MBR installation, start with:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

If the System Reserved partition is mounted as S:, recreate the BIOS boot files with:

bcdboot C:\Windows /s S: /f BIOS

On Legacy BIOS systems, the BCD store is normally located at \Boot\BCD. Do not mark an EFI System Partition active; the active command applies to Legacy BIOS/MBR boot partitions.

Common Windows Boot and Startup Files

The exact set varies by Windows version, boot mode, architecture, encryption state, and installed drivers. The following table lists common components involved in Windows startup.

What If PROCESS1_INITIALIZATION_FAILED Still Appears?

1. Disconnect unnecessary devices. Remove external drives, card readers, and secondary disks that are not required for startup.
2. Confirm disk detection. Check that BIOS/UEFI consistently detects the Windows SSD or hard disk.
3. Restore the previous storage mode. Changing AHCI, RAID, Intel RST, or Intel VMD can prevent Windows from accessing the boot device.
4. Check physical connections. Reseat SATA data and power cables or verify that the NVMe drive is installed securely.
5. Try Windows Startup Repair. Open Repair your computer, Troubleshoot, Advanced options, and Startup Repair.
6. Use System Restore. Restore Windows to a point created before the error appeared.
7. Uninstall a recent update. Use the Advanced options menu when the problem began immediately after an update.
8. Test the disk. Use the SSD or hard-drive manufacturer’s diagnostic utility and review SMART health information.
9. Restore a system image. A known-good backup may be safer than continuing to repair a failing installation.
10. Back up files before reset or reinstall. Use Lazesoft File Manager, Data Recovery, or another bootable environment to copy important data first.

Which Repair Method Should You Use?

← Windows Recovery Download Lazesoft Recovery Suite →