Fix System Restore Error 0x8007045d in Windows 11

System Restore error 0x8007045d stops Windows 11 from completing a restore point rollback, usually because a driver or the restore engine cannot read or write to the disk during the process. This guide walks through the fixes that clear the error and let System Restore finish, starting with the safest options and moving to more involved ones.

What You’ll Need

Administrator access to the Windows 11 PC
A stable power connection (laptop should be plugged in)
Optional: a Windows 11 installation USB drive if you need to run Startup Repair or use Command Prompt from the recovery environment

Step-by-Step

Restart the PC and try System Restore again. The error often appears after a partial driver update or a temporary disk hiccup. A clean reboot clears pending I/O operations. Go to Start, type “Create a restore point,” open it, click System Restore, and attempt the restore once more.
Run System Restore in Safe Mode. Boot into Safe Mode (Settings > System > Recovery > Advanced startup > Restart now, then Troubleshoot > Advanced options > Startup Settings > Restart, press 4). In Safe Mode, third-party drivers and services are not loaded, which removes many causes of the 0x8007045d error. Open System Restore from the Control Panel and retry.
Disable antivirus temporarily. Third-party security software can lock system files during the restore. Open your antivirus app, find the shield or protection settings, and turn off real-time protection for the duration of the restore. Re-enable it immediately after the restore finishes.
Run a disk check on the system drive. Open Command Prompt as administrator (Start, type “cmd,” right-click, Run as administrator). Run chkdsk C: /f /r. When prompted to schedule the check on restart, press Y and reboot. Let the scan complete; it may take 30-60 minutes. Afterward, retry System Restore.
Free up disk space. System Restore needs room to write the restored files. Open Settings > System > Storage, and remove temporary files or uninstall large programs you no longer need. Aim for at least 10-15 GB free on the system drive. Then go to System Protection settings and confirm the restore point still exists.
Create a new restore point and try restoring to that. Sometimes the existing restore point is corrupted. Open System Protection, click Create, name it, and wait. Then run System Restore and choose this new point to see if it completes.
Use System File Checker (SFC) and DISM. Corrupted system files can cause the error. In an elevated Command Prompt, run sfc /scannow. After it finishes, run DISM /Online /Cleanup-Image /RestoreHealth. Reboot and try System Restore again.
Perform a Startup Repair. Boot from the Windows 11 installation USB, select your language, click Repair your computer, then Troubleshoot > Advanced options > Startup Repair. This fixes boot-level issues that can block the restore process. After it runs, reboot normally and attempt the restore.
Disable and re-enable System Protection. This clears the restore point store. Go to System Protection, select the system drive, click Configure, choose Disable system protection, and click OK. Reboot, then re-enable protection and create a fresh restore point. Note: this deletes all existing restore points, so only do this if you have no other option.
Run System Restore from the Recovery Environment. Boot into Advanced startup (Settings > System > Recovery > Advanced startup). Choose Troubleshoot > Advanced options > System Restore. This runs the restore outside of the normal Windows session, which avoids many file-locking issues.

Common Mistakes

Skipping the disk check. The 0x8007045d error is frequently a read/write failure. Running chkdsk first saves time by ruling out bad sectors or file system corruption.
Leaving antivirus running. Real-time protection can intercept file operations during the restore, causing the error to reappear. Disable it fully, not just the “quick scan” option.
Restoring to a very old point. Older restore points are more likely to contain files incompatible with current drivers. Try a more recent point first.
Not checking disk space. If the drive is nearly full, the restore engine cannot write the restored files. Free space before retrying.

Tips

Create restore points regularly. Set System Protection to create a point before major updates or driver installs. Manual points before risky changes are a good habit.
Keep your system drive healthy. Run chkdsk every few months and use the Storage Sense feature to keep temporary files from accumulating.
Use the “System Restore” from the login screen. If Windows won’t boot fully, hold Shift while clicking Restart on the login screen to reach Advanced startup and run System Restore from there.
Document your restore point dates. Knowing what you changed recently helps you pick the right point and avoids restoring too far back.

Troubleshooting

If the error persists after all the above steps, the restore point itself is likely damaged or the system drive has deeper issues. Try the following:

Test the hard drive health. Open Command Prompt as administrator and run wmic diskdrive get status. If it returns anything other than “OK,” the drive may be failing. Back up important data immediately.
Use a different restore point. If you have multiple points, try an older one. If none work, the System Protection store is corrupted.
Reset this PC. As a last resort, go to Settings > System > Recovery > Reset this PC. Choose “Keep my files” to reinstall Windows while preserving your personal data. This replaces system files without deleting your documents. Back up anyway before doing this.
Check for pending Windows updates. Sometimes a half-installed update interferes with System Restore. Go to Settings > Windows Update, install all pending updates, reboot, and retry.

Frequently Asked Questions

Q: Will I lose my personal files if I run System Restore?
A: No. System Restore only changes system files, installed programs, and registry settings. Your documents, photos, and other personal files remain untouched.

Q: Why does the error appear only sometimes?
A: Intermittent 0x8007045d errors usually point to a driver or service that occasionally locks files, or a disk that has developing bad sectors. The chkdsk step is the most likely fix for this pattern.

Q: Can I fix this without a Windows installation USB?
A: Yes, most steps in this guide work from within Windows. The Startup Repair step requires a USB, but you can skip it and rely on Safe Mode and the Recovery Environment’s System Restore instead.

Q: How long does a disk check take?
A: On a modern SSD, chkdsk usually finishes in 10-30 minutes. On a large or slow hard drive, it can take over an hour. Let it run to completion without interrupting.

Q: Does disabling System Protection delete my restore points?
A: Yes. When you turn off System Protection for a drive, all existing restore points for that drive are deleted. Only do this if you have no other option, and create a new point right after re-enabling it.

Q: What if the error appears on a different drive, not C:?
A: The steps are the same, but run chkdsk on that specific drive letter (e.g., chkdsk D: /f /r) and make sure that drive has enough free space.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →