VirtualBox Error: Could not get storage format medium (VERR_NOT_SUPPORTED) with Disk2VHD.VHD File

VirtualBox Error: Could not get storage format medium (VERR\_NOT\_SUPPORTED) when using .VHD file created by Disk2VHD

Have you encountered the error "Could not get storage format medium (VERR\_NOT\_SUPPORTED)" while trying to attach a .VHD file created by Disk2VHD to VirtualBox? This article will provide a detailed explanation of the issue and offer solutions to help you resolve it.

Understanding the error

This error occurs because VirtualBox does not support .VHD files created by Disk2VHD by default. Disk2VHD uses a specific version of VHD that VirtualBox does not recognize.

Converting .VHD to a VirtualBox-compatible format

You can use a third-party tool called VBoxManage to convert the .VHD file to a VirtualBox-compatible format.

Instructions for converting .VHD files:

1. Download and install VirtualBox from the official website: VirtualBox Downloads

2. Open a command prompt or terminal and navigate to the location where the .VHD file created by Disk2VHD is saved.

   cd C:\Users\stirba\Desktop

3. Type the following command to convert the .VHD file to a VirtualBox-compatible format:

   VBoxManage convertdd --format VDI VirtualBox.vhd VirtualBox\_Converted.vdi

   Replace VirtualBox.vhd with the name of your .VHD file and VirtualBox\_Converted.vdi with the desired name for the converted file.

4. Launched VirtualBox and attach the converted file created in Step 3.

Additional Solutions

If the above solution does not work for you, consider the following alternative methods:

• StarWind V2V Converter - A free and easy-to-use third-party tool for converting virtual machines between various formats.
• VMware vCenter Converter - A powerful, free, and feature-rich solution from VMware for converting virtual machines between different formats.

Recommendations

To avoid this issue in the future, consider using a VirtualBox-compatible format when creating virtual hard disks.

Summary and References

• VirtualBox Forums - Similar issue discussed
• VirtualBox Manual - VBoxManage documentation