| Previous | Next |
| ERROR_CLOUD_FILE_INVALID_REQUEST | ERROR_CLOUD_FILE_CONNECTED_PROVIDER_ONLY |
ERROR_CLOUD_FILE_READ_ONLY_VOLUME
CFAPI cannot persist the requested state on a read-only volume
ERROR_CLOUD_FILE_READ_ONLY_VOLUME is returned when an operation must modify placeholder data, reparse metadata, hydration ranges, pin state, in-sync state, or sync-root registration on a volume that is mounted read-only. Reading an already hydrated file may still be possible, but state-changing cloud operations require filesystem writes.
Confirm the volume attributes and the reason it is read-only, such as snapshot media, policy, filesystem damage protection, or a read-only mount. Also verify that the path was not redirected to a read-only clone while the provider still believes it is the registered root. The remedy is to use a writable supported location or restore the volume to a healthy writable state; provider authentication and remote connectivity do not change local volume writability.
What to inspect
- Check the actual volume containing the placeholder, not only the apparent path.
- Identify whether the failing operation writes content, metadata, or sync-root state.
- Move or recreate the sync root on a writable supported filesystem when required.
References
- Microsoft: registering a sync root at a filesystem path
- Microsoft: placeholder updates modify local metadata
- Microsoft: pin-state changes require access to the placeholder
Looking for a different code? Search another status or error code.