How to Fix VSS Timeout Error VSS_E_FLUSH_WRITES_TIMEOUT
VSS_E_FLUSH_WRITES_TIMEOUT is a VSS timeout error and may be reported by your backup software using the code 0x80042313 when using the writer “Microsoft Hyper-V VSS Writer” or when backing up VMware.
However, this VSS timeout error may occur on hosts without Hyper-V as well.
Try the following options to fix VSS_E_FLUSH_WRITES_TIMEOUT:
Repair Strategy #1
Using the registry editor, "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\SPP" - If need be, create a new registry value of type DWORD with name "CreateTimeout" - Change value to 12000000(2*10*60*1000 = 20 mins) in decimal
The above should increase the VSS timeout to 20 mins
Repair Strategy #2
Check using VSSUIRUN.EXE or vssadmin list shadows whether there are any VSS shadows on the system.
If you aren’t using Windows Server Backup or some other backup software that relies on VSS shadows, go ahead and delete all of them using
vssadmin delete shadows /all
Repair Strategy #3
Check fragmentation levels, free RAM (1GB minimum), and free disk space (at least 10GB).
If you are backing up virtual machines, check inside the VMs in the Event Viewer for more error details.
Increase RAM and free disk space and test again.
Repair Strategy #4
Several types of applications make VSS timeout errors more likely: Some antivirus software may create an incompatibility. Try uninstalling it (not just switching off real-time scanning). In addition, make sure no defragmentation, antivirus scans, or any other heavy hard drive activity is taking place when initiating the backup.
Recommended Step In Addition to Above Steps
Use VssDiag from our BackupChain website //backupchain.com/VssDiag.html and run it on the host to gather additional info. If you are backing up VMs, run it inside the affected VM, too.
VssDiag should be able to find errors leading to VSS_E_FLUSH_WRITES_TIMEOUT.
Backup Software Overview
BackupChain Server Backup SoftwareDownload BackupChain
Cloud Backup
Backup VMware Workstation
Backup FTP
Backup VirtualBox
Backup File Server
Hyper-V Backup
Backup Hyper-VPopular
- Hyper-V Links, Guides, Tutorials & Comparisons
- Veeam Alternative
- How to Back up Cluster Shared Volumes
- DriveMaker: Map FTP, SFTP, S3 Site to a Drive Letter (Freeware)
Resources
- Free Hyper-V Server
- Remote Desktop Services Blog
- SCDPM Blog
- SCOM Blog
- V4 Articles
- Knowledge Base
- FAQ
- Sitemap
- Backup Education
- Backup Sichern
- Hyper-V Scripts in PowerShell
- FastNeuron
- BackupChain (Greek)
- BackupChain (Deutsch)
- BackupChain (Spanish)
- BackupChain (French)
- BackupChain (Dutch)
- BackupChain (Italian)
Backup Software List
BackupChain
Veeam
Unitrends
Symantec Backup Exec
BackupAssist
Acronis
Zetta
Altaro
Windows Server Backup
Microsoft DPM
Ahsay
CommVault
IBM
Other Backup How-To Guides
- Get All VHDX for All VMs with this PowerShell Script
- Destination Path Too Long Fixed: Freeware Tool Deletes Long Path
- 0x800705aa How to Fix ERROR NO SYSTEM RESOURCES
- List of Effective Hyper-V Backup Strategies
- Hyper-V, VMware, VirtualBox Feature Comparison
- Resolving VSS_WS_FAILED_AT_FREEZE Backup Errors
- How to fix: Selected writer ‘Microsoft Hyper-V VSS Writer’ is in failed state, VSS_WS_FAILED_AT_PREPARE_SNAPSHOT
- Granular Backup Software for Hyper-V
- How to fix ‘Microsoft Hyper-V VSS Writer’ is in failed state, Writer Failure code: 0x800423f3
- KB 2885541 Packet sniffing tool does not sniff all network traffic through port mirroring on Windows 2012 Server VMs
- Windows Server 2022 ISO Final Release Free Download
- What is Deduplication?
- Guidelines for Installing Microsoft Exchange 2013 in Hyper-V
- File Server Backup Software for Windows
- How to Fix VolSnap 28 Error “The shadow copy could not be created…
- What is Hyper-V and What Operating Systems are Supported?
- How to Fix VolSnap Error ..a critical control file could not be opened
- Windows 11 Hyper-V Backup, Step-by-Step
- How to Fix: Folder name too long to delete
- Reboot a virtual machine in Hyper-V from the command line