In such scenarios, you may be required to restore your Registry backup to reinstate your Windows 10 to what it was. A situation like this may also arise out of a buggy update. There is an automated secret backup of your Registry that Windows creates but you have to manually enable it. Today, we will be showing you how to restore a Registry backup using Command Prompt.

How to restore Registry using Command Prompt in Windows 11/10

The main steps involved in restoring your Registry backup using the command prompt in Windows 11/10 are: Let us go into the detailed version now. As already stated, there is a backup copy of your Registry stored in the folder %windir%\System32\config\RegBack but we have to make use of the command prompt to make this folder accessible and store the database here. What we will do here is copy files from the RegBack folder (where all updated Registry files are stored) and paste them into the System32\config folder. If you try to locate and open the RegBack folder in your Windows 10 computer, you’ll find it to be empty. Microsoft disabled the functionality for systems running on Windows 10 now. You can still make Windows 10 automatically backup the Registry – but in this post, our method will center around the Command Prompt. First things first, you will have to restart your PC under the Advanced Startup options. It’s pretty easy to do so. Close all the programs that you have running on your PC and open your Windows settings. Click on Update & Security > Recovery and you’ll find a Restart Now button under Advanced Startup.

Once that is underway and the Advanced Startup blue screen shows up, click on Troubleshoot. Then, select Advanced Options and click on Command Prompt. This is going to run Command prompt on your PC as an administrator with the first command-line being X:\Windows\System32. Now, you need to access the drive where Windows is installed. Typically it’s the C:\ folder, which is the default folder under action every time the command prompt is opened, but since you’ve booted your PC in a recovery mode, it may change to D:. Thus, type the following and press Enter. You can make sure that you’re in the right directory by using the dir command. If the directory shows the Windows folder, as shown below, you’re going in the right direction. If not, you will have to try browsing through other drives.

Next up, type the following command to enter the System32 folder and press Enter.

Now, you have to create a folder as a temporary backup of files on your config folder. We’re doing this because there is a copy of Registry files in the config folder too. To do so, type the following command line and press enter This won’t be followed by any action since here all you’re doing is creating a backup folder. Copy files into this folder with the command below. Once entered, you will see 11-12 files being copied. Wait till that’s over before you proceed.

To move back to working with the RegBack folder, which houses a backup of Registry files, you have to use the ‘cd’ command as prescribed below and use ‘dir’ to verify its contents: While going through the directory, keep an eye on the files’ bit sizes. If any of the files show 0 to be their size, you are supposed to stop the process right there. Continuing any further can cause damage to your PC.

All that’s left for you to do is copy the files from the config folder to the RegBack folder. The following copy command will facilitate you with doing so. In the process of moving these files, you’ll be posed with questions as to whether or not you want to overwrite the files. Press Enter and the Y key on every question to confirm. Once done, close the window by pressing on the ‘X’ icon. After that, your computer will start up and if you were facing any problems booting your system, they must be solved now. We hope our guide made it convenient for you to navigate your way through the advanced startup’s command prompt setup and that you were able to restore your computer’s Registry successfully. While this process centered around Windows 11/10, similar steps seem to have worked for Windows 8.1 and 7 as well.