Repair method of the MSFT_Volume class
Repairs the volume.
Syntax
UInt32 Repair(
[in] Boolean OfflineScanAndFix,
[in] Boolean Scan,
[in] Boolean SpotFix,
[out] UInt32 Output,
[out] MSFT_StorageJob REF CreatedStorageJob,
[out] String ExtendedStatus
);
Parameters
OfflineScanAndFix [in]
Set to TRUE to perform an offline scan and fix.
Scan [in]
Set to TRUE to scan the volume.
SpotFix [in]
Set to TRUE to perform spot fixes on the volume.
Output [out]
The output of the repair operation.
CreatedStorageJob [out]
Returns a reference to the storage job object used to track the long-running operation.
ExtendedStatus [out]
A string that contains an embedded MSFT_StorageExtendedStatus object.
This parameter allows the storage provider to return extended (implementation-specific) error information.
Return value
Success (0)
Not Supported (1)
Unspecified Error (2)
Timeout (3)
Failed (4)
Invalid Parameter (5)
This command is not supported on x86 running in x64 environment. (7)
Access Denied (40001)
An unexpected I/O error has occurred (40004)
The specified file system is not supported (43001)
Cannot perform the requested operation when the drive is read only (43006)
The repair failed (43007)
The scan failed (43008)
A snapshot error occurred while scanning this drive. You can try again, but if this problem persists, run an offline scan and fix. (43009)
A scan is already running on this drive. Chkdsk can not run more than one scan on a drive at a time. (43010)
A snapshot error occurred while scanning this drive. You can try again, but if this problem persists, run an offline scan and fix. (43011)
A snapshot error occurred while scanning this drive. Run an offline scan and fix. (43012)
Cannot open drive for direct access (43013)
Cannot determine the file system of the drive (43014)
Requirements
Requirement | Value |
---|---|
Minimum supported client | Windows 8 [desktop apps only] |
Minimum supported server | Windows Server 2012 [desktop apps only] |
Namespace | Root\Microsoft\Windows\Storage |
MOF | Storagewmi.mof |
See also
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for