Multiplicity keeps computer from going to sleeep

I just changed my new laptop to be the Primary and I have the same issue. This is not going to be acceptable if I can't put my laptop to sleep (Imagine if I have to leave somewhere and put it in my bag really quick).

Is there a setting or something I can do to help prevent this behavior?

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

That would not be a problem as you would be away from the Primary.

Please ensure you do not have these enabled:

Sean Drohan
Stardock Support Manager

I would also recommend updating to the 3.55 release as it had changes for connected standby setups.

Ok, so:

1) When I make the full switch, this new laptop will be my primary. So hopefully there is a solution in that scenario. (it will sit in a dock a lot and be mainly used for KVM instead of just KM duties across multiple monitors)

2) I did have the "prevent.." one checked on my current primary and unchecked that. I did update my current primary to 3.55 and still no go (secondary was still on 3.55). The only solace is if I hit the power button again on the lock screen, it goes to sleep, but I would rather not have to do this.

Thanks,
Frank

Hello,

I've got a similar issue with two Dell computers. My main work PC is the primary, and all check boxes advised in earlier posts are cleared. On the "slave" unit which has no keyboard and mouse, Multiplicity is setup as a secondary.

On the slave/secondary Dell (new XPS 2021 edition), I'm no longer able to put the computer to sleep when Multiplicity is installed. When I click start > power > sleep, the laptop briefly sleeps and then wakes back up again. This is regardless of whether I use the shared mouse (preferred) or the laptop's own trackpad/keyboard. 

I'm running Multiplicity V3.57, Build 00103 on both units. I have Windows 10 21H2 19044.1387 running on the slave PC.

On event viewer on the slave PC, I see a Kernel-Power event ID 507 stating that the system is exiting Connected Standby with reason: "Input Keyboard" or "Input Mouse" depending on what I used to trigger the sleep function.

With Multiplicity "unloaded" using the tooltray menu, the system sleeps without problem.

I've recently bought the full licence for this, so hoping a fix can be found.

Thanks team.

Please check that this is not enabled:

Sean Drohan
Stardock Support Manager

I can confirm that it is not checked.

If you move the PC in question off the grid, does it then work?

Sean Drohan
Stardock Support Manager

Hi Sean. I made the change as requested (I have the licence for the KM version), but problem is still there.

If I unload Multiplicity on slave unit, I can sleep fine. Attempting to sleep using the trackpad to trigger it caused an event-viewer ID of 507 stating that it was exiting connected standby with an input reason of keyboard.

Thanks.

On the settings page do you have "prevent secondary computers auto sleeping whilst using this computer" enabled?

Correct. Not selected.

What version number does it say on the about page?

Neil - I've answered all of these in my my original post. Thanks.

All quiet on the support front. Can I provide any log files, or further details? Any ideas on what could be going wrong? Do you have a test version you want me to try? Let me know as having to quit Multiplicity every time I want my laptop to sleep is getting a bit tiresome! Thanks.

There is no update or test version at this time I am afraid.

Sean Drohan
Stardock Support Manager