12
11
Let me please explain the scenario what I went through.
I have a Transcend SSD which I use to boot my PC which I upgraded from Windows 8 to Windows 8.1.
I have two other hard disk drives (one tera byte and other is 320 GB). Yesterday I received a notification from the SSD utility that there is a firmware update available. I read the instructions which came along it which stated that the drive will be completely erased if I update it. Naturally I had to backup the entire drive. I used the command :
wbAdmin start backup -backupTarget:F: -include:C: -allCritical -quiet
The F drive was my other hard drive of 320 GB (Single partition).
It took a while and came the message that the backup has been done successfully.
I made a system restore disk using the utility from the control panel.
I then made the firmware update usb drive by the utility provided and then booted from the USB and successfully updated the firmware.
Then I booted from the system restore disk I created earlier to restore my old image. However when I tried to restore it, it tried to restore it on my other hard drive instead. I then went to command prompt, used the diskpart
command and accidentally selected the wrong drive (the one which contained my backup) and used the clean
command.
And there my whole backup was gone!
I then installed a fresh OS using my original DVD (of Windows 8) on the SSD. I tried the recovery tools and all I was able to recover is my VHDX file (which is usually inside the folders created by the wbAdmin
command). I tried mounting the image and thankfully it is safe and I can mount it.
Now the thing is that I want to write the complete VHDX file to my SSD so that I can get back my old and working OS.
Can anyone please help me with the things I have? I just have my VHDX file.
2Thank you for posting this! I have a "Windows image backup" (VHDX file) but the regular Windows restore utility refused to restore it, saying (something like) there was not a suitable place to restore it to. I found at least three different explanations of why this could happen and tried their workarounds - nothing. This technique worked. Really makes me wonder why Microsoft doesn't provide an override on whatever checks it's making; as this backup is obviously perfectly good! – Jamie Hanrahan – 2018-09-10T13:14:03.537
1Windows build-in restore only returned errors: 0x800703ed (the volume doesn't contain a recognizable file system) and 0x80070057 (the parameter is incorrect). Whatever workaround was tried, ejecting disks, etcetera. This method took al long time to convert at USB2 speed, but worked! – Pro Backup – 2019-05-26T18:19:46.107
Will this work if instead of mounting the vhdx you are native booted from the vhdx? – user5389726598465 – 2019-09-09T00:12:43.583
Should command 5 show progress or just sit at the command prompt for like hours? – user5389726598465 – 2019-09-11T05:36:05.580
Yes, the "New-WindowsImage" command takes a long, long time before it starts to show any progress. Converting a 500GB image on an i7, it took a couple of hours before the command show the progress bar. :( – Erik Anderson – 2019-09-11T16:56:47.633