Windows 10 1903 KB4515384 update Causing Multiplicity 3 to keep disconnecting

All, not sure if anyone else ran into this problem but yesterday I installed the Windows 10 1903 KB4515384 update which is supposed to fix an issue of the taskbar cortana search bar and search indexer causing the CPU to frequently spike. It fixed it alright but then it caused a bunch of other problems including but not limited to a broken start menu. Adding to that my experience was that after I installed the update on both my computers at work, the secondary would frequently disconnect even after multiple reboots to the primary and secondary, until finally the secondary would quit connecting altogether. The solution, uninstall the update on both machines and then block it from re-installing.

Hope this helps someone

Advanced Search

Subscribe to this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

AzDude

Join Date 11/2002

+261

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

AzDude
Stardock Community Assistant

Successfully updated karma reason!

I've been seeing something similar recently, though I haven't specifically tied it to KB4515384 yet. (I was affected by the start menu search failure on my primary.) I'll try rolling it back on my secondary to see if it helps.

My disconnects feel like they might be tied to the screensaver kicking in, though it typically recovers eventually.

Successfully updated karma reason!

Yeah I'd noticed that also. However with that update, the secondary would completely refuse to reconnect.

Successfully updated karma reason!

Quoting techforged,

reply 3

Yeah I'd noticed that also. However with that update, the secondary would completely refuse to reconnect.

With what as the error? Were you connecting to the Secondary via IP or hostname? If by IP, did the Secondary still have the IP the Primary thought it should have?

Sean Drohan
Stardock Support Manager

Successfully updated karma reason!

Update: I had previously backed out KB4515384 on my primary because of the Start Menu search bug, but it was still installed on my secondary. Since backing it out on the secondary yesterday, I have had no disconnects.

The only issue I still have occurs when the secondary has been inactive long enough for the monitor to shut off. In this case, when I drag my mouse to the secondary, there are several seconds of latency where the mouse is non-responsive. Even if I drag it back toward the primary, nothing happens. Using a hotkey to jump back to the primary does make the mouse responsive immediately. If I take no action, everything is fine after a few seconds. I've experienced this well before KB4515384 was published and am just treating it as a minor annoyance.

Successfully updated karma reason!

I wasn't getting an error. The popup on the primary would just say the secondary disconnected and that's it. However when I go to multiplicity on the secondary it still thinks its connected to the host via ip address. Now since I've removed that update, I havent had any issues with disconnecting except for whenever i drop off wifi but that's solvable.

Successfully updated karma reason!

Welcome Guest! Please take the time to register with us.

There are many great features available to you once you register, including:

Richer content, access to many features that are disabled for guests like commenting and posting on the forums.
Access to a great community, with a massive database of many, many areas of interest.
Access to contests & subscription offers like exclusive emails.
It's simple, and FREE!

View all recent posts

Mark all posts as read Delete cookies created by the forum Return to Top

Stardock Forums v1.0.0.0 #108492 web02 Server Load Time: 00:00:00.0000188 Page Render Time: