NoMachine 8.9.1

What's new in this version:

- Uninstalling NoMachine on Windows fails when using the SYSTEM account
- The remote desktop is not locked with the native lock screen when the 'root' user is physically logged-in
- Black screen occurs after logout from XFCE desktop running in a custom session
- The nx user appears in the list of users allowed to unlock the disk FileVault is enabled
- Cannot open a Flatpak application on Linux when a NoMachine server installed
- Cannot set ultra-wide custom resolutions in web sessions
- The nxserver process hangs while reading data from backend db with a large amount of data
- Virtual desktops started from command line are counted in the connections limit counter
- ETS reports a misleading error when the desktop environment cannot start on the node because of d-bus limits reached
- Audio forwarding on SuSE SLES stops working after some hours
- The nxnode.bin process uses 100% of all cores when the remote screen on Wayland is in power save mode
- Automatic recordings of local desktop are not saved
- Automatic recording doesn't work for AD domain users
- A write error on the UDP socket can cause the termination of the nxd service
- Sudden termination of a custom session when kde-plasma-desktop is installed
- Local and remote printers are no longer listed in the client UI after CUPS has been reinstalled on server side
- Node groups are no longer synchronized after the upgrade of Enterprise Terminal Server Cluster
- The user cannot logout from a virtual desktop via web when 'Save this password' is selected
- On Windows, pressing right-ctrl locks the control key on
- Rules associated to a node are left when the node is deleted
- Cannot change port 4000 for nxd via UI after the upgrade to v8
- The 'nxserver --startmode' command reports wrong information when Upstart is in use
- Nodes become unreachable when the ClientMenuConfiguration key is set