Sign in with
Sign up | Sign in
Your question
Solved

Can't boot Windows 7: Reboot and select proper boot device; diskpart, there are no fixed disks to show

Last response: in Systems
Share
March 29, 2013 10:03:16 AM

Hey everybody,

Having some issues with a new build. I'll try to write concisely so there's minimum wall of text, and I would greatly appreciate any advice.

What happened:
I have no optical drive, installed Windows 7 64 off a USB and successfully started Windows. Used another USB to try to install AVG antivirus, but apparently you need to be connected to the internet to install. So I put in my PCI wireless card, used another computer to download the drivers off Asus' website, put the driver on a USB, plugged in that USB and it froze my computer. I could move the mouse around however nothing would respond (clicks, keyboard).

So I hit reset on my case, get POST but get message: Reboot and select proper boot device or Insert Boot Media in selected Boot device and press a key. Having my W7 USB plugged in and pressing a key just returns the same message. I tried setting up my W7 USB again but that has not fixed it.

I can get in BIOS and start the W7 install, but am not able to install (no drives are recognized), nor can I repair (again, no drives are found). Using command prompt from the "language" screen on W7 install, then:
>diskpart
>list disk
I get the message "there are no fixed disks to show". CMD is already being run as administrator at that point.

So this is where I'm stuck. Some reading has me worried that his might be a rootkit, but I'm totally lost as to what to do. Again, any help is appreciated.

Specs:
Gigabyte GA-Z77-HD3
Crucial M4 256 GB
i5-3350P
Powercolor HD7870 Tahiti LE (ez edition)
Corsair Vengeance 8GB LP
SeaSonic G Series SSR-550RM 550W
ASUS PCE-N15 (wireless card)
March 29, 2013 10:26:12 AM

Have you removed any other internal HDs recently? most likely your boot sector is messed up. If you installed windows on the computer with more drives then just the C drive, then removed one of the drives, the computer refuses to boot because what it sees as a vital part of it is missing. place back all drives, flash included, into the computer that was in it when you first installed windows.

If it came with windows installed, and just started doing this then your computer may or may not have been incorrectly shut down and the computer did not have enough time or power to save the neccisary files and configurations resulting in a missing or corrupted boot sector.

m
0
l
March 29, 2013 10:27:17 AM

basically, it considers your flash drive as essential. I would go into your computer and make sure that your boot order doesnt include the flash drive, and worst case, you might need another fresh install.
m
0
l
Related resources
March 29, 2013 10:41:12 AM

Hi Tidus, I have no other HDDs (just my single SSD). I built this computer myself.

I have to apologize - I didn't think to do this until after I posted this message. I swapped both the Sata cable and the power connection for my SSD, and now the drives are recognized! I did 3 startup repairs (recommended on another site), the first time the Root cause found was system volume on disk is corrupt, file disk repair (chkdsk) was successful. The other two repairs didn't find any problems.

I went into BIOS and set my SSD to as my boot drive (otherwise I was still getting Reboot and select proper boot device), and I'm back in Windows. I'm having a friend come over to temporarily use an optical drive... I'd rather not go through this again. But thank you, for your very quick response.

I'm still puzzled though, as to what exactly caused this problem. As I stated, before the problem, I'd booted just fine. I don't see why either my Sata/power cables suddenly stopped working, and replacing them allowed me to repair my startup?
m
0
l

Best solution

March 29, 2013 10:47:14 AM

im thinking there was something wrong with one of the conections.
and replacing the cords and resetting the boot order from flash to SSD fixed the fact taht it was looking for your flashdrive, but not finding it. it didnt register that your SSD was an acceptable boot, so it just called errors.

glad i was able to provide some assistence
Share
!