What does Windows error code 369 (ERROR_FILE_SYSTEM_VIRTUALIZATION_UNAVAILABLE) mean?

 
Could be also:
ConstantTypeOS
CRYPTO_LIBRARY_INTERNAL_ERRORBugCheck CodeWindows
Previous Next
ERROR_STORAGE_LOST_DATA_PERSISTENCE ERROR_FILE_SYSTEM_VIRTUALIZATION_METADATA_CORRUPT

ERROR_FILE_SYSTEM_VIRTUALIZATION_UNAVAILABLE

The projected namespace provider is not available to service the request

Projected File System exposes files and directories from a backing store through a user-mode provider. Directory enumeration, placeholder creation, and file-data recall can require provider callbacks. This status means the virtualization mechanism exists, but the provider or its active virtualization instance cannot currently answer the operation.

Check whether the provider process is running, the ProjFS optional component is enabled, and PrjStartVirtualizing completed for the correct virtualization root. A temporary shutdown, crash, upgrade, or disconnect from the backing store can make projected entries unavailable even though cached local files remain readable. Distinguish provider availability from network reachability and from ordinary access-control failures.

What to inspect

  • Confirm the provider process and virtualization instance are active.
  • Check provider logs for callback or backing-store failures.
  • Retry only after the provider lifecycle has returned to runtime state.

References


Looking for a different code? Search another status or error code.