How to fix Error 596 on Windows 11

by

Troubleshooting Guide: Delayed Write Failed (Error 596)

Why This Error Happens

Error 596, “Delayed Write Failed,” occurs when Windows attempts to flush cached data from RAM to a physical storage device (local disk, USB drive, or network share) but the write operation fails or times out. This is typically caused by a failing hard drive/SSD, a corrupted file system, an unstable network connection to a mapped drive, or a faulty USB cable/port causing intermittent disconnects. Since Windows uses write-back caching for performance, the data sitting in memory is lost permanently once the write operation is abandoned.

Step-by-Step Resolution Guide

  1. Check the Physical Connection (For External/USB Drives)
    Unplug and reconnect the USB drive using a different port (preferably a rear USB port on desktops, not a front panel or hub). Try a different USB cable, as faulty cables are a common cause of this error on external drives.

  2. Run CHKDSK to Scan for Disk Errors
    Open Windows Terminal (Admin) and run the following command, replacing X: with the affected drive letter:

   chkdsk X: /f /r

If it is the system drive (C:), Windows will prompt you to schedule the scan on the next restart. Type Y and reboot.

  1. Verify Network Stability (For Mapped Network Drives)
    If the error occurs on a network share, open Settings > Network & Internet > Advanced network settings and check the adapter status. Additionally, disable “Power Management” for the network adapter:
  • Go to Device Manager > Network Adapters.
  • Right-click your adapter > Properties > Power Management.
  • Uncheck “Allow the computer to turn off this device to save power.”

  1. Update or Roll Back Storage Drivers
    Navigate to Device Manager > Disk drives. Right-click the affected drive and select Update driver. If the error started immediately after a recent update, select Properties > Driver tab > Roll Back Driver instead.

  2. Check Drive Health via PowerShell
    Run PowerShell as Administrator and execute:

   Get-PhysicalDisk | Select FriendlyName, MediaType, HealthStatus

If the HealthStatus returns “Warning” or “Unhealthy,” the physical disk requires backup and replacement immediately.

Alternative or Verification Steps

  • Verification: After applying the fixes, copy a large file (1GB+) to the previously affected drive/share and monitor Event Viewer (Windows Logs > System) to ensure no new Event ID 26 or 50 errors appear.
  • Alternative Fix: If the error persists on an external drive, format the drive using NTFS (rather than exFAT) via This PC > Right-click Drive > Format, as exFAT is generally more susceptible to sudden disconnection corruption than NTFS.