Because you cannot rely on the empty RegBack folder, you must use alternative recovery methods to restore your system registry or fix the underlying boot loop. Try these solutions in order. Solution 1: Use System Restore via Command Prompt
Type C: and press Enter, then type dir to see if the Windows folder is present.
Select a restore point dated before your system started crashing. Follow the prompts and restart your PC. regback copy not working
How to Fix the "RegBack Copy Not Working" Error in Windows If you are trying to recover a corrupted Windows system using the Command Prompt, you might have run into a major roadblock: the RegBack folder is completely empty, or copying the files does nothing. You type the copy commands, but your system still refuses to boot, or you notice the file sizes in the directory are listed as 0 bytes.
Boot into the menu (or boot from a Windows installation USB). Because you cannot rely on the empty RegBack
There are several reasons why RegBack copy may not be working as expected. Some common causes include:
Historically, Windows maintained a backup of the registry in %Windir%\System32\config\RegBack . If the main registry hives ( SYSTEM , SOFTWARE , etc.) in \config became corrupted, IT professionals could copy files from RegBack to restore functionality. Select a restore point dated before your system
While the folder and the scheduled task still exist, they no longer populate with data by default. If you are currently in the Windows Recovery Environment (WinRE) trying to copy these files to fix a "Blue Screen of Death" (BSOD), and they show as 0 KB, those files cannot be used to repair your system. How to Fix "RegBack Copy Not Working" for Future Use