Copy Not Working: Regback

The Scheduled Task named RegIdleBackup (located in Task Scheduler Library\Microsoft\Windows\Registry) still exists. In older versions, this task triggered during system idle time to copy hives to RegBack. In modern versions, the task trigger remains, but the action has been effectively nullified or deprioritized by the OS logic.

Microsoft provided a registry tweak to re-enable the legacy behavior.

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.

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.

If you are trying to restore your Windows registry using the copy *.* .. command in the RegBack folder and it isn't working, it is likely because Microsoft disabled automatic registry backups starting in Windows 10 version 1803. In newer versions, the files in \System32\config\RegBack often show a size of 0 KB, making them useless for recovery.  Why "copy . .." Fails 

Empty Backups: By default, Windows no longer populates the RegBack folder to reduce the overall disk footprint of the operating system. regback copy not working

0 KB Files: If you run dir in the RegBack folder and see 0-byte files (DEFAULT, SAM, SECURITY, SOFTWARE, SYSTEM), the copy command will technically "work" but will overwrite your current registry with empty files, potentially making the system unbootable.  Immediate Fixes for a Boot Loop 

If you are stuck in a "Repair Loop" and RegBack is empty, try these alternatives: 

System Restore: This is the intended replacement for manual registry backups. Run rstrui.exe from the command prompt in the Advanced Startup options to revert to a previous state.

Startup Repair: Use the built-in "Startup Repair" tool from the Windows Recovery Environment (WinRE) to automatically detect and fix boot issues.

Reset this PC: If restore points are unavailable, use the "Keep my files" reset option to reinstall Windows while preserving your data.  How to Re-enable RegBack (For Future Use) 

If you want to ensure RegBack works in the future, you must manually re-enable the feature via the Windows Registry Editor:  Open Regedit.

Navigate to: HKLM\System\CurrentControlSet\Control\Session Manager\Configuration Manager. The Scheduled Task named RegIdleBackup (located in Task

Right-click and create a new DWORD (32-bit) Value named EnablePeriodicalBackup. Set the Value data to 1.

Restart your computer. Windows will now periodically back up the registry to the RegBack folder again. 

For official troubleshooting steps and further details on registry management, you can visit Microsoft Support. 

Do you have a System Restore point available, or are you currently stuck at the command prompt? 

Ensure your system drive (usually C:) has at least 2 GB of free space.

After freeing space, run the RegIdleBackup task again.

If you are looking for regback because Windows won't boot and you are using the Command Prompt from the Recovery Environment (WinRE), Solution 1 won't help you right now. The message that "regback copy not working" is

You have two remaining options:

| Cause | Explanation | |-------|-------------| | Windows 10/11 behavior change | Starting Windows 10 version 1803, Microsoft changed RegBack: hives are no longer backed up to RegBack by default (Task Scheduler disabled). Existing files may be placeholders or empty. | | Volume Shadow Copy (VSS) misuse | If you copy directly while registry is in use, you get locked files. Copying via reg save command is required, not file copy. | | NTFS permissions | SYSTEM has full control; even Administrators may not have read access by default to copy live hives. | | Corrupt registry backup task | The RegIdleBackup task fails silently; last write times on RegBack files show months/years old. | | Antivirus / real-time protection | Some security software blocks read access to registry hives as anti-tampering. |

The "RegBack" folder is intentionally empty on Windows 10/11.

Starting with Windows 10 build 1709 (Fall Creators Update), Microsoft changed the default behavior of the Registry backup mechanism. To save disk space and reduce background I/O, Microsoft disabled automatic registry backups to the RegBack folder.

If you navigate to C:\Windows\System32\config\RegBack today, you will likely see files of 0KB or 64KB (placeholder files). This is not a bug—it is the new default.

Instead of relying on regback, enable System Restore. It backs up the registry as part of a restore point.