Running W10 Pro. Had my Start Menu popping open instantly when I pressed
on the Windows logo key. Then after installing KB5058379 (or rather
having it shoved down my throat by M$), the Start Menu began opening
only after a short pause. Not a really long pause, but a short pause
that's just long enough to be annoying.

Has anybody else here experienced this problem?

TIA.

--
John C.

I filter out all crossposts and garbage from trolls.

Take back Microsoft from India.


--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On Thu, 5/22/2025 9:26 AM, John C. wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I pressed
on the Windows logo key. Then after installing KB5058379 (or rather
having it shoved down my throat by M$), the Start Menu began opening
only after a short pause. Not a really long pause, but a short pause
that's just long enough to be annoying.

Has anybody else here experienced this problem?

TIA.

That doesn't seem to be MenuShowDelay (400 default, 4000 max or four seconds).

A security feature, like Process Isolation or sandbox of the StartMenuExperience ?

I don't think it is related to Search, as my menu doesn't show a search.

[Picture]

https://i.postimg.cc/J731YQ0r/Win10-Start-Menu-Gregore-33.gif

If your graphics had become un-accelerated... you'd notice it everywhere.

Paul



--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

Keywords: VanguardLH,VLH

"John C." <r9jmg0@yahoo.com> wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I
pressed on the Windows logo key. Then after installing KB5058379 (or
rather having it shoved down my throat by M$), the Start Menu began
opening only after a short pause. Not a really long pause, but a
short pause that's just long enough to be annoying.

I have Windows updates disabled, so I haven't yet gotten KB5058379. I
already have 22H2, and the description of the KB says (for 22H2) there
is a servicing stack update. That's Microsoft "improving" their Windows
Update client often to facilitate getting Win10 users to move to Win11.

I'd try going into the fluff and cutsy display settings to eliminate
menu delay, and other glitz:

- Run: C:\Windows\System32\sysdm.cpl
- Advanced tab.
- Performance settings.

You could select the pre-defined "Best performance" profile. I usually
start there, and end up with only the following options enabled:

Enable Peek
Show shadows under mouse pointer
Show thumbnails instead of icons
Show translucent selection rectangle
Show contents while dragging
Smooth edges of screen fonts
Use drop shadows for icon labels on the desktop

All the rest are deselected (disabled). I don't want menus to be
animated by fading them in and out, or smooth scrolling that slows down
me scrolling fast and immediately.

I also have Winaero Tweaker which has a "Menu Show Delay" setting it
exposes. Load Winaero, and search on "delay". Mine is currently set to
200 ms. That allows me to pass the mouse pointer over a menu without it popping open the menu list, but is pretty short should I rest the mouse
pointer atop a menu. If you don't have WinAero, they have a help page
to explain what the setting does, and how to change it using regedit:

https://winaero.com/how-to-speed-up-menus-in-windows-10-and-change-the-menu-delay/

I've assumed you performed the typical standard troubleshooting step of restarting Windows after any update. Just because an update doesn't
tell you a restart is needed doesn't mean you shouldn't restart Windows.
You might also changing the menu delay, restart Windows, and change it
again since sometimes you have to change a setting to kick it in the ass
to get honored.

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: Usenet Elder (3:633/280.2@fidonet)

On Thu, 5/22/2025 4:37 PM, VanguardLH wrote:

"John C." <r9jmg0@yahoo.com> wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I
pressed on the Windows logo key. Then after installing KB5058379 (or
rather having it shoved down my throat by M$), the Start Menu began
opening only after a short pause. Not a really long pause, but a
short pause that's just long enough to be annoying.

I have Windows updates disabled, so I haven't yet gotten KB5058379. I already have 22H2, and the description of the KB says (for 22H2) there
is a servicing stack update. That's Microsoft "improving" their Windows Update client often to facilitate getting Win10 users to move to Win11.

I'd try going into the fluff and cutsy display settings to eliminate
menu delay, and other glitz:

- Run: C:\Windows\System32\sysdm.cpl
- Advanced tab.
- Performance settings.

You could select the pre-defined "Best performance" profile. I usually
start there, and end up with only the following options enabled:

Enable Peek
Show shadows under mouse pointer
Show thumbnails instead of icons
Show translucent selection rectangle
Show contents while dragging
Smooth edges of screen fonts
Use drop shadows for icon labels on the desktop

All the rest are deselected (disabled). I don't want menus to be
animated by fading them in and out, or smooth scrolling that slows down
me scrolling fast and immediately.

I also have Winaero Tweaker which has a "Menu Show Delay" setting it
exposes. Load Winaero, and search on "delay". Mine is currently set to
200 ms. That allows me to pass the mouse pointer over a menu without it popping open the menu list, but is pretty short should I rest the mouse pointer atop a menu. If you don't have WinAero, they have a help page
to explain what the setting does, and how to change it using regedit:

https://winaero.com/how-to-speed-up-menus-in-windows-10-and-change-the-menu-delay/

I've assumed you performed the typical standard troubleshooting step of restarting Windows after any update. Just because an update doesn't
tell you a restart is needed doesn't mean you shouldn't restart Windows.
You might also changing the menu delay, restart Windows, and change it
again since sometimes you have to change a setting to kick it in the ass
to get honored.

I tested the Menu Show Delay, and setting it to 4000 from the default 400,
made no difference to the Windows key opening the Start Menu. Same speed
as clicking the Start icon in the corner, with the mouse.

I would be looking at my collection of "add-ons" for inspiration,
OpenShell or whatever, for an answer.

It could be, that the program itself, is having trouble
changing power states, in which case the thing should be tested
using some tab in Task Manager and looking for hints there.
Maybe it is taking some time going from Suspend to Running.

Paul

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

Keywords: VanguardLH,VLH

Paul <nospam@needed.invalid> wrote:

On Thu, 5/22/2025 4:37 PM, VanguardLH wrote:

"John C." <r9jmg0@yahoo.com> wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I
pressed on the Windows logo key. Then after installing KB5058379 (or
rather having it shoved down my throat by M$), the Start Menu began
opening only after a short pause. Not a really long pause, but a
short pause that's just long enough to be annoying.

I have Windows updates disabled, so I haven't yet gotten KB5058379. I
already have 22H2, and the description of the KB says (for 22H2) there
is a servicing stack update. That's Microsoft "improving" their Windows
Update client often to facilitate getting Win10 users to move to Win11.

I'd try going into the fluff and cutsy display settings to eliminate
menu delay, and other glitz:

- Run: C:\Windows\System32\sysdm.cpl
- Advanced tab.
- Performance settings.

You could select the pre-defined "Best performance" profile. I usually
start there, and end up with only the following options enabled:

Enable Peek
Show shadows under mouse pointer
Show thumbnails instead of icons
Show translucent selection rectangle
Show contents while dragging
Smooth edges of screen fonts
Use drop shadows for icon labels on the desktop

All the rest are deselected (disabled). I don't want menus to be
animated by fading them in and out, or smooth scrolling that slows down
me scrolling fast and immediately.

I also have Winaero Tweaker which has a "Menu Show Delay" setting it
exposes. Load Winaero, and search on "delay". Mine is currently set to
200 ms. That allows me to pass the mouse pointer over a menu without it
popping open the menu list, but is pretty short should I rest the mouse
pointer atop a menu. If you don't have WinAero, they have a help page
to explain what the setting does, and how to change it using regedit:

https://winaero.com/how-to-speed-up-menus-in-windows-10-and-change-the-menu-delay/

I've assumed you performed the typical standard troubleshooting step of
restarting Windows after any update. Just because an update doesn't
tell you a restart is needed doesn't mean you shouldn't restart Windows.
You might also changing the menu delay, restart Windows, and change it
again since sometimes you have to change a setting to kick it in the ass
to get honored.

I tested the Menu Show Delay, and setting it to 4000 from the default 400, made no difference to the Windows key opening the Start Menu. Same speed
as clicking the Start icon in the corner, with the mouse.

I would be looking at my collection of "add-ons" for inspiration,
OpenShell or whatever, for an answer.

It could be, that the program itself, is having trouble
changing power states, in which case the thing should be tested
using some tab in Task Manager and looking for hints there.
Maybe it is taking some time going from Suspend to Running.

Paul

I didn't think about resuming from a low-power mode. My desktop is
configured for high performance, so no sleeping ever. Not even during
the night when I sleep since quite often I wake up and want to
immediately use the computer. To me, the savings in electricity is not
worth the nuisance of a snoozing computer.

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: Usenet Elder (3:633/280.2@fidonet)

John C. wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I pressed
on the Windows logo key. Then after installing KB5058379 (or rather
having it shoved down my throat by M$), the Start Menu began opening
only after a short pause. Not a really long pause, but a short pause
that's just long enough to be annoying.

Has anybody else here experienced this problem?

TIA.

I rebuilt my iconcache and that seemed to help. My thanks to everybody
who replied.

--
John C.

I filter out all crossposts and garbage from trolls.

Take back Microsoft from India.


--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

John C. wrote:

John C. wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I pressed
on the Windows logo key. Then after installing KB5058379 (or rather
having it shoved down my throat by M$), the Start Menu began opening
only after a short pause. Not a really long pause, but a short pause
that's just long enough to be annoying.

Has anybody else here experienced this problem?

TIA.

I rebuilt my iconcache and that seemed to help. My thanks to everybody
who replied.

I guess I was imagining things. Either that or the fix was only temporary.

Personally, I think M$ implemented this problem deliberately in order to
subtly get people to by new computers or at least to go with the hated W11.

--
John C.

I filter out all crossposts and garbage from trolls.

Take back Microsoft from India.


--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

John C. wrote:

John C. wrote:

John C. wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I pressed >>> on the Windows logo key. Then after installing KB5058379 (or rather
having it shoved down my throat by M$), the Start Menu began opening
only after a short pause. Not a really long pause, but a short pause
that's just long enough to be annoying.

Has anybody else here experienced this problem?

TIA.

I rebuilt my iconcache and that seemed to help. My thanks to everybody
who replied.

I guess I was imagining things. Either that or the fix was only temporary.

Personally, I think M$ implemented this problem deliberately in order to subtly get people to by new computers or at least to go with the hated W11.

Unlikely a conspiracy that KB5058379 includes a deliberate attempt to
upgrade to new hardware or win10 with win 11.
- other folks would have reported this issue, especially those already responding in this group.

Temporarily create a new logon profile, test to validate the same
symptom occurs.

Go back to the original profile.
- change keyboard settings (a faster Repeat Delay and Rate setting)
- Delete and Rebuild the Search Index; ensure Windows Search 'Service'
is configured as Automatic(Delay Start)
- Note: if your logon profile system folders(Pictures and Music
folder has a large quantity of files exclude those system folders from
Search) - add them later after testing without. Also clear out any unnecessary files in Documents and Downloads including any no longer
valid shortcuts to any other non Windows drives or partitions.


--
....w¡ñ§±¤ñ

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On Sat, 5/24/2025 8:15 AM, John C. wrote:

John C. wrote:

John C. wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I pressed >>> on the Windows logo key. Then after installing KB5058379 (or rather
having it shoved down my throat by M$), the Start Menu began opening
only after a short pause. Not a really long pause, but a short pause
that's just long enough to be annoying.

Has anybody else here experienced this problem?

TIA.

I rebuilt my iconcache and that seemed to help. My thanks to everybody
who replied.

I guess I was imagining things. Either that or the fix was only temporary.

Personally, I think M$ implemented this problem deliberately in order to subtly get people to by new computers or at least to go with the hated W11.

Have you tried setting up a temporary account, logging in as
that account, and testing the menu response time ? Does the
problem go away when you do that ?

Similarly, if you do a clean side-by-side install and put
another copy of the OS on the same machine, patch it up to the
same up-to-date state, does it also do that ?

If everyones menu had just gone to hell, don't you think there
would be a mega-thread about it by now ??? I flipped over to the
Test Machine (a second keyboard mouse monitor on my desk),
pushed the Windows key, and the response time is
a third of a second or so.

In the Windows Update history on that machine, KB5058379
2025-05 Cumulative Update foe windows 10 Version 22H2
was installed on May 17, 2025. That's one week ago.

One thing I do notice, is with Task Manager open, pressing the
Windows key is causing some network spikes. the behavior is not
exactly reproducible each time (not the same amount of activity),
but there does seem to be some correlation there. Perhaps you've blocked
some networking activity related to pressing the Start button ? Maybe
it is timing out on something network related.

Paul

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

Keywords: VanguardLH,VLH

"John C." <r9jmg0@yahoo.com> wrote:

John C. wrote:

John C. wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I
pressed on the Windows logo key. Then after installing KB5058379
(or rather having it shoved down my throat by M$), the Start Menu
began opening only after a short pause. Not a really long pause,
but a short pause that's just long enough to be annoying.

I rebuilt my iconcache and that seemed to help. My thanks to everybody
who replied.

I guess I was imagining things. Either that or the fix was only
temporary.

Did you ever test with Win10 booted into its Safe Mode?

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: Usenet Elder (3:633/280.2@fidonet)

John C. <r9jmg0@yahoo.com> wrote:

John C. wrote:

John C. wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I pressed >> on the Windows logo key. Then after installing KB5058379 (or rather
having it shoved down my throat by M$), the Start Menu began opening
only after a short pause. Not a really long pause, but a short pause
that's just long enough to be annoying.

Has anybody else here experienced this problem?

TIA.

I rebuilt my iconcache and that seemed to help. My thanks to everybody
who replied.

I guess I was imagining things. Either that or the fix was only temporary.

Personally, I think M$ implemented this problem deliberately in order to subtly get people to by new computers or at least to go with the hated W11.

You don't say what you consider "a short pause".

That said. FWIW, on my wife's Windows 10 (Home) 22H2 system (with
KB5058379), the response is quite fast, probably well under half a
second (perhaps Paul's 400 milliseconds?) and that is on a slow machine.

FYI, the Windows Start Menu is never used on that (or any other)
system - we use Open-Shell Menu - and on the very first use, there is
indeed a delay of perhaps two seconds, but on subsequent invocations,
the response is as mentioned.

N.B. My own machine is a much faster Windows 11 system, but the
response time of the Start Menu is about the same as on the Windows 10
system.

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: NOYB (3:633/280.2@fidonet)

On Mon, 5/26/2025 5:52 AM, Frank Slootweg wrote:

John C. <r9jmg0@yahoo.com> wrote:

John C. wrote:

John C. wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I pressed >>>> on the Windows logo key. Then after installing KB5058379 (or rather
having it shoved down my throat by M$), the Start Menu began opening
only after a short pause. Not a really long pause, but a short pause
that's just long enough to be annoying.

Has anybody else here experienced this problem?

TIA.

I rebuilt my iconcache and that seemed to help. My thanks to everybody
who replied.

I guess I was imagining things. Either that or the fix was only temporary. >>
Personally, I think M$ implemented this problem deliberately in order to
subtly get people to by new computers or at least to go with the hated W11.

You don't say what you consider "a short pause".

That said. FWIW, on my wife's Windows 10 (Home) 22H2 system (with KB5058379), the response is quite fast, probably well under half a
second (perhaps Paul's 400 milliseconds?) and that is on a slow machine.

FYI, the Windows Start Menu is never used on that (or any other)
system - we use Open-Shell Menu - and on the very first use, there is
indeed a delay of perhaps two seconds, but on subsequent invocations,
the response is as mentioned.

N.B. My own machine is a much faster Windows 11 system, but the
response time of the Start Menu is about the same as on the Windows 10 system.

But the code for the Open Shell, was likely loaded. There is initialization activity when a desktop comes up, and some of that must include pre-loading things like menu code, so there isn't a pause. There must be some
other dependency which is not ready. Or something that is not actually
loading when it is supposed to.

I tested the Registry entry that has a range of 400..4000 by setting
it to the 4000 value, and that did not cause a four second delay
after the Windows key was pressed.

As for the general comment, that the OS constantly gets in the
users way, I was seeing a lot of that yesterday, and it did not
leave a good taste particularly. You have to wonder what goes on
in Design Intent meetings for this stuff. I was trying to get a download
to speed up, and use more of my line rate, and in the end what it
took was, shutting down every Windows box in the room, running a
Live Linux stick on just one machine, and doing the download. THEN
it ran at line rate. That's why I pay a high Internet fee every
month, just so I can watch that once in a while :-)

On the old MacOS, we used to disable the "zoomRects Animation", as
it made the system seem more snappy. But the animation on the
Windows key menu, isn't of a very long duration, so disabling that
is unlikely to make things feel snappy. A person on an underpowered
machine, would be more likely to benefit from turning off all the
special effects. And there are scroll throttles in place, to make
faster and slower machines, closer on desktop animation speed.
We don't want the customers to feel money-well-spent on a
faster CPU.

Paul

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

Paul wrote:

John C. wrote:

John C. wrote:

John C. wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I pressed >>>> on the Windows logo key. Then after installing KB5058379 (or rather
having it shoved down my throat by M$), the Start Menu began opening
only after a short pause. Not a really long pause, but a short pause
that's just long enough to be annoying.

Has anybody else here experienced this problem?

TIA.

I rebuilt my iconcache and that seemed to help. My thanks to everybody
who replied.

I guess I was imagining things. Either that or the fix was only temporary. >>
Personally, I think M$ implemented this problem deliberately in order to
subtly get people to by new computers or at least to go with the hated W11.

Have you tried setting up a temporary account, logging in as
that account, and testing the menu response time ? Does the
problem go away when you do that ?

I should have mentioned that I use Open Shell. In the past though, it's
never had any effect on Start Menu opening speed.

Similarly, if you do a clean side-by-side install and put
another copy of the OS on the same machine, patch it up to the
same up-to-date state, does it also do that ?

I'm afraid I'd never do such a thing due to the built in instability of
W10. It took me a great deal of effort to simply reinstall Windows 10
and all the programs I use from scratch, then tweak it the way I do.

If everyones menu had just gone to hell, don't you think there
would be a mega-thread about it by now ???

No need to get emotional about it. 80)>

I flipped over to the
Test Machine (a second keyboard mouse monitor on my desk),
pushed the Windows key, and the response time is
a third of a second or so.

Yes, that's about the length of the delay that I'm experiencing. It's
just enough to disorient me. Prior to the delay appearing, there was
literally no perceptible (note the word "perceptible") delay whatsoever.
And it was like that going back as far in time as W95.

In the Windows Update history on that machine, KB5058379
2025-05 Cumulative Update foe windows 10 Version 22H2
was installed on May 17, 2025. That's one week ago.

Right. And my OP was on the 22nd, a few days after the Start Menu delay
showed up.

One thing I do notice, is with Task Manager open, pressing the
Windows key is causing some network spikes.

My computer isn't on a network. I see a spike in CPU usage whenever I
press the start button though.

the behavior is not
exactly reproducible each time (not the same amount of activity),

Yes, I noticed this too. In fact, the spike is lower each time I do it
if I do it three or four times. The delay is about the same though.

but there does seem to be some correlation there. Perhaps you've blocked
some networking activity related to pressing the Start button ?

I have no idea what that would be.

Maybe it is timing out on something network related.

Could be. I use a router, but only my computer is plugged into it via a
CAT-5 cable. I've disabled wireless completely.

Windows 10 is a shitty, poorly coded, slow, buggy operating system. And
now Microsoft is trying to force me to go to an even worse version of
their greed-and-privacy-raping motivated crapware. Every day it seems, a
new W10 related problem appears and I have to spend literally an hour or
more dealing with it.

Thanks very much for replying, Paul

--
John C. No ad, CD, cripple, demo, nag, pay, pirated, share, spy,
time-limited, trial or web wares for me please.

I filter out crossposted messages, anything from various trolls and
block dizem.com. If you do the same, this newsgroup will be easier for
you to read.

Take back Microsoft from India.

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

Keywords: VanguardLH,VLH

"John C." <r9jmg0@yahoo.com> wrote:

Paul wrote:

Have you tried setting up a temporary account, logging in as that
account, and testing the menu response time ? Does the problem go
away when you do that ?

I should have mentioned that I use Open Shell. In the past though,
it's never had any effect on Start Menu opening speed.

The state of your Windows changes with an update. Many changes to Open
Shell were the result of changes in Windows.

Disable Open Shell, restart Windows, and test the Start menu that
Microsoft supplied. Start with the basics before compounding the
scenario with additional software.

If using Microsoft's Start menu resolves the issue, and since Open Shell
lets you backup its settings, save your settings into an XML file (to
later let you import them) or save the HKCU\Software\IvoSoft registry
key to a .reg file. Then reset Open Shell (click the Backup button to
see the drop-down list of options) to its install-time setup, and retest
Open Shell's Start menu for delay. You need to debug Open Shell, not
the standard Start menu.

You could search Open Shell's Github project under its Issues tab to see
if there have been problems with its Start menu, like:

https://github.com/Open-Shell/Open-Shell-Menu/discussions/1269 https://github.com/Open-Shell/Open-Shell-Menu/issues/2212

There are a lot of settings in Open Shell that are not available in
Microsoft's Start menu.

https://github.com/Open-Shell/Open-Shell-Menu/issues/2212

That one mentions KB5058379 as a possible candidate for Open Shell's
delay. That notes there is no delay when using Microsoft's Start menu.

For further discussion on a 3rd-party/non-standard Start menu
replacement, you might want to focus on asking a community that itself
is focused on that substitute Start menu product, like:

https://github.com/Open-Shell/Open-Shell-Menu/discussions

I didn't bother to check how active is that community to discuss Open
Shell.

What happened when you tried Paul's suggestion of creating and logging
into a new Windows account, and test with both Open Shell disabled and
then enabled?

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: Usenet Elder (3:633/280.2@fidonet)

Keywords: VanguardLH,VLH

Paul <nospam@needed.invalid> wrote:

VanguardLH wrote:

"John C." <r9jmg0@yahoo.com> wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I
pressed on the Windows logo key. Then after installing KB5058379 (or
rather having it shoved down my throat by M$), the Start Menu began
opening only after a short pause. Not a really long pause, but a
short pause that's just long enough to be annoying.

I'd try going into the fluff and cutsy display settings to eliminate
menu delay, and other glitz:

- Run: C:\Windows\System32\sysdm.cpl
- Advanced tab.
- Performance settings.

You could select the pre-defined "Best performance" profile.
....

https://winaero.com/how-to-speed-up-menus-in-windows-10-and-change-the-menu-delay/

I tested the Menu Show Delay, and setting it to 4000 from the default 400, made no difference to the Windows key opening the Start Menu. Same speed
as clicking the Start icon in the corner, with the mouse.

I would still try the other performance tweaks to see if any affect the
load time of the Start menu. Did you test if the superfluous and glitzy animation, fade, slide, and smooth options had no effect on the Start
menu? Microsoft might've decided to apply the cutsy options there, too.

Since the OP finally admitted to using Open Shell, there are tweaks in
there, too, that can affect the Start menu. That Open Shell worked well
for years does not obviate a Windows update causes it problems. That
project has made lots of changes to accommodate changes to Windows.
Isn't the point of Open Shell to replace the Start menu? Obviously the
first troubleshooting step should have been to disable Open Shell,
restart Windows, and retest for the Start menu delay when using
Microsoft's Start menu.

If the OP wants to use Open Shell then he needs to debug Open Shell, but
he should first check if the standard Start menu is afflicted, too.

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: Usenet Elder (3:633/280.2@fidonet)

John C. <r9jmg0@yahoo.com> wrote:

Paul wrote:

[...]

I should have mentioned that I use Open Shell. In the past though, it's
never had any effect on Start Menu opening speed.

Huh? If you use Open-Shell Menu, then why do you even bother with
Windows 10's native Start menu?

As I mentioned, I also use Open-Shell Menu on Windows 10 and 11 and
have never ever used the Windows 10 native Start menu. In order to try
to reproduce your 'problem', I had to find out how to invoke the native
Start menu (because it's 'hidden' by Open-Shell Menu).

So I could/can do everything I need with Open-Shell Menu, so why can't
you?

Can you give an example where you need the native Start menu?

[...]

I flipped over to the Test Machine (a second keyboard mouse monitor
on my desk), pushed the Windows key, and the response time is a
third of a second or so.

Yes, that's about the length of the delay that I'm experiencing. It's
just enough to disorient me. Prior to the delay appearing, there was literally no perceptible (note the word "perceptible") delay whatsoever.
And it was like that going back as far in time as W95.

You're joking, right!? A third of a second, for something you hardly
use and probably don't need to use at all, is a 'problem', in the
sense that it "disorients" you!?

[...]

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: NOYB (3:633/280.2@fidonet)

John C. wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I
pressed on the Windows logo key. Then after installing KB5058379 (or
rather having it shoved down my throat by M$), the Start Menu began
opening only after a short pause. Not a really long pause, but a
short pause that's just long enough to be annoying.

Has anybody else here experienced this problem?

TIA.

I have KB5058379 installed and do really notice any delay. Using 4.4.195.
--
<Bill>

Brought to you from Anchorage, Alaska



--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

Bill Bradshaw wrote:

John C. wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I
pressed on the Windows logo key. Then after installing KB5058379 (or
rather having it shoved down my throat by M$), the Start Menu began
opening only after a short pause. Not a really long pause, but a
short pause that's just long enough to be annoying.

Has anybody else here experienced this problem?

TIA.

I have KB5058379 installed and do really notice any delay. Using
4.4.195.

I should proof read better. I meant "do not really."
--
<Bill>

Brought to you from Anchorage, Alaska



--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)

On 25/05/26 06:18 AM, VanguardLH wrote:

Paul <nospam@needed.invalid> wrote:

VanguardLH wrote:

"John C." <r9jmg0@yahoo.com> wrote:

Running W10 Pro. Had my Start Menu popping open instantly when I
pressed on the Windows logo key. Then after installing KB5058379 (or
rather having it shoved down my throat by M$), the Start Menu began
opening only after a short pause. Not a really long pause, but a
short pause that's just long enough to be annoying.

I'd try going into the fluff and cutsy display settings to eliminate
menu delay, and other glitz:

- Run: C:\Windows\System32\sysdm.cpl
- Advanced tab.
- Performance settings.

You could select the pre-defined "Best performance" profile.
....

https://winaero.com/how-to-speed-up-menus-in-windows-10-and-change-the-menu-delay/

I tested the Menu Show Delay, and setting it to 4000 from the default 400, >> made no difference to the Windows key opening the Start Menu. Same speed
as clicking the Start icon in the corner, with the mouse.

I would still try the other performance tweaks to see if any affect the
load time of the Start menu. Did you test if the superfluous and glitzy animation, fade, slide, and smooth options had no effect on the Start
menu? Microsoft might've decided to apply the cutsy options there, too.

Since the OP finally admitted to using Open Shell, there are tweaks in
there, too, that can affect the Start menu. That Open Shell worked well
for years does not obviate a Windows update causes it problems. That
project has made lots of changes to accommodate changes to Windows.
Isn't the point of Open Shell to replace the Start menu? Obviously the
first troubleshooting step should have been to disable Open Shell,
restart Windows, and retest for the Start menu delay when using
Microsoft's Start menu.

If the OP wants to use Open Shell then he needs to debug Open Shell, but
he should first check if the standard Start menu is afflicted, too.

Good point, vanguardLH. I just checked and the regular Start Menu opens instantaneously.

By the way, when I go to:

Control Panel
System
Advanced system settings
Advanced
Performance
Settings...

I have "Custom:" selected and have the following enabled:

Show shadows under mouse pointer
Show shadows under windows
Show thumbnails instead of icons
Show translucent selection rectangle
Show window contents while dragging
Smooth edges of screen fonrts
Use drop shadows for icon labels on the desktop

Regardless, Open Shell seems to be causing the Start Menu delay. I don't
know why this is happening, because it wasn't doing this before the update.

Check out this discussion:

https://github.com/Open-Shell/Open-Shell-Menu/issues/2212

Naseband says "appeared for me around the same time even though I did
not install the Windows update (kb5058379?)." In my OP, this is the
same timeframe and update I mentioned.

Right now though, I'm trying to install a new water heater and will have
to get back to this.

--
John C. No ad, CD, cripple, demo, nag, pay, pirated, share, spy,
time-limited, trial or web wares for me please.

I filter out crossposted messages, anything from various trolls and
block dizem.com. If you do the same, this newsgroup will be easier for
you to read.

Take back Microsoft from India.

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On 25/05/26 08:11 AM, Frank Slootweg wrote:

John C. <r9jmg0@yahoo.com> wrote:

Paul wrote:

[...]

I should have mentioned that I use Open Shell. In the past though, it's
never had any effect on Start Menu opening speed.

Huh? If you use Open-Shell Menu, then why do you even bother with
Windows 10's native Start menu?

As I mentioned, I also use Open-Shell Menu on Windows 10 and 11 and
have never ever used the Windows 10 native Start menu. In order to try
to reproduce your 'problem', I had to find out how to invoke the native
Start menu (because it's 'hidden' by Open-Shell Menu).

So I could/can do everything I need with Open-Shell Menu, so why can't
you?

Can you give an example where you need the native Start menu?

[...]

I flipped over to the Test Machine (a second keyboard mouse monitor
on my desk), pushed the Windows key, and the response time is a
third of a second or so.

Yes, that's about the length of the delay that I'm experiencing. It's
just enough to disorient me. Prior to the delay appearing, there was
literally no perceptible (note the word "perceptible") delay whatsoever.
And it was like that going back as far in time as W95.

You're joking, right!? A third of a second, for something you hardly
use and probably don't need to use at all, is a 'problem', in the
sense that it "disorients" you!?

[...]

Frank, you can't compare what I experience with what you experience and
expect there to be no difference. NO, I'm NOT joking. In my case, the
delay is exactly long enough to frustrate and disorient me. And I'm not
alone in this:

https://github.com/Open-Shell/Open-Shell-Menu/issues/2212

Attempting to derail this discussion by ridiculing me as you have just
done is unworthy of you.

--
John C. No ad, CD, cripple, demo, nag, pay, pirated, share, spy,
time-limited, trial or web wares for me please.

I filter out crossposted messages, anything from various trolls and
block dizem.com. If you do the same, this newsgroup will be easier for
you to read.

Take back Microsoft from India.

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

John C. <r9jmg0@yahoo.com> wrote:

On 25/05/26 08:11 AM, Frank Slootweg wrote:

John C. <r9jmg0@yahoo.com> wrote:

Paul wrote:

[...]

I should have mentioned that I use Open Shell. In the past though, it's
never had any effect on Start Menu opening speed.

Huh? If you use Open-Shell Menu, then why do you even bother with
Windows 10's native Start menu?

As I mentioned, I also use Open-Shell Menu on Windows 10 and 11 and
have never ever used the Windows 10 native Start menu. In order to try
to reproduce your 'problem', I had to find out how to invoke the native Start menu (because it's 'hidden' by Open-Shell Menu).

So I could/can do everything I need with Open-Shell Menu, so why can't you?

Can you give an example where you need the native Start menu?

[...]

I flipped over to the Test Machine (a second keyboard mouse monitor
on my desk), pushed the Windows key, and the response time is a
third of a second or so.

Yes, that's about the length of the delay that I'm experiencing. It's
just enough to disorient me. Prior to the delay appearing, there was
literally no perceptible (note the word "perceptible") delay whatsoever. >> And it was like that going back as far in time as W95.

You're joking, right!? A third of a second, for something you hardly
use and probably don't need to use at all, is a 'problem', in the
sense that it "disorients" you!?

[...]

Frank, you can't compare what I experience with what you experience and expect there to be no difference. NO, I'm NOT joking. In my case, the
delay is exactly long enough to frustrate and disorient me. And I'm not
alone in this:

https://github.com/Open-Shell/Open-Shell-Menu/issues/2212

Attempting to derail this discussion by ridiculing me as you have just
done is unworthy of you.

I see that you failed to answer my three other specific questions
(which were mostly repeated in this last one).

Not to mention that the answer to the last one is irrelevant, if you
had answered the earlier ones.

Someone is indeed "Attempting to derail this discussion", but I'm
afraid it's not me.

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: NOYB (3:633/280.2@fidonet)

Frank Slootweg wrote:

John C. wrote:

Frank Slootweg wrote:

John C. wrote:

Paul wrote:

[...]

I should have mentioned that I use Open Shell. In the past though, it's >>>> never had any effect on Start Menu opening speed.

Huh? If you use Open-Shell Menu, then why do you even bother with
Windows 10's native Start menu?

I *don't* bother with the W10 native Start Menu. Ever.

As I mentioned, I also use Open-Shell Menu on Windows 10 and 11 and
have never ever used the Windows 10 native Start menu. In order to try
to reproduce your 'problem', I had to find out how to invoke the native
Start menu (because it's 'hidden' by Open-Shell Menu).

Press and hold the shift key while clicking on the Start button with
your mouse. You can also hold the shift key down while simultaneously
pressing the Windows key.

So I could/can do everything I need with Open-Shell Menu, so why can't >>> you?

??? I never said that I can't

Can you give an example where you need the native Start menu?

Why bother since I never, ever use it.

[...]

I flipped over to the Test Machine (a second keyboard mouse monitor
on my desk), pushed the Windows key, and the response time is a
third of a second or so.

Yes, that's about the length of the delay that I'm experiencing. It's
just enough to disorient me. Prior to the delay appearing, there was
literally no perceptible (note the word "perceptible") delay whatsoever. >>>> And it was like that going back as far in time as W95.

You're joking, right!? A third of a second, for something you hardly
use and probably don't need to use at all, is a 'problem', in the
sense that it "disorients" you!?

Repeated over and over and over etc.

[...]

Frank, you can't compare what I experience with what you experience and
expect there to be no difference. NO, I'm NOT joking. In my case, the
delay is exactly long enough to frustrate and disorient me. And I'm not
alone in this:

https://github.com/Open-Shell/Open-Shell-Menu/issues/2212

Attempting to derail this discussion by ridiculing me as you have just
done is unworthy of you.

I see that you failed to answer my three other specific questions
(which were mostly repeated in this last one).

I wasn't bothering because they are irrelevant to my OP. Entirely.

Not to mention that the answer to the last one is irrelevant, if you
had answered the earlier ones.

Someone is indeed "Attempting to derail this discussion", but I'm
afraid it's not me.

No, it's you all right. I have better things to do with my time than
argue with you.

Over and out.

--
John C. No ad, CD, cripple, demo, nag, pay, pirated, share, spy,
time-limited, trial or web wares for me please.

I filter out crossposted messages, anything from various trolls and
block dizem.com. If you do the same, this newsgroup will be easier for
you to read.

Take back Microsoft from India.

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

John C. <r9jmg0@yahoo.com> wrote:

Frank Slootweg wrote:

John C. wrote:

Frank Slootweg wrote:

John C. wrote:

Paul wrote:

[...]

I should have mentioned that I use Open Shell. In the past though, it's >>>> never had any effect on Start Menu opening speed.

Huh? If you use Open-Shell Menu, then why do you even bother with
Windows 10's native Start menu?

I *don't* bother with the W10 native Start Menu. Ever.

That was the confusing bit.

From the start, you mentioned "Start Menu" (see the subject line)
without mentioning Open-Shell (Menu). Later you mentioned Open-Shell,
but it wasn't clear the delay was in Open-Shell Menu, as you kept
mentioning Start Menu, which is the native Windows menu, because
Open-Shell Menu is - well - called Open-Shell Menu.

That was of course all clear to you, but not to us. Our crystal balls
are in the shop.

That's why the answers to my (and others') questions were/are
important.

You've now answered those - thanks - and all is clear. Case closed.

[My questions and your answers deleted.]

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: NOYB (3:633/280.2@fidonet)

John C. wrote:

Over and out.

At least that's some form of progress!!!

Having proved its related to a 3rd party app and not the Windows 'Start
Menu', you've also proved the fallacy in your earlier statement that it
was MSFT KB that caused the problem.


Personally, I think M$ implemented this problem deliberately in
order to subtly get people to by new computers or at least to go
with the hated W11.
</qp>




--
....w¡ñ§±¤ñ

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On Wed, 28 May 2025 14:07:31 -0400, ...winston wrote:

[snip]

Personally, I think M$ implemented this problem deliberately in
order to subtly get people to by new computers or at least to go with
the hated W11.

I remember hearing that the real purpose of Windows is to sell hardware.

--
Mark Lloyd
http://notstupid.us/

The fool says in his heart, "There is no God." The Wise Man Says it to
the World.

--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)