Windows 10: Error in mounting VHDX file

Hi,


I have Created a VHDX file Ihave stored so many important files in it today when i try to open it is saying


Make sure the file is in an NTFS volume and isn't in a compressed folder or volume





i have seen in properties when i try to unchuck the compress file option

it is not applyingto the file


please help me my contact number: 9603855406

:)

 

Error when mounting ISO files

Hi,



Thank you for writing to Microsoft Community Forums.



I understand when you are trying to delete/rename/move the ISO files after mounting it you get an error message. It could be possible that the ISO file is mounted and that is the reason you are unable to modify it.



I suggest you to eject the ISO file and then try to modify it. Please follow the steps mentioned below:

1. Press Windows key + E, to open
   File Explorer.
   
2. Click on This PC on the left pane, you will find the mounted ISO file.
   
3. Right click on the ISO file and click on Eject. Try modifying the ISO file now.
   

Please reply with the status of the issue, we will be glad to help you further.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

Mount or Unmount VHD or VHDX File in Windows 10


Hi, and thanks for your reply.

There is no problem with File Backups. It is the System Image Backup .vhdx file which I am trying to view, using it to mount a VHD (Drive M which appears empty to File Manager. As you suggested I had a good look at the W7 tutorial for file mounting, and explored some of its links, but to no avail.

I also tried to mount the VHD with Diskpart from elevated command prompt: Diskpart; select vdisk file=filename.vhdx; attach vdisk. There was no need to assign a drive letter as Windows remembered it, which is annoying. M: was again empty.

Then, Windows PowerShell: Mount-VHD -Path "[location of vhd]". This cmdlet failed with error message "Mount-VHD is not recognised as the name of a cmdlet ...". Googling this, I found this could be due to the absence of a Hyper-V module for Windows PowerShell. Now, I know that Hyper-V Virtualization does not come with W10 Home but does with W10 Pro. Could my problem be related? Could it be that the image file is vdhx rather than vdh which I assume was the format in W7? I am out of my depth here, and don't want to experiment without advice.

Out of interest I checked UEFI Bios and found Virtualisation Technology to be disabled, and Hyper-V missing from the Programs and Features list in Control Panel. With some trepidation I tried Enabling Virtualisation. Programs and Features list was unchanged, as was the PowerShell outcome and the zero content of M: after attaching via Disk Management. I returned Virtualisation to Disabled.

Drive M:'s properties show its partition type to be GUID, not MBR.

Grateful for any further thoughts. Thanks.

 

vhdx file mounts but shows empty

Mounted a recent vhdx file created by windows 10 system image copy
shows up as empty.
Mounted an older vhd file and showed up fine.
Created a new system image and imediately restored using it-restored fine.
Mounted same vhdx and shows up empty.
Properties show as having several gigs of info.
Ran error checking and showed no errors.
All was fine until one of the recent windows updates (not sure which one).
I've searched all over but no solutions found.
Am I really the only one with this problem?