How to fix Error 795 on Windows 11

by

Windows Error 795: Volume Corruption Log Internally Corrupted

Why This Error Happens

Error 795 occurs when NTFS’s self-healing mechanism detects that one of its internal volume corruption logs—used to track file system inconsistencies—has itself become corrupted, often due to unexpected power loss, improper shutdown, storage hardware faults, or disk sector errors. Since the log responsible for recording detected corruptions is unreliable, Windows cannot guarantee that previously flagged (or new) corruptions are being tracked correctly. As a result, the operating system flags the volume for a full scan to rebuild the log and verify actual disk integrity.

Step-by-Step Resolution Guide

  1. Identify the affected volume by opening Event Viewer (eventvwr.msc), navigating to Windows Logs > System, and locating Event ID 795 to note which drive letter is referenced.

  2. Run CHKDSK with repair flags on the affected volume. Open Command Prompt as Administrator and run:

   chkdsk C: /f /r /x

Replace C: with the affected drive letter. If it’s the system drive, you’ll be prompted to schedule the scan on next reboot—type Y and restart.

  1. Manually trigger NTFS self-healing verification using the built-in repair tool by running:
   fsutil repair initiate C: 0x01

This forces Windows to rebuild the corruption log and re-verify the volume without a full offline scan.

  1. Check the repair status afterward with:
   fsutil repair query C:

This confirms whether self-healing completed successfully and whether further action is needed.

  1. Update storage drivers and firmware via Device Manager or the manufacturer’s utility, since faulty SSD/HDD firmware can cause recurring log corruption even after a successful CHKDSK pass.

Alternative or Verification Steps

  • After the scan completes, re-check Event Viewer > Windows Logs > System for a follow-up Event ID (like 796 or 140) confirming successful volume repair with no further corruption detected.
  • If Error 795 recurs shortly after repair, run wmic diskdrive get status or use the manufacturer’s disk diagnostic tool (e.g., CrystalDiskInfo) to rule out failing hardware as the root cause.