Historically, the regback command (available via reg save or the legacy RegBack folder at C:\Windows\System32\config\RegBack) was designed to create a copy of the core Registry hives (SAM, SECURITY, SOFTWARE, SYSTEM, DEFAULT).
These backups were meant as a last-resort recovery option if the main registry became corrupted.
The message that "regback copy not working" is more than a minor annoyance—it is a warning that your system lacks a critical recovery tool. A corrupt registry without a backup can lead to hours of troubleshooting, data loss, or even a full OS reinstallation.
Fortunately, the solutions are straightforward. In most cases, simply setting EnablePeriodicBackup to 1 and manually running the RegIdleBackup task restores full functionality. If not, checking disk space, permissions, and task scheduler integrity will resolve the issue. And if all else fails, manual registry backups and third-party tools provide a reliable fallback.
Do not wait until your system crashes to discover that your registry has no backup. Verify your RegBack folder today—because when disaster strikes, a working registry backup is your best friend. regback copy not working
Have you encountered a "regback copy not working" scenario that these steps didn't resolve? Check the comments below for community-driven solutions, or consult Microsoft's official documentation on the RegIdleBackup task. Your system's stability depends on a healthy, regularly backed-up registry.
The issue where the RegBack copy command fails or the folder appears empty is a deliberate design change by Microsoft, not a bug. Starting with Windows 10 version 1803, Windows no longer automatically backs up the system registry to the RegBack folder to reduce the overall disk footprint. 💡 Why It Is "Not Working"
Empty Folders: If you navigate to \Windows\System32\config\RegBack, you will likely see registry hives (DEFAULT, SAM, SECURITY, SOFTWARE, SYSTEM) with a size of 0 KB.
Command Failures: When using the command copy *.* .. in the recovery console, you may receive the error "The system cannot find the file specified" or "0 file(s) copied" because the source files are empty or missing. 🔧 How to Fix and Re-enable RegBack Historically, the regback command (available via reg save
If you want to restore this legacy behavior so you have a manual recovery point in the future, you must edit the registry:
Open Registry Editor: Press Win + R, type regedit, and hit Enter.
Navigate to: HKLM\System\CurrentControlSet\Control\Session Manager\Configuration Manager.
Create a New Value: Right-click, select New > DWORD (32-bit) Value. Name it: EnablePeriodicBackup. Set Value: Double-click it and change the Value data to 1. Restart: Reboot your computer. Have you encountered a "regback copy not working"
Trigger the Task: To populate the folder immediately, go to Task Scheduler > Microsoft\Windows\Registry and right-click the RegIdleBackup task to select Run. 🚑 Alternatives for Immediate System Recovery
Since RegBack is often empty when you need it most, use these alternatives for a no-boot situation: Windows 10 & 11 Enable Regback
RegBack does not fix registry corruption because backups are empty/old.The Registry hives (SOFTWARE, SYSTEM, SAM, SECURITY, DEFAULT) are loaded into memory the second Windows boots. The kernel has an exclusive lock on these files (%SystemRoot%\System32\config\). You cannot copy a file that the operating system has open for read/write access. This is an anti-corruption feature.
Sometimes, the underlying disk has corruption or the Registry structure is damaged beyond standard repair. In this case:
Once you have confirmed that RegBack copy is working (files are non-zero and recent), here is how to perform a full registry restore—useful if your system is unbootable.