COM Error Codes (VOLMGR, BCD, VHD, SDIAG)
The following table provides a list of error codes used by COM-based APIs.
If you are experiencing difficulty with an application you are installing or running, contact customer support for the software that is displaying the error message. To obtain support for a Microsoft product, go to https://support.microsoft.com.
| Constant/value | Description |
|---|---|
|
The regeneration operation was not able to copy all data from the active plexes due to bad sectors. |
|
One or more disks were not fully migrated to the target pack. They may or may not require reimport after fixing the hardware problems. |
|
The configuration database is full. |
|
The configuration data on the disk is corrupted. |
|
The configuration on the disk is not insync with the in-memory configuration. |
|
A majority of disks failed to be updated with the new configuration. |
|
The disk contains non-simple volumes. |
|
The same disk was specified more than once in the migration list. |
|
The disk is already dynamic. |
|
The specified disk id is invalid. There are no disks with the specified disk id. |
|
The specified disk is an invalid disk. Operation cannot complete on an invalid disk. |
|
The specified disk(s) cannot be removed since it is the last remaining voter. |
|
The specified disk has an invalid disk layout. |
|
The disk layout contains non-basic partitions which appear after basic paritions. This is an invalid disk layout. |
|
The disk layout contains partitions which are not cylinder aligned. |
|
The disk layout contains partitions which are samller than the minimum size. |
|
The disk layout contains primary partitions in between logical drives. This is an invalid disk layout. |
|
The disk layout contains more than the maximum number of supported partitions. |
|
The specified disk is missing. The operation cannot complete on a missing disk. |
|
The specified disk is not empty. |
|
There is not enough usable space for this operation. |
|
The force revectoring of bad sectors failed. |
|
The specified disk has an invalid sector size. |
|
The specified disk set contains volumes which exist on disks outside of the set. |
|
A disk in the volume layout provides extents to more than one member of a plex. |
|
A disk in the volume layout provides extents to more than one plex. |
|
Dynamic disks are not supported on this system. |
|
The specified extent is already used by other volumes. |
|
The specified volume is retained and can only be extended into a contiguous extent. The specified extent to grow the volume is not contiguous with the specified volume. |
|
The specified volume extent is not within the public region of the disk. |
|
The specified volume extent is not sector aligned. |
|
The specified parition overlaps an EBR (the first track of an extended partition on a MBR disks). |
|
The specified extent lengths cannot be used to construct a volume with specified length. |
|
The system does not support fault tolerant volumes. |
|
The specified interleave length is invalid. |
|
There is already a maximum number of registered users. |
|
The specified member is already in-sync with the other active members. It does not need to be regenerated. |
|
The same member index was specified more than once. |
|
The specified member index is greater or equal than the number of members in the volume plex. |
|
The specified member is missing. It cannot be regenerated. |
|
The specified member is not detached. Cannot replace a member which is not detached. |
|
The specified member is already regenerating. |
|
All disks belonging to the pack failed. |
|
There are currently no registered users for notifications. The task number is irrelevant unless there are registered users. |
|
The specified notification user does not exist. Failed to unregister user for notifications. |
|
The notifications have been reset. Notifications for the current user are invalid. Unregister and re-register for notifications. |
|
The specified number of members is invalid. |
|
The specified number of plexes is invalid. |
|
The specified source and target packs are identical. |
|
The specified pack id is invalid. There are no packs with the specified pack id. |
|
The specified pack is the invalid pack. The operation cannot complete with the invalid pack. |
|
The specified pack name is invalid. |
|
The specified pack is offline. |
|
The specified pack already has a quorum of healthy disks. |
|
The pack does not have a quorum of healthy disks. |
|
The specified disk has an unsupported partition style. Only MBR and GPT partition styles are supported. |
|
Failed to update the disk's partition layout. |
|
The specified plex is already in-sync with the other active plexes. It does not need to be regenerated. |
|
The same plex index was specified more than once. |
|
The specified plex index is greater or equal than the number of plexes in the volume. |
|
The specified plex is the last active plex in the volume. The plex cannot be removed or else the volume will go offline. |
|
The specified plex is missing. |
|
The specified plex is currently regenerating. |
|
The specified plex type is invalid. |
|
The operation is only supported on RAID-5 plexes. |
|
The operation is only supported on simple plexes. |
|
The Size fields in the VM_VOLUME_LAYOUT input structure are incorrectly set. |
|
There is already a pending request for notifications. Wait for the existing request to return before requesting for more notifications. |
|
There is currently a transaction in process. |
|
An unexpected layout change occurred outside of the volume manager. |
|
The specified volume contains a missing disk. |
|
The specified volume id is invalid. There are no volumes with the specified volume id. |
|
The specified volume length is invalid. |
|
The specified size for the volume is not a multiple of the sector size. |
|
The operation is only supported on mirrored volumes. |
|
The specified volume does not have a retain partition. |
|
The specified volume is offline. |
|
The specified volume already has a retain partition. |
|
The specified number of extents is invalid. |
|
All disks participating to the volume must have the same sector size. |
|
The boot disk experienced failures. |
|
The configuration of the pack is offline. |
|
The configuration of the pack is online. |
|
The specified pack is not the primary pack. |
|
All disks failed to be updated with the new content of the log. |
|
The specified number of disks in a plex is invalid. |
|
The specified number of disks in a plex member is invalid. |
|
The operation is not supported on mirrored volumes. |
|
The operation is only supported on simple and spanned plexes. |
|
The pack has no valid log copies. |
|
A primary pack is already present. |
|
The specified number of disks is invalid. |
|
The system does not support mirrored volumes. |
|
The system does not support RAID-5 volumes. |
|
Some BCD entries were not imported correctly from the BCD store. |
|
Entries enumerated have exceeded the allowed threshold. |
|
Some BCD entries were not synchronized correctly with the firmware. |
|
The virtual hard disk is corrupted. The virtual hard disk drive footer is missing. |
|
The virtual hard disk is corrupted. The virtual hard disk drive footer checksum does not match the on-disk checksum. |
|
The virtual hard disk is corrupted. The virtual hard disk drive footer in the virtual hard disk is corrupted. |
|
The system does not recognize the file format of this virtual hard disk. |
|
The version does not support this version of the file format. |
|
The virtual hard disk is corrupted. The sparse header checksum does not match the on-disk checksum. |
|
The system does not support this version of the virtual hard disk.This version of the sparse header is not supported. |
|
The virtual hard disk is corrupted. The sparse header in the virtual hard disk is corrupt. |
|
Failed to write to the virtual hard disk failed because the system failed to allocate a new block in the virtual hard disk. |
|
The virtual hard disk is corrupted. The block allocation table in the virtual hard disk is corrupt. |
|
The system does not support this version of the virtual hard disk. The block size is invalid. |
|
The virtual hard disk is corrupted. The block bitmap does not match with the block data present in the virtual hard disk. |
|
The chain of virtual hard disks is broken. The system cannot locate the parent virtual hard disk for the differencing disk. |
|
The chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk. |
|
The chain of virtual hard disks is corrupted. The time stamp of the parent virtual hard disk does not match the time stamp of the differencing disk. |
|
Failed to read the metadata of the virtual hard disk. |
|
Failed to write to the metadata of the virtual hard disk. |
|
The size of the virtual hard disk is not valid. |
|
The file size of this virtual hard disk is not valid. |
|
A virtual disk support provider for the specified file was not found. |
|
The specified disk is not a virtual disk. |
|
The chain of virtual hard disks is inaccessible. The process has not been granted access rights to the parent virtual hard disk for the differencing disk. |
|
The chain of virtual hard disks is corrupted. There is a mismatch in the virtual sizes of the parent virtual hard disk and differencing disk. |
|
The chain of virtual hard disks is corrupted. A differencing disk is indicated in its own parent chain. |
|
The chain of virtual hard disks is inaccessible. There was an error opening a virtual hard disk further up the chain. |
|
The requested operation could not be completed due to a virtual disk system limitation. On NTFS, virtual hard disk files must be uncompressed and unencrypted. On ReFS, virtual hard disk files must not have the integrity bit set. |
|
The requested operation cannot be performed on a virtual disk of this type. |
|
The requested operation cannot be performed on the virtual disk in its current state. |
|
The sector size of the physical disk on which the virtual disk resides is not supported. |
|
The disk is already owned by a different owner. |
|
The disk must be offline or read-only. |
|
Change Tracking is not initialized for this Virtual Disk. |
|
Size of change tracking file exceeded the maximum size limit |
|
VHD file is changed due to compaction, expansion or offline patching |
|
Change Tracking for the virtual disk is not in a valid state to perform this request. Change tracking could be discontinued or already in the requested state. |
|
Change Tracking file for the virtual disk is not in a valid state. |
|
The requested resize operation could not be completed because it might truncate user data residing on the virtual disk. |
|
The requested operation could not be completed because the virtual disk's minimum safe size could not be determined. This may be due to a missing or corrupt partition table. |
|
The requested operation could not be completed because the virtual disk's size cannot be safely reduced further. |
|
There is not enough space in the virtual disk file for the provided metadata item. |
|
The virtualization storage subsystem has generated an error. |
|
The operation was canceled. |
|
An error occurred when running a PowerShell script. |
|
An error occurred when interacting with PowerShell runtime. |
|
An error occurred in the Scripted Diagnostic Managed Host. |
|
The troubleshooting pack does not contain a required verifier to complete the verification. |
|
The troubleshooting pack cannot be executed on this system. |
|
Scripted diagnostics is disabled by group policy. |
|
Trust validation of the diagnostic package failed. |
|
The troubleshooting pack cannot be executed on this system. |
|
This version of the troubleshooting pack is not supported. |
|
A required resource cannot be loaded. |
|
The troubleshooting pack reported information for a root cause without adding the root cause. |
Requirements
| Requirement | Value |
|---|---|
| Header |
|