| Previous | Next |
| ERROR_CLOUD_FILE_PROPERTY_BLOB_TOO_LARGE | ERROR_CHILD_PROCESS_BLOCKED |
ERROR_CLOUD_FILE_PROPERTY_BLOB_CHECKSUM_MISMATCH
The on-disk property bytes do not match their recorded checksum
ERROR_CLOUD_FILE_PROPERTY_BLOB_CHECKSUM_MISMATCH reports an integrity failure for a cloud-file property blob. This is not a remote content hash mismatch and does not by itself prove that the user file data is damaged. It means the local property-store representation cannot be accepted as the same bytes that were originally recorded.
Determine whether the failure is isolated to one placeholder, one volume, or every object written by a particular provider version. Correlate it with abrupt shutdowns, disk or filesystem errors, and recent property-format changes. The safe recovery is to reconstruct the property from authoritative provider state or recreate the placeholder using supported CFAPI paths. Recomputing and overwriting an undocumented checksum field directly would hide the symptom without proving the property contents are valid.
What to inspect
- Correlate the first failure with provider upgrades, crashes, and filesystem events.
- Verify remote identity before regenerating the local property data.
- Test whether newly created placeholders use a healthy property format.
References
- Microsoft: placeholder property-store size and state
- Microsoft: supported placeholder update operation
- Microsoft: reverting a placeholder to a regular file
Looking for a different code? Search another status or error code.