Has anyone noticed a much slower logon time on Windows 10 version 1903? On every system that I installed it, from high end systems to low end systems the time needed to logon in an account is more than doubled compared to 1803. Last week a friend asked me to check his system, since he was convinced that he had a virus or something, because his system booted slowly. Yesterday, my little niece noticed it too in her laptop. And after testing I saw a difference of >20 seconds betweeen 1803 (time needed to login 8-12 seconds) and 1903 (time needed to login 25-50 seconds ). Panagiotis
I haven't, my cold boot is less than 30 secs. Have you thought about doing a boot trace? You have to install Performance Toolkit from the SDK and use either WPRUI or xbootmgr (command line). I'd trace both 1803 and 1903 and then compare the results. I didn't do this since the XP days (bootvis) and can't help with the specifics so you have to research this a bit, but this looked like a good place to start - https://blogs.technet.microsoft.com...indows-10-or-windows-server-2016-using-wprui/ Without boot tracing, I'm afraid it's a guesswork.
I haven't notice any difference, compared with the previous build. I do have a SSD, which helps with boot times.
The cold boot until the Logon screen is a bit faster. The delay that I see is after the logon screen but is very inconsistante. On my niece's laptop the admin account logs in to a functional desktop in ~10 seconds (same as 1803), the standard user account on the other hand is a different story. This is on a fresh updated system with nothing extra installed. I start to suspect that MS messed up with the standard account settings... Those timings are on a laptop with a samsung evo 860 m2 sata3 500gb.
I am using an Admin account. Perhaps I would be seeing slower boot times too, if I wasn't using an Admin account.
Event Log service starts before the user login. I'd carefully inspect Event Viewer, look at Security sublog for any failed audits that pertain to the user with a login delay. The real question though is why is this happening on so many machines. +1
After a bit of testing I identified the problem. It is related with the logon screen/menu and multiple accounts. It seems that with version 1903 windows performs a partial/incomplete auto-login of the last user (A) even before he/she inserts the password or the verification. And remains on that state indefinitly. So if another user (B) logs in from the menu, it takes much more the time for the desktop to appear... and that slow loading time will remain until the system reboots or until that semi logged in user (A) logs in. If user (B) logs of and then from the prelogon screen he presses the shutdown button windows will warn him that the other user (A) is currently active (even though he never logged-in) and he will lose his unsaved work. time to boot log in (I checked multiple times). From cold startup to logon screen, ~10 seconds From logon screen to the last user (A), ~10 seconds From logon screen to another user (B): - If User (A) is already logged in, ~10 seconds - If User (A) has not looged in (= partial state), ~30 seconds Panagiotis
I can't reproduce this in a vanilla 1903 VM - to the point that I wonder if we're using the same OS . Admin and 2 standard users I created all login in a couple of seconds. Of course, the initial login is slower (approx. 30 secs) as the account is being set up, but all subsequent logins take no more than 6 seconds. There is no discernible difference between login times of admin and user, I tried to switch admin-user, user-user, user-admin. Can't reproduce that either. I login with a standard user, and when I logoff and proceed to shutdown I get no warning that another user (that didn't login) is active/logged in. Didn't try on a physical system, may do it later.
How to reproduce. Give on account A a password login (admin account). Login to that account A and reboot. After the reboot, login directly to account B (does not matter if it has a password or not). Log out from B and reboot or shut down from the logon screen = should give a warning/prompt. It happens only on the Initial boot (if fast startup is disabled) or when rebooting (first reboot I do not remember if it happens on multiple reboots). If fast startup is enabled it does not happen during the shutdown and does not appear unless you reboot. edit: another thing that happens every now and then is that, if you select an account (without a password) it performs a login without having to press the login button. Other times you have to select the account and then press the login button to perform the login... haven't figured out yet why it happens.
I followed this exactly. My admin account did not have a password, standard users did - no prompts or slow logins. As soon as I add a password to admin account, reboot and login as user, I get a prompt on shutdown/reboot that another user is logged in. This also happens if you first login as user, reboot and login as admin. Remove admin password again - no prompt on shutdown/reboot regardless of who is logged in. Login times are still a couple of seconds in all cases. I can confirm this. If you logged in with an account without a password, on reboot it will login to that account automatically. ... I initially suspected this issue has something to do with 'fast startup' as this is the glaring difference between VM and a real system - there are neither 'hibernation' nor 'fast startup' options' in VM's power settings. After this, I'm not so sure.
Thanks for testing. The slow login could be related with the power options since on 1903 each user can set his/her own power saving options. (2 different acounts try to load their own power settings at the same time) Both this and the semi-login should be related with the custom background at the logon screen, for each user... is the only thing that I can think of. Panagiotis
I figured it out. The user is indeed semi-logged in, you can check this in Task Manager's 'Users' tab, the 'never-logged' user will show as 'disconnected'. Responsible for this behavior is this freaking feature - Turn it off, and the symptoms stop. You have to turn it off for every user you don't want to log in in the background. Naturally.
@Seer Thank you very,very much. I missed that setting because the greek translation is a bit off. If I remember correctly that option existed in 1803 too, but did not gave such problems...
You're welcome, Panagiotis Who knows how exactly that feature works and what has changed under the hood since 1803. Maybe it works differently now. It's strange that the isuue does not appear when admin is without a password, but I'm done and am not looking into it anymore. Perhaps it's a bug. Perhaps, perhaps. This is what happens when you lack the official documentation. In any case, glad we (kinda) sorted it out. Take care.
The one thing I remember about that setting is that its supposed to help the process of updating Windows. I always had it On but I dont know if it does smooth things out or not as I run as Administrator, no PW and don't have any other accounts in the computer. My guess on what that setting does has always been that if you use a PW, when updating Windows, after reboot, the reboot bypasses having to sign in (thats my guess), and finish applying the update. Is only a guess, as I dont know how the WU process works when you use PW or have more than one account in the computer. My computer boots straight to the desktop. Bo
