Windows Server Backup (Azure Backup) system state backup fails

Hello CJ Vallade | Second To None

Thank you for posting your query on Microsoft Q&A platform.

We are looking into your issue and will keep you posted updates.

Thanks,

Suchitra.

Hello @CJ Vallade | Second To None System State backups depend entirely on VSS. If any required writer (especially System Writer) is missing, failed, or timing out, Windows Server Backup reports a generic engine error instead of a detailed message.

Could you please verify below details and let us know the results?

1. Verify VSS writers: Run from an elevated command prompt and share us the output screenshot?

vssadmin list writers

2. Check Cryptographic Services permissions:

System Writer depends on Cryptographic Services. Incorrect permissions here cause silent failures.

Check Event Viewer:

• Application log
• Source: VSS
• Event ID: 8193 or 8213

If you see messages indicating insufficient permissions, this is a confirmed root cause.

3.Restart the following services and re‑check writers:

• Cryptographic Services
• Volume Shadow Copy
• Microsoft Software Shadow Copy Provider

Then re‑run:

vssadmin list writers

If System Writer returns to Stable, retry the backup.

4. Validate Windows Server Backup health, Even when installed, WSB can be corrupted.

Check:

Get-WindowsFeature Windows-Server-Backup

If already installed, remove and reinstall the feature and this does not delete backups.

5. Confirm scratch space & antivirus exclusions

System State backup requires free space on the OS volume, not just the backup target.

Microsoft requires:

• 5–10% free space on the volume hosting the scratch folder
• Antivirus must exclude:
  • MARS / WSB binaries
  • Scratch folder
  • cbengine.exe

SFC repairs system files, but does not fix VSS writer registration, Cryptographic Services ACLs, or COM+ metadata, which are the actual dependencies for System State backups.

Thanks,

Suchitra.

Hello @CJ Vallade | Second To None

We haven't heard back from you. Could you please let us know if the suggested resolution helped/ addressed your concern.

If the resolution did not help, feel free to share more details about the challenge you’re still facing. Any additional information such as your current issue or specific errors will help us perform a deeper analysis and provide more targeted guidance.

If the issue persists, could you share the following?

1. Output of “vssadmin list writers” (just copy/paste the text)
2. Results of Get-WindowsFeature for Windows-Server-Backup
3. Any VSS-related Event IDs (8193/8213) in the Application log
4. Free space on your OS volume (especially where the scratch folder lives)
5. Version of the MARS agent you’re running

Thanks,

Suchitra.