Win10 modifications to UEFI/BIOS

Topic

New Reply

I have a question regarding what Win10 does to a UEFI/BIOS. I understand on some systems it stores data (I believe licensing or Activation data) in the UEFI.

My question is “does this action have any effect on what UEFI/BIOS settings are available for changing?” and “if a system originally had a Win10 install (either OEM or User) would this have an effect if the system was repurposed for another (non-Windows) OS?” Searchs here have not given me an answer.

In a nutshell, is the machine limited after a Win10 install?

1 user thanked author for this post.

Kirsty

Reply | Quote

Replies

If you’re talking about the SLIC tables, they’re something that computer OEMs install into the firmware to make Windows (of the correct version) activate automatically when it is installed on that PC.  I’m not sure of the specifics (like whether you need to use the OEM version of Windows from your computer’s manufacturer or if the generic OEM images will work without modification), but the gist is that the product key is embedded in the firmware.  Windows 7 used general keys for different computer manufacturers and Windows editions, while Windows 8 and beyond use individual keys in each PC.

This does not affect your ability to install other OSes on the PC.  You can put Windows, Linux, etc., on the PC without any trouble because of the SLIC info in the firmware.  It’s done by the OEM at the time the PC is manufactured, not when you install Windows 10 on the PC yourself, if you decide to do so.

It’s also possible there was some other thing that I haven’t heard about, and that it’s not the SLIC tables that you are referring to.  In that case, all I can tell you is that the three new (manufactured 2017 or 2018) laptops I bought with Windows 10 already on them work or worked just fine with Linux, while 8.1 installed and ran on both of the ones I tried to put it on, but didn’t run ideally because of a lack of 8.1 drivers.

My desktop PC, one that was originally manufactured and sold in component form, had Windows 10 on it for a while, but it now runs 8.1 and Linux without issue.  It uses UEFI, and all the disks in the system (like all my UEFI PCs) are all UEFI/GPT partitioned.  The only MBR partitioned system I have left is my 2008 Core 2 Duo, which uses BIOS.

Windows 10 hasn’t caused any of my PCs to have any issues with installing other OS versions, in other words.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon 6.2
XPG Xenia 15, i7-9750H/32GB & GTX1660ti, Kubuntu 24.04
Acer Swift Go 14, i5-1335U/16GB, Kubuntu 24.04 (and Win 11)

1 user thanked author for this post.

Bill C.

Reply | Quote

Many thanks. Actually, I was not sure if I was asking about the SLIC tables specifically. I guess with all the talk of MS “owning” the hardware, I wanted to be ultra double sure. LOL

I was just asked if I wanted a Skylake box with Win10. I do not want Win10, but depending on the maker and details of the system, I may consider it as a Linux machine to play and educate myself on virtualization.

Reply | Quote

Were you maybe referring to secure boot?  https://www.howtogeek.com/175641/how-to-boot-and-install-linux-on-a-uefi-pc-with-secure-boot/

Here is some good general info on UEFI:

What Is UEFI, and How Is It Different from BIOS?

https://www.howtogeek.com/56958/

What You Need to Know About Using UEFI Instead of the BIOS

https://www.howtogeek.com/175649/what-you-need-to-know-about-using-uefi-instead-of-the-bios/

Windows 10 Pro 22H2

2 users thanked author for this post.

Elly, Bill C.

Reply | Quote

JohnW:

That “may” be what I remember reading about. I just remember it had to do with Win10 machines.

So far I have installed Linux on 3 UEFI machines with no issues, but none of them had Win10 on them or secure boot enabled, and it was easy to get into the UEFI and make a change to the Secure Boot and also the Fast Boot (which I do not enable as I want to see any warnings or startup messages).

I had not been focusing on these features as I am doing a new hardware build with a new distro, but this new offer made me think back. I just did not want to hit the dreaded ‘grayed out’ settings block.

Thanks for the links, they are now in my library of links.

Reply | Quote

I have installed Linux, Win 7, and Win 10, on retail motherboards with UEFI.  So far no issues.

I recall hearing talk a few years ago about secure boot, but my impression was that only enterprise systems were being locked by default, so I have never seen that.

Windows 10 Pro 22H2

1 user thanked author for this post.

Bill C.

Reply | Quote

All three of the UEFI laptops I put Linux on recently (2018) have shipped with Win 10 Home with secure boot enabled.  I simply turned it off… no problem.  The laptops consisted of a low-end Dell, a midrange Dell gaming model, and a low end Acer.

I believe that MS initially required OEMs to ship with secure boot enabled, but that it be optional (in the 8.1 days, if I recall) on regular PCs (meaning the user of the PC can turn it off), but that they now just require that secure boot be enabled and do not any longer require that it be optional, leaving that up to the OEM.  Still, I don’t imagine there will be many OEMs that will ship with Secure Boot permanently enabled.  It would cut off the buyers who may be looking to install a non secure-boot OS with no upside to the OEM (unless MS made them a sweetheart deal of some kind).  I definitely would return any PC that wouldn’t let me turn it off!

After I migrated to Mint 19 on the Acer, I noticed that an update for GRUB was available, and it said in the name that it was “signed.”  After installing it, I rebooted and tried enabling Secure Boot in my UEFI, and sure enough, Mint booted just fine!

I was going to leave it on, as it does provide a security boost, but I discovered that having it on won’t let Virtualbox VMs boot on that PC.  I was surprised that the UEFI setting affected the VM at all, but I definitely could not start any of the VMs until I turned Secure Boot off once again.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon 6.2
XPG Xenia 15, i7-9750H/32GB & GTX1660ti, Kubuntu 24.04
Acer Swift Go 14, i5-1335U/16GB, Kubuntu 24.04 (and Win 11)

3 users thanked author for this post.

JohnW, Bill C., jburk07

Reply | Quote

@ Bill C.

In 2012, M$ mandated the OEMs to sell only new UEFI computers with preinstalled Win 8. UEFI requires GPT disks, 64bit OS and the Secure Boot feature.
### UEFI computers can be manually set to install in Legacy BIOS mode, eg using MBR/ms-dos disks and 32bit OS = Compatibility Support Module enabled = UEFI disabled automatically.

Secure Boot, when enabled, only allows bootloaders that have been certified/signed by the user or by M$/her agent Verisign, to be booted. AFAIK, the signed bootloader files have to be stored in the non-volatile Flash memory chip called NVRAM that is part of the BIOS firmware, before the bootloader can be booted = the bootloader will be displayed in the Boot Menu of BIOS Setup, eg Windows Boot Manager, Ubuntu/shimx64.efi, etc. …
https://www.rodsbooks.com/efi-bootloaders/index.html
https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/
https://nwrickert2.wordpress.com/2013/05/13/notes-on-uefi-windows-and-linux/
### Secure Boot should be disabled when installing Linux or Win 7.

The OEMs have different implementation for UEFI BIOS firmware. Hence, certain OEM Win 8.x/10 laptops, eg Acer, Asus and HP, have an obstructive or pro-M$ BIOS Setup setting for “Select an UEFI file as trusted for executing”,(= the Live Linux USB or just-installed Linux cannot boot). For the fix, please refer to …
https://community.acer.com/en/discussion/543729/efi-dual-boot-not-seeing-linux-on-nitro-5-an515-51-78c6
https://itsfoss.com/no-bootable-device-found-ubuntu/
https://forums.linuxmint.com/viewtopic.php?t=236560

At end 2016 or earlier, certain new high-end OEM Win 10 ultrabooks came with RAID disk mode using the proprietary Intel RST driver, eg Lenovo Yoga 900 13ISK, Ideapad 710/720, Dell XPS 13/15, etc = the internal hard-drive cannot be detected by the Linux Installer. …
https://triplescomputers.com/blog/uncategorized/solution-switch-windows-10-from-raidide-to-ahci-operation/
https://www.dell.com/community/Linux-Developer-Systems/Dell-XPS-13-9350-November-2015-Install-Ubuntu-15-10/td-p/4683278/page/2

Cheap OEM Win 8.x/10 netbooks that come with Intel Atom Bay Trail and Cherry Trail processors and/or 32GB eMMC flash storage are very difficult to install Linux, …
http://www.jfwhome.com/2016/01/04/latest-steps-to-install-ubuntu-on-the-asus-t100ta/
https://gist.github.com/franga2000/2154d09f864894b8fe84 (Ubuntu on Acer Aspire Switch)
https://www.instructables.com/id/Linux-Kiosk-Tablet-From-Acer-Aspire-Switch-10-Bayt/
https://forums.linuxmint.com/viewtopic.php?f=46&t=272614&p=1499628#p1499628 (Re: Unable to Install on Lenovo ideapad Miix 310)
https://forums.linuxmint.com/viewtopic.php?f=46&t=256446 (Dell Inspiron 11 P24T 32GB eMMC install)
### Such cheap netbooks often have M$’s Connected-Standby or InstantGo or Always-Connected feature which disallows Legacy BIOS install mode.

Buying a new UEFI OEM Win 10 computer to install Linux is like walking through a minefield.

2 users thanked author for this post.

jburk07, Bill C.

Reply | Quote

Many thanks for the indepth info.

THe reson I asked was I am being offered an Intel Skylake OEM installed Win10 desktop PC for almost free. Once I look at it, I will decide if it is worth having, depending on specs, as it will be a test bed and learning tool. I will check out the UEFI settings and your links before I commit.

ALso a big thank you to @Ascaris for the info about the Secure Boot and VMs. I would have never thought to even ask about that.

This is definitely a thread for saving for future reference. Its value is both specific and adds to my questions to ask myself library (as most users have no idea about what they bought, i will have to check for myself first, beyond the Speccy/HWiNFO scans).

As an aside, when I was overheard talking about this possible acquisition, I was told of the household overbooking rule, any new resident computers can only take up residency when there is a bonafide vacancy. Goodbye ancient AMD/ATI Athlon2 (originally Vista, now LXLE Linux) box, it has been educational.

1 user thanked author for this post.

Ascaris

Reply | Quote

That is very likely the most polite phrasing I have ever read for the ultimatum of “not one more (whatever)!”

If the overbooking rule was communicated so kindly as you have shared, Bill, I consider you a very lucky man. One or both of you have real diplomatic skills.

1 user thanked author for this post.

Bill C.

Reply | Quote

It was a gently said reminder/ongoing joke. I tend to be a collector and packrat of various items, and castoff itemes needing very minor repairs. The only ones with resistance are those that are labeled dust collectors, and magazine subscriptions. Things that are fixable (and DO get fixed) are OK, and formal collectibles are OK; IF they stay in their designated field and do not branch out.

A few months ago when walking the dog, I saw a large boxed industrial type of vacuum cleaner with a sheet of paper taped to it with MOVING – FREE!!! written in a Sharpie. I called home and said bring the truck I found something. After a brief discussion it was picked up. It was never used with the majority of parts still in sealed bags.

Now both floors have vacuums. The benefit is the large shop vac takes a leaf mulching attachment which we purchased.

Sorry for the digression, but I did like your comment. I remember from a movie, “A man has to know his limits…”

Reply | Quote

FWIW, I never had any trouble installing Linux on my Inspiron 11 or the Swift 1, both low-end Intel Atom-based laptops with eMMC drives.  I did make sure to buy them from vendors that have a good return policy (no restocking fee on returns) in case it didn’t work out, as was the case with the Dell gaming laptop I returned.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon 6.2
XPG Xenia 15, i7-9750H/32GB & GTX1660ti, Kubuntu 24.04
Acer Swift Go 14, i5-1335U/16GB, Kubuntu 24.04 (and Win 11)

Reply | Quote

What I just remembered is my main desktop, a self-built PC with an Intel DX58SO2 mothrboard has a UEFI / BIOS boot switch in the BIOS itself.

It reads in the BIOS and BIOS Manual as follows:
UEFI boot • Enable / • Disable
Enables or disables Unified Extended Firmware Interface (UEFI) Boot. UEFI Boot must be enabled in order to boot to a drive larger than 2 TB (terabytes).
Enable: BIOS will attempt to boot via UEFI before using the legacy boot sequence.
Disable: BIOS will use the legacy boot sequence.
For information on UEFI, refer to http://www.uefi.org/home. That Manual is dated October 2010.

When I built the PC in early 2011, it defaulted to BIOS, and the drives are MBR. That partially explained why I never had an issue with my later nVidia GTX-660Ti graphics card. Many of the initial nVidia 600 Series cards needed their video BIOS flashed to be UEFI compatible when folks upgraded to Windows 8. In early 2011, vary large 2GB+ SATA2 HHDs were not yet common and cheap. Many of the motherboard’s BIOS settings appear now to have been set up for maximum future flexibility well before the release of Windows 8 in October 2012.

I do not remember if this was actually a feature in the initial BIOS of the board at purchase. It is not in the MB manual, and there were 3 BIOS updates in the 2 years following the build. The 2GB spinner Data drive is GPT, but it is not a boot drive and was readable from install with no formatting.

Reply | Quote

Ascaris wrote:

After I migrated to Mint 19 on the Acer, I noticed that an update for GRUB was available, and it said in the name that it was “signed.” After installing it, I rebooted and tried enabling Secure Boot in my UEFI, and sure enough, Mint booted just fine! I was going to leave it on, as it does provide a security boost, but I discovered that having it on won’t let Virtualbox VMs boot on that PC. I was surprised that the UEFI setting affected the VM at all, but I definitely could not start any of the VMs until I turned Secure Boot off once again.

That’s an interesting wrinkle!  Thanks for sharing that!  As a VirtualBox user myself, I do find that surprising.

Windows 10 Pro 22H2

Reply | Quote

Ascaris wrote:

All three of the UEFI laptops I put Linux on recently (2018) have shipped with Win 10 Home with secure boot enabled. I simply turned it off… no problem. The laptops consisted of a low-end Dell, a midrange Dell gaming model, and a low end Acer. I believe that MS initially required OEMs to ship with secure boot enabled, but that it be optional (in the 8.1 days, if I recall) on regular PCs (meaning the user of the PC can turn it off), but that they now just require that secure boot be enabled and do not any longer require that it be optional, leaving that up to the OEM. Still, I don’t imagine there will be many OEMs that will ship with Secure Boot permanently enabled. It would cut off the buyers who may be looking to install a non secure-boot OS with no upside to the OEM (unless MS made them a sweetheart deal of some kind). I definitely would return any PC that wouldn’t let me turn it off!

I build my own desktop systems, and the UEFI/BIOS on the OEM motherboards (bare bones, no OS provided) that I have used (Asus) have never been crippled.  But I have noticed a trend on laptops with pre-installed Windows (such as my low-end Acer) to have some UEFI/BIOS settings “customized” (i.e. crippled), so that some settings are not available to the end user.  Must be related to the “deals” that MS is offering to the OEMs.  Buyer beware!

Windows 10 Pro 22H2

1 user thanked author for this post.

Elly

Reply | Quote