I've assigned shortcut keys to numerous application shortcuts (right click the shortcut > Properties > Shortcut tab > Shortcut key). I've been using these shortcut keys for years with no problems, but this morning they stopped working normally.

When I press they shortcut key I see a very brief change in the cursor's state, then nothing launches. However, they do work in two situations:

  1. If any Windows folder is open

  2. Very weirdly—if Firefox is running; I've found no other program that enables the shortcut keys in this way

Other relevant details:

  • Most of the shortcuts are in C:\ProgramData\Microsoft\Windows\Start Menu\Programs

  • Shortcuts directly on the desktop have the same problem

  • All shortcut keys are of the form form Shift-Ctrl-Alt-(key)

  • DISM.exe and sfc /scannow reported problems but fixed them, and now they report all is clear

  • Multiple malware scanners say all is well

  • Possibly related: when I booted up this morning, my desktop shortcuts—which are normally grouped by topic—were all clustered together in the standard desktop "align to grid" configuration, even though "align to grid" wasn't enabled

Any idea what's gone wrong and how to fix it?

I'm wondering whether this could be a problem introduced by a Microsoft OS update. Windows Update History says the following were applied yesterday (Patch Tuesday 9/11/2018):

  • 1
    A number of Windows 10 updates have caused issues with shortcuts, such as disabling the keyboard shortcuts to links and requiring links to be in specific locations. Though I know of no fix within Windows, some free third-party tools such as Clavier+ provide workarounds. See superuser.com/questions/1280211/… Sep 12, 2018 at 23:09

2 Answers 2


The actual cause is Nvidia's overlay, which as of 2019 is called "In-Game Overlay" in the settings page within GeForce Experience, and is controlled by the "NVIDIA Share" process. The overlay itself also listens for hotkeys; presumably that interaction is the source of the problem.

To be clear - as the asker indicated, this concerns the unfortunately-named shortcut key assignable in the properties of a Windows shortcut (see https://i.imgur.com/573caBf.png).

As a workaround, disabling the "In-Game Overlay" setting within GeForce Experience will prevent the indicated problem - that shortcut keys no longer work when you are on the desktop, i.e. all programs are minimized. Enabling the overlay feature will prevent shortcut keys from working in that situation.

Unlike the asker, I found that the shortcut keys will work so long as any program* is unminimized - it does not even need to be focused. Nvidia's overlay has special behavior regarding the desktop itself, but this bug is not dependent on the related setting (Privacy Control -> Desktop Capture) within the nVidia Overlay.

*This includes, for example, even the properties pane of a shortcut. However, it does NOT include UWP apps such as the modern Windows Calculator or the modern Personalization dialog. It also does not include the Nvidia Overlay itself, nor utilities like RainMeter.

  • I confirm the above as of Windows 10 Pro 1909 Update and Nvidia Driver Version 441.20 the problem still persist. And the workaround is to disable Nvidia In Game Overlay as @Tofof mentioned. His answer should be accepted answer as it fully covers the issue.
    – patrykos91
    Nov 20, 2019 at 21:40

This problem has resolved. The cause was either the 9/2018 Windows Update or—more likely—nVidia's driver.

This morning, the October 2018 Windows Update finally became available for me to install (Windows 10, version 1809). As soon as I installed it, my third monitor stopped being recognized. At that point, shortcut keys were still working in the problematic way described in the question.

In troubleshooting the monitor problem, I deinstalled my nVidia driver and reinstalled the latest version. Once I finally got all of my monitors working again, shortcut keys were working consistently.

So either:

  1. the fix was in the October 2018 Windows Update, and for some reason there was a delay before it took effect; or
  2. more likely, since the problem resolved after re-installing nVidia's driver, the problem was somehow caused by that software

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .