The logic behind the regback method is simple: Windows is supposed to keep a backup of these vital registry hives in a folder named RegBack . If your active registry gets corrupted, the idea is to copy these "good" backups from RegBack into the main Config folder, overwriting the bad files.
Prior to Windows 10 version 1803, the Windows Task Scheduler ran a task called "RegIdleBackup." This task would automatically backup the registry hives to the C:\Windows\System32\config\RegBack folder periodically. This was a safety net for power users and administrators. regback copy -.- .. not working
Consequently, when you navigate to that folder via Command Prompt, you see nothing but empty placeholders or 0 bytes files. Attempting to run a copy command on empty files results in "not working" errors, and even if it did work, you would essentially be overwriting your corrupt registry with... nothing. The logic behind the regback method is simple:
However, starting with Windows 10 version 1803 (April 2018 Update), Microsoft disabled this functionality to reduce the overall disk footprint of Windows. The operating system no longer automatically backs up the registry to the RegBack folder. This was a safety net for power users and administrators