Right-click the Configuration Manager folder, select New > DWORD (32-bit) Value . Name It: Title the new entry EnablePeriodicBackup . Set Value: Double-click it and set the "Value data" to 1 .
For those who prefer the command line, you can run this as an Administrator in Command Prompt: reg add "HKLM\System\CurrentControlSet\Control\Session Manager\Configuration Manager" /v EnablePeriodicBackup /t REG_DWORD /d 1 /f This single line achieves the same result as the manual Registry Editor steps. After running it, restart your system.
Once completed, run the deployment image tool: dism /image:C:\ /cleanup-image /restorehealth Alternative Solutions for System Recovery
This error occurs when you try to use regback as a file copy operation rather than the reg utility. regback copy not working
What specific or symptom caused you to look for the RegBack folder?
Since the RegBack files are empty, the fastest way to replace a corrupted registry is by using a System Restore point. This rolls back your system registry to a previous working state without deleting your personal files.
If your system is still running (or you can run Command Prompt from recovery), you can try to repair your system image itself using the Deployment Imaging Service and Management Tool (DISM). Right-click the Configuration Manager folder, select New >
Since Windows 10 version 1803, the folder is empty or contains 0 KB files by design. Microsoft disabled automatic registry backups to reduce the operating system's disk footprint.
: If you are tech-savvy, you can use the command prompt in recovery mode to pull registry files from a "Shadow Copy" created by Windows. This is essentially what System Restore does, but it can be done manually if the standard UI fails. Reset Your PC
xcopy D:\Windows\System32\config\RegBack\* D:\Windows\System32\config\ Use code with caution. For those who prefer the command line, you
In the center pane, right-click the task named and click Run .
If you want to ensure the RegBack folder works in the future, you must manually re-enable the legacy behavior via the Windows Registry Editor.
Need more troubleshooting? Check your Windows Event Logs under "Applications and Services Logs > Microsoft > Windows > CAPI2" for deeper Registry operation errors.