How to fix Error 796 on Windows 11

by

Windows 11 Error 796: Volume Corruption Log Unavailable

Why This Error Happens

Error 796 occurs when the NTFS file system cannot access one of the volume’s corruption tracking logs, typically because the log file itself has become corrupted, is locked by another process, or the underlying disk sectors hosting the log are damaged. This often surfaces during CHKDSK operations or when the Volume Corruption Log Service attempts to record or read integrity data on a volume that hasn’t been properly maintained. In many cases, this is triggered by an improper shutdown, a failing drive, or file system metadata corruption that prevents Windows from managing self-healing NTFS logs correctly.

Step-by-Step Resolution Guide

  1. Run CHKDSK with repair flags — Open Command Prompt as Administrator and run:
   chkdsk C: /f /r /x

Replace C: with the affected drive letter. If the volume is in use, confirm the scheduled scan on next restart and reboot the system.

  1. Check the NTFS self-healing status — Verify that Windows’ automatic file system repair feature is enabled by running:
   fsutil repair query C:

If it returns disabled, enable it with:

   fsutil repair set C: 1
  1. Inspect disk health with WMIC/PowerShell — Run the following in an elevated PowerShell window to check for underlying hardware issues:
   Get-PhysicalDisk | Select-Object FriendlyName, HealthStatus, OperationalStatus

If HealthStatus shows “Warning” or “Unhealthy,” the log corruption may be a symptom of failing hardware.

  1. Manually clear corrupted log flags — If CHKDSK cannot resolve the issue, force a full dismount and remount of the volume metadata:
   fsutil resource setautoreset true C:\

This resets the resource manager transaction logs associated with the volume, which can clear a stuck corruption log reference.

  1. Review Event Viewer logs — Open Event Viewer (eventvwr.msc), navigate to Windows Logs > System, and filter for Event ID 796. Cross-reference timestamps with any recent disk or driver-related events to confirm whether the issue is isolated to the file system or linked to a hardware fault.

Alternative or Verification Steps

  • Verify the fix: Re-run chkdsk C: /scan after completing the steps above. If no errors are reported and Event Viewer shows no new Event ID 796 entries after a few reboots, the log has been successfully repaired.
  • Alternative solution: If the error persists, back up your data immediately and consider reformatting the volume, as persistent corruption log failures despite repair attempts often indicate an underlying physical disk problem that software fixes cannot resolve.