Secondary machines only work AFTER you log in

from Stardock Forums

I have updated to the latest Multiplicity as well as the latest Windows 11 update. I'm seeing some odd behavior that I never saw under v3.

When my laptops which have Multiplicity installed as a secondary I can only use those laptops in seamless mode AFTER I log into them. Before I could move the mouse and log in without issue, but now I have to log in with an attached keyboard and mouse and THEN everything works as expected.

Has anyone else seen this? Any ideas why I'm seeing this behavior?

For reference:

  • I'm running the latest Windows and Multiplicy versions
  • Everything works fine, including copypasta one the machines have been logged in
  • All machines are hard wired Ethernet, on the same subnet

Any suggestions are welcome

multiplicity
5,101 views 14 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. Please include more details on your system.

  1. Windows 10 or 11? Also need its full version and OS Build, please use Winver.exe.
  2. Multiplicity full version number.

Thank you.
Basj,
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

Primary Computer

Windows OS: Windows 11 Pro, Version 24H2, Build 26100.2894

Multiplicity: Version 4 Pro (No updates available)

 

Laptop #1

Windows OS: Windows 11 Pro, Version 24H2, Build 26100.2894

Multiplicity: Version 4 Pro (No updates available)

 

Laptop #2

Windows OS: Windows 11 Enterprise, 24H2, OS build 26100.2894

Multiplicity: Version 4 Pro (No updates available)

The two laptops sit on a desk with the lid closed but configured so the laptop does not go to seep. To get multiplicity started I have to raise the lid, log in, and then Multiplicity kicks into seamless mode and Multiplicity works fine.

 

 

Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #3 from Stardock Forums Top

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #4 from Stardock Forums Top

Do you actually need to login or will it connect if you simply open the display?

Also I assume those laptops both have external displays?

Reply #5 from Stardock Forums Top

Both laptops do have external displays and I do need to raise the lid. I need access to the keyboard and the internal display as thhe external one doesn't turn on until after I raise the lid. Raising the lid is not enough for Multiplicty to kick in and allow me to use the Primary's keyboard and mouse

Reply #6 from Stardock Forums Top

Quoting COGger, reply 5

Both laptops do have external displays and I do need to raise the lid. I need access to the keyboard and the internal display as thhe external one doesn't turn on until after I raise the lid. Raising the lid is not enough for Multiplicty to kick in and allow me to use the Primary's keyboard and mouse
End of COGger's quote

I suspect if you left it long enough it probably would connect once the lid is open.

My gut feeling here is this is a Modern Standby/Always On/Instant On/Whatever it is called this week power saving thing.  MP3 would let things reconnect in that mode which would cause issues if the device really was in that mode, but MP4 changed it to ignore incoming connections when in that mode as it wouldn't work.

But it isn't taking into account more than one screen and upon the power down of the primary screen it thinks it is entering the power saving mode and I think it clearly actually didn't do this due to the extra screen but MP stops incoming connections.

If you run powercfg -a from a command prompt does this indicate S0 support on the laptops?

Reply #7 from Stardock Forums Top

It does. What should I change?

 

Laptop #1:

powercfg -a
The following sleep states are available on this system:
    Standby (S0 Low Power Idle) Network Connected
    Hibernate
    Fast Startup

The following sleep states are not available on this system:
    Standby (S1)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.

    Standby (S2)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.

    Standby (S3)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.

    Hybrid Sleep
        Standby (S3) is not available.
        The hypervisor does not support this standby state.

Laptop #2:

powercfg -a
The following sleep states are available on this system:
    Standby (S0 Low Power Idle) Network Connected
    Hibernate

The following sleep states are not available on this system:
    Standby (S1)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.

    Standby (S2)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.

    Standby (S3)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.

    Hybrid Sleep
        Standby (S3) is not available.
        The hypervisor does not support this standby state.

    Fast Startup
        This action is disabled in the current system policy.

Reply #8 from Stardock Forums Top


When my laptops which have Multiplicity installed as a secondary I can only use those laptops in seamless mode AFTER I log into them. Before I could move the mouse and log in without issue, but now I have to log in with an attached keyboard and mouse and THEN everything works as expected.
End of quote

If you open the config on the Primary and 'test' the connection:

Does it report that it works?

Is this perhaps a timing thing, that when you reboot the Secondary (I assume that is the process you are referring to), if you wait a bit longer, does it then work?

If you lock the Secondary, are you still able to access it then after?

Sean Drohan
Stardock Product Lifecycle Manager

Reply #9 from Stardock Forums Top

When I test either laptop when Multiplicity is not reacting to moving the mouse to either laptop the test fails. Obviously the test works once I log in. :)

If Multiplicity is working and I lock the screen(s) Multiplicity continues to work.

Oddly with laptop #1 (Which is set to never shut down the computer; only the display) Multiplicity seems to "unload" itself after some time after 45 minutes (Screen turns off @ 30 min) and I have to log back in. Then it all works fine.

Odd stuff going on. If this was my job with a vendor issue like this  I'd definitely be calling vendor support with the proverbial "WTF?" :D

I never contact vendors with the simple stuff :D

Reply #10 from Stardock Forums Top

For reference Dell just released a BIOS update and some driver updates for laptop #1. After the application of said updates and a reboot. Multiplicity did load without opening the screen. I'll do some more testing tonight/tomorrow to check how everything behaves.

Reply #11 from Stardock Forums Top

Sorry for the delay.

Laptop #1 (Which never turns off) multiplicity will work after a hard reboot upon the initial log in screen, but goes back to the behavior of not working if you let the machine idle for more than 30 minutes

Laptop #2 (Which is on from 0800-1700) never has Multiplicity work without a log in even after a hard reboot and waiting up to 5 minutes before logging in. And this behavior continues the moment you lock the screen as well

 

Reply #12 from Stardock Forums Top

Quoting COGger, reply 11

Sorry for the delay.

Laptop #1 (Which never turns off) multiplicity will work after a hard reboot upon the initial log in screen, but goes back to the behavior of not working if you let the machine idle for more than 30 minutes

Laptop #2 (Which is on from 0800-1700) never has Multiplicity work without a log in even after a hard reboot and waiting up to 5 minutes before logging in. And this behavior continues the moment you lock the screen as well
End of COGger's quote

It just reads like some power setting you have is powering down the network core of one of the laptops.  As a test, I would review your Power settings on the PCs and set them to never power anything down while idle and see what happens.

https://www.windowscentral.com/how-change-power-modes-performance-or-battery-windows-11

Sean Drohan
Stardock Product Lifecycle Manager

Reply #13 from Stardock Forums Top

Quoting sdrohan, reply 12


Quoting COGger,
reply 11

Sorry for the delay.

Laptop #1 (Which never turns off) multiplicity will work after a hard reboot upon the initial log in screen, but goes back to the behavior of not working if you let the machine idle for more than 30 minutes

Laptop #2 (Which is on from 0800-1700) never has Multiplicity work without a log in even after a hard reboot and waiting up to 5 minutes before logging in. And this behavior continues the moment you lock the screen as well



It just reads like some power setting you have is powering down the network core of one of the laptops.  As a test, I would review your Power settings on the PCs and set them to never power anything down while idle and see what happens.

https://www.windowscentral.com/how-change-power-modes-performance-or-battery-windows-11

Sean Drohan
Stardock Product Lifecycle Manager

End of sdrohan's quote

If it is being caused by Modern standby then the next Multiplicity build may help this.

Reply #14 from Stardock Forums Top

I'll turn off all the power down portions to see what happens and look forward to the next Multiplicity update