Delay when opening the start menu after Windows Update

[iLoveSoy]

Describe the bug

After updating windows against my will, I have unfortunately been left with a start menu that now takes a solid half a second to actually open after clicking on it.
Clicking on it repeatedly will also lead to it lagging behind, opening and closing for a while trying to catch up.
Strangely, it only seems to effect the start menu on my first monitor, the second and third monitors' start menus still open immediately when clicked on.

Please help, it feels like I'm using an iPhone and it's abysmal.

Area of issue

Start menu

To reproduce

1. Open the start menu
2. Get angry over the long delay before it opens

Expected behavior

Open immediately like it always has

Open-Shell version

4.4.196

Windows version

Windows 10 IoT Enterprise LTSC 21H2

Additional context

No response

[McKay42]

Same here, uninstalling KB5065429 completely fixes the problem. But this is a security update, so...

[Dougo007]

I have the same issue, my partial temporary workaround is to disable the fade animation, but it seems using a custom button is also partly to blame. See if changing that helps the rage.

Edit: I also have a second screen but usually just use it as a TV. I can replicate the report above, it's affect the primary monitor only. When I set the TV as my 'primary monitor' the issue completely goes away on my laptop screen.

Edit 2: My post may have some useful info #2305

[iLoveSoy]

I have the same issue, my partial temporary workaround is to disable the fade animation, but it seems using a custom button is also partly to blame. See if changing that helps the rage.

I've never used a custom start button. Nor have I ever had fade, or any other form of animation enabled.
I tried altering all of the settings just in case, but nothing changed unfortunately.
It's refreshing to finally have an issue that isn't purely isolated to me though.

I'd share an image for reference, but it's not really a problem that can be quantified through a static medium.
I could always construct a gif to visualize it if necessary however.

[Dougo007]

One thing that caught my eye this morning is that when I enable the second monitor the custom button blinks 5-6 times and when disabling it blinks 1-2 times.

Edit: I accidentally left the setting to show taskbar on all monitors. Turning it off led to it still blinking but only once, it may or may not be related to this primary issue.

[Dougo007]

I could always construct a gif to visualize it if necessary however.

You don't need to for me, thanks though.

[ThachNgocTran]

I have the same problem on Windows 10 Pro 22H2 (64 bit).

[Dougo007]

Found out something else.

If a program is full screen and the windows key is used, instead of simply opening the start menu, if first makes the taskbar appear, then it triggers the start menu button (it lights up), then it opens the start menu. This is happening in three clearly visible steps as compared to the start menu simply opening.

I compared against the second monitor to verify that this is part of the bug.

[Dougo007]

I have a thought, and I don't know if it will help, but could it be a rendering issue?

I know when I used to play full screen games that sometimes the button would appear unexpected and rarely caused me to need to quick Open Shell. I was actually using Classic Shell up to now and updated hoping the issue was fixed between that time point and now.

I believe this because

1. the button flickers when enabling and disabling the second screen
2. It only affects the primary monitor, the bug is not present in any secondary monitor
3. no keystrokes are lost, I don't think it's a loading issue

To be fair, I'm not a Windows developer, or much of a UI programmer at all, even in my own field, Salesforce. I'm actually a Release Manager who has some developer background. I also know that when someone says something to me that's completely off the mark, it can cause me to think of something that I wouldn't have otherwise. So I hope this helps.

[hazyfossa]

I can reproduce this without OpenShell on vanilla Windows 10. Uninstalling KB5065429 fixes the issue. The lag between taskbar click and action is like solid 5 seconds for me.

[McKay42]

Workaround from reddit while keeping KB5065429 installed, links here and here.

Use regedit to manually disable the WpnService + WpnUserService + WpnUserService_xxxxx services. So if you don't care about any of the Windows push notification services, then this is a viable fix.