How to fix Error 385 on Windows 11

by

Troubleshooting Guide: Error 385 – “The Virtualization Operation Is Not Allowed on the File in Its Current State”

Why This Error Happens

This error occurs when Windows’ file virtualization layer (used for UAC compatibility and legacy app support) attempts to redirect or copy a file that is currently locked, in use by another process, or excluded from virtualization by policy. It commonly happens when an application tries to write to a protected directory (like Program Files) while the file is open elsewhere, has incorrect NTFS permissions, or resides on a volume where virtualization has been disabled. Corrupted file system metadata or a disabled Windows Application Compatibility service can also trigger this behavior.

Step-by-Step Resolution Guide

  1. Check if the file is locked by another process:
  • Open Task Manager (Ctrl+Shift+Esc) → Details tab.
  • Close any application that might have the file open, or use a tool like Process Explorer to find and terminate the locking handle.
  1. Verify UAC Virtualization is enabled for the app:
  • Right-click the application’s .exe → Properties → Compatibility tab.
  • Ensure “Run this program as an administrator” is unchecked if you want virtualization to apply (virtualization only works for non-elevated, non-admin apps).
  1. Check and repair NTFS permissions:
  • Navigate to the folder containing the file (e.g., C:\Program Files\YourApp\).
  • Right-click → Properties → Security tab → Advanced.
  • Ensure the Users group has “Modify” or “Write” permissions, or reset permissions to inherit from the parent object.
  1. Restart the Application Information service:
  • Press Win + R, type services.msc, press Enter.
  • Locate Application Information, right-click → Restart.
  1. Run System File Checker and DISM:
  • Open Command Prompt (Admin) and run:

    sfc /scannow
    DISM /Online /Cleanup-Image /RestoreHealth
  • Restart your PC after completion.

Alternative or Verification Steps

  • Verify the fix: Try the original file operation again (save, copy, or install) and confirm Error 385 no longer appears in Event Viewer under Windows Logs → Application.
  • Alternative solution: If virtualization isn’t required, disable it entirely via Local Group Policy Editor (gpedit.msc → Computer Configuration → Windows Settings → Security Settings → Local Policies → Security Options → “User Account Control: Virtualize file and registry write failures to per-user locations” → set to Disabled), then retry the operation with proper admin rights instead.