wooxo / vhd2disk Goto Github PK

This feature would be awesome. But I read the author has not enough time for adding much stuff (understandable) and I don't know if I'm skilled enough ATM to add it. It seems to be worldwide the only free solution, this is a little bit strange.

It would be nice if you could fix the issues with VHDTool or included its functionality into Vhd2Disk. VHDTool's issues are at https://github.com/TobiasFaller/VHDTool/issues.

Can you make a binary release, please?

It would be nice if it could automatically unmount a mounted drive so it can be used to restore a ramdisk before programs load (I have made a script using a program that does it and is using Drive Snapshot at the moment).

It would be nice if you included the functionality of Disk2VHD to it and changed its name.

L'outil de disk2vhd pour télécharger:
https://technet.microsoft.com/en-us/sysinternals/ee656415

Ou vous avez des idées pour réaliser cette fonctionalité? Merci.
Cordialement
Stlcours

For me, it shows it as ' \.\PhysicalDrive ᶦⁿˢᵉʳᵗ ᵈʳᶦᵛᵉ ⁿᵘᵐᵇᵉʳ ʰᵉʳᵉ '

Are there any command line Options for Vhd2Disk?

If not, do you plan to add those in a future release?

It would be nice if it showed a message stating that it needs to reboot when selecting a boot disk in order to restore it and after the user OK's it, it then reboots and loads a part of itself that does the restoring during the period where ChkDsk, etc. runs before Windows continues to boot. After that, it'll restart and let it boot.

It would be nice if you made one soon that includes my suggestions.

I hope this helps others with the same issue...

Hi, I ran into this error a couple of times and was unable to restore a .vhd to a new drive.

Can't write on physical drive. It's probably mounted.
You need to put it off line before to be able to write on it.
Microsoft choose this way for security reason...
It's nice for us and avoid to overwrite a non wanted drive.

The .vhd was about 220GB, so it took quite a while and I never made it to the end.
It appears like Windows was automatically rescanning the disks and mounted the the drive I was currently restoring.

I reproduced this behaviour by manually rescanning the disks while restoring, which produces the same error.

I then disabled automount in diskpart, ("automount" to check current setting; "automount disable/enable" to change the setting) started a new restore attempt and it worked.

Could this command be integrated into the program?

On start of a restore session -> "automount disable"
End or Cancel of restore session -> "automount enable"

(don't forget to re-enable automout if you had the same issue and found this)

I'm trying to use this tool to write to a disk that isn't physical - in my case a veracrypt volume. It's absolutely possible to write to disks like that on a sectory-by-sector basis, but it doesn't show up.

Since veracrypt volumes are always single volumes (i.e. no partitions), and you can select a partition, seemingly, in vhd2disk, I thought the step towards also selecting a partition as a target wouldn't be a big one.

Then again, I know nothing about low-level win32 programming, so I have no idea if it's as easy as my brain describes it to me.