What's new in Hamachi 2.2.0.630
Feb 11, 2019
New in Hamachi 2.2.0.627 (Dec 17, 2018)
- This release contains various improvements to the Hamachi client.
New in Hamachi 2.2.0.615 (Nov 26, 2018)
- Fixed an issue that caused the Hamachi application to exit when trying to run the diagnostics tool
New in Hamachi 2.2.0.614 (Nov 13, 2018)
New in Hamachi 2.2.0.579 (Jul 10, 2017)
- Fixed an issue that caused LogMeIn Hamachi to consume excess resources.
New in Hamachi 2.2.0.578 (May 23, 2017)
- Fixed an issue that caused LogMeIn Hamachi to consume excess resources
New in Hamachi 2.2.0.558 (Mar 2, 2017)
- General stability and security enhancements
New in Hamachi 2.2.0.550 (Feb 2, 2017)
- Improved stability for the reconnect procedure.
- Automatic update checking has been improved in the Hamachi client.
- Adapters are now disabled when the client is turned off. Bridged adapters (GW client) are kept enabled for connectivity purposes.
New in Hamachi 2.2.0.541 (Nov 15, 2016)
- Resolved an issue that prevented Hamachi from enabling when waking from sleep mode on Windows 10.
- Resolved an issue that prevented Hamachi from connecting when starting Windows on PCs with Fastboot enabled.
New in Hamachi 2.2.0.493 (Sep 13, 2016)
- Resolved an issue that prevented the Diagnostic Tool from finding drivers on 64bit Windows.
New in Hamachi 2.2.0.472 (Jun 8, 2016)
- Improved UI scaling on high DPI screens
New in Hamachi 2.2.0.428 (Jun 8, 2016)
New in Hamachi 2.2.0.422 (Jun 8, 2016)
- This release fixes the bug that caused the Hamachi gateway to forget settings due to the gateway network adapter being removed/re-added with each service restart.
New in Hamachi 2.2.0.420 (Apr 6, 2016)
- When Hamachi is uninstalled, all Hamachi-related files are removed if the "Remove all user settings" option is selected.
- Fixed the Maximum Transmission Unit (MTU) value for TAP dev devices and bridges.
- Resolved an issue with gateway networks that prevented the bridge from being created on first connection after the client's role was changed from member to gateway while offline.
New in Hamachi 2.2.0.410 (Mar 23, 2016)
- This release resolves an issue with the Diagnostics Tool incorrectly reporting inconsistent timestamp errors.
New in Hamachi 2.2.0.406 (Nov 17, 2015)
New in Hamachi 2.2.0.385 (Aug 6, 2015)
- This maintenance release resolves issues with peer-to-peer communication on certain configurations
New in Hamachi 2.2.0.383 (Aug 3, 2015)
- This release fixes adapter issues after upgrading to Windows 10
- Note:
- This fix requires that the malfunctioning NetWork bridge be removed
New in Hamachi 2.2.0.375 (Jul 14, 2015)
- Support for Windows 10:
- The Hamachi client can now be used on computers running Windows 10.
- Hamachi Self-Diagnosis:
- This releases introduces Hamachi Self-Diagnosis as part of the Hamachi client. This feature is designed to help you resolve problems that may arise while using Hamachi.
New in Hamachi 2.2.0.319 (Feb 18, 2015)
- Minor stability improvements
New in Hamachi 2.2.0.291 (Jan 21, 2015)
- User experience enhancements
New in Hamachi 2.2.0.279 (Dec 2, 2014)
- Enhancements:
- When launching an unattached Hamachi Client without signing in with a LogMeIn ID, users can start a limited version of Hamachi in order to attach the client to an account.
- Other:
- Improved stability for new installations (fixed a crash caused by the login/registration window)
- Various bug fixes
New in Hamachi 2.2.0.266 (Dec 2, 2014)
- Fixed an issue where a client was created without an empty nickname
- Other stability improvements
New in Hamachi 2.2.0.279 (Dec 2, 2014)
- Enhancements (Windows & Mac):
- When launching an unattached Hamachi Client without signing in with a LogMeIn ID, users can start a limited version of Hamachi in order to attach the client to an account.
- Improvements (Windows 8, 8.1 and 2012):
- Fixed an issue that reset the bridge IP address to static instead of DHCP after a system reboot
- Resolved an issue that caused the Windows default gateway IP address to be empty on a Hamachi Gateway Client
- Hamachi bridge settings are now removed on uninstall
- Other:
- Improved stability for new installations (fixed a crash caused by the login/registration window)
- Various bug fixes
New in Hamachi 2.2.0.266 (Dec 2, 2014)
- Fixed an issue where a client was created without an empty nickname
- Other stability improvements
New in Hamachi 2.2.0.258 (Nov 4, 2014)
- Various stability improvements
New in Hamachi 2.2.0.255 (Oct 27, 2014)
- Various stability improvements
New in Hamachi 2.2.0.232 (Sep 3, 2014)
- Improved LogMeIn Guardian error reporting
- Fixed an issue with the Windows 8 driver that caused the client to crash
- Resolved an issue in gateway networks where pending Hamachi mobile clients attempting to go online caused the client to crash
New in Hamachi 2.2.0.222 (Jul 16, 2014)
- Resolved an issue where some computers did not connect after coming back from sleep state.
New in Hamachi 2.2.0.214 (Jun 24, 2014)
- This release fixes a bug that caused system instability on high-load servers with multiple CPUs.
New in Hamachi 2.2.0.193 (Jun 24, 2014)
- Improvement: Enhanced error reporting
New in Hamachi 2.2.0.188 (May 14, 2014)
- This release resolves an issue that caused the client to crash during uPNP discovery
New in Hamachi 2.2.0.173 (Apr 16, 2014)
- When installing Hamachi, some users will be given the option to install Google Chrome together with Hamachi.
New in Hamachi 2.2.0.130 (Feb 5, 2014)
- This release fixes a bug that caused system instability on Window 8 and Windows 2012.
New in Hamachi 2.2.0.114 (Feb 5, 2014)
- This release fixes a bug that caused system instability and sleep-related service problems on Window 8 and Windows 2012
New in Hamachi 2.2.0.109 (Feb 5, 2014)
- This release fixes a bug that caused a network driver crash on Windows 8.1/2012 R2
New in Hamachi 2.2.0.105 (Dec 3, 2013)
- This release fixed an issue that caused the service to start slowly on some computers
New in Hamachi 2.2.0.100 (Nov 4, 2013)
- When installing to Windows XP, the engine configuration directory path is set correctly
- LMIGuardian now installs properly to 64-bit devices
New in Hamachi 2.2.0.58 (Nov 4, 2013)
- Improvements:
- LogMeIn Guardian is now integrated with Hamachi. If Hamachi crashes, you can use LMI Guardian to send error reports to LogMeIn.
- Configuration has been moved to another directory to enable OS upgrades (e.g. from Windows 7 to Windows 8)
- Users on Windows 8 and above can now enable gateway mode.
- Fixes were introduced to resolve the following issues:
- Tunnel reset being sent to mobile client peers
- Unexpected client reset
- Unexpected service closing
- For some OS X clients, gateway networks were not releasing routes upon logout or network disable
- Could not browse peer if VPN Alias address was set
New in Hamachi 2.1.0.374 (Oct 2, 2013)
- DNS suffix is now sent to mobile peers in Gateway networks
- Several bugfixes
New in Hamachi 2.1.0.362 (Oct 2, 2013)
- Hamachi ui.exe will no longer use excessive CPU resources when the Hamachi service is set to start manually
- The notification dialog no longer hides other dialogs
- The link in the notification regarding network capacity now properly communicates the ID of the network that needs to be upgraded
New in Hamachi 2.1.0.294 (Oct 2, 2013)
- Hamachi log file improvement:
- The Hamachi crash log file now contains the version information of the Mac client.
- Client improvements:
- On the Hamachi client, .local has been added to the ping [client ID] and copy [client ID] context menu options of Hamachi peers. For example, ping 123-456-789 has been changed to ping 123-456-789.local in the context menu. This change has no effect on functionality.
- Hamachi interface on Windows:
- In IPv6-only mode, the Network Location Awareness service on Windows clients did not qualify the Hamachi interface as a public interface. As a result, it is now possible to set up Hamachi as a Work or Home network which is less restrictive than public networks. This, in turn, causes less issues with firewall settings.
- Fixes:
- Command line clients trim address:
- The command line version of the Hamachi client trimmed the IP address of peers. This error effected Mac and Linux clients.
- Notification window on Windows clients:
- It was not possible to move the notification window on Windows clients.
- Menu bar icon missing in offline mode:
- The envelope icon on the menu bar was not visible on Mac clients when there was a message for the client but the client was offline.
- Gateway did not check OS type on Windows:
- The Hamachi client did not send information about the type of operating system that the client was running. The client only communicated whether it was running a 32 or 64-bit OS. As a result, this information was not displayed on the Networks > My Networks page of the LogMeIn website.
- Cannot connect to engine” error:
- In some cases, due to a communication error between the Hamachi GUI and the Hamachi engine, the client failed to start and displayed a Cannot connect to engine message. This issue effected Windows and Mac clients.
- Masked password field:
- When you create a network on the Hamachi client, it was possible to see the entered characters in the password field. As of this release, the content of the password field is masked. This issue effected Windows and Mac clients.
New in Hamachi 2.1.0.284 (Oct 2, 2013)
- The IP address of the default gateway was not updated from 5.x.x.x to 25.x.x.x. As a result, certain firewalls prevented applications from establishing connection over Hamachi.
New in Hamachi 2.1.0.262 (Oct 2, 2013)
- Server relay link issue:
- In some cases, when the Hamachi client used direct link to connect to a peer, it dropped its via server relay link if the relay link was not in use for a longer period of time.
- Custom routes in a gateway network on Windows clients:
- Windows clients in a gateway network did not propagate custom routes. As a result, Hamachi did not use pre-defined network subnets.
- Hamachi virtual NIC failure on Windows:
- In some cases, configuration of the Hamachi virtual NIC failed on Windows clients.