Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x80070091

System Restore failed with 0x80070091 or 0x81000203 on Windows 10 and 11

12 min read Updated October 5, 2026 Windows Crashes & Boot Recovery

Fix it now

0x80070091 is ERROR_DIR_NOT_EMPTY – the directory is not empty. The restore engine tried to replace a folder whose contents it could not clear, which is a locking problem rather than a broken restore point. Running the restore from outside Windows, where those files are not in use, is the fix.

Run the first in an elevated Command Prompt; the second opens System Properties

vssadmin list writers
sysdm.cpl
  1. Run the restore from the recovery environment rather than from inside Windows. Hold Shift while choosing Restart, then Troubleshoot, Advanced options, System Restore. Files locked in a running session are free there.
  2. If it still fails and names a folder, note it. The usual one is the Store application folder under Program Files.
  3. From the recovery environment’s Command Prompt, find the Windows volume with diskpart and list volume, then move the folder aside: ren "D:\Program Files\WindowsApps" WindowsApps.old, using whichever letter recovery assigned.
  4. Retry System Restore from the same menu.
  5. Back in Windows, check the shadow copy machinery with vssadmin list writers. It should return a list, with every writer in a stable state and no last error.

Rename, do not delete. If the restore fails for another reason you can put the folder back exactly as it was, and Windows will not have to rebuild anything it did not need to.

If the restore completes and the machine starts normally, you are done. If the shadow copy service itself is failing, the next section separates that from the restore problem.

Why it happens

System Restore keeps no copies of its own. It asks the Volume Shadow Copy Service for a point-in-time snapshot when a restore point is created, and asks for it back when you roll one in. Applying a restore point means replacing system files, drivers and registry hives from that snapshot while leaving documents alone. So there are two halves that fail independently, and the codes tell you which one you have.

0x80070091 is an application failure, not a creation failure. ERROR_DIR_NOT_EMPTY means exactly what it says: the engine tried to clear a directory and could not. The Store application folder is the usual offender, because its contents are owned by a system identity and hard-linked into the component store, and a running Windows will not let them go. Nothing about that indicates a damaged restore point, which is why the same restore that fails from the desktop succeeds from the recovery environment.

The rest of the codes come from underneath. 0x80042302 is VSS_E_UNEXPECTED_ERROR – a Volume Shadow Copy Service component encountered an unexpected error. 0x80042306 is VSS_E_PROVIDER_VETO, returned when the snapshot provider receives an expected error and vetoes the operation; Microsoft’s Data Protection Manager error list describes the same value as the writer or the provider being in a bad state. 0x8000FFFF is E_UNEXPECTED, catastrophic failure, which is the general-purpose answer returned when nothing more specific came back.

0x81000203 turns up in the same conversations and deserves an honest answer: Microsoft publishes no meaning for it. It appears from the System Protection property page and from the System Restore wizard when the request into the shadow copy machinery does not complete, and every explanation you will find online comes from a forum. Treat it as a signal to go and look at the shadow copy service directly rather than as a diagnosis in itself.

A protected folder blocks the rollback

You have this one if 0x80070091, and the message names a directory – most often the Store application folder under Program Files.

  1. Start the recovery environment and open the Command Prompt.
  2. Identify the Windows volume with diskpart and list volume; the letters differ from what you see inside Windows.
  3. Rename the folder rather than deleting it: ren "D:\Program Files\WindowsApps" WindowsApps.old.
  4. Run System Restore from the Advanced options menu, then check Store applications afterwards and repair any that misbehave.

Never do this on a running system. The folder is in use, the rename will either fail or half-succeed, and you will have made the situation worse than the error you started with.

The shadow copy services are not running

You have this one if The System Protection tab reports an error as soon as you open it, or vssadmin list writers returns nothing useful.

  1. In Services, confirm Volume Shadow Copy and Microsoft Software Shadow Copy Provider are set to Manual rather than Disabled.
  2. Start them from an elevated prompt: net start vss and net start swprv.
  3. Confirm with vssadmin list writers, which should return a list rather than an error.
  4. If a writer is listed but unstable, restart the service that hosts it, or restart the machine – writers reset on a restart.

The provider or a writer is failing underneath

You have this one if 0x80042302, 0x80042306 or 0x8000FFFF, and the Application event log carries VSS entries around the time of the attempt.

  1. Read the Application log entries from the VSS source immediately before the failure; they usually name the component rather than the symptom.
  2. Restart the service that owns the failing writer. The VSS service itself hosts the registry, COM+ class registration database, shadow copy optimization and ASR writers; other writers belong to their own application’s service.
  3. Restart the machine if a service restart does not clear it.
  4. Repair the servicing components with dism /Online /Cleanup-Image /RestoreHealth and sfc /scannow if writers keep failing after a restart.

Do not re-register the VSS DLLs. Microsoft publishes that procedure for Windows Server 2003 only, and states that trying it on Windows Vista, Windows Server 2008 or later can produce results that require reinstalling Windows to resolve.

There is no space for restore points, or protection is off

You have this one if No restore points appear at all, or the newest one is far older than you expect.

  1. Open System Protection with sysdm.cpl and go to the System Protection tab.
  2. Select the system drive, choose Configure, confirm protection is on, and give it a sensible maximum.
  3. Adjust the allocation with vssadmin resize shadowstorage /for=C: /on=C: /maxsize=20GB, noting that Microsoft warns resizing may cause existing shadow copies to disappear.
  4. Prove it works: Checkpoint-Computer -Description "Manual test" -RestorePointType MODIFY_SETTINGS in an elevated PowerShell session.

Windows limits how often a restore point is created automatically, so an attempt made shortly after another point may appear to do nothing. Leave a gap before concluding it is broken.

Full reference

The tools, and which are actually documented

Command Purpose In the vssadmin reference?
vssadmin list writers Lists subscribed shadow copy writers and their state Yes, client and server
vssadmin list shadows Lists existing shadow copies Yes, client and server
vssadmin delete shadows Deletes shadow copies Yes, client and server
vssadmin resize shadowstorage /for=C: /on=C: /maxsize=20GB Sets the space available for shadow copies Yes, client and server
vssadmin list providers Lists shadow copy providers, including third-party ones Not in the current reference
vssadmin list shadowstorage Shows the space allocated per volume Not in the current reference
sysdm.cpl Opens System Properties, where System Protection is configured –
rstrui.exe Opens the System Restore wizard directly –

The last two vssadmin verbs work on the machines most people run them on, but Microsoft’s current command reference documents only four subcommands and does not list them. That is worth knowing when you are writing a runbook someone else will follow: build the documented ones into the procedure and treat the others as useful extras.

The thing not to do

Do not stop the VSS services and re-register ole32.dll, oleaut32.dll, vss_ps.dll, es.dll, swprv.dll, eventcls.dll and the rest with regsvr32, and do not run vssvc /register. That sequence is published by Microsoft for Windows Server 2003 only, and the same article states plainly that it is not for use with Windows Vista, Windows Server 2008 or later, because component installation is manifest based from those releases onwards and manual registration can produce unexpected results that may require reinstalling Windows to resolve. It is one of the most widely copied pieces of bad advice about VSS.

What to do instead is duller and works: restart the service that hosts the failing writer, restart the machine, and repair the servicing components with DISM and SFC. If a writer keeps failing after a restart, it is usually reacting to a real fault in the application it represents, and that application’s own logs are where to look.

Reading the codes

Code Published as What it means for you
0x80070091 ERROR_DIR_NOT_EMPTY (145) A directory could not be cleared. Restore from outside Windows
0x81000203 Not published by Microsoft Seen from System Protection and the restore wizard. Go and look at VSS directly
0x80042302 VSS_E_UNEXPECTED_ERROR A VSS component hit an unexpected error. Read the Application log
0x80042306 VSS_E_PROVIDER_VETO The provider vetoed the operation. In DPM’s error list, the writer or provider is in a bad state
0x8000FFFF E_UNEXPECTED: catastrophic failure No more specific error was available. The log entries around it carry the content

When restores work from recovery but never from the desktop

That pattern means something in the running session is holding files open. Pause real-time protection and any backup agent while you restore. Check the provider list for a third-party provider left behind by uninstalled backup software – and if one is there, reinstall that product and uninstall it properly with the vendor’s tool rather than removing the provider by hand.

Turning System Protection off, even briefly, deletes every existing restore point on that volume. If you are troubleshooting because you want to use one of those points, do not touch that setting until after you have restored.

Proving it afterwards

  1. Run vssadmin list writers and confirm every writer reports a stable state with no last error.
  2. Create a restore point deliberately with Checkpoint-Computer and confirm it appears in the wizard.
  3. Roll that test point in on a machine you can afford to disturb, so you know the whole path works rather than just the creation half.
  4. Watch the Application log for VSS errors over the following days, including during any backup window.
  5. If the machine is protected by a backup product, run one full job and confirm it completes.

Every code this article covers

Code What it points at Source
0x80070091 ERROR_DIR_NOT_EMPTY (145): the directory is not empty. The restore engine could not clear a folder it needed to replace Microsoft Learn
0x81000203 Seen from the System Protection property page and the System Restore wizard when the request into the shadow copy machinery does not complete. Microsoft publishes no meaning for this value not published by the vendor
0x80042302 VSS_E_UNEXPECTED_ERROR: a Volume Shadow Copy Service component encountered an unexpected error Microsoft Learn
0x80042306 VSS_E_PROVIDER_VETO: returned when the snapshot provider receives an expected error and vetoes the operation. Microsoft’s DPM error list describes the same value as the writer or provider being in a bad state Microsoft Learn
0x8000FFFF E_UNEXPECTED: catastrophic failure. Returned when no more specific error was available Microsoft Learn

Confirm the fix worked

  1. The restore completed and the machine starts and signs in normally.
  2. vssadmin list writers shows every writer in a stable state with no last error.
  3. A restore point created manually with Checkpoint-Computer appears in the System Restore wizard.
  4. No new errors from the VSS source appear in the Application event log over the following days.
  5. If a folder was renamed, confirm Store applications work and then remove the .old copy deliberately rather than leaving it.

Questions people ask about this

Will System Restore delete my documents?

No. It targets system files, drivers, registry settings and installed programs. Files in your profile are left alone, which also means it will not bring back a document you deleted. It is a configuration rollback, not a backup.

Should I re-register the VSS DLLs?

No. That procedure is published by Microsoft for Windows Server 2003 only, and the same article states it is not for use with Windows Vista, Windows Server 2008 or later, where manual registration can produce results that may require reinstalling Windows. Restart the service that hosts the failing writer instead.

Why did my restore points disappear?

Several ordinary things remove them: the space allocated to shadow copies filling so older points are dropped, a disk cleanup, a feature update, System Protection being turned off, or a resize – Microsoft warns that resizing shadow storage may cause shadow copies to disappear.

Is renaming the Store application folder safe?

As a step taken from the recovery environment, yes. Windows recreates what it needs, though some Store applications may need repairing afterwards. Rename rather than delete so it can be reversed, and never do it on a running system.

Does any of this need paid software?

No. Everything here is built into Windows and nothing about these codes indicates an activation problem. If you want scheduled, verifiable recovery rather than restore points, that is an argument for a backup product – but it is not a fix for this error.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error DRIVER_CORRUPTED_MMPOOL 0x000000D0 and driver pool corruption bugchecks License Error SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x0000007E on Windows 10 and 11 License Error NTFS_FILE_SYSTEM 0x00000024 – volume corruption behind the blue screen Free Fix MEMORY_MANAGEMENT 0x0000001A and PFN_LIST_CORRUPT 0x0000004E blue screens
โ† Back to Knowledge Base