Windows Backup Server execution failed (0x80080005) error [FIX]
The Windows Backup Server execution failed (0x80080005) error is one that can pop up for some users attempting to back up data or set up restore points. The full error message states: The backup application could not start due to an internal error. Server execution failed (0x80080005). As a consequence, users can’t back up the required data or set up a restore point.
Why the backup application won’t start due to the internal error code 0x80080005? Fix this by restarting the Volume Shadow Copy Service which deals with the system backup. This procedure should bring full control to your administrative account and resolve the error. You can also take the ownership manually or clear the System Volume Information folder.
Check the detailed instructions below.
What Does Server Execution Failed Mean?
The Server execution failed error message means the Windows Backup service isn’t starting. Windows Backup relies on Volume Shadow Copy, and the 0x80080005 error can often be due to a PC not having full control of the System Information Volume folder.
- Restart the Volume Shadow Copy Service
- Take Ownership of the System Volume Information Folder
- Clear the System Volume Information Folder
1. Restart the Volume Shadow Copy Service
- First, try restarting the Volume Shadow Copy service to make sure it’s running. To do that, open Cortana with the Windows key + S hotkey.
- Input ‘Command Prompt’ in the search box.
- Right-click Command Prompt to select its Run as administrator setting.
- Then enter ‘net stop sdrsvc’ in the Prompt’s window, as shown directly below, and press Return.
- To restart Volume Shadow Copy service, input ‘net start sdrsvc’ and press Enter.
2. Take Ownership of the System Volume Information Folder
Some users might need to take ownership of the System Volume Information folder to fix the Server execution failed issue. That will ensure their user groups have full access rights for that folder.
This is how admin users can take ownership of the System Volume Information folder:
- First, users need to log in to an admin account. Users can activate a built-in admin account to log in to by entering ‘net user administrator /active:yes’ in the Command Prompt or users can convert a standard current account to an admin one with the Change account type option.
- Open the Run accessory.
- Enter ‘cmd’ in Run’s text box.
- Press the Ctrl + Shift + Enter hotkey to open an elevated Command Prompt.
- Input ‘net stop SDRSVC’ and press Return to stop the Volume Shadow Copy service.
- Then enter ‘takeown /F “C:\System Volume Information” /A’ in the Prompt, and press the Return key. The Prompt window should then say, “System Volume Information now owned by the administrator’s group.”
- Restart the System Volume Information service with the ‘net start SDRSVC’ command.
- Exit the Command Prompt, and then restart the desktop or laptop.
- Thereafter, try to start Windows Backup within an admin account.
3. Clear the System Volume Information Folder
As an additional extra to the above fix, users can also erase System volume Information files to clear out that folder after taking ownership.
Users can do that by entering ‘del “C:\System Volume Information\WindowsImageBackup\Catalog”’ in the Command Prompt as shown in the snapshot directly below. Stop the Volume Information Service with the ‘net stop SDRSVC’ command before clearing the folder. Then restart the service afterward.
Those are some of the more probable resolutions for the Server execution failed (0x80080005) error. Taking ownership of the System Volume Information folder is the most widely confirmed resolution for kick-starting the Windows Backup service. However, the other resolutions might also fix the issue for some users.
RELATED ARTICLES TO CHECK OUT:
All the Windows laptops come with the hotkeys to increase and decrease the display brightness. If that does not work, you can use the brightness […]
A number of VMware users have reported encountering the error message Your system does not support the requested display settings when trying to connect to […]