HELP! Recover Windows 10 from C: Partition?

SpeedyVV

Supreme [H]ardness
Joined
Sep 14, 2007
Messages
4,211
Ok, brother-in-law accidentally put the wrong power cord!

td;dr Windows 10 PC no longer boots and the Windows system partitions are foobar.

The C: drive looks completely intact.

So is there a way to recreate the system from that C: drive? I have extra drives to copy stuff back and forth if required and extra PCs.

Tried all sorts of partition tools to recreate systems partitions but just cant get it to boot :-(
 

Stanley Pain

2[H]4U
Joined
Apr 5, 2001
Messages
2,486
If there's data on it you want to recover, boot into Ubunutu from a USB drive, recover the files you want then re-install windows.

You might be able to repair the boot problem by booting the Windows installation media and trying the recovery options.
 

Mazzspeed

2[H]4U
Joined
Dec 27, 2017
Messages
2,693
As Stanley said:

- Boot into ubuntu live media.
- Back up user profile to external drive.
- Reinstall Windows.
- Activate hidden Administrator account.
- Log into Administrator account.
- Transfer user profile back into your newly created profile.
- Reinstall all software.

Bear in mind that if the drive is in an unclean state you will need to remove it and plug it into another Windows machine to backup the user profile.
 

amittalkin

Limp Gawd
Joined
Jun 19, 2015
Messages
362
There is program called @ctive partition recovery, you can try that to recover your partitions. Then boot from Windows 10 installation media and fix boot sectors.
 

auntjemima

Supreme [H]ardness
Joined
Mar 1, 2014
Messages
6,372
As Stanley said:

- Boot into ubuntu live media.
- Back up user profile to external drive.
- Reinstall Windows.
- Activate hidden Administrator account.
- Log into Administrator account.
- Transfer user profile back into your newly created profile.
- Reinstall all software.

Bear in mind that if the drive is in an unclean state you will need to remove it and plug it into another Windows machine to backup the user profile.
He's looking for a way to save the C: partition, not copy his user details. Just based on his post alone and having other PC's he can throw it in tells me he is already capable of that. He wants to take that booting windows partition and fix it, either in place or on another drive.
 

Stanley Pain

2[H]4U
Joined
Apr 5, 2001
Messages
2,486
He's looking for a way to save the C: partition, not copy his user details. Just based on his post alone and having other PC's he can throw it in tells me he is already capable of that. He wants to take that booting windows partition and fix it, either in place or on another drive.
Which I also alluded to in my post. Boot from Windows install media and do a recovery from there. If it can fix the boot issue it will.
 

Mazzspeed

2[H]4U
Joined
Dec 27, 2017
Messages
2,693
He's looking for a way to save the C: partition, not copy his user details. Just based on his post alone and having other PC's he can throw it in tells me he is already capable of that. He wants to take that booting windows partition and fix it, either in place or on another drive.
So fire up a live distro, start up Gparted and mark the boot partition as bootable. If that doesn't work there's nothing you can do but back up the user profile and reinstall, as Windows Recovery is about as useful as sfc /scannow in most situations.
 

xx0xx

Gawd
Joined
Oct 20, 2005
Messages
657
Is it possible that fixboot / rebuildbcd / fixmbr recovery stuff could help in this type of instance? I haven't had too much luck lately with fubar'd W10 boot fixes though, on a number of machines that have gone south recently. Apparently MS has royally screwed up their own recovery commands
 

Mazzspeed

2[H]4U
Joined
Dec 27, 2017
Messages
2,693
Is it possible that fixboot / rebuildbcd / fixmbr recovery stuff could help in this type of instance? I haven't had too much luck lately with fubar'd W10 boot fixes though, on a number of machines that have gone south recently. Apparently MS has royally screwed up their own recovery commands
I've tried this process many times with no success. You either get an error or the commands appear to work but actually do nothing at all.
 

auntjemima

Supreme [H]ardness
Joined
Mar 1, 2014
Messages
6,372
I've tried this process many times with no success. You either get an error or the commands appear to work but actually do nothing at all.
I've had it work, but never on a UEFI partition. But I've repaired 2 or 3 MBR ones. It definitely is not a guarantee, though, that's for sure.
 

Mazzspeed

2[H]4U
Joined
Dec 27, 2017
Messages
2,693
May I suggest that before the OP does anything he at least backs up the entire user profile...
 
  • Like
Reactions: xx0xx
like this

PliotronX

2[H]4U
Joined
Aug 8, 2000
Messages
2,070
I've had it work, but never on a UEFI partition. But I've repaired 2 or 3 MBR ones. It definitely is not a guarantee, though, that's for sure.
Bootrec and automatic repair seem to do fuck all for EFI but we recently repaired two using bcdboot after assigning a letter to the EFI partition.
 

Mazzspeed

2[H]4U
Joined
Dec 27, 2017
Messages
2,693
Bootrec and automatic repair seem to do fuck all for EFI but we recently repaired two using bcdboot after assigning a letter to the EFI partition.
Try my advice above using Gparted and making sure the partition is marked as bootable, I've encountered that issue also with EFI partitions..

I'm still not totally sold on UEFI.
 

PliotronX

2[H]4U
Joined
Aug 8, 2000
Messages
2,070
Try my advice above using Gparted and making sure the partition is marked as bootable, I've encountered that issue also with EFI partitions..

I'm still not totally sold on UEFI.
Your suggestion appears to be wipe and replace because marking it as bootable isn't the full story. UEFI is necessary for faster boot times, secure boot, and the use of booting from NVME so its better to learn the ways and means ;)
 

B00nie

[H]F Junkie
Joined
Nov 1, 2012
Messages
8,449
Most likely the OPs problem is that he had no control over the drives during the installation (typical windows problem) and his true boot sector with hidden windows partitions resided on the drive that is now toast. The system will not become bootable by setting the "C:" partition bootable since it's not really the boot partition that the system expects. What the OP has to do is to plug a new SATA/M.2 drive back to the same port where the fried drive used to be and attempt a boot repair. Sometimes even that won't work and the only option is to reinstall at that point.

You should never have anything but your boot drive plugged in during windows install, otherwise you can and will end up with a cluster fuck of a setup like the OP seems to have. Windows will randomly just do what it chooses to do and the end user cannot control it.
 
Top