System Restore error 0x80070091 means Windows could not complete the restore because a file or folder in the restore point could not be accessed or modified—usually due to permission issues, a corrupted system file, or a locked item. The fix typically involves running the restore from Safe Mode, using the Deployment Image Servicing and Management (DISM) tool to repair system files, or manually resetting the affected folder’s permissions. Below, we break down what causes this error, how to resolve it step by step, and how to prevent it from happening again.
Background: What Is System Restore and Why Does It Fail?
System Restore is a built-in Windows feature that takes snapshots of critical system files, registry settings, and drivers—called restore points—before significant changes like installing software or updating drivers. When you run a restore, Windows reverts those components to the state they were in at the snapshot. Error 0x80070091 (which translates to “The directory is not empty”) typically appears when the restore process tries to replace a folder that contains files it cannot handle. This can happen if a file is locked by a running process, if the folder has unusual permissions, or if the system file itself is corrupted. The error is more common after a failed update or when third-party security software interferes with file operations.
How System Restore Works
System Restore relies on the Volume Shadow Copy service, which creates a point-in-time copy of protected system files. When you initiate a restore, Windows uses that snapshot to overwrite current files with the older versions. The process is not a full backup—it does not touch personal documents, photos, or other user data. It only affects system files, installed programs, and registry settings. The restore operation runs in a special environment that avoids most conflicts, but if a file is in use by a service or driver, or if the file system has errors, the restore can fail with 0x80070091. Understanding this helps because the error is rarely about the restore point itself being bad; it is usually about the current state of the system preventing the restore from writing files.
Common Causes of Error 0x80070091
- Corrupted system files – Damaged system files can prevent the restore process from replacing them.
- Permission issues – A folder or file may have restrictive access control lists (ACLs) that block the restore operation.
- Antivirus or security software – Third-party security tools may lock files or interfere with the restore process.
- Disk errors – Bad sectors or file system corruption can cause the restore to fail.
- Pending updates – A partially installed Windows update can leave the system in an inconsistent state.
Step-by-Step Fixes for Error 0x80070091
Try these methods in order, as they progress from least to most invasive. Always back up important data before attempting system-level repairs.
- Run System Restore from Safe Mode – Safe Mode loads only essential drivers and services, which can bypass file locks. Restart your PC, press F8 (or Shift + Restart) to access Advanced Boot Options, choose Safe Mode, and then run System Restore from the Recovery Environment.
- Use DISM and SFC to repair system files – Open Command Prompt as administrator and run
DISM /Online /Cleanup-Image /RestoreHealth, thensfc /scannow. This repairs corrupted system images and files that may be causing the error. - Check disk for errors – Run
chkdsk /f /rin an elevated Command Prompt. This scans for bad sectors and file system issues. You may need to restart to complete the scan. - Reset folder permissions – If the error mentions a specific folder (like
Program FilesorWindows), you can take ownership and reset permissions usingtakeownandicaclscommands. For example:takeown /f "C:\Program Files\WindowsApps" /r /d yfollowed byicacls "C:\Program Files\WindowsApps" /reset /t /c. - Disable third-party antivirus temporarily – If you have a third-party security suite, disable its real-time protection and try the restore again. Re-enable it afterward.
- Perform a Startup Repair – Boot from a Windows installation USB, choose “Repair your computer”, then “Startup Repair”. This can fix boot-related issues that interfere with restore.
How to Choose the Right Fix
Start with the least disruptive option. If the error occurs immediately after a failed update, DISM and SFC are often the quickest solution. If you have recently installed security software, try disabling it first. If the error persists, Safe Mode is a reliable next step because it eliminates most background processes. Disk errors are less common but should be ruled out early with chkdsk. Resetting permissions is more advanced and should be done only if you are comfortable with command-line tools, as incorrect changes can worsen issues. If none of these work, you may need to consider a system reset or using a different restore point.
Preventing Future System Restore Errors
- Create restore points regularly and before major changes.
- Keep your system files healthy by running
sfc /scannowperiodically. - Ensure your hard drive has enough free space (System Restore needs at least 300 MB, but more is better).
- Avoid force-shutting down your PC, as this can corrupt system files.
- Use a reliable antivirus and keep it updated, but avoid aggressive real-time scanning during system changes.
Frequently Asked Questions
Will System Restore delete my personal files?
No. System Restore only affects system files, installed programs, and registry settings. Your documents, photos, and other personal data are not touched. However, programs installed after the restore point may be removed, and their settings will be lost.
Can I fix error 0x80070091 without losing my data?
Yes, all the fixes listed above are non-destructive to personal files. Even resetting permissions or running DISM does not delete user data. A system reset is the only option that may remove apps, and even then you can choose to keep personal files.
Why does the error mention “directory is not empty”?
This is the literal meaning of error code 0x80070091. It occurs when Windows tries to replace a folder that contains files it cannot delete or overwrite, often because of permissions or a locked file. The fixes above address those root causes.
How long does a System Restore take?
Typically 15 to 30 minutes, but it can take longer if the restore point is large or the system is slow. If it hangs for over an hour, you may need to force restart and try a different fix.
Is it safe to use DISM and SFC?
Yes, these are built-in Windows tools designed to repair system files. They do not affect personal data. However, they require administrative privileges and may take several minutes to complete. If DISM fails, you may need to provide a Windows installation media as a source.
What if none of these fixes work?
If the error persists, you can try using a different restore point, or use the “Reset this PC” feature from Settings > Update & Security > Recovery. This reinstalls Windows while giving you the option to keep your files. As a last resort, a clean installation will definitely resolve the issue, but it will remove all installed programs.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Clone a Hard Drive That Won’t Boot: Full Guide
- Gboard Not Working on iPhone? 8 Fixes That Actually Work
- Fix Unable to Start the Bluetooth Stack Service
- Destiny 2 Connection Error Codes: Step-by-Step Fix
- Fix Discord Picking Up Game Audio on Windows
- How to Sign in to Third-Party Apps with Your Apple ID