When the secondary device is turned off or disconnected, the mouse cannot return to the primary device.

Hello,
Sorry to hear you are having issues. 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.

Thank you,
Basj,
Stardock Community Assistant.

Successfully updated karma reason!

sdRohan

Join Date 10/2012

+726

Quoting ,

quoting post

Just as the title suggests. When my secondary device is shut down or disconnected from the network, if the mouse happens to be on the display of the secondary device at that time, I have no way to return the mouse to the primary device. The only option is to restart the computer.

I tried to set a shortcut key, but in fact, the shortcut key never took effect.

The operating system of my secondary device is windows10 19045, and that of my primary device is windows11 26100. The version of multiplicity4 I'm using is 4.01pro.

As a test, if you unplug \ disable the network connection on the Primary, does the cursor return?

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

When the mouse was on the display of the secondary device, I tried to disconnect the network connection of the primary device, but the cursor still couldn't return. I made a series of attempts. Even when I reconnected to the network, I still couldn't restore the control of the keyboard and mouse. After restoring the network connection, it is also necessary to log out or restart the computer in order for the device to be used normally.

So far, the conclusion drawn is that if the mouse is on a secondary device, no matter which device goes offline, it will cause the keyboard and mouse to be unable to be controlled. Even if "Connected Device" pops up in the lower right corner of the screen after reconnecting to the network, the control of the keyboard and mouse cannot be restored normally. Only by restarting/logging out the computer can it return to normal.

Successfully updated karma reason!

sdRohan

Join Date 10/2012

+726

Quoting yanlanfeixue,

reply 3

When the mouse was on the display of the secondary device, I tried to disconnect the network connection of the primary device, but the cursor still couldn't return. I made a series of attempts. Even when I reconnected to the network, I still couldn't restore the control of the keyboard and mouse. After restoring the network connection, it is also necessary to log out or restart the computer in order for the device to be used normally.

So far, the conclusion drawn is that if the mouse is on a secondary device, no matter which device goes offline, it will cause the keyboard and mouse to be unable to be controlled. Even if "Connected Device" pops up in the lower right corner of the screen after reconnecting to the network, the control of the keyboard and mouse cannot be restored normally. Only by restarting/logging out the computer can it return to normal.

I want to be clear, but I suspect you already know this, that this is not typical behavior. I could test this (and have hundreds of times) and not reproduce it. While you are experiencing this, I don't suspect it's every time either, its just when certain conditions are met and its unclear what those conditions are.

If your Primary PC had a touchscreen, I don't doubt that if you restarted the MP service from the systray, it would return the mouse control to it (were the network connection still disconnected)

Something is telling MP that the connection is still alive is the issue.

For the time being, ensure your mouse cursor is on the primary before you do anything to kill the secondary. At least try to restart the Secondary MP service on it (same as in the pic above).

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Quoting sdRohan,

reply 4

Quoting yanlanfeixue,

reply 3

When the mouse was on the display of the secondary device, I tried to disconnect the network connection of the primary device, but the cursor still couldn't return. I made a series of attempts. Even when I reconnected to the network, I still couldn't restore the control of the keyboard and mouse. After restoring the network connection, it is also necessary to log out or restart the computer in order for the device to be used normally.

So far, the conclusion drawn is that if the mouse is on a secondary device, no matter which device goes offline, it will cause the keyboard and mouse to be unable to be controlled. Even if "Connected Device" pops up in the lower right corner of the screen after reconnecting to the network, the control of the keyboard and mouse cannot be restored normally. Only by restarting/logging out the computer can it return to normal.

I want to be clear, but I suspect you already know this, that this is not typical behavior. I could test this (and have hundreds of times) and not reproduce it. While you are experiencing this, I don't suspect it's every time either, its just when certain conditions are met and its unclear what those conditions are.

If your Primary PC had a touchscreen, I don't doubt that if you restarted the MP service from the systray, it would return the mouse control to it (were the network connection still disconnected)

Something is telling MP that the connection is still alive is the issue.

For the time being, ensure your mouse cursor is on the primary before you do anything to kill the secondary. At least try to restart the Secondary MP service on it (same as in the pic above).

Sean Drohan
Stardock Product Lifecycle Manager

Yes. I also think it was a certain factor that led to MP's wrong judgment. But I want to know the reason why the hotkey cannot be used. Could these two things be caused by the same factor? If the hotkey works properly, perhaps I won't be bothered by the previous problem.

I set "alt +f12" to "Switch to Primary computer", but in fact, it never took effect, no matter when I pressed it.

Successfully updated karma reason!

sdRohan

Join Date 10/2012

+726

Quoting yanlanfeixue,

reply 5

Quoting sdRohan,

reply 4

Quoting yanlanfeixue,

reply 3

When the mouse was on the display of the secondary device, I tried to disconnect the network connection of the primary device, but the cursor still couldn't return. I made a series of attempts. Even when I reconnected to the network, I still couldn't restore the control of the keyboard and mouse. After restoring the network connection, it is also necessary to log out or restart the computer in order for the device to be used normally.

So far, the conclusion drawn is that if the mouse is on a secondary device, no matter which device goes offline, it will cause the keyboard and mouse to be unable to be controlled. Even if "Connected Device" pops up in the lower right corner of the screen after reconnecting to the network, the control of the keyboard and mouse cannot be restored normally. Only by restarting/logging out the computer can it return to normal.

I want to be clear, but I suspect you already know this, that this is not typical behavior. I could test this (and have hundreds of times) and not reproduce it. While you are experiencing this, I don't suspect it's every time either, its just when certain conditions are met and its unclear what those conditions are.

If your Primary PC had a touchscreen, I don't doubt that if you restarted the MP service from the systray, it would return the mouse control to it (were the network connection still disconnected)

Something is telling MP that the connection is still alive is the issue.

For the time being, ensure your mouse cursor is on the primary before you do anything to kill the secondary. At least try to restart the Secondary MP service on it (same as in the pic above).

Sean Drohan
Stardock Product Lifecycle Manager

Yes. I also think it was a certain factor that led to MP's wrong judgment. But I want to know the reason why the hotkey cannot be used. Could these two things be caused by the same factor? If the hotkey works properly, perhaps I won't be bothered by the previous problem.

I set "alt +f12" to "Switch to Primary computer", but in fact, it never took effect, no matter when I pressed it.

Alt + F12 is likely reserved, try Ctrl+Alt+F12

Successfully updated karma reason!