Error 0xc000014c

N

Nonnado

Member
Joined
Dec 30, 2024
Posts
11
Hello everyone,

I’m facing a similar issue to one previously reported by another user, where I’m unable to boot my hard drive with Windows 10. All my project files are stored on it.

When I attempt to boot from this hard drive, I get a blue screen with the following message:

File: \windows\system32\config\system
Status: 0xc000014c
Info: Windows failed to load because the system registry file is missing or corrupt.

I successfully created a bootable USB using the Win10 MediaCreationTool_22H2. I attempted the following commands without success:

bash
Copiar código
sfc /scannow /offbootdir=d:\ /offwindir=d:\windows <br>dism /image:d:\ /cleanup-image /restorehealth /source:f:\esd\sources\install.esd <br>
I also tried rebuilding the BCD for my hard drive, but nothing happened.

This issue has occurred before, and I was able to recover using a System Restore Point. However, there are no restore points available this time.

What should I do?
 
Nonnado said:
every time I boot from this hard drive, it shows "Interactive logon process initialization has failed."
Click to expand...
According to Stellar Info >
Process1 Initialization Failed is a blue screen error that may cause multiple system issues such as malfunctioning, boot failure, etc.
blue screen error called “Process1 Initialization Failed” appears when the boot files are damaged. This issue most frequently occurs following a hardware or software installation.
 
ET_Explorer said:
According to Stellar Info >
Process1 Initialization Failed is a blue screen error that may cause multiple system issues such as malfunctioning, boot failure, etc.
blue screen error called “Process1 Initialization Failed” appears when the boot files are damaged. This issue most frequently occurs following a hardware or software installation.
Click to expand...
After following the methods suggested on the Stellar Info site to fix the "Process1 Initialization Failed" error, unfortunately, the issue persists.

The attempted methods include:

  • Running CHKDSK.
  • Running SFC.
  • Using DISM (it seemingly didn't complete 100%, stopping at 54.7%).
  • Deleting the Bootcat.cache file: I couldn't find this file in the Windows/System32/CodeIntegrity folder to force its recreation by the system.
Despite these attempts, the error remains unresolved.

As an alternative, I found a suggestion on the site you shared, recommending replacing the Bootcat.cache file with a copy from a similar operating system. Unfortunately, I was unsuccessful in this attempt as well.




Maxstar said:
It seems you get the following message as described here: [FIX] Sign-in Process Initialization Failure In Windows 10

Have you already tried to perform a startup repair using the Windows ISO from the Recovery Environment?
Click to expand...

I noticed that when I used the Windows ISO, I received warnings about some errors. I will redo the process step by step and report them. One result I already have is from DISM. When I use the Recovery Environment, DISM stops at 54.7% for this hard drive. The log is attached.
 

Attachments

The solution is to replace the system hive with a good copy of it.

If you don't have a non-corrupted copy of the system hive, you should provide (i.e., upload here) a copy of the corrupted system hive (in c:\windows\system32\config).
We (i.e., we is Maxstar) will try to repair the system hive with the mentioned tool developed by X Bluerobot.
Then, we (i.e., Maxstar) will upload here the repaired system hive.
You will put it in in c:\windows\system32\config and your OS should hopefully boot normally.

Otherwise, you could try to do it on your own, following the mentioned guide in the third reply (i.e., post number 4).
 
xilolee said:
The solution is to replace the system hive with a good copy of it.

If you don't have a non-corrupted copy of the system hive, you should provide (i.e., upload here) a copy of the corrupted system hive (in c:\windows\system32\config).
We (i.e., we is Maxstar) will try to repair the system hive with the mentioned tool developed by X Bluerobot.
Then, we (i.e., Maxstar) will upload here the repaired system hive.
You will put it in in c:\windows\system32\config and your OS should hopefully boot normally.

Otherwise, you could try to do it on your own, following the mentioned guide in the third reply (i.e., post number 4).
Click to expand...
Here is the copy of the Windows/System32/config folder.
 

Attachments

Note: I've removed the SOFTWARE hive from the config folder because it contains sensitive data!

The SYSTEM hive looks good, so you have successfully repaired this file. So please do the following to replace the corrupt and missing files.

1. Download WinSxS.zip and extract this file on the USB-stick with the Windows ISO.
2. Run the following DISM command and replace X with the driveletter of the USB-stick.
Code: 
Dism  /image:D:  /Cleanup-Image  /RestoreHealth  /Source:X:\WinSxS
 

Attachments

Code: 
X:\sources>dism /image:C: /Cleanup-Image /RestoreHealth /Source:E:\WinSxS

Deployment Image Servicing and Management Tool
Version: 10.0.19041.3693
Image Version: 10.0.19045.5247

The size of the temporary directory may be insufficient to complete this operation.
This could result in unexpected behavior.
Use the /ScratchDir option to point to a folder with enough temporary space.

At least 1024 MB is recommended.

[=======================55.3%

Error: 605
The specified buffer contains malformed data.

The DISM log file can be found at: X:\Windows\Logs\DISM\dism.log

The generated DISM log file is attached.
 

Attachments

Last edited by a moderator:
Please don't quote the previous posts!

1. Are you able to boot normally after the startup repair as mentioned in the blog post of Kapil Arya (post #7)? [How To] Perform Automatic Or Startup Repair In Windows 10
2. Was this a dual-boot system with Linux or other Windows versions?
3. The latest log shows 627 corruptions which has to due with error 0x8007025d - ERROR_BAD_COMPRESSION_BUFFER

We can fix this problem, but from the Recovery Environment is quite difficult, so please let us now if your tried the startup repair! And when an error message appears post it in the next reply.
 
I did what was asked in suggestion 1, 2:

1-
Startup Repair

Startup Repair couldn't repair your PC.

Press "Advanced options" to try repairing your PC or "Shut down" to turn off your PC.
Log file:

2- I have another hard drive with Windows 11. The boot setups are not shared (dual-boot; they were installed separately). Once, when I encountered this same issue, I ran bcdboot D:\Windows on the disk that boots normally, and I was able to log into that system via dual boot successfully. Now, this is no longer possible.

I'm ready to try, since my college programs are all installed on this HD.

Another detail: When I run "chkdsk C: /f /r /x" in the restoration environment, at the end of the log it appears

Code: 
Administrator: X:\Windows\SYSTEM32\cmd.exe

File data verification completed.
Duration of phase (User file recovery): 14.42 minutes.

Stage 5: Looking for invalid free clusters...
120,883,482 free clusters processed.

Free space verification completed.
Duration of phase (Free space recovery): 0.00 milliseconds.

No file system issues were found.
No action is needed.

976,093,144 KB total disk space.
489,528,884 KB in 1,594,521 files.
746,136 KB in 219,527 indexes.
0 KB in bad sectors.
2,284,196 KB in use by the system.
65,536 KB occupied by the log file.
483,533,928 KB available on disk.

Total allocation units on disk: 244,023,286.
4,096 bytes in each allocation unit.
120,883,482 allocation units available on disk.
Total duration: 15.29 minutes (91798686 ms).
Failed to transfer logged messages to the event log with status 6.

X:\Sources>
 
That message from chkdsk is normal, when you run it in the Recovery Environment it cannot write the results to the Windows Event logs.

Please run the following commands in the Recovery Environment and take a picture of the result.
Code: 
diskpart
list disk
sel disk 0
list volume
list partition
detail disk
 
Hmm, so Disk 1 is the drive with Windows 11 installed? If so you can try the following:

1. Disconnect Disk 1 (W11)
2. Run the startup repair again on the drive for Windows 10.

But perhaps someone else has a better idea to try first in this case..
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top