Share via


How to use Regback to fix failure to boot

Question

Sunday, April 14, 2019 8:57 PM

One of the methods that has worked for failure to boot is Regback.

There is a bug in the method that had worked:

https://www.thewindowsclub.com/regbak-lets-you-backup-and-restore-the-windows-7-registry-easily

https://borncity.com/win/2018/11/05/windows-10-regback-fails-in-v1803-1809/

If the command vssadmin.exe list shadows

is used it will display the shadow copies.

How do you use a shadow copy to recover registry hives?

Please list step by step methods

All replies (7)

Monday, April 15, 2019 6:16 AM

Hi,

If we cannot boot up and want to replace hive files, we need to boot from WinRE, and open CMD. 

1. Go to C:\windows\system32\config

2. Backup the current system/software hive:

      Ren system system_backup
**      Ren Software Software_backup **

3. Replace the system / software hive by:

     Copy C:\windows\system32\config\regback\software C:\windows\system32\config\software
     Copy C:\windows\system32\config\regback\system C:\windows\system32\config\system
 
4. Other HIVE we can replace is: SAM, Default and Security.

5. Restart the machine. 

Best regards,

Yilia 

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Monday, April 15, 2019 7:18 AM

How can the registry hives be backed up if the file size displays 0?

Isn't the bug the failure to backup the hives when the computer is health.

Without the backup there are no options when the computer is unhealth > so that when attempting to restore them the file sizes display zero?

In the video they also comment on the size of the files.

What is the work around for the windows 1803 and 1809 bug compared to windows 1709?

Is there a different command?

Is there a different method to fix the bug?


Monday, April 15, 2019 8:11 AM

Hi,

The OS will automatically backup a HIVE file (including system / software / SAM / default / Security hive file) when last successfully logon into desktop.

According to my experience, the HIVE files size cannot be zero if the computer runs well. If their size display 0, it could be corrupted. It means we can copy all the following files from a similar server or a parallel installed OS:

**c:\windows\system32    **
c:\windows\system32\drivers

Best regards,

Yilia 

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Monday, April 15, 2019 12:59 PM

The Regback method was working well for unexpected boot failure up through Windows 1709.

Beginning with 1803 the same method failed.

See the two links in the opening post.

The Regback method is used when the computer is healthy to restore the computer to a healthy state.  If the method fails (file size 0) then the computer will remain the failure to start or unbootable state.

During boot failure these are the steps that are typically used to perform regback:

https://www.youtube.com/watch?v=AFKHWUS9g8g

What options are there now with Windows 1803 and 1809?

The steps need to work in windows RE (failure to boot)


Tuesday, April 16, 2019 7:45 AM

Hi,

Yes, I checked the Regback folder in 1803 and 1809 version, one is 0 and the other is empty. I think it could be a potential issue in those version. 

We can use Windows 10 built-in feedback hub (type feedback hub in search box) to give Microsoft a valuable feedback and I am going to submit this case to Microsoft via our channel. 

Best regards,

Yilia 

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Friday, April 26, 2019 3:27 AM

Hi,

Just want to confirm the current situations.

Please feel free to let us know if you need further assistance.   

Best regards,

Yilia

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Monday, July 22, 2019 3:51 PM

I just read that as of v1809 the Registry is no longer backed up which is a bummer now that I need it!

Marci