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

    • About bloody time. I have got PRs with hundred of files and the Web UI just struggling to even load the pages.
    • I wonder if it was applying secure boot certificates/dbx files?
    • I recently tried edge. It seems a lot better. A lot of the junk in it is gone. It seems less bloated and snappy.
    • Lethal fake phone chargers are still being sold on Amazon and eBay, UK watchdog warns by Paul Hill Credit: Pexels The UK consumer rights organization, Which?, is claiming that “potentially lethal knock-off chargers” are still being sold on online marketplaces seven years after it exposed the danger of these chargers. In its latest investigation, it bought 15 USB phone chargers from several online marketplaces and found they were missing key information, meaning they cannot be legally sold in the UK. Which? bought the 15 chargers from seven online marketplaces. These were Amazon (including Amazon Haul), AliExpress, B&Q Marketplace, Debenhams Marketplace, and eBay. It said that the chargers were so badly made that anyone using them was at risk of electric shock. Over half the chargers also posed fire and explosion risks. Of the chargers purchased, one was a fake Apple USB-C 35W power adaptor charger. To confuse buyers, the box was branded with an Apple logo, but testing found it to be a fake. Further testing picked up arcing sounds after 10 seconds of use, where a current jumps between two parts of the electrical circuit, which can cause fires, explosions, or electric shock. The manufacturers of this particular charger also put modeling clay inside it to make it feel more weighty, robust, and genuine. Not all of the chargers were technically faulty; however, some were missing key packaging, markings, and documentation, meaning they can’t be sold in the UK legally. Which? said that it is now campaigning alongside a coalition of safety groups and businesses for new laws that make online marketplaces responsible for ensuring the safety of products that they choose to list on their websites. It also said the government needs to start using powers under the Product Regulation and Metrology Act, which was adopted last July, to impose safety requirements on online marketplaces via secondary legislation, but so far, there have been delays. No matter what country you are in, be sure to properly research what you are buying and only buy authentic chargers to prevent fires. You can read more about Which?’s research here.
    • Visual Studio finally gets long-awaited feature that developers will love by Usama Jawad Visual Studio Code is Microsoft's popular, lightweight, open-source code editor, it is actually Visual Studio that is the company's flagship integrated development environment (IDE). Although the IDE already offers a boatload of useful features for developers, Microsoft has finally introduced a long-requested capability that will be loved by many. While developers have already been able to create Git pull requests (PRs) directly within Visual Studio for the past couple of years, it had not been possible to review a PR without switching to the browser, until now. Microsoft revealed in December 2025 that it is working on UX that enables developers to do just that, and fast-forward to June 2026, and Visual Studio finally has native capabilities to open and inspect a PR, discuss feedback, and wrap up the review, all without switching to the browser. This integration works for both GitHub and Azure DevOps (including on-prem). Developers have access to multiple surfaces to open a PR, including Git Repository, Git Changes, and the Git menu in Visual Studio. Once you open a PR, all the important details will be immediately visible to you, from where you can navigate to various levels of granularity and branch states, depending on the reviews that you are engaged in. As you would expect, you also get a diff view that enables you to see code changes inline or side-by-side in a separate panel. You can also review commit-by-commit. Additionally, this UX fosters collaboration as you can leave comments, reply to threads, and resolve conversations easily. Naturally, you can also leverage Copilot to apply a code suggestion to fix a potential issue. When you are done, you have the ability to approve, complete, and merge the PR. This is a pretty major feature as it has been requested heavily for the past few years. You can try it out in Visual Studio 2026 version 18.7, made available here recently. Microsoft plans to enhance this experience further in future releases with comment filtering, a timeline of PR activity, and more.
  • Recent Achievements

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

    1. 1
      +primortal
      499
    2. 2
      PsYcHoKiLLa
      174
    3. 3
      +Edouard
      160
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!