| Previous | Next |
| STATUS_CLOUD_FILE_METADATA_TOO_LARGE | STATUS_NOT_A_CLOUD_FILE |
STATUS_CLOUD_FILE_PROPERTY_VERSION_NOT_SUPPORTED
The cloud property store format is incompatible
Cloud Files providers attach platform and provider metadata to placeholders under a registered sync root. This status means the property representation presented to the operation has a version outside the supported contract. The placeholder can still be recognizable as a cloud file while one property block cannot be interpreted.
A version mismatch commonly points to provider and operating-system skew, an incomplete rollback, or metadata restored from a newer implementation. Rewriting the version field alone is unsafe because the payload layout and semantics may also differ. The provider should migrate metadata through a documented upgrade path or recreate it from its authoritative cloud state.
What to inspect
- Record OS build, Cloud Files platform version, provider version, sync-root ID, and property version.
- Check upgrade and rollback history for a provider that previously wrote newer metadata.
- Compare a newly created placeholder from the current provider with the affected item.
- Use provider-supported migration or metadata regeneration rather than patching the version bytes.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Cloud Files API portal
- Microsoft: Cloud Filter API reference
- Microsoft sample: Cloud Mirror
Looking for a different code? Search another status or error code.