Please check the trouble-shooting section in the documentation.

Please check the trouble-shooting section in the documentation.

ShareMouse should run as smooth as you can see in our demonstration video - We use regular off-the-shelf hardware.

Please check our performance optimizing tips in the manual.

Please check the product documentation with solutions to restore the mouse pointer on Windows 10.

Please check, if the file exist in file directory "C:\Program Files (x86)\ShareMouse\smkey.dll".

If it doesn't exist, please check if an “Antivirus” or “AntiSpyware” software may may falsely interpret it as a malicious keylogger and block accessing this. Such programs have a "quarantine feature" which puts such files on hold. Please refer to the documentation of such security program and take proper action to release the file essentially required by ShareMouse.

Background information: ShareMouse requires a software hook to read the mouse and keyboard input. Unfortunately, malicious software uses a similar piece of software program. However, ShareMouse does not collect or transmit your input anywhere else while malicious key loggers are sending your information over the internet. ShareMouse is safe to use and you can safely allow "sharemouse.dll" in your security software. If in doubt, you can safely lock up ShareMouse from accessing the internet. Other than the short time of liense registration and optional software update checks, ShareMouse does not need an internet connection.

If this doesn't help, it seems, that your ShareMouse installation is corrupted. Please try a complete uninstallation, reboot and reinstallation.

The macOS system function "Secure Input" protects sensitive text input (such as password input) from being spied out by malicious programs.

This feature is activated by the program, that receives the text input and it has to be disabled by the same program after data entry. For example, the Safari browser is enabling "Secure Input" in password input fields.

Unfortunately, some applications do not to seem to release "Secure Input" rendering any subsequent text input invisible for 3rd party apps, including ShareMouse.

This not an error in ShareMouse and ShareMouse has no way to remotely disable "Secure Input". If this would be possible, also malware would make use of such remote disabling, making the security feature "Secure Input" obsolete.

Work around: Disable "auto-submit" feature of any auto-login feature and/or close and restart the application, that caused the interference.

You can specifiy a dedicated network adapter ShareMouse uses to send data in the section "network" of the ShareMouse settings.

Additionally/Alternatively, you can restrict/define a list of IP addresses (specific for each network connection) ShareMouse shall listen to in section "Clients" of the ShareMouse settings.

To prevent ShareMouse from picking up new IP addresses, disable sending the own IP address over UDP option.

To isolate your setup from other ShareMouse setups on a shared network, apply a password protection to either setup.

You many want ot prefer wired ethernet connections as Wifi network connection may tend to lose connection from time to time.

macOS 10.15 "Catalina" requires manual user confirmation to allow ShareMouse saving data onto the hard disk. Please double-check the installation instructions and make sure that all authorizations are configured for ShareMouse in macOS security settings.

You can drag & drop files and text between computers but not programs.

Note, that an application may be of several hundreds of Megabytes size and also need to be licensed on a particular computer.

  • Update to the latest ShareMouse version which includes compatibility improvements.
  • Try if ShareMouse screen dimming feature helps to resolve the issue.
  • Experiment with the ShareMouse options "IOHID Input Simulation" and "Simulate CTRL, SHIFT, CMD and OPTION keys as flag events".
  • Remote Desktop applications tunnel mouse/keyboard input of the physical host computer into the remote session. If available, experiment with mouse/keyboard related settings in your Remote Desktop application.

ShareMouse allows you to seamlessly move the mouse pointer between displays to control the other computer but you cannot use its screen real estate. This would be a totally different kind of program.

If the Mac wakes up unwantedly because ShareMouse is running, disable option "Wakeup on LAN" in the macOS energy saving setttings.

If hibernation synchronization does not work, configure macOS not to automatically lock a session in hibernation mode. On Microsoft Windows, you can set this in the "Login Options". On the Mac this can be set in "Security » General".

MacOS (or other appcliations) may enable the mouse pointer after ShareMouse disabled it. For example, macOS unhides the mouse pointer automatically if you leave the monitor through the Apple Dock.

Unfortunately, there is nothing ShareMouse can do to work around this 3rd party software behavior.


If you control a Windows PC from a Mac (or vice versa), keep in mind that those run on different operating systems with different keyboard layout. While most letters are at the same position, special characters such as the at-symbol (@) are entered completely different on either OS.

Windows: ALTGR+Q (alternatively CTRL+ALT+Q)


To make things even more complicated, the CTRL and CMD keys are exchanged in MacOS vs Windows. This means, if you want to remote enter the at-symbol on a Windows PC from your Mac, you would need to type CMD+ALT-Q on your Mac. As the ALT key is the same on both OS, you would need to press ALT+L on Windows to remotely enter the at-symbol on the Mac.

You can remap the keys CTRL, CMD and ALT in the ShareMouse for Mac program settings.

We have found out, that a macOS system task seem to hang if ShareMouse launches a system program required to check for issues created by the macOS feature "Secure Input".

Work around: If you experience high CPU load, disable option "Secure Input warning" under "Settings » Keys".

For ShareMouse it is completely irrelevant if the input device is connected through a cable or a bluetooth connection. It does not touch anything bluetooth related but uses the mouse as reported by the operating system. On the software side the input device software driver is responsible for anything hardware connection related (and of course the hardware itself).

You would need to check the input hardware and its software driver for connection issues.