Windows Server 2022 — Windows Server Backup Fails with VSS 0x80780166 — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Quick Checks
3. Deep Diagnosis
4. Primary Fix
5. Verification
6. Prevention & Hardening

Symptom & Impact

Scheduled backups fail with VSS errors, leaving restore points stale and recovery objectives at risk. Failures often occur under I/O pressure or writer instability. Organizations lose confidence in backup integrity until root cause is removed.

Quick Checks

Review VSS writer states, shadow storage allocation, and backup target accessibility.

vssadmin list writers
vssadmin list shadowstorage
wbadmin get status
Get-Volume

Deep Diagnosis

Inspect backup operational logs and isolate writers stuck in failed or timed-out state.

Get-WinEvent -LogName 'Microsoft-Windows-Backup' -MaxEvents 120
Get-WinEvent -LogName Application -MaxEvents 120 | Where-Object {$_.ProviderName -match 'VSS|VolSnap'}
fltmc volumes

Primary Fix

Restart dependent services, resize shadow storage where needed, and rerun backup with clean writer state.

Restart-Service VSS
Restart-Service swprv
vssadmin resize shadowstorage /for=C: /on=C: /maxsize=20%
wbadmin start backup -backupTarget:F: -include:C: -allCritical -quiet

Verification

A full backup job should complete and VSS writers must remain Stable with no error condition.

wbadmin get versions
vssadmin list writers
Get-WinEvent -LogName 'Microsoft-Windows-Backup' -MaxEvents 30

Prevention & Hardening

Monitor writer health before schedules and reserve adequate shadow storage on critical volumes.

schtasks /Query /TN 'MicrosoftWindowsWindowsBackup*'
vssadmin list shadowstorage
Get-Counter 'LogicalDisk(C:)% Free Space'