Close
Skip to content

4 Comments

  1. Don Saul
    July 27, 2021 @ 9:42 pm

    YES! This was the only set of instructions that worked for me. I had cloned a regular HD to an SSD, but the new SSD would not boot. Turns out there was no SYSTEM partition. I used AOEMI to shrink the C: partition, create a new partition, labeled it system, then cloned a valid SYSTEM partition to this new one. Then I ran the steps above, and it worked. Whew. Thanks!

    Reply

  2. Jesse Catlow
    February 26, 2021 @ 5:55 pm

    THANK YOU!!! After trying all the other fixes, this is the one that got me back up and running. You are very much appreciated.

    Reply

  3. Richard Ankur
    April 13, 2020 @ 11:43 am

    Worked

    Reply

  4. Bob Miller
    January 18, 2020 @ 5:57 am

    Worked like a charm…

    Steps 7 & 8 is kinda confusing! You log out of/exit DISKPART in step 6 and then steps 7 & 8 is shown running the updates from [DISKPART> bcdboot C:\windows /s Z: /f All (or UEFI)] and the updates actually run from an:

    Administrator: Command Prompt
    [C:\Windows\System32> bcdboot C:\windows /s Z: /f All (or UEFI)] — at least in my case "ALL" worked.

    Reason for me finding your work-around. Just tried to boot up this morning and the beautiful BSOD decided to show up.

    MSI MoBo, Win 10, 6700K, 32gb

    Unable to get anywhere and found my keyboard was not responding, out came old faithful. Still not able to boot into anything, not even the Bios. Finally woke up, maybe the the Bios crashed, and moved Bios Sw from B to A.

    Success, system woke up and and I found that my Raid 0 was broke. Not good. Reset UEFI to boot Raid and rebooted back into the bios and my Raid was reset and shown as bootable. Nice, but, still wouldn't boot into Windows. With the original OS disk loaded I was able to get to a Administrator: Command Prompt.

    After an hour or so of trying the usual BS and not getting anywhere and not wanting to rebuild, started the Google thing.

    Up pops your page, interesting! Had not seen this page before and not wanting to take the time to rebuild because I've been working on a project and wanted to get it finished decided, "Why not".

    The system booted right up the second try. Closed the system down, plugged all internal & external drives, along with the keyboard back in and rebooted.

    Running like nothing ever happened and saved me at least a days work.

    Thank you for posting this workaround/fix.

    Bob Miller

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

css.php