| Previous | Next |
| ERROR_INVALID_FLAGS | ERROR_FILE_INVALID |
ERROR_UNRECOGNIZED_VOLUME
the volume does not contain a recognized file system. please make sure that all required file system drivers are loaded and that the volume is not corrupted.
ERROR_UNRECOGNIZED_VOLUME means that windows detected a volume but could not mount it as a filesystem it recognizes. In this case, the decisive context is opening a raw, removable, virtual, encrypted, or newly attached volume, together with disk and volume identifiers, partition layout, filesystem probe results, and sector size.
Where the result appears
- opening a raw, removable, virtual, encrypted, or newly attached volume.
- mounting media formatted for another operating system or appliance.
- accessing a damaged partition or filesystem boot sector.
- bringing online storage that depends on a filesystem or encryption driver.
Typical causes
- the filesystem is unsupported or its driver is missing/disabled.
- the media is intentionally unformatted or contains a non-filesystem payload.
- partition metadata or filesystem structures are damaged.
- the volume is encrypted, locked, incomplete, or presented through the wrong storage layer.
Evidence to collect
- disk and volume identifiers, partition layout, filesystem probe results, and sector size.
- whether the media is expected to be NTFS, ReFS, FAT/exFAT, optical, encrypted, or vendor-specific.
- storage and filesystem event logs plus health diagnostics.
- recent formatting, imaging, resizing, encryption, snapshot, or virtual-disk operations.
For this condition, begin the investigation with disk and volume identifiers, partition layout, filesystem probe results, and sector size. Correlate it with whether the media is expected to be NTFS, ReFS, FAT/exFAT, optical, encrypted, or vendor-specific and check whether the filesystem is unsupported or its driver is missing/disabled. Capture the original this result immediately after the failing call so later cleanup does not replace the thread-local error value.
Handling and recovery
Do not format the volume automatically. First establish whether the contents are expected and whether the correct driver, unlock step, or virtual-storage layer is present. If corruption is suspected, capture an image or use an approved recovery path before write-capable repair tools.
Any retry policy for it should be tied to evidence that the media is intentionally unformatted or contains a non-filesystem payload has changed. Before another attempt, verify storage and filesystem event logs plus health diagnostics. If the volume is encrypted, locked, incomplete, or presented through the wrong storage layer still applies, stop the retry sequence and preserve the first diagnostic event.
Common misinterpretation
This result does not mean the physical disk is absent. Windows can see the device while being unable to interpret the volume contents.
Guidance for developers
When surfacing this result through another layer, retain its Win32 domain, numeric value, and the operation described by mounting media formatted for another operating system or appliance. A useful telemetry record also includes recent formatting, imaging, resizing, encryption, snapshot, or virtual-disk operations. For windows-related handling, decisions must use the numeric value and documented API contract rather than localized wording.
A focused test should reproduce the condition in which partition metadata or filesystem structures are damaged, assert this result, and confirm that the program releases resources associated with accessing a damaged partition or filesystem boot sector. The recovery test should also verify that disk and volume identifiers, partition layout, filesystem probe results, and sector size is refreshed before the operation resumes.
References
Looking for a different code? Search another status or error code.