| Previous | Next |
| STATUS_FILE_SYSTEM_VIRTUALIZATION_PROVIDER_UNKNOWN | STATUS_CLOUD_FILE_SYNC_ROOT_METADATA_CORRUPT |
STATUS_FILE_SYSTEM_VIRTUALIZATION_INVALID_OPERATION
The item state does not permit this virtualization transition
Projected items move through states controlled by both ordinary file-system activity and provider operations. An update that is valid for a placeholder may be invalid after the item becomes a full local file, is modified, renamed, opened incompatibly, or otherwise leaves the state expected by the provider. This status rejects the transition rather than applying ambiguous metadata changes.
The provider should query current on-disk state immediately before issuing the operation and handle races with applications. Retrying the same stale command is unlikely to help. Diagnostics should relate the provider command to file identity, notification history, open handles, and the current placeholder or tombstone state.
What to inspect
- Record file identity, attributes, reparse data, provider metadata, open handles, and the requested virtualization operation.
- Check for a rename, local modification, deletion, or provider callback that raced with the command.
- Refresh item state and reconcile with the backing store before deciding whether to retry.
- Do not force metadata changes that would overwrite local user data or lose provider identity.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Windows Projected File System
- Microsoft sample: projected file system provider
- Microsoft Windows classic sample: ProjFS provider code
Looking for a different code? Search another status or error code.