Error when trying to re-mount a VHDx (the version does not support this version of the file format)

Question

Hi,
I have a vhdx on a NAS that I use for server backup. I created the VHDx via disk management, mounted it and assigned drive letter X. I now created a script that gets triggered upon startup via task scheduler to remount the VHD. If I try to mount it however,
it tells me this:
No matter what I try, I can't mount it. Double clicking just says this:
Eventviewer spits out error 137: The default transaction resource manager on volume X: encountered a non-retryable error and could not start.  The data contains the error code.
How do I trouble shoot this? oO Originally I had created the VHD as expanding, where now I recreated it at it's full size of 900GB. Maybe that will make a difference.
Thanks for the help
Cheers
Maike

Answer 1

Hi Maike,
Do you mean that you can mount the VHDX via disk management but cannot mount it via a script? If so, please provide the diskpart’s mount commands in the script.
In the meantime, check if destination partition is NTFS formatted.
Problem with Attach VHD function: The version does not support this version of the file format
http://www.paulauskis.lt/2010/03/problem-with-attach-vhd-function.html
Please Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]
Hi Mandy,
I can not mount it after a reboot. So I create the VHDx via disc management and attach it afterwards without problem. After the server reboots and the attached VHDx dropps, I can't remount it. Gives me the errors I posted above.
As I had mentioned above, I recreated the VHDx at it's full size this time, rather than expanding. That worked just fine and I can remount after reboot.
So I consider this dealt with ;)
Thanks anyway!