Just providing an update on the Start menu delay o...
# microsoft-os
n
Just providing an update on the Start menu delay on Server 2025 issue that I mentioned a few months back. Got a solution from MS, and it will affect all of us. This issue: After installing the Citrix VDA software on Server 2025 VM, there will be a noticeable 2-4 second delay from the time you click on the Start menu to the time it is displayed. This is because Microsoft changed the behavior of StartMenuExperienceHost.exe to not automatically start at logon. They did this to speed up the logon process, and the change was originally targeting Windows 365 and Cloud PC. No idea why it's hitting Server 2025, but it is what it is. This is because their code looks for a multi-session terminal server and activates the new behavior. I believe it's activated once you install the RDS role, which is the first thing that the VDA installer does. The solution: Microsoft provided me with a registry fix that reverses this behavior back to the standard behavior where the process runs at user logon.
Copy code
Path: HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\StartMenu
Value: PrelaunchOverride
Type: REG_DWORD
Data: 1
I'm baking this into our OS layer, but this should also work deployed via Computer GPP, as it is effectively immediately.
πŸ™Œ 4
πŸ™ŒπŸΌ 1
j
Eh? Start Menu doesn't run automatically???
n
Correct, StartMenuExperienceHost does not run automatically when the OS detects that it's a multi-session terminal server.
Big brains over at MS on that decision.
d
That sounds so fucking stupid, that it actually might be true
πŸ˜‚ 1
πŸ’― 1
m
Holy moley.
j
Well I guess if you don't do anything at logon you'll get a faster logon process, sure
🧠 1
πŸ™Œ 1
n
When he told me it was by design I legit started laughing until I realized he wasn't kidding.
πŸ˜† 1
j
That's like the old "logon scripts don't run at logon any more to speed up logons" they introduced on Server 2012.
n
I get wanting to speed up the logon process, but causing the user to actually experience a delay is way worse since it's interactive. Wild.
This is also what happens when you break up a simple, single process and now have multiple components for it (Start menu, search host, etc.)
j
Exactly. You ever seen how fast logons to Windows NT4 are on modern hardware? Sub one-second
n
I asked him for the name of the developer who created UWP apps but he wouldn't tell me
πŸ˜‰ 1
πŸ˜‚ 1
🀣 1
one day I will find him
j
Satan
πŸ˜… 1
j
Thanks a mill Nick, what a bunch of muppets at MS ...
n
Muppetsoft has a nice ring to it, actually
πŸ˜‚ 1
gonna trademark that shit
I will say, the developer/engineer from MS that I've been working with this on has been terrific. Easily the best support from MS that I've ever received (low bar, I know), but he has gone out of his way to dig into this. Even found the person responsible for the change and contacted them for details, etc.
πŸ‘ 1
And he's working on the next steps: i.e., how to notify others of this, possible other ways to handle this (GPO being the obvious one).
r
@Devin McCubbins ^---
❀️ 1
m
I am here for following…
n
Still waiting on a final update from MS with the new public info, but I know from my thread on Reddit that this is now resolved for everyone else
❀️ 1
j
Confirmed resolved from someone I spoke to as well
m
i need to test this on Win11 multisession!