HRESULT 0xC05CFF00 (ERROR_SVHDX_ERROR_NOT

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: The requested server-side Shared VHDX error record is no longer available for retrieval.

Could be also:
Constant	Type	OS
STATUS_SVHDX_ERROR_NOT_AVAILABLE	NTSTATUS	Windows

Previous	Next
ERROR_SVHDX_ERROR_STORED	ERROR_SVHDX_UNIT_ATTENTION_AVAILABLE

ERROR_SVHDX_ERROR_NOT_AVAILABLE

What is unavailable

ERROR_SVHDX_ERROR_NOT_AVAILABLE means that a caller asked the Shared VHDX server for additional error information, but the requested record was not available. It is not a statement that the virtual disk is healthy, that the earlier command was accepted, or that no SCSI error occurred. It only says that the server cannot supply that particular error payload at the time of the request.

This status is especially important after ERROR_SVHDX_ERROR_STORED. Stored details are associated with a particular failure context. A later query can miss them because the wrong request context was used, the server no longer retains the record, the operation was superseded, or the caller did not preserve the original diagnostic handle and correlation data. The correct response is to investigate the original operation, not to reinterpret the absence of extended data as success.

Diagnostic distinction

ERROR_SVHDX_ERROR_STORED says that a detailed error and sense payload was retained server-side.
ERROR_SVHDX_ERROR_NOT_AVAILABLE says that the requested payload cannot be obtained now.
A SCSI reservation conflict or Unit Attention is a substantive storage-state result; this code can merely prevent its details from being retrieved after the fact.

Practical investigation

Keep the first failure HRESULT, request identifier, virtual disk path or object ID, and timestamps from both client and server logs.
Check whether a failover, session reconnect, migration, disk reopen, or management operation occurred between the original failure and the error-data query.
Do not repeat a reservation or metadata-changing operation solely to obtain a better error message. First confirm the current registration, reservation, and ownership state.
When reproducing the issue in a non-production environment, collect the detailed result immediately after the failed operation rather than after unrelated I/O has continued.

References

Looking for a different code? Search another status or error code.