In earlier releases of Windows, the operating system routinely created background backup snapshots of your critical system Registry hives (SAM, SECURITY, SOFTWARE, SYSTEM, and DEFAULT) inside the C:\Windows\System32\config\RegBack folder. Starting in Windows 10 and continuing in Windows 11, Microsoft disabled this automatic backup behaviour by default to reduce the overall storage footprint of the operating system. Fortunately, you can re-enable this automated safeguard using a simple Registry configuration.
Why Re-Enabling Automated Registry Backups Matters
The Windows Registry stores low-level operating system configurations, hardware driver associations, and software user settings. While System Restore Points offer broad recovery options, having direct access to intact, offline Registry hive backups offers unique advantages:
- Offline Blue Screen Recovery: If an incomplete Windows Update, corrupted driver, or malware renders your PC unbootable (causing a BSoD loop), you can boot into Windows Recovery Environment (WinRE) or a command prompt and copy clean hive files directly from
RegBackintoconfig. - Negligible Storage Overhead: A complete set of backup hives typically consumes between 50 MB and 150 MB of disk space—an insignificant amount on modern solid-state drives.
- Scheduled Idle Maintenance: Once enabled, Windows executes the backup during idle system maintenance without causing CPU or disk bottlenecks while you are actively working.
Method 1: Enable Automatic Backups via Registry Editor (GUI)
You can configure the required system value directly through the Windows Registry Editor:
- Press Windows Key + R to open the Run dialogue box.
- Type
regeditand press Enter (click Yes if prompted by User Account Control). - In the Registry Editor address bar at the top, paste the following key path and press Enter:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Configuration Manager - Right-click in the empty space within the right-hand pane, hover over New, and select DWORD (32-bit) Value.
- Name the new value exactly:
EnablePeriodicBackup - Double-click
EnablePeriodicBackup, change its Value data from0to1, and ensure the base is set to Hexadecimal. - Click OK to save the change, then close the Registry Editor.
- Restart your computer to allow the Windows kernel to initialize the backup sub-routine.
Method 2: Enable Automatic Backups via Command Prompt (Fastest)
If you prefer an instant terminal command, you can inject the DWORD value with administrative privileges:
- Click the Start button, type
cmd, right-click Command Prompt, and select Run as administrator. - Paste the following command into the terminal window:
reg add "HKLM\System\CurrentControlSet\Control\Session Manager\Configuration Manager" /v EnablePeriodicBackup /t REG_DWORD /d 1 /f - Press Enter. The prompt will return “The operation completed successfully.”
- Restart Windows.
How to Manually Trigger and Verify the RegBack Task
Rather than waiting days for Windows Idle Maintenance to trigger the first backup cycle, you can initiate the task immediately via Task Scheduler:
- Press Windows Key + R, type
taskschd.msc, and press Enter. - In the left sidebar, expand the folders:
Task Scheduler Library > Microsoft > Windows > Registry. - In the centre pane, locate the task named RegIdleBackup.
- Right-click RegIdleBackup and select Run.
- Allow 30 to 60 seconds for the task to complete, then press F5 to refresh the status. The Last Run Result should display
The operation completed successfully. (0x0).
Verifying Your Backup Files on Disk
To confirm that your Registry hives have been written successfully:
- Open File Explorer and navigate to:
C:\Windows\System32\config\RegBack - You will now see non-zero file sizes for
DEFAULT,SAM,SECURITY,SOFTWARE, andSYSTEM. - If the folder appears empty or asks for permission, click Continue to grant administrative viewing rights.
Restoring automated Registry backups provides an indispensable safety net against catastrophic system errors, ensuring your Windows 11 installation remains resilient and recoverable even when standard boot recovery tools fail.