How to Fix VSS Error 0x80070005 Access Denied

Volume Shadow Copy (VSS) error 0x80070005, which translates to “Access Denied,” typically appears when Windows system restore, backup tools, or third-party software try to create a shadow copy but lack the necessary permissions. This guide walks you through the most effective fixes, from checking service permissions to adjusting registry keys, so you can restore your backup functionality.

What You’ll Need

• Administrator account access on the affected Windows PC
• Knowledge of your Windows version (Windows 10, 11, Server, etc.)
• Optional: a backup of your registry before making changes (use File > Export in regedit)

Step-by-Step

1. Run the Affected Tool as Administrator

Often, the error occurs because the backup or restore utility isn’t running with elevated privileges. Right-click the application (e.g., Command Prompt, your backup software) and select “Run as administrator.” If this resolves the issue, you can set the program to always run as administrator via its Properties > Compatibility settings.

2. Verify the Volume Shadow Copy Service is Running

1. Press Win + R, type services.msc, and press Enter.
2. Scroll to Volume Shadow Copy (or “VSS”).
3. Double-click it. Ensure the Startup type is Manual (default) and the Service status is Running. If not, click Start.
4. Also check the Microsoft Software Shadow Copy Provider service. Set its startup type to Manual and start it if it’s stopped.
5. Restart the service by right-clicking it and choosing Restart, then try your backup again.

3. Check the VSS Service Log On Account

In the same service properties window, go to the Log On tab. The service should log on as Local System Account. If it’s set to a specific user account, change it to Local System, apply, and restart the service.

4. Grant Permissions to the VSS Writers

Sometimes the error is specific to a VSS writer (like the SQL Server writer or Exchange writer).

1. Open an elevated Command Prompt (Run as administrator).
2. Type vssadmin list writers and press Enter.
3. Look for writers with a State of “Failed” or “Unknown”. Note the Writer Name.
4. For the affected writer, you may need to grant the SYSTEM account full control over the writer’s registry key. This is advanced; typically you’d locate the key under HKLM\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl and ensure the relevant user has 1 (allowed).

5. Modify the VssAccessControl Registry Key

This is a common fix for the 0x80070005 error, especially when using third-party backup tools.

1. Press Win + R, type regedit, and press Enter. Accept the UAC prompt.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl.
3. If the key doesn’t exist, right-click on VSS, select New > Key and name it VssAccessControl.
4. Inside that key, right-click and create a new DWORD (32-bit) Value.
5. Name it NT AUTHORITY\SYSTEM (if not already present) and set its value to 1.
6. Also add a DWORD for NT AUTHORITY\NETWORK SERVICE and NT AUTHORITY\LOCAL SERVICE with value 1 if they are missing.
7. Close regedit and restart your computer.

6. Reset the VSS Permissions via Command Line

If the registry edit doesn’t help, you can reset the VSS access control list using a script. This is a bit more technical but often resolves persistent issues.

1. Open Notepad as administrator.
2. Paste the following lines (this is a sample; ensure you understand it before running):
   sc stop vss
sc config vss start= disabled
sc config vss start= demand
sc start vss
   Save the file as reset_vss.bat.
3. Right-click the .bat file and select Run as administrator.
4. After it runs, restart your PC.

7. Check Disk for Errors

Sometimes a corrupted file system can trigger access denied errors. Run a disk check:

1. Open an elevated Command Prompt.
2. Type chkdsk C: /f /r and press Enter.
3. If prompted, type Y to schedule the check on reboot, then restart your PC.

8. Perform a Clean Boot

Third-party software (like security suites) can interfere with VSS. Perform a clean boot to isolate the cause:

1. Press Win + R, type msconfig, and press Enter.
2. Go to the Services tab, check Hide all Microsoft services, then click Disable all.
3. Go to the Startup tab and click Open Task Manager.
4. Disable all startup items, then restart. If the error disappears, re-enable services one by one to find the culprit.

Common Mistakes

• Editing the wrong registry key: Ensure you are in VssAccessControl, not the parent VSS key.
• Using a non-administrator command prompt: Many steps require elevated privileges; if you skip this, you’ll get the same error.
• Setting the VSS service to Automatic: The default is Manual; changing it to Automatic can cause other issues.
• Forgetting to restart after registry changes: Most registry edits require a reboot to take effect.

Tips

• Always back up your registry before making changes (right-click the key > Export).
• If you use third-party backup software, check its own logs for more specific error details.
• Keep Windows updated; Microsoft often patches VSS-related bugs.
• If you have a system restore point, try creating a new one after the fix to confirm it works.

Troubleshooting

If the error persists after all steps:

• Check the System Event Log: Open Event Viewer (eventvwr.msc), go to Windows Logs > System, and look for VSS or volsnap errors around the time of the failure. The details may point to a specific component.
• Use the VSS Troubleshooter: Windows has a built-in troubleshooter for System Restore and backup. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters, then run the System Restore or Backup and Restore troubleshooter.
• Check if the issue is with a specific shadow copy: Run vssadmin list shadows in an elevated command prompt. If there are old shadow copies, delete them with vssadmin delete shadows /for=C: /oldest (replace C: with your drive) and try again.
• Re-register VSS components: In an elevated command prompt, run:
  cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
vssvc /deregister
net start vss
net start swprv
  Then restart your PC.
• Consider system file corruption: Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an elevated command prompt.

Frequently Asked Questions

Why does 0x80070005 happen only during backup, not during normal use?

VSS requires specific permissions to access system files and registry hives. Backup software often runs under a different user context (like SYSTEM or a service account) that may not have the necessary rights, triggering the access denied error.

Can I fix this error without editing the registry?

Yes, sometimes simply running the backup tool as administrator or restarting the VSS service fixes it. The registry method is just one of several options.

Will this error affect my system’s performance?

No, the error itself doesn’t slow down your PC. It only prevents shadow copies from being created, which can affect system restore and backup features.

Is it safe to delete existing shadow copies?

Yes, deleting old shadow copies is safe, but you’ll lose the ability to restore to those older points. It’s a good idea to create a fresh restore point after fixing the issue.

Does this fix work on Windows Server?

Yes, the steps are similar for Windows Server, but you may need to adjust for your specific server roles (like Exchange or SQL Server) that have their own VSS writers.

What if the error appears when using System Restore?

Try the same steps, especially checking the VSS service and registry permissions. Also ensure that System Protection is enabled for the drive (System Properties > System Protection).

Related

• Fix Google Play Store Errors: Step-by-Step Guide
• Fix Overheating iPhone iOS 11: 12 Proven Ways
• ECG App on Apple Watch: Step-by-Step Guide