Two changes on Windows startup after BIOS update

[JovenCalixto]

Hello everyone

I have a MSI Z590 tomahawk WIFI MOBO and, after updating the BIOS to its v2.90 version I found two changes that I think may be related. I tried to turn back the BIOS to v2.80 and repairing windows with an iso file but it didn't solve the issues.

1- The first change is that, even though I have numlock on at startup both in windows registry and in BIOS settings, it doesn't turn on in the log in screen, having to turn it on manually. Howevee, I've noticed that, at startup, all my keyboard's RGB lights turn on with the numlock light also turned on (this is during the time I can enter the BIOS, being it on when I enter it), then all the lights go off and on again (still the numlock light is on), then they turn off again until windows starts at its log in screen when all the LEDs turn on again but the numlock light doesn't turn on.

2- The second change I think may be related to the first one is that Windows "doesn't startup until I log in". With this I mean that, before the update, startup programs were able to start before I entered the password, for example, if I were to set a program that started a countdown of 10 seconds at startup (in this case Process Lasso, a program I used a year ago that had a premium ad at startup), I would find that the countdown had started and advanced at the log in window, being at 3 seconds left or has ended when I logged in. Now, I reinstalled this program only to test this change, finding out that the countdown starts after I log in, this is also noticeable on other programs that had started before I logged in and were now running when I entered the password and now they start after the log in process. Also I find that if I introduce the password without the numeric keyboard, when I log in numlock turns on automatically.

This changes aren't too concerning for me, as it only implies to start numlock manually when logging in and my PC is fast enough to load windows in seconds after I log in. However, I want to know the cause out of curiosity and, if there is a simple solution to it, solve it.

Thank you

P.D: Sorry if this thread is too dense, but English is not my first language.

 

[Athlonite]

Hello everyone

I have a MSI Z590 tomahawk WIFI MOBO and, after updating the BIOS to its v2.90 version I found two changes that I think may be related. I tried to turn back the BIOS to v2.80 and repairing windows with an iso file but it didn't solve the issues.

1- The first change is that, even though I have numlock on at startup both in windows registry and in BIOS settings, it doesn't turn on in the log in screen, having to turn it on manually. Howevee, I've noticed that, at startup, all my keyboard's RGB lights turn on with the numlock light also turned on (this is during the time I can enter the BIOS, being it on when I enter it), then all the lights go off and on again (still the numlock light is on), then they turn off again until windows starts at its log in screen when all the LEDs turn on again but the numlock light doesn't turn on.

2- The second change I think may be related to the first one is that Windows "doesn't startup until I log in". With this I mean that, before the update, startup programs were able to start before I entered the password, for example, if I were to set a program that started a countdown of 10 seconds at startup (in this case Process Lasso, a program I used a year ago that had a premium ad at startup), I would find that the countdown had started and advanced at the log in window, being at 3 seconds left or has ended when I logged in. Now, I reinstalled this program only to test this change, finding out that the countdown starts after I log in, this is also noticeable on other programs that had started before I logged in and were now running when I entered the password and now they start after the log in process. Also I find that if I introduce the password without the numeric keyboard, when I log in numlock turns on automatically.

This changes aren't too concerning for me, as it only implies to start numlock manually when logging in and my PC is fast enough to load windows in seconds after I log in. However, I want to know the cause out of curiosity and, if there is a simple solution to it, solve it.

Thank you

P.D: Sorry if this thread is too dense, but English is not my first language.

Check the fastboot setting in your BIOS alot of stuff will not be initialized until after login if it's turned on so that boot up is as fast as it can be

 

[eidairaman1]

Before bios updates, do a clear cmos, after bios updates do a clear cmos to set a baseline, then re-implement bios settings.

Check how to clear the log in screen and go straight to desktop on youtube.

 

[JovenCalixto]

Check the fastboot setting in your BIOS alot of stuff will not be initialized until after login if it's turned on so that boot up is as fast as it can be

I disabled fastboot but numlock is still off at startup. However, thank you for your tip about fastboot.

Before bios updates, do a clear cmos, after bios updates do a clear cmos to set a baseline, then re-implement bios settings.

Check how to clear the log in screen and go straight to desktop on youtube.

Is clearing CMOS the same as resetting settings to default on BIOS?

 

[pavle]

I always used just reset to defaults when updating BIOS, then restart and then editing BIOS the way I wanted, never any problem.