windows and macOS is conflicting

[goku223344]

Ok, this is weird. I woke up today to find out that my Windows 10 has a Blue screen Of Death. It says Bad System Config. I have windows 7 and 10 installed on my computer and also MacOS sierra. When I go into the boot option it says bootable windows manager on my drive that has the MacOS sierra. And I can't boot from the drive that actually has the windows 10 OS. So I booted up my Windows 7 and all the drives look normal. THe drive with the windows 10 has all the files for W10. And the drive for the Hackintosh has all the files for the Hackintosh. It's just when I turn my computer on my computer mistakes my Hackintosh for a Windows drive. Do anyone have a fix?

 

[UtterDisbelief]

Ok, this is weird. I woke up today to find out that my Windows 10 has a Blue screen Of Death. It says Bad System Config. I have windows 7 and 10 installed on my computer and also MacOS sierra. When I go into the boot option it says bootable windows manager on my drive that has the MacOS sierra. And I can't boot from the drive that actually has the windows 10 OS. So I booted up my Windows 7 and all the drives look normal. THe drive with the windows 10 has all the files for W10. And the drive for the Hackintosh has all the files for the Hackintosh. It's just when I turn my computer on my computer mistakes my Hackintosh for a Windows drive. Do anyone have a fix?

Hi there.

I have seen quite a few messages on here recently saying that the Windows Boot Manager is causing problems booting.

I am not sure if a recent Windows update has changed something, but the problems seem quite common now.

Basically, as a rule of thumb, you should not have a Windows Boot anything on your macOS drive. However you would expect that if the Windows drive is intact and has no Mac EFI on it, that it should boot. Can you boot it using the F12 Gigabyte boot selection menu?

 

[goku223344]

Hi there.

I have seen quite a few messages on here recently saying that the Windows Boot Manager is causing problems booting.

I am not sure if a recent Windows update has changed something, but the problems seem quite common now.

Basically, as a rule of thumb, you should not have a Windows Boot anything on your macOS drive. However you would expect that if the Windows drive is intact and has no Mac EFI on it, that it should boot. Can you boot it using the F12 Gigabyte boot selection menu?

Both my windows and Mac OS is on separate ssd, and all of this happened when I was asleep so Idk exactly what caused this lol. But when I try use f12 it says that my Mac drive is the windows boot manager and my windows boot manager is nowhere to be found

 

[UtterDisbelief]

Both my windows and Mac OS is on separate ssd, and all of this happened when I was asleep so Idk exactly what caused this lol. But when I try use f12 it says that my Mac drive is the windows boot manager and my windows boot manager is nowhere to be found

Yes, that seems to be the problem - the Windows Boot Manager getting written to the macOS drive boot sectors. At least, that is what seems to be happening and is reported by the BIOS. By coincidence my own setup is on two SSDs and I haven't (yet!) had this problem.

You can use the Terminal command version of "diskutil list" to see what partitions are hidden where.

I think the problem might happen when Windows is installed on the system first. Hard to pin down though. You might be able to refresh the BIOS with only the Mac drive attached. Might clear the menu. Not sure if it will persist though.

So check what partitions are where first. Check with the Windows drive disconnected - does the Windows Boot Manager still show in the F12 BIOS menu?

 

[Going Bald]

Yes, that seems to be the problem - the Windows Boot Manager getting written to the macOS drive boot sectors. At least, that is what seems to be happening and is reported by the BIOS. By coincidence my own setup is on two SSDs and I haven't (yet!) had this problem.

You can use the Terminal command version of "diskutil list" to see what partitions are hidden where.

I think the problem might happen when Windows is installed on the system first. Hard to pin down though. You might be able to refresh the BIOS with only the Mac drive attached. Might clear the menu. Not sure if it will persist though.

So check what partitions are where first. Check with the Windows drive disconnected - does the Windows Boot Manager still show in the F12 BIOS menu?

This is a common problem when the Windows drive is not connected to the first port the UEFI scans as the system boots up. Windows wants to be FIRST ALWAYS. The way to avoid this problem is to make sure the Win10 drive is connected to the first port the system scans for presence of a drive. Generally, this may be done by disabling the splash screen of the board UEFI so you can see what is happening and noting the order of the ports as the system scans and boots up. Usually, the board OEM numbers the SATA ports with the first port having the lowest number, but I am not sure how it is handled with the M.2 slots. If you have M.2 slots, they will probably be first, but determining which is which when you have more than one can be a problem. In general, the one closest to the CPU is most likely to be first due to physical system architecture.

 

[UtterDisbelief]

This is a common problem when the Windows drive is not connected to the first port the UEFI scans as the system boots up. Windows wants to be FIRST ALWAYS. The way to avoid this problem is to make sure the Win10 drive is connected to the first port the system scans for presence of a drive. Generally, this may be done by disabling the splash screen of the board UEFI so you can see what is happening and noting the order of the ports as the system scans and boots up. Usually, the board OEM numbers the SATA ports with the first port having the lowest number, but I am not sure how it is handled with the M.2 slots. If you have M.2 slots, they will probably be first, but determining which is which when you have more than one can be a problem. In general, the one closest to the CPU is most likely to be first due to physical system architecture.

Ah, interesting. Thanks

I haven't explored yet, but have seen that some motherboards disable certain SATA sockets when an m.2 is present. Not sure of the differences between SATA m.2 and NVME