slow windows desktop keyboard shortcuts

Solution 1:

The original question deals with Windows 7, but it's happening now for new reasons in Windows 10. Here's a general answer that deals with both situations.

The general problem

There's an excellent explanation of the problem and its cause at the 2012 MSDN post Why is there sometimes a long delay between pressing a hotkey for a shortcut and opening the shortcut?

Executive summary: before launching a program via its shortcut key, Windows first polls all currently running programs and asks "Is this your shortcut key?" If so it switches focus to that window rather than spinning up a new copy of the program.

The problem happens when a window somewhere refuses to answer the question. This can be a program that's generally non-responsive for some reason, though it can also happen for other reasons (see below). Windows waits 3 seconds before muttering "jerk" under its breath and moving on to the next window to ask it the same shortcut question.

Finding unresponsive programs

1. Start Windows, then before opening any other programs try a shortcut key. Do you experience a delay? If so, go to step 3.
2. Launch any other programs you typically run. Do you experience a delay? If not, wait until you do.
3. One by one, stop each interactive program; cycle through them with Alt-Tab to be sure you've got them all. After stopping each one, see whether the shortcut delay has gone away.
4. Still have a delay? Do the same thing with the icons in the taskbar's notification area (aka the "system tray"): right click and exit, checking for the shortcut delay after each one. You might need to expand the notification area to see all of those icons.

Now that you know your culprit, you get to decide: is that program worth the delay it causes? For example, Adobe Creative Cloud has sometimes caused problems for me, so I just tell it not to run when Windows starts. I can still use Illustrator etc. without it running.

If you can't live without the program, either live with the shortcut key delay or, as "user 99572 is fine" suggests, try a macro program like AutoHotKey.

Windows 10: Action Center

Windows Action Center can also cause the delay. (This might be a problem in Windows 8 too; I skipped from 7 to 10). Whenever you see this:

it means the Action Center has system notifications for you to review—which also causes the shortcut key delay, even though the Action Center isn't non-responsive per se.

Click the icon and clear the notifications, then the icon will look like this, and Action Center should no longer cause a shortcut key delay:

If a notification comes up repeatedly and you find it unhelpful, right click it and tell Windows to turn off notifications for that application.

BUT... sometimes Action Center can cause problems even if no notifications are waiting. Even with no notifications showing, I've often cleared up this problem simply by opening and closing Action Center. You can do this quickly with the [Windows]-A shortcut key combination.

Windows 10: unresponsive background processes

Sometimes a background process can cause this problem too. Two in particular are:

• Calculator
• Store

There might be others culprits as well. The significant thing is that these are foreground applications that, for some reason, appear as background processes even though you might not have actually run them. This problem might happen with other apps, and might be limited to Metro apps (TBD).

You can use some or all of the following techniques to eliminate these processes:

1. Kill them manually with the task manager whenever you notice them.
2. As discussed in harrymc's answer to this related superuser question, turn off specific background apps at Settings > Privacy > Background Apps. Not all apps can be turned off in this way.
3. As discussed in Helen's answer to the same superuser question as above, disable Superfetch.

After using techniques #2 and #3, these rogue background processes no longer appear on my computer.

New problem in Windows 10 build 1809 (2/2019): Settings App

This Windows build has introduced a new and pernicious shortcut inhibitor. As soon as you start Windows, go to task manager. You have the problem if you see Settings running as a background task:

If you kill this task, shortcut keys will be fast again, but the Settings app will reappear a while later, re-introducing the problem.

As noted by Cerno in the comments, Windows 10 Enterprise users are able to prevent Settings from running in the background by going to Settings > Privacy > Background Apps. But for Windows Home and Professional users, "Settings" does not appear in the background app list. (If anyone knows of a way to make it appear, please post in the comments.)

July 2020 Update on Settings: After installing Windows 10 Pro v2004 Build 19041.388 (7/2020), my computer became unstable and I had to reinstall Windows. Since doing this, "Settings" now appears as an option in Settings > Privacy > Background Apps. I don't know whether this happened because of installing Build 19041.388 or because of the subsequent reinstall. In any case, disabling Settings as a background app has (finally!) resolved the problem for me.

Other...

This 3-second timeout probably doesn't cause every keyboard shortcut delay.

One one of my laptops, whenever Adobe Creative Commons is running in background I sometimes experience a delay lasting as long as 30 seconds before launching an app. That's 10 times the timeout Window uses before giving up on a non-responsive process, so something else must be going on in this case.

Solution 2:

If you're on Windows 10, try killing "Application Frame Host" (ApplicationFrameHost.exe). This made the delay disappear on my system.

Note that if you kill this process, it will close any modern (UWP = Universal Windows Platform) apps you have running.

Solution 3:

My personal experience was that there was a program that was delaying Windows' handling of the hotkey. For myself it was Steam, for Andreas it was Akamai.

To diagnose which application is responsible simply close an application and try your hotkey again. Once you figure out who the culprit is, decide whether it's a service that you can deal with not running at all times.

I know this is a fairly old question, but after not finding an answer I stumbled upon the solution and felt the need to share it with the community.

Solution 4:

The problem might have some to do with how Windows finds these shortcuts. Any reasonable person might expect that they store the shortcut data in the registry, the registry resides in RAM, and they put everything else in there. :-)

Instead the key shortcuts for .LNK and .URL are inside the shortcut itself.

As you can see in the picture, after trying to trace down where it was in the registry (it's not), I found the change in the shortcut own data itself.

There are 2 major locations where this data is scanned from, anywhere in all of the Start menu, and via the desktop folder.

When people find that removing some program, or some web program, "fixes" the problem, maybe it has to do with items, or mappings, or some unapproved stuff in the Start menu or the desktop?

After realising the method used, it was easy enough to take the advice of using another method other than windows, to do the same things.

The Notepad shortcut method used, is going to add microbes of delay also. A shortcut to a text file itself, that will eventually open a Notepad, will get to go through a fun process. Find the class bounce around in the registry, find the associated program, open that program, and pass in that parameter.

Most program shortcuts can have quoted whole paths "C:\Windows\notepad.exe", instead of using environment variables to eventually locate the program, in the many environment variable paths. Many programs like to stuff their program path into the environment variable path, they have even broken the "search path" there by making the line to long.

Most program shortcuts can also have quoted parameters placed after the quoted program path "d:\documents\todo.txt". This has the computer finding the file direct without searching or guessing, and passing the file to it immediately. (The quotes are only necessary when there are spaces.)

If you want to see speed, try it as "C:\Windows\notepad.exe" "d:\documents\todo.txt" and cut out the middleman. Create the shortcut for the program instead (notepad), and add a parameter for the .TXT file into the program shortcut. OK it's like DOS now. :-) But faster.

To check the environment variables (which is only for specific issues), go to "System", and in the "System Properties", in "Advanced" bring up the "Environment Variables" and look at the mess in the PATH variable.