Hello Friends, this post containing information about backup failed with error message The system writer is not found in the backup. Put a lot efforts to resolve the issue while the resolution was very simple. There are other writers also associated with different-2 services. If we talk about the system writer, it is associated with “Cryptographic Services” service.
How To Fix System Writer Error
Issue: While running system state backup of Windows server 2012 server then backup failed having error The system writer is not found in the backup.
Error: Once system state backup failed, just checked the error messages which was like “The system writer is not found in the backup“. Thereafter opened event viewer and found below logs inside Application Logs.
a) The log’s event id was 512 with source “CAPI2”. The entire log was look like below:
The Cryptographic Services service failed to initialize the VSS backup “System Writer” object.
Could not open the EventSystem service for query.
Access is denied.
b) Another error log was showing with event id 517 and source as “backup”.
Error Message: The backup operation that started at ‘xxxx-xx-xxxxx:xx:xx.xxxxxxxx0xxxxx’ has failed with following error code ‘0x80780102‘ (The system writer is not found in the backup.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
Cause: The issue is related to system writer.
To check the presence and status of “system writer”, run “vssadmin list writers” command at command prompt with admin privileges.
Resolution: Firstly, opened services and restart “Cryptographic Services” service. But it didn’t resolve the issue. Then stop / start this service through command line and the writer “System Writer” starts showing in “vssadmin list writers” command output. Give a try to do this from command prompt and sort out the issue.
net stop cryptsvc
net start cryptsvc
- Few Useful Commands
- GPO To Control Login To Windows 10 With PIN
- Turn Off Picture Password
- Laptop Lid Closing Action
- Trust relationship between this workstation and primary domain failed