PSA: Dual Boot Users :: Hardware and Operating Systems

All Discussions > Steam Forums > Hardware and Operating Systems > Topic Details

Bad 💀 Motha 21 Jul @ 6:45pm

PSA: Dual Boot Users

If you dual boot WinOS and Linux on the same machine, watch out, because this might be a real problem for many users >>>

https://www.tomshardware.com/tech-industry/cyber-security/microsoft-signing-key-required-for-secure-boot-uefi-bootloader-expires-in-september-which-could-be-problematic-for-linux-users

Last edited by Bad 💀 Motha; 21 Jul @ 9:34pm

< >

Showing 1-7 of 7 comments

Phénomènes Mystiques 21 Jul @ 8:59pm

If you dual-boot, make sure to use TWO SSD's not the same because Windows CAN/WILL corrupt...

They say to install Windows prior to Linux but Windows will fail eventually, ALWAYS use TWO SSD's for both Windows and Linux (with tri-booting three SSD's, nothing huge 500GB will suffice < 250GB for linux)

Thank you, Bad 💀 Motha for the awareness.

(I have personally seen Windows corruption while dual-booting win and linux so this is a test of warning and experience > Windows and Linux CANNOT be booted/should NOT BE TRUSTED on same boot drive).

Last edited by Phénomènes Mystiques; 21 Jul @ 9:01pm

Bad 💀 Motha 21 Jul @ 9:17pm

Yes best way to dual boot really is to install each OS to each separate drive; one at a time.

For example; SSD #1, install OS. Done. Unhook or remove SSD #1 and connect/insert SSD #2 and install other OS....

I know that can be a pain with M2 SSDs but it's all for the best. Now each OS knows nothing about one another and has no boot loader of any kind to link drives or OS' in any ways.

Even a prebuild Desktop or Laptop from HP or DELL others a Boot Menu from your BIOS with a hotkey such as F10, F11, F12 from here is where users can easily select which drive to boot from with ease, thus which OS to boot into.

Or disable Fast-Boot in UEFI BIOS and when PC POSTs, enter BIOS and double-click the drive of choice to boot to, and thus the OS of choice.

Relying on a WinOS or Linux bootloader will only lead to troubles down the road.

Once inside an OS, such as Win10/11 for example you could then go into Disk Management and for the other drive being Linux for example (such as D drive) you can go and select to make that drive Off-line. Now the drive will sit in an idle power saver state and not be touched in any ways by WinOS. You can regain access to said drive if need to throw some files onto it if needed by selecting to make the drive Online again.

Last edited by Bad 💀 Motha; 21 Jul @ 9:20pm

Omega 22 Jul @ 7:11am

All you have to do is update your firmware. A firmware update to fix this is queued in fwupd.

Most people running Linux have secure boot disabled, so this will not affect most of them.

Bad 💀 Motha 22 Jul @ 10:36pm

Originally posted by Omega:
All you have to do is update your firmware. A firmware update to fix this is queued in fwupd.

Most people running Linux have secure boot disabled, so this will not affect most of them.

I should have pointed out this more of an issue for people who dual boot on older Motherboards. Even a Build done over that COVID lock down period, the Motherboard is either already beyond warranty or nearing that period; after this it is rare for a Motherboard to ever get a BIOS update issued out.

smokerob79 22 Jul @ 10:48pm

Originally posted by Bad 💀 Motha:
Originally posted by Omega:
All you have to do is update your firmware. A firmware update to fix this is queued in fwupd.

Most people running Linux have secure boot disabled, so this will not affect most of them.

I should have pointed out this more of an issue for people who dual boot on older Motherboards. Even a Build done over that COVID lock down period, the Motherboard is either already beyond warranty or nearing that period; after this it is rare for a Motherboard to ever get a BIOS update issued out.

years of intel use and abuse is showing in you.....my AMD board saw updates 5 years after first release and it had a 3 years warranty

$#!Tel....its not longer inside.....NOO no NOOO......

Bad 💀 Motha 22 Jul @ 11:24pm

Originally posted by smokerob79:
Originally posted by Bad 💀 Motha:

I should have pointed out this more of an issue for people who dual boot on older Motherboards. Even a Build done over that COVID lock down period, the Motherboard is either already beyond warranty or nearing that period; after this it is rare for a Motherboard to ever get a BIOS update issued out.

years of intel use and abuse is showing in you.....my AMD board saw updates 5 years after first release and it had a 3 years warranty

$#!Tel....its not longer inside.....NOO no NOOO......:The_Slayer:

Depends on the board; my Intel boards had 5 years too. That support though is rare and dictated by the maker. Like ROG boards are more likely to see future updates compared to cheaper board models. The old TUF Sabertooth series had 5 years for example.

Omega 23 Jul @ 1:41am

Originally posted by Bad 💀 Motha:
Originally posted by Omega:
All you have to do is update your firmware. A firmware update to fix this is queued in fwupd.

Most people running Linux have secure boot disabled, so this will not affect most of them.

I should have pointed out this more of an issue for people who dual boot on older Motherboards. Even a Build done over that COVID lock down period, the Motherboard is either already beyond warranty or nearing that period; after this it is rare for a Motherboard to ever get a BIOS update issued out.

The secure boot key firmware is updated separately of the UEFI.