The failure of regback to copy registry files is not a bug, but a feature change in Windows 10 (1803+) and Windows Server 2019+. The folder is intentionally left empty. Administrators must adjust their disaster recovery playbooks to utilize the EnablePeriodicBackup registry key or move toward VSS-based backups to ensure registry hives are securely archived.

The Windows Registry is a critical component of the operating system, storing vital settings and configurations. Creating a backup copy of the registry using REGEDIT is a recommended practice, allowing users to restore their system to a previous state in case of errors or unwanted changes. However, some users may encounter issues when attempting to create a backup copy using REGEDIT. In this write-up, we will explore the possible causes and solutions for REGEDIT backup copy not working.

Article last updated: 2025

The Windows Registry is the central database that stores low-level settings for the operating system and installed applications. A corrupted registry can lead to blue screens, application crashes, boot failures, and system instability. That is why Windows includes a built-in feature called (Registry Backup), which automatically creates copies of registry hives (SAM, SECURITY, SOFTWARE, SYSTEM, DEFAULT) in the C:\Windows\System32\config\RegBack folder.

Right-click and create a new named EnablePeriodicalBackup . Set the Value data to 1 .