PC won't boot to Windows 10 from SSD

Anonymous

I bought my PC years ago with only a HDD. I added a SSD myself afterwards. When I booted my PC after a hard shutdown/electricity fallout I had only my HDD in BIOS. I then boot from HDD, get an error and let the PC reboot. After a few times the SSD would be recognized in BIOS and I could change the SSD to default.

I got tired of this proccess a few days ago and found a tip to disable the hdd-partition with diskpart. The first time I had a hardreset again (mouse and keyboard froze and pc didn't shutdown with a single press on startbutton), I couldn't do the HDD boot-trick and tried changing the cables from hdd to ssd (ssd in sata1). This didn't help. In diskpart I made the SSD partition active. I now can see the SSD in BIOS, but booting gives an error "An operating system wasn't found.". When I retry diskpart, the partition could be made active again. It seems like this resets..

Bootrec.exe /FixMbr was successful

Bootrec.exe /FixBoot gives no access error (there could be some parts left of a dual boot setup)

chkdsk gives no problems found

Mediatool boot:

This PC can't be recovered with start-uprepair.
You need to choose which installation of Windows you would like to put back when using Systemrecovery.
Reboot, select a operating system and select Systemrecovery. No systemcopy available.

How could I make my pc boot again?

PC: MEDION AKOYA P5367 D EU (MSN: 10015458)

Motherboard: MS-7728

BIOS version: E7728MLN.209

SSD: Kingston SV200 (128GB)

HDD: ST1509DL003-9V (1500GB)

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

107 answers

Anonymous

2018-08-22T14:19:55+00:00
Thanks for the clear reply. I'll answer your questions and try your suggestions as soon as possible!
- BIOS is UEFI
- SSD is (now) visible in BIOS op both places
- If I am right, I can only run Diskpart and Boot Repair from the bootable installation media, because the OS isn't booting. I can't get it in safe mode either.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2018-08-22T15:10:30+00:00

Hi,

Part of the problem may be with how your Installation Media was created...

Like I mentioned before, but the opposite... Or that you need to boot with it differently... That would explain the Bootrec.exe /FixBoot gives no access error

What you might look for is "UEFI" boot device in the BOOT OPTIONS menu on the manufacturer's screen where you enter Bios... Just a different key...

Something like ESC, F9, F11, F12...

You might see something like "UEFI Optical Drive", or "UEFI USB", as opposed to simply "Optical Drive" for instance...

A Flash Drive for UEFI Bios should be "Initialized" as GPT (GUID) and have a file system of FAT32...

A Flash Drive created for Legacy Bios using a MBR Initilized drive, formatted as NTFS MIGHT work if you select it as a "UEFI" drive in Boot Options...

GPT drives as required for a boot device in UEFI machines do not use "Active""Not Active"... It is not a valid setting for a GPT drive..

BTW... UEFI machines use "WindowsBootManager" as the Boot Device, not the actual drive\partition it is on... (EFI Partition)...
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2018-08-22T19:01:37+00:00

BIOS indeed names the mediatool usb UEFI and it is already FAT32 formatted.

I made the HDD partition active.

BOOTREC /FIXMBR -> success

BOOTREC /FIXBOOT -> access denied

BOOTREC /REBUILDBCD -> 1 installation found on D: (SSD). When I accept the installation to boot list, I get an error: systemdevice not found.

My volumes (according to diskpart) are mixed up: C: = HDD, D: = SSD (which was the opposite).

EDIT: I can make the partition of the SSD active again. This seems not to be saved, closing diskpart and opening it results in the same statusupdate. I even can mark it as active or inactive twice and not get a message that it currently is one of them already.

EDIT2: In GParted the SSD has a boot flag, meaning it is active already.

EDIT3: I can boot the USB as "USB KEY", not as UEFI. After that the BUILDBCD works again, FIXBOOT still access denied. I do see Go to WIndows 10 Home, but immediately got a reboot then. Same operating system wasn't found when booting from SSD.
Was this answer helpful?

0 comments No comments
Anonymous

2018-08-23T01:00:05+00:00

Hi,

I'm surprised Gparted will make anything Active on a UEFI machine with a GPT drive... That is not supposed to be possible...

GPT drives no not use "Active" for the Boot Device... UEFI machines boot from the Windows Boot Manager that is located on a 150MB or so, Fat32 partition...

Only the older Legacy Bios uses "Active" partitions for the boot device...

Regardless... Your Boot Device would be the EFI partition... Not the entire SSD..

Do you have a EFI partition on both drives , or just possibly the HDD ?

I think you need to select "UEFI USB Key" if there is such a thing...

Not in your Bios, but the Boot Options menu I mentioned... This is separate from the actual Bios and usually displays more "One Time" Boot Options...

I can't find any pictures of what Gparted flags look like as far as "Active" or "Boot Device"...

I'm just about positive the errors you are getting with the BootRec stuff is because of how you are booting with the flash drive... I recently had a similar problem...

BTW... What Windows Build is on the Flash Drive... Build 16299 has issues with some of it's repair functions
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2018-08-23T11:33:43+00:00

MediaCreationTool1803 was on the USB stick.

A repairstation created on the newest version of Windows 10 has the same results as above.

Both don't have a EFI-partition, but do have a EFI folder on the root.

See some screenshots attached.

When I disable Legacy USB Support (like below) the USB drives for repair aren't found.
Was this answer helpful?

0 comments No comments