How to fix Error 372 on Windows 11

by

Windows 11 Troubleshooting Guide: Error 372 – Unknown File System Virtualization Provider

Why This Error Happens

Error 372, with the message “The provider that supports file system virtualization is unknown,” typically occurs when the Windows Projected File System (ProjFS) optional feature is either disabled or not properly registered with the OS. This component is essential for applications that use virtualized file systems, such as Git (for large repositories), OneDrive Files On-Demand, or certain developer tools like WSL and Docker. The error surfaces when the associated filter driver (prjflt.sys) fails to load, is corrupted, or the feature was never enabled during Windows setup.

Step-by-Step Resolution Guide

  1. Enable the Windows Projected File System Feature
  • Press Win + R, type optionalfeatures, and hit Enter.
  • Scroll down to find Windows Projected File System.
  • Ensure the checkbox is ticked. If it’s already checked, uncheck it, click OK, restart your PC, then re-enable it and restart again.
  1. Enable via PowerShell (Alternative Method)
  • Open PowerShell as Administrator.
  • Run the following command:
    powershell
    Enable-WindowsOptionalFeature -Online -FeatureName Client-ProjFS -NoRestart
  • Restart your computer once the command completes successfully.
  1. Verify the ProjFS Driver Service is Running
  • Open the Services app (services.msc).
  • Locate Windows Projected File System Mini Filter Driver.
  • Ensure the Startup type is set to System or Automatic and the status shows Running (if applicable to your system configuration).
  1. Check and Repair System File Corruption
  • Open Command Prompt as Administrator.
  • Run the System File Checker to repair corrupted system files:
    cmd
    sfc /scannow
  • Follow up with a DISM health check:
    cmd
    DISM /Online /Cleanup-Image /RestoreHealth
  • Restart your PC after both commands complete.
  1. Update Windows 11
  • Navigate to Settings > Windows Update.
  • Install any pending updates, as Microsoft frequently patches driver registration issues related to ProjFS in cumulative updates.

Alternative or Verification Steps

  • Verify the fix: Open PowerShell and run Get-WindowsOptionalFeature -Online -FeatureName Client-ProjFS. The State should read Enabled. Then, relaunch the application that triggered Error 372 (e.g., Git or Docker) to confirm the virtualization process completes without errors.
  • Alternative fix: If the error persists, try re-registering the driver manually via an elevated Command Prompt using fltmc load prjflt, then reboot the system.