Mouse stickiness change with multiple monitors after Windows 8.1 Update 1: Bug or feature?

Anonymous
2014-04-06T22:26:14+00:00

There is a new bug that won't let the mouse to the other screen unless you move the mouse quickly across the monitor edge. Before, this would only happen on the corner edges to allow easier access to the charms and apps bar. Now, it happens to the whole edge.

These four videos demonstrate that the mouse stickiness issue happens in both desktop and metro mode and that it is inconsistent - only happening sometimes. I hope these videos help paint a clear picture of what is going on.

Desktop Mode

http://youtu.be/-0mrPXXtkfw No bug

http://youtu.be/3TVYvu4Yi5g Bug

Metro Applications

http://youtu.be/hOEeo9r0xs8 No bug

http://youtu.be/b-Usdhnvl3A Bug

Is this issue already known and will there be a hotfix, or is this a new feature?

November 12th 2014 Update

Mouse stickiness still a problem as of today for Windows 8.1. As of Windows 10 Build 9879 which was released today, the mouse stickiness is fixed! This mouse stickiness only happens when dragging a window around and is used to assist in snapping windows. Outside of this, the stickiness issue is gone! I think this was what Microsoft intended to do with the mouse stickiness, but I believe it was a hard bug to diagnose, but they finally fixed it!

November 2nd 2014 Update

Mouse stickiness still a problem as of today for Windows 8.1. As of Build 9860 of Windows 10 Technical Preview, the mouse stickiness bug/feature has started happening.

June 9th 2014 Update

Still no official word from Microsoft. I have found a fix, but it is more of a workaround. Just don't use any metro apps, and it should be fine. Very rarely you will get the stickiness again. If it does occur anyways just press WIN + P and click Duplicate. After all monitors are duplicated, press WIN + P again and then click Extend to go back, and the mouse stickiness issue should be gone.

May 16th 2014 Update

According to Shawn "Cmdr" Keene \[MVP\] at the end of page 2, this is NOT a bug and it is an intentional design. I hope that Shawn is incorrect and would like further verification by an employee of the Windows development team.

There is also a "fix" by editing some registry values, but this removes the mouse stickiness on the corners and makes it very hard to access the apps and charms bar in between monitors. I do not believe this is a fix to the problem.

May 5th 2014 Update

Still no word from Microsoft that this is a bug or feature.

Windows for home | Previous Windows versions | Search, touch, and mouse

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

56 answers

Sort by: Oldest
  1. Anonymous
    2014-09-10T09:05:13+00:00

    This is very very VERY annoying:

    I am the user and I know better than my PC, what I want to do. How does Microsoft dare, that they know better than me, how I want to use my mouse?

    I work with 3 monitors on my PC since years, I know how to use a mouse. For me everything worked fine until yesterday (09.09.2014):

    I bought a new mouse and this was the first time, I experienced this issue. 

    So that means: old mice (Microsoft Comfort 6000, Logitech MX518) work fine. New mouse G502 does not work as it should...

    Amzing featur: you have to use OLD devices to work (when you work the whole day, you get mad with this bug).

    Someone mentioned registry entries... anyone has more details please?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-10-12T17:52:15+00:00

    It's not a bug, it's a feature. To fix it you need to change three values in the registry. Go to HKCU\Control Panel\Desktop and look for DWORD value MouseMonitorEscapeSpeed, change it's value data to 1.

    Next, go to HKCU\Software\Microsoft\Windows\CurrentVersion\ImmersiveShell\EdgeUI. You will see three items listed there, two blue and one red. Change the value data of the two blue items to 1. Restart windows explorer or restart the PC (restarting explorer.exe in task manager is the easier way). Congratulations! You have successfully gotten rid of the "screen edge mouse stickiness". I hope this has helped. Let me know if you have any further questions regarding this issue. 

    Oh, I forgot to add that "HKCU" actually stands for HKEY_CURRENT_USER. I just shortened it because I didn't feel like typing all of that.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-10-12T18:13:07+00:00

    I've already done that, however in ImmersiveShell, EdgeUI is the only value listed.  There aren't two blue values as you say and it's not its own branch either, just a single value, but both EdgeUI and MouseMonitorEscapeSpeed were set to 1 months ago, and I still have the issue.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-11-03T04:29:45+00:00

    Windows 10 Technical Preview build 9860 has this bug also, now. In the previous build, the first Technical Preview, there wasn't the mouse stickiness issue. I've updated the original post with this information, and I hope we can get an official statement from Microsoft if this is in fact a feature or bug.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-11-14T18:25:42+00:00

    November 12th 2014 Update

    Mouse stickiness still a problem as of today for Windows 8.1. As of Windows 10 Build 9879 which was released today, the mouse stickiness is fixed! This mouse stickiness only happens when dragging a window around and is used to assist in snapping windows. Outside of this, the stickiness issue is gone! I think this was what Microsoft intended to do with the mouse stickiness, but I believe it was a hard bug to diagnose, but they finally fixed it!

    But how do we stop this behaviour?!?! The previous fixes have worked thus far for the mouse sticking on it's own. Now it's INCREDIBLY tedious dragging Windows around unless I use extreme mouse speeds.

    Was this answer helpful?

    0 comments No comments