| Previous | Next |
| STATUS_FILE_SYSTEM_VIRTUALIZATION_METADATA_CORRUPT | STATUS_FILE_SYSTEM_VIRTUALIZATION_PROVIDER_UNKNOWN |
STATUS_FILE_SYSTEM_VIRTUALIZATION_BUSY
A conflicting virtualization operation is still active
This status represents transient contention in a virtualized file namespace. A provider callback, placeholder update, enumeration, hydration-like population, or root transition can hold state that prevents another operation from proceeding safely. It is not evidence that the backing data is missing or that the root metadata is corrupt.
Blind tight-loop retries can amplify the problem by increasing callback pressure and queue depth. The caller should retain the operation context, observe cancellation and timeout rules, and use bounded backoff where the API contract permits retry. Provider diagnostics should expose which callback or root operation remained outstanding.
What to inspect
- Record the operation, path, provider callback type, thread, cancellation state, and time spent outstanding.
- Inspect provider queues and long-running enumeration or data-supply callbacks.
- Check for recursive access where the provider touches its own virtualization root while servicing a callback.
- Use bounded retry with telemetry; do not delete placeholders to clear ordinary contention.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Windows Projected File System
- Microsoft: starting a ProjFS virtualization instance
- Microsoft sample: projected file system provider
Looking for a different code? Search another status or error code.