None of the above worked.
System Writer error
Hi. I have a server that is running windows Server 2016 standard edition and i'm having a problem with doing cloud backups and local automatic backups. Whenever a backup is trying to take place, the following error comes up "System state backup of component [System Protected Files;] failed". I have had a look at the VSS list and all the writers that are listed are in stable condition with no errors, it's only system writers that is not listed. I have done the following:
- Stop and start VSS service
- Reregister the VSS DLL files
- Restart the server numerous times
kindly advise on a solution to this problem.
Windows for business | Windows Server | Devices and deployment | Other
2 answers
Sort by: Most helpful
-
-
Q&A Assist2026-02-16T15:43:40.75+00:00 AI generated content. This question contains an answer created with AI from Q&A Assist. Learn moreTo resolve the issue of the missing System Writer in your VSS (Volume Shadow Copy Service) list, you can follow these steps:
- Check Registry Settings: Open the Registry Editor and navigate to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControlEnsure that the value forNT AUTHORITY\NETWORK SERVICE(REG_DWORD) is set to1. You may also want to check the entries for other services such asLOCAL SERVICEandNetworkServiceas indicated by event ID 8213. - Verify Permissions: Ensure that the process hosting the System Writer has sufficient access rights. It should be running under a local account such as Local System, Administrator, Network Service, or Local Service.
- Restart Services: After making changes, restart the following services:
- COM+ Event System
- Volume Shadow Copy
- Check VSS Writers: After performing the above steps, open an elevated command prompt and run the command
vssadmin list writersto verify that the System Writer is now listed.
If the System Writer still does not appear, you may need to investigate further by checking the Application event log for any related errors that could provide additional insights into the problem.
References:
- Check Registry Settings: Open the Registry Editor and navigate to the following key: