Windows | NT Family

~/wim/Windows/ /run/media/…/OS/Windows`

Then I copied `system32/config` back over, started the VM, it spun, and...

[The Crash – Kavinsky](https://www.youtube.com/watch?v=ig8wfLhPi5w&t=45s)

https://preview.redd.it/kvut2nnmpq7f1.png?width=1412&format=png&auto=webp&s=2eece553b405a19add3d2da82a042b1e4dbd54c8

It worked. I have managed to fix a broken Windows 10 install all the while `ddrescue` was still dutifully working in the background trying its hardest to get those remaining 45MBs. I can later redo what I did just in case those 45MBs had something extra in there that wasn't just system files I overwrote. If I really wanted, I could do some deep analysis using the `ddrescue` map and seeing what files got winged by the damage by checking if that file happened to be stored where `ddrescue` couldn't recover.

So hopefully, in some way, my long winded post here has some useful bits of information for anyone who does cloning often or has a need to experiment different fixes and be able to easily blow them away if they don't work.

# Could you just reinstall?

Yes.

I very much could have and it'd be a another anti-climatic end to yet another broken Windows install. But pitching this back at the person with a reinstalled copy of Windows and telling them "Just reinstall all your stuff, your files are in Windows.Old" just didn't feel right, especially since the damage was 45MB somewhere in some core Windows files. Maybe this might be some inspiration to try experimenting to see if some crazed idea would get a install running again, or some divine intervention where a Microsoft engineer will look at my plight and think "You know that just sucks to do blind" and Windows improves a bit on telling you when things go wrong. Either way, hope all of this is useful somehow..

https://redd.it/1ler6o5
@r_Windows

YouTube

The Crash

Provided to YouTube by IIP-DDS

The Crash · Kavinsky

Teddy Boy

℗ Record Makers

Released on: 2005-12-12

Producer: Kavinsky
Music Publisher: Concord Music Publishing
Music Publisher: Record Makers
Composer: Vincent Belorgey

Auto-generated by YouTube.

www.tgoop.com/r_Windows/36670

1 viewJun 18 at 21:09

~/wim/Windows/ /run/media/…/OS/Windows`

Then I copied `system32/config` back over, started the VM, it spun, and...

[The Crash – Kavinsky](https://www.youtube.com/watch?v=ig8wfLhPi5w&t=45s)

https://preview.redd.it/kvut2nnmpq7f1.png?width=1412&format=png&auto=webp&s=2eece553b405a19add3d2da82a042b1e4dbd54c8

It worked. I have managed to fix a broken Windows 10 install all the while `ddrescue` was still dutifully working in the background trying its hardest to get those remaining 45MBs. I can later redo what I did just in case those 45MBs had something extra in there that wasn't just system files I overwrote. If I really wanted, I could do some deep analysis using the `ddrescue` map and seeing what files got winged by the damage by checking if that file happened to be stored where `ddrescue` couldn't recover.

So hopefully, in some way, my long winded post here has some useful bits of information for anyone who does cloning often or has a need to experiment different fixes and be able to easily blow them away if they don't work.

# Could you just reinstall?

Yes.

I very much could have and it'd be a another anti-climatic end to yet another broken Windows install. But pitching this back at the person with a reinstalled copy of Windows and telling them "Just reinstall all your stuff, your files are in Windows.Old" just didn't feel right, especially since the damage was 45MB somewhere in some core Windows files. Maybe this might be some inspiration to try experimenting to see if some crazed idea would get a install running again, or some divine intervention where a Microsoft engineer will look at my plight and think "You know that just sucks to do blind" and Windows improves a bit on telling you when things go wrong. Either way, hope all of this is useful somehow..

https://redd.it/1ler6o5
@r_Windows

BY Windows | NT Family