How to fix Error 472 on Windows 11

by

Windows 11 Storage Stack Error 472 (STATUSACCESSDENIED)

Why This Error Happens

This error occurs when the Windows storage stack (Partmgr, Volsnap, or the disk class driver) attempts an I/O operation—such as a volume mount, snapshot creation, or write—but is blocked by insufficient permissions at the kernel or filesystem level. It commonly results from corrupted NTFS security descriptors on the volume, a third-party disk encryption or antivirus filter driver intercepting the I/O request, or Group Policy/Local Security Policy restrictions on removable/fixed storage access. In some cases, it also occurs when the Volume Shadow Copy Service (VSS) cannot access a volume due to a locked or in-use handle.

Step-by-Step Resolution Guide

  1. Check Event Viewer for context
    Open eventvwr.msc → navigate to Windows Logs > System, filter by Event ID 472, and note the associated driver (e.g., disk, volsnap, partmgr) and the disk/volume GUID referenced in the details tab.

  2. Verify and repair volume permissions
    Open an elevated Command Prompt and run:

   icacls D:\ /reset /T /C

Replace D:\ with the affected drive. This resets NTFS ACLs to inherited defaults, resolving access denials caused by corrupted security descriptors.

  1. Run CHKDSK and SFC to rule out corruption
   chkdsk D: /f /r
   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

Reboot after CHKDSK schedules the repair on next restart.

  1. Check Local Security Policy for storage restrictions
    Open secpol.msc → Local Policies > Security Options → look for “Devices: Restrict… floppy access” or similar storage lockdown policies. Also check gpedit.msc under Computer Configuration > Administrative Templates > System > Removable Storage Access for deny-write/read rules that may apply to fixed disks in managed environments.

  2. Identify and temporarily disable filter drivers
    Run fltmc filters in an elevated prompt to list active filesystem filter drivers. Third-party antivirus, encryption (e.g., BitLocker-To-Go conflicts, VeraCrypt), or backup software filters are common culprits. Temporarily disable third-party AV/encryption software and retest the storage operation.

Alternative or Verification Steps

  • Verify the fix: Reproduce the original action (mount, snapshot, write) and confirm no Event ID 472 appears in Event Viewer within 10 minutes of the operation.
  • Alternative fix: If the error persists, boot into Safe Mode and repeat the failing operation—if it succeeds, a third-party driver/service is the root cause; use msconfig or Autoruns to isolate and permanently disable the conflicting service.