Mouse only works on one window or on windows of one application - and how to restore normal operation

Robin Whittle 0 Reputation points
2026-04-27T15:35:28.2233333+00:00

Further to the locked question https://learn.microsoft.com/en-us/answers/questions/4105102/mouse-only-works-on-one-window for which there was no useful answer, with 40+ people having indicated they had the same question, here is my experience and a way I found to break out of this state. This is on Windows 11 Pro 64 bit with a Logitech M575 trackball, hereafter "the mouse".

The behaviour is that the mouse left button only has its proper functionality in one window, if the application has just one window, or perhaps in multiple windows of an application, Firefox in my case. This might not be obvious, because that one functional window might not be visible, since it is hidden by others, or I guess it could be minimised. Also, the window could be on another desktop. So the observed behaviour may be that the mouse buttons no longer work at all. I recall that I was not able to right-click the Task bar to bring up Task Manager.

Closing that window caused some other window - such as one which was on top of all the others except the one just closed, including a window of a different application - to function properly with the mouse left button. (The right button seemed to suffer the same problems, but I did not test this,)

The Windows button on the keyboard brings up the Start menu, but mouse left-button clicks on it do nothing.

Alt-Tab brings up the facility for dragging windows from one desktop to another, but any attempt to do so, which involves clicking the left button with the cursor over the mini-window I want to drag, cancels the whole facility and returns me to the ordinary desktop currently selected. Likewise left-clicking anywhere else.

One approach would be to turn the computer off and on again. I was going to do this and used the Windows key to bring up the Start menu, from which I used tab and/or row keys to get to and hit Enter for the Shutdown > Restart menu item.

Since I had more than one application which Windows was not able to close immediately, due to them potentially having user data which had not been saved, Windows put up a list of these applications, or rather the many windows, some of which were for the same application, with an option for me to cancel if I did not want to potentially lose such user data.

After the cancel operation was complete, which took 30 seconds or more, my desktop (and others when I switched to them) appeared, with application windows still running, I think because they were on this list of application windows which Windows was not able to close on its own.

Then, the mouse buttons worked on all windows.

I have no idea what got the system into this perplexing state, but it has happened to me several times since around early 2026. This is surely a BUG.

Windows for home | Windows 11 | Performance and system failures
0 comments

1 answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-04-27T15:35:54.9833333+00:00

    The described behavior matches known issues where mouse input is effectively “captured” or blocked so that clicks only work in a specific window or desktop context. There are two relevant patterns in the provided material and both point to system-level bugs rather than a hardware fault:

    1. Mouse actions blocked across desktops / virtual desktops (Windows 8.1 / Server 2012 R2)
      In earlier Windows versions, mouse actions could be blocked when creating or using a virtual desktop because mouse hooks were invoked across desktops. This caused clicks not to behave as expected in some windows or desktop contexts. Microsoft confirmed this as a bug and fixed it via a security update (KB3002885).
    2. UI elements (Start button, charms, app controls) not responding (Windows 8.1)
      Another confirmed bug caused the Start button and other UI elements not to respond to mouse input, while keyboard and touch still worked. Workarounds included restarting Windows Explorer or signing out and back in. Disabling certain corner navigation behavior reduced recurrence.

    While those documented issues are for Windows 8.1/Server 2012 R2, they show that:

    • Mouse input can be misrouted or blocked at the shell/desktop level.
    • The system can end up in a state where keyboard still works but mouse clicks only work in limited contexts or not at all.
    • Restarting shell components or forcing Windows to re-evaluate running apps/desktops (for example, via sign-out, restart, or update) can restore normal behavior.

    In the scenario described:

    • Only one window (or one app’s windows) responds to mouse clicks.
    • Keyboard shortcuts (Windows key, Alt+Tab) still work.
    • Initiating a restart, then canceling at the “apps preventing shutdown” screen, forces Windows to enumerate and interact with all open windows. After this, mouse input works normally again.

    This is consistent with a shell/desktop input-routing bug similar in nature to the documented issues. The cancel operation during shutdown effectively acts like a partial shell reset: Windows re-queries and interacts with all top-level windows, which appears to break the stuck state and restore normal mouse routing.

    Given the available documentation, the most closely aligned mitigations are:

    1. Force a shell reset when the problem occurs
      Instead of fully rebooting, try the equivalent of the Windows 8.1 workaround:
      • Open Task Manager (Ctrl+Shift+Esc or Ctrl+Alt+Del → Task Manager).
      • Locate Windows Explorer in the Processes list.
      • Right-click it and choose Restart.
    2. Sign out and sign back in
      • Use the Windows key to open Start.
      • Use keyboard navigation to select the account menu and choose Sign out.
      • Sign back in.
        This resets the user shell and desktop session without a full reboot.
    3. Full restart if needed
      • If the shell reset or sign-out does not help, perform a full restart. The behavior described (attempting restart, then canceling when prompted about unsaved work) is effectively a variant of this that happens to reset the problematic state.
    4. Keep system fully updated
      Since similar mouse-blocking issues were fixed by cumulative/security updates in earlier versions, ensure Windows 11 is fully updated via Settings → Windows Update → Check for updates.

    The behavior described is consistent with a system bug in input routing rather than a Logitech device or driver problem. The practical recovery steps, based on documented similar issues, are to restart Windows Explorer, sign out/in, or restart the system, and to keep Windows updated so that any underlying shell/input bugs are addressed by future fixes.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.