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

I tried the registry tweak for escape velocity, did both entries, restarted and it seemed to work. then it came back....

really frustrating. 

I found that if you win+p, and then click duplicate, then win+p again and go back to extend it fixes the problem relatively quick.

After messing around with this issue I think I found out what is the "intended feature" and how to avoid it.

When you have a metro app open, a new bar appears at the top (to drag around to move the metro app to different monitors, or minimize, or close the app.

This bar only appears when the mouse is at the top of the screen (or for a short period of time after you open the metro app).

When this bar is visible, then the mouse will be sticky-edged on all monitors for the full border.

If you wait the period of time for the bar to disappear, the sticky-edges will disappear and revert to how they performed in windows 8.1 (pre-update 1). It will only be sticky near the corners.

I think the main problem is, if you use the minimize, or close option on the bar of the metro app then windows considers this option still "on" so the mouse will be sticky-edged.

The way I avoid this if I want to minimize or close the metro app is by:

1- opening metro app.

2- wait for bar to disappear (by keeping mouse away from top)

3- Alt+Tab to a desktop app. (Or drag a desktop window from different monitor and overlap the metro app which minimizes the app)

4- If I want to close the app, I right click on the app in the taskbar and close it. If I want it minimized I just drag a window from the desktop (on a diff monitor) on top of the metro app to minimize it.

Either way, I feel that this new "metro bar" at the top of metro apps isn't optimal for PCs with multiple monitors.

Hopefully in the next update the either add an option or remove the 'sticky edges' association with their new metro-app bar.

Sorry. This does not work for me.

I have used the registry edits with no solid success.

I tried your recommendation to open a metro app, let the title bar hide and then alt tab out to the desktop...

The moment that I do not move my mouse fast enough to "escape" the screen... the problem becomes much worse. I mean it literally forces me to jerk the mouse across the edge in order to swap.

Microsoft needs to remove this feature until they get it fixed... or give us the checkbox to turn it off, since the registry edit isn't working for everyone.

 have used the registry edits with no solid success.

Does that mean the registry value is going back to default somehow?  If so and you know the frequency of occurrence (or can stand the overhead) you could run ProcMon to capture when it happens.  Supposedly there is also a method of tracking registry events using Auditing but I am only familiar with using ProcMon to do this.

HTH

Robert Aldwinckle
---

My mouse was still sluggish after going through all the fixes in this thread. I then thought that it might be an issue with my screen since I am trying to get it to work on my secondary screen which is a 32" LG. After switching my secondary monitor to "Game" mode in the picture settings of the screen itself, the problem went away.

Could it be a refresh rate problem? When I was in any other mode the mouse was lagging and felt "heavy" across my extended desktop.

My original monitor (22") was working fine and so I originally thought it was a driver issue or a resolution issue but I was already up to the max resolution.

I have tried this with 3 monitors now (LG, Samsung, and Sharp) and all are working fine once put in "Game" mode.

I hope this helps someone. This would have been a deal breaker for me had I not fixed the issue.

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?