Windows 10: Windows 11 - Long shutdown times, lockscreen and start menu search unresponsive to keyboard.

Issue:Recently when I booted up my pc, I couldn't get to the enter password page of the lockscreen with my keyboard, but I still could with my mouse. After logging into the OS by entering the password with my keyboard, I've noticed that the start menu search is unresponsive to my keyboard. Restarting explorer.exe didn't help, so I restarted my pc. Restarting my pc took longer than expected. Usually it's ~1 minute but it took ~5 minutes this time. After restarting everything worked fine though, so I didn't think too much of it.The next day, the exact same thing happened. So I decided to do some

:)

 

Start Menu Search

Hi,

About your issue regarding the Start menu or Search, in order for us to assist you better. Please answer the question:

• Were there any recent changes made to your system prior to the issue?

In the meantime, we suggest you to check this link:
Troubleshoot problems opening the Start menu or Cortana. It contains troubleshooting steps prior to the issue.

We'll look forward to your response.

 

Windows 11 start menu button unresponsive

After applying the cumulative february update (windows 11) my start menu became unresponsive, even completely freezing my firefox browser sometimes when i tried to open the start menu, i couldn´t click anywhere else for some second, I deleted the update and waited for march update, now the problem is more or less resolved but I still have the problem that the start menu isn´t as responsive as it was, now it usually takes up to 4 second to open after I press the windows button on my keyboard, before all these update it had an almost instant response, please help me out I tried to search for answers across the internet but haven´t found anything that resolves my problem, thanks

 

Start menu typing is very unresponsive and looks like it's doing an internet search in the background

Typing after bringing up my Windows 10 (1703, OS Build: 15063.674) start menu is extremely unresponsive; many key presses do not result in any characters registered in the search string. Only if I wait about 3 seconds between each key press do I more reliably
get text entered into the start menu search.

I notice that, after typing a first key after bringing up the start menu, there's a half to one second delay before the 'Best Match' list is updated, after which there's a blue highlight on the top item in the list. The blue highlight (background colouring
on the top result) quickly disappears (goes white) before reappearing again about two seconds later. If I wait the 3 seconds or so for the blue highlight to reappear on the top item in the start menu search results then I find that the next key press gets
registered. Only the next single keypress, however; multiple key presses after that almost always get lost/ignored.

Now, if I disable my internet network access (through disabling my ethernet adapter), then all start menu key presses are immediately responsive an searches work exactly as they used to and should.

I've done a bit of reading elsewhere and noticed that a couple of settings might relate to this behaviour. I've shown my current settings below -

• gpedit.msc: local computer policy > computer configuration > administrative templates > windows components > search
  • do not allow web search: Enabled
  • Don't search the web or display web results in search: Enabled
  • Don't search the web or display web results in search over metered connections: Enabled
• regedit: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search
  • ConnectedSearchUseWeb: 0

So it looks as though all settings related to any kind of internet searching when typing in the start menu would appear to disable any internet search, but the fact that disabling my network access returns responsiveness would suggest there's still might
be some sneaky, annoying thing elsewhere that's not heeding these settings.

In case it's relevant, I also have 'developer mode' turned on.

Might there be some office network group policies that conflict or override any of these 'local' settings that might account for this behaviour? I should mention that not everyone on my work group domain suffers from this behaviour; only other that I know
of has this issue, while everyone else, on the same version of windows, seems to have normally responsive start menu search typing.

Are there any other settings elsewhere that would explain this behaviour and the terribly unresponsive start menu search?

Does anyone have any ideas as to what's causing this and how to fix it?

Thanks

Dan