Get-VHD [[-Path] <String[]>] [-ComputerName <String[]>] [-CimSession <CimSession[]>] [-Full] [-AsJob] [<CommonParameters>]
| Property | Description | |----------|-------------| | Path | Full path to the VHD/X file | | VhdFormat | VHD (legacy) or VHDX (modern) | | VhdType | Fixed , Dynamic , or Differencing | | FileSize | Current file size on disk (bytes) | | Size | Maximum virtual disk capacity (bytes) | | ParentPath | Path to parent disk (if differencing) | | DiskIdentifier | Unique GUID of the virtual disk | | BlockSize | Block size in bytes | | LogicalSectorSize | 512 or 4096 bytes | | IsAttached | Boolean indicating if the VHD is currently attached to a VM or the host | get-vhd
The get-vhd command had given him the vitals. It told him the patient was alive, but it hadn't put the patient on the operating table. The IsAttached: False status was the final barrier. The data existed, but it was locked behind a door the operating system refused to open. The file was "attached" to the drive controller, but not to the logic. The data existed, but it was locked behind