Share via

Corrupted Registry Unable to Boot - How To Fix with CMD From Bootable Installation USB? DISM Issues

Anonymous
2019-05-18T03:41:47+00:00

Hello all,

 Last night, Windows 10 pushed an update. In the morning, it was stuck in a reboot loop where it would continually fail to repair itself. 

  I spent the day trying to fix it, but I couldn't find anything that worked. Currently, I am stuck with "The operating system couldn't be loaded because the system registry file is missing or contains errors.

Error Code 0x0000225 "

Here's what I tried that did NOT work (And made it worse):

  • Attempting to repair the BCD (Access denied)
  • Disabling automatic recovery mode in the BCD (Which now means I can't access command prompt from the native system, and I also can't reset the setting)
  • chkdsk (No errors found)
  • sfc /scannow (No errors found)
  • DISM /Online /Cleanup-Image /RestoreHealth   (Various issues, highlighted below)

DISM is the most promising, but I can't get it to run. My only way to work on the system is to boot into the installation USB, and navigate to the command prompt. Whenever I run DISM, it errors "Error 50   DISM does not support servicing Windows PE..." and if I remove /Online with /Source:X:\Windows I get "Error: 87   the cleanup-image option is unknown". 

I don't have an option to do a system reset keeping personal data, because I can't do anything with the native system. Initially I didn't want to deal with reinstalling 100 gigabytes of programs because of a windows update... But now that seems like it would have taken half the time.

I'd like to at least try using the DISM tool, but I can't get it to work from the install USB. 

Any help is appreciated.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

17 answers

Sort by: Most helpful
  1. Anonymous
    2019-05-18T19:28:05+00:00

    There is no reset option. 

    Options for bootable install USB are as follows: 

    1. System Restore
    2. Uninstall Updates
    3. System Image Recovery
    4. Startup Repair
    5. Command Prompt
    6. UEFI Firmware Settings

    Once again, none of these options are viable, and again, I would rather not begin with a new install. 

    If I have help, then repairing, rebuilding, and/or replacing the registry will go a lot quicker.

    6 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-05-18T14:27:38+00:00

    Thank you for the quick response.

    I'll respond in the same order:

    1.) I can only use the "Repair Your Computer" from the bootable USB. 

    2.) Booted in like before to the USB, no issues here

    3.) Startup Repair fails like usual, which was the initial problem. There is no "Reset PC" option under troubleshoot, because this is the bootable USB. I cannot access the troubleshoot options on the main system.

    4.) I am going to do everything I can to avoid a new install. 

    Do you have any insight about how to make DISM run?

    6 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-05-18T03:45:01+00:00

    Hi RCA. I'm Greg, an installation specialist and 9 year Windows MVP here to help you.

    Here are steps to recover from failed Updates or Version Update install which causes Windows to fail to start or function:

    1. Try whichever method works here to get into Advanced Startup Options to run System Restore if this is a Windows Update, or Go Back to Old Version if this is a version update. https://www.tenforums.com/tutorials/2294-advanc.... Easiest is to restart or force shutdown the PC 3 times.

    If you are able to access System Restore or Go Back and it fails, skip to step 3.

    1. If necessary create bootable installation media to access the repair options if not accessible by any other method: http://windows.microsoft.com/en-us/windows-10/m.... The bootable media is also the only method that doesn't require the password if you're stuck on that.

    Boot media by powering up the PC while pressing the BIOS Boot Menu Key: https://www.sysnative.com/forums/hardware-tutor...

    You may need to enter BIOS/UEFI Setup to turn off Fast Boot if it won't allow the Boot Menu key to interrupt starting Windows: https://www.mydigitallife.net/comprehensive-lis...

    Choose UEFI version of media if offered, browse to second screen to Repair Your Computer link, then Advanced Troubleshoot options to run System Restore to a point before the problem began, or choose More Options to Go Back to Old Version if this was a version Update.

    If it rolls back then you can hide the Windows Updates and Version Upgrade responsible until they mature by installing and running immediately the Hide Updates tool: https://www.howtogeek.com/224471/how-to-prevent...

    1. If this fails try a Startup Repair, or go back to Troubleshoot Options on the previous screen to Reset your PC which will save your files while reinstalling Windows.
    2. If that fails you can use the booted media to Clean Install the latest version which should get you past all difficulties as it has hundreds of thousands of others who have followed the steps in this link and never come back to report another problem: http://answers.microsoft.com/en-us/windows/wiki... The link compiles the best possible install of Windows 10 that will stay that way as long as you stick with the tools and methods given.

    There is a step to rescue files from the same bootable media: http://answers.microsoft.com/en-us/windows/wiki...

    Make sure during the booted install to follow the illustrated steps to delete all partitions down to Unallocated Space to get it cleanest, then click Next to let it auto-create the needed partitions, format them and begin install - this makes it foolproof.

    The media provided for the Clean Install is Version 1809 and normally the problems go away with the Clean Install, however if they don't you can find earlier version media to use here: https://tb.rg-adguard.net/public.php

    Burn to DVD or create bootable 8+gb flash stick installer using this tool installed to Windows: https://www.microsoft.com/en-us/download/detail...

    Then once you're back in Windows 10, you can block the problem Windows or Version Update using one of these methods: https://www.howtogeek.com/224471/how-to-prevent...

    Good news, Microsoft is changing Update policies soon as announced recently here: https://blogs.windows.com/windowsexperience/201...

    Until then you can manage Updates with all possible options here:

    https://www.makeuseof.com/tag/manage-windows-up...

    I hope this helps. Feel free to ask back any questions and let us know how it goes. I will keep working with you until it's resolved.

    ______________________________________________

    Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

    4 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-05-18T15:54:25+00:00

    I have an update (no solution yet):

    I made a backup of C:\Windows\System32\config\*

    I deleted all files and subfolders in config\

    I copied X:\Windows\System32\config\*     to      C:\Windows\System32\config\*

    Shut off computer, and restarted. Windows begins to boot. After loading a few seconds, it hits a blue screen with the error: "CRITICAL PROCESS DIED"

    I then replaced the DRIVERS file I copied into C:\Windows\System32\config\  with my old DRIVERS file. 

    Reboot, same error. 

    I enabled boot logging, and tried again. Also note that I DID attempt to use the auto fix from the bootable install disk, but it still fails. 

    Here are the contents of the boot log:

    Version 10.0 (Build 17763)

    BOOTLOG_LOADED \SystemRoot\system32\ntoskrnl.exe

    BOOTLOG_LOADED \SystemRoot\system32\hal.dll

    BOOTLOG_LOADED \SystemRoot\system32\kd.dll

    BOOTLOG_LOADED \SystemRoot\system32\mcupdate_GenuineIntel.dll

    BOOTLOG_LOADED \SystemRoot\system32\drivers\msrpc.sys

    Maybe this will give some insight into the issue at hand. I assume that the process dies as msrpc.sys attempts to run (and may be the process that dies). 

    Update 2: I reverted config on C back to the original, then only replaced the SYSTEM file. The system will attempt to boot, fail because critical process died, but NOW, it "gathers information" and reboots. After the reboot, the system file is broken again.

    3 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2019-05-18T18:18:05+00:00

    You should have the choice for Reset on the Troubleshoot in the bootable media which may work better because it doesn't rely on the onboard files.

    If not I would save time by skipping to the Clean Install which should get you past all difficulties as it has millions of others who have followed the steps in this link and never come back to report another problem: http://answers.microsoft.com/en-us/windows/wiki...

    Make sure during the booted install to follow the illustrated steps to delete all partitions down to Unallocated Space to get it cleanest, then click Next to let it auto-create the needed partitions, format them and begin install - this makes it foolproof.

    If you have files that aren't backed up you can use the same bootable media to try to rescue your files using this method: http://answers.microsoft.com/en-us/windows/wiki...

    You will get and keep the best possible install to the exact extent you stick with the steps, tools and methods in the linked tutorial. It's a better install than any amount of money could buy and a great learning experience that will make you the master of your PC because you will learn everything that works best and how to apply it with your own hands.

    0 comments No comments