0x00000067 Fix: CONFIG_INITIALIZATION_FAILED Error

0x00000067 has a value of 0x00000067 and indicates that the registry configuration failed. In this bug check, the registry could not allocate the pool it needed to contain the registry files, which should not occur during normal startup. A common first triage sequence is to check registry boot settings, then the disk, then RAM, then boot records.

This guide is part of our Windows BSOD stop codes: full list and fixes series.

What does stop code 0x00000067 mean in Windows?

It is a startup-time bug check named CONFIG_INITIALIZATION_FAILED, and it points to registry configuration loading before normal Windows services begin. (Microsoft Learn)

What it looks like

You may see a blue screen at the logo, repeated restarts before the desktop appears, or a machine that drops into WinRE and never reaches the sign-in screen. If Windows still opens, the failure is less severe than a hard boot loop and can often be handled from the desktop first.

According to Bug Check 0x67 CONFIG_INITIALIZATION_FAILED – Windows drivers — Microsoft says the bug check value is 0x00000067. (source)

What usually causes 0x00000067?

The most common starting point is a corrupted registry or startup configuration. After that, disk or partition damage is the next thing to check, followed by unstable RAM. Less commonly, bad boot records, malware, or a recent driver change can trigger the same startup failure.

Why the registry is first

Microsoft says the registry configuration failed and that the registry could not allocate the pool needed to contain the registry files. That pool is allocated very early in system initialization, so failures here happen before many other parts of Windows are fully available. (Microsoft Learn)

Why disk, RAM, and boot records come next

A damaged system partition can stop the registry from loading cleanly. Unstable memory can corrupt reads during startup. Boot-record damage can block the handoff before Windows even reaches the registry stage. That order matters because it keeps the first tests safe and the most likely causes ahead of less common ones.

What should I try first?

If Windows still boots, back up data first, then open an elevated Command Prompt and run SFC and DISM. If Windows will not boot, enter Windows Recovery Environment and open Command Prompt there. Use the branch that matches your state; do not jump straight to registry edits when a rollback or file repair is safer.

If Windows still opens

1. Open Start and type cmd.
2. Right-click Command Prompt and choose Run as administrator.
3. Run sfc /scannow.
4. Run DISM /Online /Cleanup-Image /RestoreHealth.
5. Restart the PC and test whether it boots normally.

If Windows will not open

1. Enter WinRE by forcing shutdown during boot, then choose Troubleshoot > Advanced options > Command Prompt.
2. Run chkdsk C: /f /r.
3. If the machine still loops, run the boot repair commands in the boot-record section below.

Can corrupted registry files cause 0x00000067?

Yes. A damaged registry hive or a failed startup change can stop configuration loading before the desktop appears. Recent registry cleaners, manual edits, failed updates, or a restore that did not complete cleanly can all leave Windows unable to initialize the startup configuration.

What to do if the problem started recently

1. Boot into WinRE and select Troubleshoot > Advanced options > System Restore.
2. Pick a restore point from before the last update or registry change.
3. Complete the rollback and restart the PC.
4. If Windows still fails, move to disk checks next.

When manual registry edits are risky

Do not edit hives by hand unless you already have a backup and a clear reason. If the issue began after an update, driver install, or cleanup tool, System Restore is safer than trying to rebuild registry files one by one. A bad edit can leave the machine unable to boot at all.