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-27T16:17:10+00:00

Hi,

Some of the stuff like Eset need to actually be removed... Not just uninstalled... removed with a tool from Eset, for instance...

I'm not sure if that is the error the A\V stuff causes though..

Try this... I mentioned before... Use Partition Wizard to delete the contents of the Downloads Folder of the System Reserved Partition...

Then try the Repair Install again with out the flash drive...

If that doesn't work, you might try deleting the 548MB System Reserved partition, and resizing the OS partition to fill in the space...

Some of this is getting deep, so if you feel uncomfortable with something, say so...
Was this answer helpful?

0 comments No comments
Anonymous

2018-08-27T15:44:49+00:00

I just finished the install from within Windows and USB drive and HDD hooked on:

0x80070002 - 0x20009 SAFE_OS with PREPARE_ROLLBACK

No other external drives and ESET anti-virus off.
Was this answer helpful?

0 comments No comments
Anonymous

2018-08-27T15:26:46+00:00

Hi,

I will leave it up to you to decide what next...

Did the install continue with out the HDD hooked up and flash drive plugged in ?

I know one generated an error about the System Reserved, and another about the Safe_OS Phase, but lost track of which...

I will have to put all the communications on a PDF or something, I think..
Was this answer helpful?

0 comments No comments
Anonymous

2018-08-27T15:20:33+00:00

This install from within Windows stops at "Checking if there is enough free space available". When I plug in the USB drive again, the install is continued..
Was this answer helpful?

0 comments No comments
Anonymous

2018-08-27T15:07:02+00:00

Something else to check out of curiosity... Look in MSCONFIG at the BOOT Tab... Do you see more then one OS listed ?

Only 1 OS, Windows 10 Home (marked as current)

Another option would be to try the repair again with the HDD hooked up and "Not Hidden"... Maybe the needed boot files can be found there, since it was hooked up when you installed Win 10 to the SSD...

I am now trying this.
Was this answer helpful?

0 comments No comments