How to use Logitech MX Keys, MX Master in BIOS

I have the MX Keys. Pressing FN + Function key is required when the keyboard is set in FN mode. To enter Function Key mode, hold FN and press Escape once. This switches the keyboard to the other mode. Now FN must be held down when using the built-in alternate functions of most of the same function keys, such as keyboard brightness up/down, mic mute, back/pause/forward, speaker mute, and volume down. On my system, volume up is not assigned to a function key, but is on the right of the same row and works regardless of how the function mode is set. When Function Key mode is enabled, do not hold the FN key to use the F1 through F12 function keys for function key operations.

A nice feature once you get the hang of it. Same goes for using the 1/2/3 buttons to connect to other devices: a big strength of this keyboard - mine is set up for my 1 desktop/2 laptop/3 iPad. Switch between them with the touch of a button, cool. Same goes for the matching mouse.
I haven't found a way to get into the BIOS with a direct Bluetooth connection (ASUS B650E-F). I believe the motherboard system loads enough USB drivers to allow use of the dongle, but not Bluetooth directly. I haven't seen anyone able to use this keyboard in the BIOS without an adapter.

Just use the Unify dongle and you won't have any problems.
www.amazon.de/-/en/Logitech®-Unifying-USB-receiver-Black/dp/B07W6JKH17

Source: www.reddit.com/r/logitech/comments/s2mf4s/how_to_use_logitech_mx_keys_mx_master_in_bios/?tl=de&rdt=42847

 

Last edited: Feb 7, 2025

Hey there ... I'm doing 6 boots ... 5 WIN 11s ... and a Windows 8.1 ... I have all kinds of fun.

 

How do you have this set up? Is an OS per drive, or a single drive with partitions? And how are you loading these? With the default bootloader, BIOS, or another third party tool?

 

Dual Boot: Windows tutorial for multiple operating systems installed in parallel

Source: German
https://www.computerbild.de/artikel...lierte-Betriebssysteme-parallel-30561955.html

English Translator
https://www-computerbild-de.transla...l=auto&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp

 

Installing SINGLE OS on each disk and using BIOS to switch will be more stable.
Biggest advantage being if one disk is down ... the other is perfectly autonomous.

 

The dual boot scenario is not really recommended for much else other than really testing, IMO. I have done dual boot configs in the past that seemingly no amount of care taken will keep it from eventually fucking shit up beyond reproach. It might work ok for a year, maybe two, but eventually it will screw up in some way and most likely cause some sort of data loss in the process. Dual boot scenarios that use the same physical disk for two different operating systems are to be avoided at all cost. Dual boot config's that run a separate physical drive for each OS being used are much better, but still prone to catastrophic failure if/when it gets compromised.

Sure, you can disable the interfaces, but internet activities (i.e. email, browsing, shopping, warez, porn, gaming, etc, etc...) and all the functions that make internet activities safe (internet facing NIC, firewalls, VPN, a/v, anti-malware, etc...) are not needed or wanted on a production machine. These things just waste system resources that are better spent on production efforts. Plus, on a sans internet production box, there is physically no way for anything running on that machine to phone home and/or deactivate itself. A private local area network is fine for being able to easily xfer data to/from all your machines and will prove very useful in a number of ways. However that local private network does not need A/V, Firewall, VPN, etc so it is not impactful to production at all.

Two machines set up for the different usage modes are the BEST solution for a long lasting trouble free experience. This may not be your cup of tea, but after much operational testing on my part I have found it to be the best solution in the long run for my work flows and opeartions.

 

Last edited: Feb 7, 2025

Using two user accounts AND installing software only for ONE user can solve a lot of troubles on the same OS install.

If you want to add a security layer, you can disable IP stack on host OS. So nothing is linked to internet.
And use a virtual machine to browse internet and scan files BEFORE installing them.
Like a Linux virtual machine.

 

What I did instead of dual booting:
I have Steam and other game launchers installen in Sandboxie.
Thats awesome. Everything works, I've not once ran into incompatibilities.
And everything is locked away. No matter what crap the game installs, it sits in a folder and is executed when I start the launcher. I got a link that automaticly launches steam within sandboxie just by double clicking.
So I don't even feel any difference from running stuff nativly.
Best thing: Whenever I install windows, I just install sandboxie, open my steam sandbox and I'm good to go.
I use the same steam folder since windows 8,1. Then win 10 and now win 11.
Never changed anything just opened steam and was good to go with all the games that were installed.
Including several hardware upgrades over the years.