Nothing special. Just plug in some spare mice, pens, tablets or touchscreens and/or keyboards. MouseMux will detect the newly plugged in devices and automatically add them. Generally what people do is buy a USB hub and use that to plug in more mice and keyboards. Theoretically you can add unlimited devices, we tested up to 32 simultaneous users (64 input devices).

MouseMux supports Windows 7, 8, 10 and 11, including all Server editions. The program comes in both 32-bit and 64-bit versions and will automatically select the appropriate architecture.

Occasionally a virus scanner will flag MouseMux as unsafe. Under the hood MouseMux has lots of complex behavior and emulates part of the input layer of Windows, some virus scanners will find that behavior suspect and will raise the alarm. We're in continuous contact with manufacturers of security tools to keep MouseMux white-listed. Please drop us a line if your virus scanner flags MouseMux as suspect.

Yes. MouseMux has a 'capture device' which will capture mouse input injected by most remote desktop programs, so the remote user will become a separate MouseMux user/cursor. You can try out this functionality in trial mode to see how it works. The mouse cursors are rendered in such a way that remote desktop programs will show the cursors on the remote screen too. See the manual for further explanation.

Yes. MouseMux has a 'capture device' which will capture mouse input injected by most auto-clicker/macro/robo-clicker programs, so the clicker will control a separate MouseMux user/cursor. You can try out this functionality in trial mode to see how it works. See the manual for further explanation.

Some high precision touchpads inject their input into the Windows subsystem. To catch that input you have to enable the 'capture device'. Once enabled you will be able to use your touchpad as normal. See the manual for further explanation.

The Logitech unifying receiver acts as a generic USB HID device and as such MouseMux will work fine and detect both mouse and keyboard input. It will however not be able to separate between devices during saving and loading because the receiver (re)creates device IDs, so settings for each mouse may get lost.

When MouseMux starts it will try to minimize required CPU resources to play nice with your system but this may also result in laggy cursors. To fix this you can enable 'High priority threading' in the settings dialog, and try moving the 'Main loop speed' all the way to the left. For multiplex mode there is also a 'high priority multiplexing' option. You may also want to try disabling 'Hardware motion' in the output tab, and enable buffered input and coalescing for high DPI devices.

Try enabling 'Force hardware dragging' in the output tab of the user. This will force MouseMux to use hardware dragging and will fix a number of issues with dragging, painting, etc. You can additionally enable 'Force hardware motion' to force any motion through the hardware layer.

Yes! MouseMux will route each device to a 'user', so your pen is a 'user', your touch screen and your mouse are other 'users'. Touching your screen will just move the 'touch screen user' while your mouse will move a different user/cursor. Screen real estate is much easier to manage! You can even blank a cursor to completely remove any visual effects that may be annoying during touch.

Yes! MouseMux can convert any source device type to any target device type. It reads an input device and builds a generic input event. Inside MouseMux these events can be manipulated (adding pressure or rotation data, inverting an axis, translating coordinates) and then outputted as any device type. You can mimic pen behavior with a mouse, use your pen as a touch device, or even use two mice to simulate multi-touch interactions.

Keyboard pairing links a keyboard to a mouse; together they represent a virtual user. Pairing is simple: move a mouse and hit a key on the keyboard you want to pair. If you have two mice but one keyboard, you can synchronize the keyboard to all users so it works like normal Windows, following the window with focus. If you have two keyboards and two mice, keep Multi Keyboard checked and pair each keyboard to an individual mouse for fully independent operation.

Yes, we have SDKs for both Windows and Web. The SDK allows MouseMux to run in the background and perform various actions via API calls, creating virtual mouse pointers and users programmatically. Check the SDK documentation for more information.

MouseMux generates telemetry to help us understand how it behaves on various systems. All data is anonymized; no personal data is sent to our servers. No interaction data is sent: no keystrokes, no window titles, etc. We mainly gather which features are used, performance timings, and diagnostic warnings. See our full telemetry documentation for the complete list of what is collected.

Your license includes one year of free updates. MouseMux is actively developed and the program is regularly updated. After the first year, you can optionally renew for continued updates at a discounted rate.