Disable UEFI in bios

[Lv80_Boots]

I have recently installed a Fatal1ty z170 k6+ mobo and I can't seem to find where in the bios to disable UEFI or to even to put it in legacy mode! Is there no way to do this?

 

[Darkbreeze]

Why, specifically, are you trying to disable UEFI or enable legacy mode?

The only two settings that pertain to this will be the enable/disable of the "boot manager" setting, and enable/disable of CSM (Compatibility support module). With CSM disabled it should be in full WHQL UEFI mode, with it enabled it should support both UEFI and legacy devices. Boot manager should, and I say should because I am not 120% certain of this, but it should either force or disallow the Windows UEFI boot manager or enable legacy style boot settings. You may need to play around with these two settings or contact ASRock as I see no other settings, same as you, that relate to UEFI or non-UEFI boot modes.

 

[photonboy]

Manual. Checking now...

 

[photonboy]

http://66.226.78.22/downloadsite/Manual/Fatal1ty%20Z170%20Gaming%20K6+.pdf

I'm guessing what you want is on Pg.103.

For better help tell us exactly what your purpose is. If running W8/W10 then ideally you want UEFI with Secure Boot enabled (to prevent boot-time malware infiltration).

As said above though, disabling UEFI, or more specifically enabling Legacy for specific devices is only done for unsupported hardware.

AFAIK there's no good reason likely for you to be enabling Legacy mode unless dealing with Linux. Even then, I suggest using a distro that's compatible.

Other:
To be clear, what you call the "BIOS" is now the "UEFI". People keep calling it the BIOS, and some call it the UEFI-BIOS so it's a bit confusing. You can't "disable the UEFI" really just workaround compatibility for some legacy devices that have issues with how UEFI works.

https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface

Note:
"..with most UEFI firmware implementations providing legacy support for BIOS services. "

Again, the legacy part is a workaround for older devices. I think some video cards required flashing their firmware to support UEFI or you needed to run a legacy mode.

 

[Lv80_Boots]

I can't install Windows 10 on my SSD drive and also have it as the boot drive it puts the boot manager on my HDD but Windows on my SSD. When I disconnect any of the HDD the installation goes to like 85% and crashes, my old asrock board doesn't allow for UEFI so I was able to test an install on it just fine to make sure the drive was still good. I'll have to to check again as I didn't look for "CSM" and the two manuals that come with the board don't say much of it

 

[photonboy]

https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Booting

You should read the entire BOOTING section.

 

[photonboy]

I can't install Windows 10 on my SSD drive and also have it as the boot drive it puts the boot manager on my HDD but Windows on my SSD. When I disconnect any of the HDD the installation goes to like 85% and crashes, my old asrock board doesn't allow for UEFI so I was able to test an install on it just fine to make sure the drive was still good. I'll have to to check again as I didn't look for "CSM" and the two manuals that come with the board don't say much of it

Okay, this is the info you should include when you post.

I'm a bit confused what you're doing here, but from what I can see your issue would be solved if you properly installed Windows 10 to the SSD.

It looks like you moved a W10 install from one machine to another? That's not how it's done. Unless W10 has changed things, I don't think the license is transferable but even if it was you would need to REINSTALL it.

1) Insert SSD (no other HDD/SSD)
2) Boot to W10 DVD/USB Installation media
3) DELETE any existing partitions
4) enter key if new, unactivated license (if upgrading existing W7->W10, activated install you would skip the key)
5) Finish install, drivers etc, verify activation.

*There's some variation on that depending on where you got your W10 license. You can also create a W10 Install media from MS media creation tool:
https://www.microsoft.com/en-ca/software-download/windows10

 

[Darkbreeze]

Yes, you would need to do a CLEAN install. Using different images won't work, and if you had Windows 10 installed on a different motherboard, then you'd need to reactivate through microsoft support, which they MAY or MAY NOT approve, depending on whether they feel generous that day since the license does not actually cover motherboard changes or moving the OS to a new system.

Usually they are pretty good about it, but you WILL need for the OS to already be installed on the new system, AND, activation should not affect that installing at all. It will show as not activated until you resolve that part of it, but it should not stop it from installing. In order to do a clean install you will need to disconnect all other drives, delete any existing partitions on the current target drive and then install to the unallocated space without creating any new partitions or performing any formatting. Windows will do that automatically. Follow these directions exactly, and it should not be a problem.

http://www.tenforums.com/tutorials/1950-windows-10-clean-install.html

 

[Lv80_Boots]

This is a clean install, if I try to install with no other drives there it crashes... Trust me I'm confused myself! But with a secondary drive there on the install it puts the boot partition on the secondary drive and will not boot from SSD as priority. This has stumped even my dad who is 40 years in the business. This is why I wanted to try the compatibility mode to see if I can even get it to install/boot from SSD.

 

[Darkbreeze]

That is because it is NOT a clean install. It might be a NEW install, but it is not a CLEAN install. A clean install would include a new boot partition, which windows would create automatically during the installation if there wasn't one already present, which there was, since windows was previously installed on the other drive and you did not disconnect that drive when you installed. As we already said, you need to disconnect the other drive and install a fresh copy of windows on the SSD. At NO point during this process should the HDD be connected, AND it would be a good idea to use a partition manager to remove the "system reserved" partition that is almost certainly still there on the HDD.

You might be able to remove it in Windows disk management, but sometimes a third party utility is necessary as windows sometimes doesn't like to allow the removal of "system" partitions. The fact that you cannot boot the windows installation on the SSD when the HDD is disconnected tells me all I need to know about where the boot partition that's being referenced during POST is located, which pretty much has to be on the HDD.

Disconnect the HDD, reinstall windows using the EXACT method outlined above at the link I provided, and once the installation has completed THEN you can reconnect the HDD.