NoMachine is the fastest remote Mac desktop you have ever tried

NoMachine for Mac

NoMachine 9.5.7

  -  103.06 MB  -  Freeware
  • Latest Version

    NoMachine 9.6.3

  • Operating System

    Mac OS X 10.7 or later

  • User Rating

    Click to vote
  • Author / Product

    NoMachine Team / External Link

  • Filename

    nomachine_9.5.7_1.dmg

  • MD5 Checksum

    4a51382e686357c92d2cbe3336d9d5fe

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system.

Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of NoMachine 9.5.7.


For those interested in downloading the most recent release of NoMachine for Mac or reading our review, simply click here.


All old versions distributed on our website are completely virus-free and available for download at no cost.


We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

Why is this app published on FileHorse? (More info)
  • NoMachine 9.5.7 Screenshots

    The images below have been resized. Click on them to view the screenshots in full size.

    NoMachine 9.5.7 Screenshot 1
  • NoMachine 9.5.7 Screenshot 2
  • NoMachine 9.5.7 Screenshot 3
  • NoMachine 9.5.7 Screenshot 4
  • NoMachine 9.5.7 Screenshot 5

What's new in this version:

Fixed:
- Automatic session recording can freeze after the user logs-in to the system
- Network port forwarding from and to macOS may not work
- Users sometimes not able to authenticate to the node by web
- In some rare cases the Windows user is unable to login to NoMachine Network
- A black screen may occur on older macOS after a reboot
- The client could suddenly close when uploading file through drag&drop from MacOS Tahoe
- Kerberos Credentials Cache forwarding may not work on the nodes
- CA-signed host certificate chain verification may fail
- CA could be not available for connections by NX protocol in multinode environments
- The 'nxserver --daemon' process suddenly terminates when connections to the physical desktop are enabled on the node
- Potential local privileges escalation through argument injection in the nxchmod.sh script
- It may be not possible to forward devices to a Windows client