Recent content by mfuentes

So my hope is that the next Diskvhd version will not create the size of the VHDX according to the physical size of the disk involved, but according to the sizes of the partitions you want to backup: That's what WindowsBackup does (with the apparently unnecessary limit of 16 TiB)

One partial win with an idea thanks to your suggestions: I abandoned disk2vhd for a moment and returned to WindowsBackup client (or wbadmin) in that +64TiB "problematic" physical disk, BUT this time I chose a <16TiB PARTITION (its known limit) and ... it worked. I obtained a valid VHDX (rather...

I succeeded doing expand/shrink o viceversa in other circumstances (apparent corruption), but already tried unsuccessfuly. This is now:

As far as I know the limit for WindowsBackup Client is just 16TiB, too small for my case. Is Wbadmin any different? Funnily I use it for V2P: I found a workaround and I can restore VHDX to Physical Disk in partitions (up to 64TiB obviously)

Thanks Bree I know it was originally without X, just that I don't use VHD anymore, always VHD X: Elon Musk told me so ;-) Even I call now my 2015 Nissan Leaf, Nissan X . And you are correct too: I also use HyperV as a tool for VHDX, but I obtain the same error as mounting the VHDX with...

Hi everyone, my first post here. I've been using Disk2vhd(x) for ages, before being acquired by Microsoft. Now version 2.02. And about two years ago I found a problem with it that's closer to be a bigger one as time passes: VHDX files can be 64 TiB maximum, right. But when using Disk2VHDX to...