Windows can't repair itself after BIOS update.

Toggle sidebar Toggle sidebar
J

Josh_216

Prominent
Jun 28, 2017
4
0
510
Hello everyone,

I own an MSI Z270-A Pro motherboard (that is about 3 weeks old) and I recently updated the BIOS to the latest version (E7A71IMS.120). The BIOS update was 100% successful, but when I try to start my computer it goes to a windows repair screen and I have attempted to repair the windows files manually through the command prompt. Now the problem is that in the command prompt, I cannot find the drive that windows is installed on to execute the sfc command. Windows is installed on a Samsung SSD 960 EVO that is in the M.2 slot on my motherboard. The SSD is showing up in the BIOS and it is set as Boot Option 1.

Also, I have two other hard drives connected and when I disconnect them and try to boot with just the SSD connected it gives me a message saying: "Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key". When this message comes up, I don't think I'm even able to get into the BIOS.

Thanks in advance!
 
Solution
G
Your hard disks were connected when you installed the OS and the boot partition was created on the first hard disk that it found (usually connected to port 0). The OS is installed on the SSD, but the HDD having the boot partition is required to boot from the SSD.
Sort by date Sort by votes
G

GhislainG

Titan
Jul 16, 2008
23,962
5
74,965
Your hard disks were connected when you installed the OS and the boot partition was created on the first hard disk that it found (usually connected to port 0). The OS is installed on the SSD, but the HDD having the boot partition is required to boot from the SSD.
 
Upvote 0 Downvote
Solution
J

Josh_216

Prominent
Jun 28, 2017
4
0
510
I see, that explains the message I am receiving when I disconnect my other HDDs. Any thoughts on why I cannot see my SSD when looking in DISKPART and at the volume list? I can't seem to do anything with my SSD through the command prompt because it won't show up and it is inhibiting me from manually repairing windows files that may be corrupt.
 
Upvote 0 Downvote
J

Josh_216

Prominent
Jun 28, 2017
4
0
510
UPDATE: ISSUE RESOLVED

Thanks for the replies GhislainG! It turns out that one of my old HDs I had plugged in had an old boot partition of windows that was corrupted from a previous build years ago. The problem was resolved when I unplugged just that HD, left the one that had the new boot partition plugged in, and then deleted the old boot partition that was causing the issue.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom