INACCESSIBLE BOOT DRIVE after adding M.2 drive

Rhothgar said:

Hi NavyLCDR. Thank you for your input and especially the code.

I haven't used it because my system is MBR. Please re-read my last post carefully and watch video as it's clear you cannot have watched it.

Perhaps you should mark this thread as solved.

NavyLCDR said:

Best of luck to you! Bye-bye.

Christ! I was really careful how I worded that. Obviously, you're overly sensitive.

That's fact! You haven't bothered to watch the video despite being confused about other posts. Madness.

Rhothgar said:

Christ! I was really careful how I worded that. Obviously, you're overly sensitive.

That's fact! You haven't bothered to watch the video despite being confused about other posts. Madness.

As I said, common courtesy is to mark a thread as solved when you have the solution so others don't keep coming in and try to help.

NavyLCDR said:

Perhaps you should mark this thread as solved.

I guarantee you will be embarrassed when you watch the video and others who have actually read what is going on and helped will understand where I am coming from and will be happy that you have over-reacted.

I don't want to get anyone's back up on this brilliant forum but GET A GRIP, MAN!

You're clearly not interested in helping so just scroll on.

- - - Updated - - -

NavyLCDR said:

Why are you using the /f UEFI switch in the BCD command? You are clearly NOT booting in UEFI mode. The switch for firmware type in the bcdboot command should be /f BIOS.

All of the above posts have made me extremely confused. On the new SSD, you have an NTFS partition that holds the windows installation. You need to mark that partition active. Then you need to run a BCDBOOT command that writes a proper BCD to it. Let's say that partition is C: . The command would be:

bcdboot C:\Windows /s C: /f BIOS

If that fails, you will need to run a bootsect command to make sure the MBR has BOOTMGR code needed to boot.

My previous post reads:-

"Do you think I should still run

Code:
bcdboot C:\Windows /l en-us /s S: /f /UEFI

but obviously with the correct switches"

Ahh, the British. Gotta love 'em! But I do appreciate that your Navy allows real beer on the ships. We only got 2 beers after being at sea for 45 continuous days. Anyway, I edited my post after I did watch your video. Good day to you, sir. Glad you got it sorted out.

NavyLCDR said:

Ahh, the British. Gotta love 'em! But I do appreciate that your Navy allows real beer on the ships. We only got 2 beers after being at sea for 45 continuous days. Anyway, I edited my post after I did watch your video. Good day to you, sir. Glad you got it sorted out.

Cool! So we're cool, yeah?

Thanks for correcting. Ignore my latest post highlighting the switches element...

I am unable to delete it. Can you edit your post please after Good day to you, Sir! and others haven't read it yet or watched the video yet.

- - - Updated - - -

And sorry for biting back.

As you can imagine, it has been a really stressful 24 hours!!!!

No issues. I get grumpy sometimes. Thank you for the forgiveness!

NavyLCDR said:

Perhaps you should mark this thread as solved.

But I wanted it to be a surprise to those that helped.

FreeBooter said:

I thought i used All parameter instead of UEFI which applies to BIOS as well or execute bellow command.

Code:

bcdboot C:\Windows /l en-us /s S: /f BIOS

OK. So this is the current situation. Link to video on my OneDrive of what happens at start-up

https://1drv.ms/v/s!Ar8AkvzZJWl9h8N9...L961w?e=6RulyM

Do you think I should still run this code below which is a merge of what you and Navy LCDR sent?

Code:

bcdboot C:\Windows  /l en-gb /s C: /f BIOS

I don't think there is any need now. See video I posted earlier.