Recommended Posts

I have a MSI GT683 which has two hard drive bays. I recently decided to upgrade to Windows 8 and add a SSD. I didn't want to move my existing spindle drive to slot 2 because it is so close to the GPU and I worried about heat. Slot 1 is well isolated from other hot components so I left the spindle drive there and put the SSD in slot 2. I set the BIOS to boot from drive 2, the SSD

I installed Windows 8 on the SSD and all went well. In Windows the system drive shows up as C even though it is disk 2, the spindle is the D drive. Exactly what I wanted!!

The problem is that I get the typical annoying "no boot device available" every time I turn the computer on. If I press F11 and manually tell it to boot from the SSD then Windows 8 starts up fine. I know you are thinking "oh, he probably screwed up his boot order." No, I am 100% sure that the SSD is the only drive that appears in my boot order. I don't understand why it would fail to boot using the boot order, but it works when I manually select the drive.

My best guess is that the Windows installer wrote the MBR to my spindle drive instead of the SSD. Any advice on how to correct this? Using bootrec /fixmbr just fixed it so I can boot from the spindle, but that isn't what I want. I thought about using a 3rd party tool to copy the MBR from the spindle to the SSD, good idea or could that cause problems?

Link to comment
https://www.neowin.net/forum/topic/1151974-strange-windows-8-boot-problem/
Share on other sites

I am guessing the System Reserved Partition is on the HD and the rest of the OS is on the SSD.

To check please do this for me in an elevated command prompt (start CMD.EXE as Administrator):

diskpart

select disk 0

list part

select disk 1

list part

exit

Copy and paste the output here so I can have a look.

Also look here http://www.hanselman.com/blog/SwitchingMyWindows7BootDiskFromDToCWithBCDBootRatherThanBCDEdit.aspx

Tim

I don't have the laptop with me at work but I have run those commands and can tell you want they say. Note: the spindle (disk 0 on diskpart) had Windows 7 installed on it at the time I installed Windows 8.

Disk 0 (spindle with old Windows 7)

Part 1 has a 100 MB system reserved, was active but I changed it to inactive

Part 2 is the rest of the 750 GB as NTFS, D drive on Windows 8, was C drive of Windows 7.

Disk 1 (SSD, Windows 8)

Part 1 has a 350 MB system reserved partition listed as Active

Part 2 is the rest of the 180 GB as a NTFS partition, C drive

My plan is to format the old Win7 drive once everything is working correctly on Win8.

EDIT: I listed the drives backwards, fixed now.

Oh that's confusing. You got 2 System Reserved partitions.

Did you check out that link? That solution may work for you.

Hmmm just had an idea. You could just swap the SATA cables around at the MOBO end to re-order the way the BIOS sees them.

  • Like 1

Oh that's confusing. You got 2 System Reserved partitions.

Did you check out that link? That solution may work for you.

Hmmm just had an idea. You could just swap the SATA cables around at the MOBO end to re-order the way the BIOS sees them.

That might work. Being a laptop the cables are well hidden, but I could see if I can get in there and switch them. I will checkout the link the next time I get in front of the computer. Yes, the two system reserved is confusing. I probably should have just taken the leap and formatted that other drive before installing Windows 8.

Hopefully this asnwer does you some good but I have a MSI motherboard as well and I came across the no boot device available when I was replacing HDs around. There should be an option in the BIOS setting which allows you to prioritize which hard drive you want to be set as the first bootable hard drive (Not to be confused with bootable device, like DVD drive, USB and etc.)

Hope that helps

I give up, it looks like Windows is hard coded to assume the Boot Code needs to be stored on Disk 0. I just set the spindle drive to be first in the boot order, it now starts up fine. It does mean that my spindle drive needs to spin up for the computer to boot, which probably adds 2-3 seconds to my boot time. It also means that if I ever format or remove that drive I will need to run the Bootrec.exe or Bootsect.exe command to write the Boot Code again, but I am not too concerned about that. The Boot Loader and my OS are still on the SSD, and that is what really matters.

For anyone else having a similar problem and trying to figure out how Windows booting works, here is a simple explanation of the 4 parts needed to boot.

BIOS Settings - The BIOS settings tell the computer which boot device to use, it then reads that device's MBR for the Boot Code.

Boot Code - Tells the BIOS startup sequence where on the hard drive to start running code. Stored in the Master Boot Record (MBR) of the boot drive. This is the thing I can't seem to get Windows to create on any disk other than Disk 0

Boot Loader (BCD) - Called by the Boot Code, typically stored in the System Reserved partition. This contains the settings needed to boot Windows (including decrypting the drive if needed), also contains the code to select which OS to start in a dual boot environment.

Operating System - Called by the Boot Loader, the OS has has many layers of code called during startup, but not relevant to this discussion.

So for me this is what I have:

Boot Code: Spindle

Boot Loader: SSD

OS: SSD

I wish it was all on the SSD, but this works fine, I will not get overly picky

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Not such a great deal, Ultimate, which gives you full 5080 features is $181.99 CAD per month, that's $2183.88 per year, I can buy the 5080 for $1809.99 CAD, then it goes up to $279.99 per month after the first billing cycle. Typical cloud rental, costs more than buying the hardware.
    • Wow, spoken like a true blind hater, you don't even provide arguments. Please, go check my comment above to @seacaptain and you'll find out why what you say doesn't make sense in this context...
    • Get used to this, with AI tooling now uncovering new vulns and getting them exploitable far faster than has ever been possible before software is going to need to be updated far more frequently. Back in the day it may take reseachers weeks or months to do what AI can now do in hours. Once its a threat is discovered it's weaponsized far more quickly, meaning you simply can't be waiting 2, 3, 4 weeks to deploy a patch, it needs to be patched immediately. Going to be interesting handling this in the enterprise space where traditionally patching has been steady, but very staged (and rightly so up until now), that is going to have to change.
    • You don't need to "close all browser sessions constantly" or wait for updates to install. The updates download in the background while you use the browser, without interrupting you, they install automatically the next time you launch the app. And they install very fast (depending on your storage speeds, of course), you have to wait at most 2-3 extra seconds, if any. Seems like you haven't used Edge in a loooooooong time...
    • Segra 1.6.0 by Razvan Serea Segra is a free, open-source OBS-powered game recorder offering fast gameplay capture, instant clips, AI highlights, deep game integration, and seamless uploads—perfect for gamers, streamers, and content creators. Lightweight, fast, zero bloat. Segra key features: Automatic Game Recording: Begin capturing gameplay the moment your game launches, with zero manual setup. Instant Clipping: Save important moments instantly using a customizable hotkey—perfect for highlights, montages, or quick shares. Segra AI Highlights: Let Segra automatically detect kills, assists, deaths, and key events to generate polished highlight reels without manual editing. Gameplay Uploads: Upload recordings and clips directly to Segra.tv for fast sharing and cloud access. Deep Game Integration: Enjoy advanced game-data tracking across hundreds of supported titles, enabling smart highlight generation and stat-informed clipping. High-Performance Capture: Record up to 4K at 144 FPS using OBS-powered technology with minimal performance impact, supporting NVENC, AMD VCE, and custom quality controls. Segra Editor: Edit recordings easily with timeline controls, segment management, and event-based navigation to build the perfect clip. Customization Options: Adjust hotkeys, output formats, storage paths, codecs, capture quality, and performance settings for a tailored recording experience. Segra 1.6.0 changelog: Recording: Added HDR support. Grand Theft Auto: Added game integration for deaths (FiveM and RAGE MP supported). Highlights: Added customizable padding for highlights. Replay Buffer: Added a shockwave visual effect when a replay buffer clip is saved. Audio: Increased the maximum sound effects volume from 100% to 200%. Hotkeys: Fixed hotkeys not triggering while unrelated keys were held. Installer: Added code signing to verify publisher identity, branded the installer, and reduced OS security warnings. OBS: Updated the supported OBS version to 32.1.2. Download: Segra 1.6.0 | 74.4 MB (Open Source) View: Segra Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
    • Rookie
      FBSPL went up a rank
      Rookie
    • First Post
      davidbazooked earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      PsYcHoKiLLa
      174
    3. 3
      +Edouard
      163
    4. 4
      Steven P.
      86
    5. 5
      ATLien_0
      80
  • Tell a friend

    Love Neowin? Tell a friend!