Since the release of NoMachine 4 there have been some alarmed reports posted in our forums about possible breakage caused by the NoMachine 4 installation. In all cases, these reports ended up being caused by erroneous or missing uninstallation of NX-compatible software released by third parties and, in some cases, even bugs caused by libraries shipped by the operating system's vendor.

In particular, NoMachine doesn't modify the user's environment or the processes run by the shell init scripts at user login. Additionally no NoMachine program is added to the environment (although many users requested that at least the command line administration program, /usr/NX/bin/nxserver would be) and no NoMachine library is installed in the system in paths where they may be involuntarily used by the user or an application. Bug or unintended side effects excluded, of course, but due to the insulation of the NoMachine environment from the host, such risks are greatly mitigated by design. At the moment, there is no Trouble Report or known issue about a NoMachine installation affecting in any way the ability of the X server or the native desktop environment to start and run.

It is important to also point out that, since the release of NoMachine 4, some third party projects have continued with open-source development of old versions, among these are FreeNX, NeatX, X2Go and Xpra. NoMachine is not reponsible for these projects. While these projects use software released by NoMachine as open-source, NoMachine does not endorse them in any way nor has any control on the quality or the functionality of the software they distribute. Please be sure you refer to the support facilities of the respective project when using NoMachine or NX software distributed by third parties.