How to make ssd bootable with with fresh install of windows 10

[shsesc]

Mx500 is not directly bootable I get trouble loading os message. I installed windows on this mx500 ssd with windows USB installation media made with media creation tool. I was trying to replace my 240gb ssd with a larger 500gb one. I tried cloning with the software that came with the crucial mx 500 ssd but that wasn't bootable either so I did a fresh install on the crucial mx500 and ran into this problem.

In my bios if I select the mx500 as primary boot device it gives me the trouble loading os message. If I select my hdd it gives me the option to load either ssd, the old or the new, regardless of whether the old one is attached, via windows manager. The mx 500 does not have the uefi symbol on it the only thing that does is the hdd I used for storage and the bootable installation media on usb. Why would that be?
I want to make this fresh install bootable since I've already installed all my music production software again.

 

If you need more info let me know.  Thanks 

[Tabs]

12 minutes ago, shsesc said:

Mx500 is not directly bootable I get trouble loading os message. I installed windows on this mx500 ssd with windows USB installation media made with media creation tool. I was trying to replace my 240gb ssd with a larger 500gb one. I tried cloning with the software that came with the crucial mx 500 ssd but that wasn't bootable either so I did a fresh install on the crucial mx500 and ran into this problem.

In my bios if I select the mx500 as primary boot device it gives me the trouble loading os message. If I select my hdd it gives me the option to load either ssd, the old or the new, regardless of whether the old one is attached, via windows manager. The mx 500 does not have the uefi symbol on it the only thing that does is the hdd I used for storage and the bootable installation media on usb. Why would that be?
I want to make this fresh install bootable since I've already installed all my music production software again.

 

If you need more info let me know.  Thanks 

It sounds like it's a non-UEFI Windows 10 install on a UEFI system.

 

You may be able to make it bootable by enabling "CSM" in your bios.

 

Note that this means you lose functionality like secure boot and fast boot.

[shsesc]

This drive is not cloned, it is a fresh install.

I can access the installation, but it is done through a selection screen which it shows whether the old ssd is connected or not. 

  How do I create a uefi installation of windows?  I did not see it as an option when I went through the installation steps. 

Is there a way to use DISKPART to make this installation uefi bootable? 

[Tabs]

2 hours ago, shsesc said:

This drive is not cloned, it is a fresh install.

I can access the installation, but it is done through a selection screen which it shows whether the old ssd is connected or not. 

  How do I create a uefi installation of windows?  I did not see it as an option when I went through the installation steps. 

Is there a way to use DISKPART to make this installation uefi bootable? 

Ah, I understand what you mean now - you want the boot menu that allows you to pick your install to not be there, and instead only boot you to the new ssd directly?

 

You can do this using the command line utility bcdedit from an administrator command prompt. You'll want to delete the entry for the old operating system, and set the correct one as default. I can give you more specific instructions if you're able to take a screenshot of bcdedit.

 

Alternatively there are programs you can download to modify your bcd (boot configuration data) store, but I've always used bcdedit.

[shsesc]

On 7/30/2018 at 12:00 PM, Tabs said:

Ah, I understand what you mean now - you want the boot menu that allows you to pick your install to not be there, and instead only boot you to the new ssd directly?

 

You can do this using the command line utility bcdedit from an administrator command prompt. You'll want to delete the entry for the old operating system, and set the correct one as default. I can give you more specific instructions if you're able to take a screenshot of bcdedit.

 

Alternatively there are programs you can download to modify your bcd (boot configuration data) store, but I've always used bcdedit.

Here is what I see with the old SSD detatched when I type BCDEDIT into powershell with admin. I've included the disk management screen so you can see what I have attached. 

I want to boot solely from the 500GB mx 500 which is listed as disk 1.   

Disk 2 was my old storage hdd and is still  mounted internally I don't know why it has the boot section on it or why it is listed as dynamic, it is only one hdd.

Disk 0 is my music software and samples ssd (internally mounted) and is plugged into Sata port 12 on my sabertooth 990fx motherboard so I don't know why it is listed as 0.  

Disk 3 and 4 are extra backup drives (external usb 3.0) I store photos and personal files and  such on. 

Disk 9, ESD-USB, is the windows media created by  windows media creation tool on a 8gb sandisk flash drive.

 

What do I need to do in BCDEDIT to be able to have the EFI system partion be on disk 1 so that it boots from that drive alone?  Am I misunderstanding the problem?

 

 

I know I could just set the wait to 5 seconds and ignore it, but then I'll be stuck if something changes with my hdd. 

 

If there is no way to change it now, after the fact, how do I reinstall windows on the MX500 500GB ssd and make it only boot from that disk?  I'd rather reinstall everything once now than have issues later.  

 

Thank you for taking the time to answer this.

 

 

 

 

[Tabs]

Okay, type this command into an administrator command prompt or PowerShell window.

 

bcdedit /delete {5e0f8863-912d-11e8-bdde-d754ac6fe1cf} /cleanup

 

This will remove the second entry form the options, and the /cleanup switch will remove it from the boot menu entirely.

 

Be VERY VERY careful. You have two GUID's there that are very similar, only separated by one digit. I checked my command three times to ensure it is the right one, so assuming you trust me, you can copy/paste it to ensure you don't make your system unbootable.

 

If you want to understand the command, you're trying to delete the entry relating to the GUID listed at the bottom as being "device unknown", the old install that you don't want in your order any more.

 

You'll see that your current GUID is  {5e0f8866-912d-11e8-bdde-d754ac6fe1cf}.

You need to delete the earlier (lowered number) one - {5e0f8863-912d-11e8-bdde-d754ac6fe1cf}.

 

If you have any questions or concerns please ask before running the command.

[shsesc]

5 minutes ago, Tabs said:

Okay, type this command into an administrator command prompt or PowerShell window.

 

bcdedit /delete {5e0f8863-912d-11e8-bdde-d754ac6fe1cf} /cleanup

 

This will remove the second entry form the options, and the /cleanup switch will remove it from the boot menu entirely.

 

Be VERY VERY careful. You have two GUID's there that are very similar, only separated by one digit. I checked my command three times to ensure it is the right one, so assuming you trust me, you can copy/paste it to ensure you don't make your system unbootable.

 

If you want to understand the command, you're trying to delete the entry relating to the GUID listed at the bottom as being "device unknown", the old install that you don't want in your order any more.

 

You'll see that your current GUID is  {5e0f8866-912d-11e8-bdde-d754ac6fe1cf}.

You need to delete the earlier (lowered number) one - {5e0f8863-912d-11e8-bdde-d754ac6fe1cf}.

 

If you have any questions or concerns please ask before running the command.

Where did you see the identifier for The "Current" drive?

 

Do I need to do a  bcdboot c:\windows   to make this boot from the current drive after deleting the "unknown" entry?

[Tabs]

Now that I've included that information on what you need to do to fix this, I'd like to answer one of your main questions from your post.

 

The reason this happened is that you installed Windows when there was already a disk installed in the machine set as a "system" drive, with an EFI partition. Windows will automatically use the same bootloader if another install is already present, meaning that you're stuck now with your hard drive containing your boot order.

 

If your hard drive dies or is removed, your SSD will become unbootable without being regenerated, which is hard to do when the system is already configured like this.

 

To prevent this in future, remove any non-data partitions from the drives you do NOT want windows on. This happened because Windows detected the EFI partition on Disk 2 during install, and used that as it's default boot configuration data store.

 

 

In your case, reinstalling and sorting this issue permanently would involve doing the following steps now:

 

1. Boot the windows installer as you did previously (either dvd or usb, whichever is easier for you).

2. When you get to the partition selection page, delete the EFI system partition on the 3TB disk listed as "Disk 2" in your above screenshot. Be careful not to delete the data partition on that disk, only the EFI partition which is 100MB in size.

3. Erase all partitions off the 500GB SSD so that it shows nothing but "unallocated space".

4. Try to create a partition on the 500gb SSD covering the whole drive. You should get a message saying windows will make extra partitions to function properly. Confirm this message, and then ensure that the EFI system partition, possibly a "recovery" partition, and the partition you just tried to create are all on the same 500GB ssd.

 

At this point, as long as all of those are on the same drive, you can select your newly created large partition and hit next.

 

That'll prevent this being an issue in future, and for future installs of Windows.

 

[Tabs]

7 minutes ago, shsesc said:

Where did you see the identifier for The "Current" drive?

 

Do I need to do a  bcdboot c:\windows   to make this boot from the current drive after deleting the "unknown" entry?

 

You can see your {current} guid by looking at the {bootmgr} config. The {resumeobject} GUID is the identifier for your currently running installation should you put your computer to sleep. It's the only GUID in the {bootmgr} block that isn't referenced anywhere in the config for the old and obsolete entry.

 

No, you won't have to set bcdboot. The /cleanup command automatically removes the entry you delete from the boot order; and if the boot order has only one entry, you do not get a selection, it simply boots straight to it.

 

If you're concerned, before running the command I posted before, run bcdedit  /export "X:\some\usb\drive\backupbcd". Then, after running the command, run bcdedit again and post the screenshot here for me to examine. That will allow you to have a backup of your current configuration that you can access from the Windows PE environment that you can restore from if something goes wrong.

 

If you wish to prevent this becoming an issue in future, you can follow my reinstallation instructions instead; either way it will fix your immediate problems, but reinstalling will allow you to replace or remove/reformat the 3TB drive in future without breaking your boot order.

Edited August 1, 2018 by Tabs
More info

[shsesc]

4 minutes ago, Tabs said:

Now that I've included that information on what you need to do to fix this, I'd like to answer one of your main questions from your post.

 

The reason this happened is that you installed Windows when there was already a disk installed in the machine set as a "system" drive, with an EFI partition. Windows will automatically use the same bootloader if another install is already present, meaning that you're stuck now with your hard drive containing your boot order.

 

If your hard drive dies or is removed, your SSD will become unbootable without being regenerated, which is hard to do when the system is already configured like this.

 

To prevent this in future, remove any non-data partitions from the drives you do NOT want windows on. This happened because Windows detected the EFI partition on Disk 2 during install, and used that as it's default boot configuration data store.

 

 

In your case, reinstalling and sorting this issue permanently would involve doing the following steps now:

 

1. Boot the windows installer as you did previously (either dvd or usb, whichever is easier for you).

2. When you get to the partition selection page, delete the EFI system partition on the 3TB disk listed as "Disk 2" in your above screenshot. Be careful not to delete the data partition on that disk, only the EFI partition which is 100MB in size.

3. Erase all partitions off the 500GB SSD so that it shows nothing but "unallocated space".

4. Try to create a partition on the 500gb SSD covering the whole drive. You should get a message saying windows will make extra partitions to function properly. Confirm this message, and then ensure that the EFI system partition, possibly a "recovery" partition, and the partition you just tried to create are all on the same 500GB ssd.

 

At this point, as long as all of those are on the same drive, you can select your newly created large partition and hit next.

 

That'll prevent this being an issue in future, and for future installs of Windows.

 

That Explains it, THANK YOU!  I will probably end up following the enumerated steps quoted above so that I don't have issues in the future. 

[shsesc]

When I copy and paste I get this ...
PS C:\Windows\system32> bcdedit /delete {5e0f8863-912d-11e8-bdde-d754ac6fe1cf} /cleanup
The delete command specified is not valid.
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.

[Tabs]

1 minute ago, shsesc said:

When I copy and paste I get this ...
PS C:\Windows\system32> bcdedit /delete {5e0f8863-912d-11e8-bdde-d754ac6fe1cf} /cleanup
The delete command specified is not valid.
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.

Can you try copying it into notepad first, and then copying it from notepad into cmd?

 

It may be copying from the forum as rich text and adding character control codes into the command.

[shsesc]

1 minute ago, Tabs said:

Can you try copying it into notepad first, and then copying it from notepad into cmd?

 

It may be copying from the forum as rich text and adding character control codes into the command.

I tried that as well as copying the GUID from the powershell and typing the rest myself.  same error.

[Tabs]

3 minutes ago, shsesc said:

I tried that as well as copying the GUID from the powershell and typing the rest myself.  same error.

 

You could try adding the /f parameter to force deletion of the entry, like so:

 

bcdedit /delete {5e0f8863-912d-11e8-bdde-d754ac6fe1cf}  /f /cleanup

 

However, I didn't believe the /f parameter would be needed since it is not an entry listed in your configuration as having a well-known identifier.

 

I would recommend backing up your bcd data prior to this, and if it completes successfully, take a screenshot afterwards.

 

If something goes wrong, do not reboot; instead restore from the bcd configuration store - or be prepared to follow my reinstallation instructions I mentioned before.

[shsesc]

 With /f added same error.

[Tabs]

Just now, shsesc said:

 With /f added same error.

In that case, I think reinstallation may be your only way to fix this problem properly.

 

I'm sorry my previous instructions didn't help to give you a temporary fix. I've only encountered this problem twice before and I've been able to remove the obsolete entries with no issue.