0x80070005 Shadow Copy Access Denied: Fixes

When a machine attempts to access a Shadow Copy or a Previous Version of a file or folder, it may return 0x80070005 (Access Denied). This error appears in the Volume Shadow Copy Service (VSS) event log, in the Previous Versions tab, or when using vssadmin list shadows. The machine is not reporting a disk failure or a corrupted file system; it is reporting that the process requesting access does not have the required permission. The error is thrown by a service, not by a user account, which is why the usual “take ownership” or “grant full control” fixes on the file or folder do nothing.

The permission that matters is the service account that the Volume Shadow Copy Service and the Microsoft Software Shadow Copy Provider run under. By default, these services run as Local System, which normally has access to all local resources. When the error appears, one of the following is true:

• The service account has been changed to a low-privilege account (e.g., Network Service or a custom user).
• The shadow copy storage (the System Volume Information folder) has had its permissions altered, blocking even Local System.
• The service is running but the VSS writers are in a bad state, causing the access check to fail.

This page covers the causes in order of likelihood and the repairs from least to most destructive. The most common cause is a misconfigured service account, not a dead disk.

Causes and How to Tell Them Apart

Repairs

1. Confirm the Service Account

The first step is to verify that the VSS services are running under the correct account. Open services.msc (Win+R, type services.msc). Locate Volume Shadow Copy and Microsoft Software Shadow Copy Provider. Double-click each, go to the Log On tab, and check that Local System Account is selected. If either is set to a different account, change it and restart the service.

If both are already Local System, proceed to the next step.

2. Check VSS Writers

A VSS writer in a failed state can cause access-denied errors even when permissions are correct. Open an elevated Command Prompt (Run as administrator) and run:

vssadmin list writers

The output lists each writer with a state. Look for any writer with a state other than Stable. If a writer shows an error, note the writer name and its error code. A common fix is to restart the service that hosts the writer (e.g., for the Registry writer, restart the Volume Shadow Copy service itself).

If all writers are stable, continue.

3. Restart VSS Services

Sometimes the service is running but in a bad state. Restart both services. In an elevated Command Prompt:

net stop vss
net start vss

Also restart the provider service:

net stop swprv
net start swprv

After restarting, try accessing the shadow copy again. If the error persists, move to the next step.

4. Verify System Volume Information Permissions

The shadow copy storage lives in the System Volume Information folder on each volume. If its permissions have been tampered with, even Local System can be denied. To check, run in an elevated Command Prompt:

icacls "C:\System Volume Information"

Replace C: with the drive that holds the shadow copies. The output should include an entry for NT AUTHORITY\SYSTEM with (F) (Full Control). If that entry is missing or shows a deny, you need to restore it. This is a sensitive folder; changing permissions incorrectly can break system restore and shadow copies further.

To reset the permissions to default, use the following command. This will replace all permissions on the folder with the default ones, which grant SYSTEM full control and Administrators read access. This does not delete any data.

icacls "C:\System Volume Information" /reset /t /c

If the folder is inaccessible even to the administrator, you may need to take ownership first. That step is more invasive and is described in the next section.

5. Take Ownership of System Volume Information (if needed)

If the previous step fails with “Access Denied” even as administrator, the folder’s ACL is severely broken. Taking ownership is the next step. This changes the owner of the folder to the Administrators group. It does not delete data.

In an elevated Command Prompt, run:

takeown /f "C:\System Volume Information" /a

After taking ownership, reset the permissions as in step 4. Then verify the SYSTEM entry exists.

6. Delete and Recreate Shadow Copy Storage

If permissions are correct but the error persists, the shadow copy storage may be corrupted. Deleting the storage removes all existing shadow copies and system restore points. This is destructive to the restore points, so do this only after confirming that you do not need any previous versions from this drive.

To delete the storage, run in an elevated Command Prompt:

vssadmin delete shadowstorage /for=C: /on=C:

This deletes the shadow copy storage for the C: drive. After deletion, recreate it with a default size:

vssadmin resize shadowstorage /for=C: /on=C: /maxsize=10%

This sets the maximum storage to 10% of the drive. Adjust the percentage as needed. Then create a new shadow copy manually to test:

vssadmin create shadow /for=C:

If the creation succeeds, the error is resolved. If it still fails with 0x80070005, continue.

7. Check Disk Space

Insufficient disk space can cause VSS to fail, but it usually produces a different error (0x8004231F). However, if the drive is completely full, access checks can fail. Check free space on the drive. If it is below 1 GB, free up space and try again.

8. System File Checker and DISM

Corrupted system files can break VSS. Run the System File Checker and then DISM to repair the Windows image. These commands do not delete personal data. Run them in an elevated Command Prompt:

sfc /scannow

After that completes, run:

dism /online /cleanup-image /restorehealth

Reboot and test.

9. Last Resort: Reinstall Windows

If all else fails, a repair install (in-place upgrade) or a clean install may be necessary. A repair install keeps your files and applications but reinstalls Windows. A clean install erases everything. Before doing either, back up your data. This is the most destructive option and should only be attempted after exhausting the above.

What People Get Wrong About This Error

The most common mistake is treating 0x80070005 as a simple file permission issue. Users try to take ownership of the file or folder they are trying to access, or they grant full control to their user account. That does nothing because the error is not about the user’s access to the file; it is about the VSS service’s access to the shadow copy infrastructure. The service runs as Local System, and the permission that matters is on the System Volume Information folder and the service’s own logon account.

Another common misdiagnosis is assuming the disk is failing. The error code is an access-denied code, not an I/O error. If the disk were failing, you would see other errors like 0x80070003 (file not found) or 0x80042302 (timeout). The natural mistake is understandable because VSS errors often appear alongside disk-related warnings in the event log, but the actual error is a permissions failure.

Finally, some users immediately try to disable UAC or run everything as administrator. That does not help because the service runs in the background and UAC does not affect service permissions. The fix is to correct the service account or the ACL on the storage folder.

FAQ

Why do I get 0x80070005 when accessing Previous Versions?

The Previous Versions feature relies on the Volume Shadow Copy Service. The error indicates that the service account lacks permission to read the shadow copy storage. Check the service logon accounts and the System Volume Information folder permissions as described above.

Can I fix 0x80070005 by taking ownership of the file?

No. The error is not about the file’s ACL. It is about the VSS service’s access to the shadow copy infrastructure. Taking ownership of the file or folder you are trying to access will not help. Focus on the service accounts and the System Volume Information folder.

Will deleting shadow copy storage erase my restore points?

Yes. Deleting the shadow copy storage removes all existing shadow copies and system restore points for that drive. Only do this if you do not need any previous versions or restore points, or if you have backed up your data.

How do I check if my VSS writers are healthy?

Open an elevated Command Prompt and run vssadmin list writers. Look for the state column; it should say “Stable” for all writers. If any writer shows an error, restart the associated service or the VSS service itself.

What does the error 0x80070005 mean in plain English?

It means “Access Denied.” The process that is trying to perform an operation does not have the necessary permission. In the context of shadow copies, it is the VSS service that is being denied, not your user account.