Windows 10: System Restore hung, now no mountable boot volume

I was working on a Win 10 X64 Home PC for some friends and thought I'd try a System Restore. It started the restore ok then got to System Restore initializi9ng and hung there for several hours. I finally had to drop power.

When I powered it back up the hard drive is no longer available. I get a unmountable boot device.
DISKPART doesn't see it, Macrium Reflect doesn't see it.

What about EaseUS Partition Recovery? Might that work? Can I run it from Kyhi's WinPE disc?
Any other alternatives to repair the partition table/MBR? TestDisk perhaps? @NavyLCDR?

:)

 

How to replace system disk (windows 10) (without having to backup mounted drive) ?

I thought I describe the setup in the first post but I will repeat it here:

I have a system disk (boot) that is C: - it has the usual stuff like documents. I have a second disk that I used a mounted volume instead of a driver letter when I set it up. This is making it difficult for window backup tool to clone the system disk. The
method that I used to use was to 'backup' the system disk - install the bootable dvd and restore the system but since the mountable volume is being treated as a 'natural' directory the backup process wants a disk that is capable of holding all content. I suppose
I could buy a bigger backup disk - do the full process and then delete all content under the mounted volume on restore. Alternatively unless windows 10 is keeping some aspect of the physical disk in the boot process (under linux uuid will change if you clone
a disk but grub is smart enough to deal with that case) I could just use dd. Seems silly to have to use linux to clone a windows disk but from this thread it sounds like ms doesn't have a viable method to deal with this situation. I've noticed a few other
bugs with mounted volumes under windows 10 so perhaps they are just plain broken under the new os ?

 

How do I find volume identifiers?

Mountvol gave me the following. These volume IDs don't look like any I've seen before or the previous values I saw in the BCD. Are they correct?

C:\Windows\system32>mountvol

Creates, deletes, or lists a volume mount point.

MOUNTVOL [drive:]path VolumeName

MOUNTVOL [drive:]path /D

MOUNTVOL [drive:]path /L

MOUNTVOL [drive:]path /P

MOUNTVOL /R

MOUNTVOL /N

MOUNTVOL /E

path Specifies the existing NTFS directory where the mount

point will reside.

VolumeName Specifies the volume name that is the target of the mount

point.

/D Removes the volume mount point from the specified directory.

/L Lists the mounted volume name for the specified directory.

/P Removes the volume mount point from the specified directory,

dismounts the volume, and makes the volume not mountable.

You can make the volume mountable again by creating a volume

mount point.

/R Removes volume mount point directories and registry settings

for volumes that are no longer in the system.

/N Disables automatic mounting of new volumes.

/E Re-enables automatic mounting of new volumes.

Possible values for VolumeName along with current mount points are:

\\?\Volume{2f45e22a-0000-0000-0000-100000000000}\

*** NO MOUNT POINTS ***

\\?\Volume{2f45e22a-0000-0000-008e-646e1d000000}\

E:\

\\?\Volume{2f45e22a-0000-0000-0000-80852e000000}\

F:\

\\?\Volume{2f45e22a-0000-0000-0000-602200000000}\

D:\

\\?\Volume{2f45e22a-0000-0000-0000-60570c000000}\

C:\

\\?\Volume{04655401-ecb9-11e7-bfa4-806e6f6e6963}\

O:\

 

Coincidentally, the drive may have failed.
Boot into Setup (Bios) is the drive listed there? If not it has failed.
If Diskpart does not see the drive, it most likely has failed.
Download the ISO image for Seatools, burn the image to CD using IMGBurn or to a USB Flash Drive with SeaFlash, all available in my signature. Boot off of the newly created media, run the Short and Long tests on the HDD, if either test fails, the HDD needs to be replaced.

 

SEatools passed okay.

I'm going to try EaseUS. Any other suggestions welcome.

 

The reason the disk was not visible to any of the tools was because it was in RAID mode instead of AHCI. Once I put it in AHCI I could access it to run chkdsk (which fixed a few problems) and Macriums's Fix boot problems, but it wouldn't boot. I put it back to RAID then it booted but I was back to the BSOD. BSOD is not creating a dump even though it's setup to for small dumps.

I put it back to AHCI and am doing a Macrium image backup then I will wipe it an do a clean install in AHCI mode of Creator update, apply all updates then restore data.

Edit: All is well now. Install completed and activated, and it's in AHC, not RAID. All data in Windows.old. Will install updates tomorrow, restore data and return the PC to owners.