There's a similar nug in Hyper-V because it does not include any such BIOS option, and starts a VM with Numlock off by default.
Properly setting the Nulock key ON when logged on, and copying the keyboard input layout and language from the current user to the system account used by the logon screen does not work.
EAch time a VM is started, or when I log off the currenty user in a VM hosted by Hyper-V, the keyboard is reset of Numlock OFF. The keyboard is also reset when I am already logged on in the VM and I just exit the viweing terminal and restart it:: as I reconnect
to the desktop with the RDP client or with the Hyper-V console, eahc time Numlock is forced off. In summary, Numlock state is NEVER remembered, but really actively forced (I even see the OSD message shown on screen when Numlock is forced off by the logon screen).
This is a strange bug of Hyper-V. I wonder why it ever needs to do that when the keyboard is not even a compact keyboard layout for a notebook (I know that some notebooks don't have any numpad, annd the numpad is emulated by presssing Numlock to remap a
part of the alphabetic keyboard: this only concerns some old quierky notebooks, most neotebooks that have a physical keyboard have a numpad today or no keyboard at all as there's only the onscreen keyboard which does not use any Numlock)
Really, this old quirk in Windows for forcing numlock off each time we get to the logon screen is stupid, and obsolete for most people. It is really disturbing. This is a bug for Windows 7, 8, 8.1, Server 2008, Server 2012, Server 2012 R2, and now Windows
10 as well ! I supposed this was a fix only for a few notebook PCs, but it would have been better to use PlugnPlay detection of those PCs that may need sometimes this working mode. For most PCs this behavior is really undesirable