Windows Creators 2017-05 cumulative update KB4020102

Extensive mouse delay and stutter

I had installed Windows Creator early April when it first was introduced. One other cumulative update was installed to my system on May 10 (KB4016871). The other day, I installed this new cumulative update and immediately started noticing extensive mouse stutter and delay. Prior to installing this small update, the mouse was working fine with multiplicity under Windows 10 creators update in subsequent update.

Thinking something had happened to my mouse in the process I switched mice with no change in the stuttering and delay. I then did a safe boot and noticed that there was no delay or stuttering. Having noticed some prior posts about earlier versions of multiplicity causing this, I returned to a normal boot but unchecked the multiplicity service and restarted. The mouse returned to its normal operating behavior with no delay or stuttering. At that point I noticed a beta for multiplicity and downloaded that and installed on all three computers and restarted all three systems. Unfortunately, the stuttering and delay returned.

My limited research into this seems to suggest that there is an issue caused by this Windows Creator cumulative update. Realizing this, I wanted to back out of this cumulative update but to my surprise, Microsoft has removed the option now of rolling back any update (note: they did allow rolling back the original Windows Creator update when it was first introduced).

Wondering if anyone else is noticing this issue and if there any workarounds?

11,605 views 3 replies
Reply #1 Top

On which computer is the delay showing and if it is the secondary does it have a mouse attached?

Reply #2 Top

I'm having the same problem.  One of the recent windows 10 updates messed up my multiplicity.  I looked at the settings in services.msc to see how multiplicity was booting up.  It said it was set to manual.  I then changed the setting to automatic.  First couple of reboots and the automatic setting took.  But when I came back a few days later,  the setting in services.msc reverted back to manual.

What gives?

I'm now thinking of just creating a batch file with the bootup for multiplicity and stick it in the startup folder for windows 10.  And see how that works.  But in the back of my mind, I'm thinking, I shouldn't have to do that.  Why should I be beta testing something that has been working for years?

You people at edgerunner need to resolve this problem.

 

Reply #3 Top

Quoting bangkokbuddy, reply 2

I'm having the same problem.  One of the recent windows 10 updates messed up my multiplicity.  I looked at the settings in services.msc to see how multiplicity was booting up.  It said it was set to manual.  I then changed the setting to automatic.  First couple of reboots and the automatic setting took.  But when I came back a few days later,  the setting in services.msc reverted back to manual.

What gives?

I'm now thinking of just creating a batch file with the bootup for multiplicity and stick it in the startup folder for windows 10.  And see how that works.  But in the back of my mind, I'm thinking, I shouldn't have to do that.  Why should I be beta testing something that has been working for years?

You people at edgerunner need to resolve this problem.

 
End of bangkokbuddy's quote

You appear to be reporting a different issue here?

The original thread poster is reporting stutter in their mouse due to a Windows update.  Your issue appears to be your service is being set to manual startup for some reason which is a very different issue.

You should contact official support using the link below, but an immediate thought is Multiplicity does not alter its service settings at all once installed, thus if they are changing the most probable explanation is something other than it is altering it.  Do you perhaps have something installed which 'optimises startup times'?

https://esupport.stardock.com/index.php?/default_import/Tickets/Submit