Hamachi 2.2.0.633 VPN Service for PC Windows

- Free subscription allows you to have eight members in a network
- Standard subscription allows you to have 32 members in a network
- Premium subscription allows you to have 256 members in a network
- Multi-network subscription or a LogMeIn Central subscription allows you to have 256 members in all your networks
* Note: The current and maximum number of network members are displayed on the Hamachi client next to name of the network. For example, 11/256 means that there are 11 members in a network that can have up to 256 members.

# New Features
* IPv6 support
- LogMeIn Hamachi supports IPv6 network protocol.
# Enhancements
* LogMeIn Hamachi2 renamed
- LogMeIn Hamachi² has been renamed to LogMeIn Hamachi.
* Exit menu item was missing from system tray menu
- The Exit menu item was removed from the system tray menu in the previous Hamachi or Mac release. It is now re-added to the system tray menu.
# Fixes
* Join network window lost focus
- The Join into a network window lost focus if the client’s join request was approved in another network in the meantime.
* Collapse/expand icon did not change from keyboard (+/-), the icon does not align
- The collapse/expand icon did not change on the client user interface if you toggled a network with the +/- keys on the keyboard.
* Gateway network issues
The following errors occurred in gateway networks:
- In some cases, network adapters were not displayed in the Start > Control Panel > Network Connections window if the gateway client either left the gateway network or changed its role to member. In this case, the network bridge of the gateway network was removed.
- The client engine unexpectedly stopped running if a member’s role was changed to Gateway on the LogMeIn website.

# Fixes

* TCP tunnel setup
An incorrect IP address was recorded during TCP tunnel setup.

* Unregistering UPnP entry
UPnP entries were not unregistered before a new one was registered.

* UPnP entries not removed from router
UPnP entries were not removed from the router's settings if the Hamachi² client was not shut down properly. This occurred for example due to system failure, or network interruption.

* Welcome messages in minimal mode
Clients running in minimal mode incorrectly received network welcome messages.
The options in the Network menu were available on the Hamachi² for Windows client in restricted mode even if joining or creating networks were disabled on the LogMeIn web interface.

You can change these client settings on the web interface by switching to Network mode and then clicking Edit next to the client you want to change. You can modify your client settings on the Settings tab.

* Enhancements
- Improved Hamachi² tunnels
- Hamachi² tunnels are now more robust, which makes it easier to establish peer-to-peer connections between clients with low quality network connections.
- Compatibility with Mediashare
- Compatibility with UPnP devices using Mediashare has been improved.

* Fixes
- System notifications were not displayed
> System notifications did not appear in the system tray.
- Client closed in restricted mode
> The Hamachi² client closed unexpectedly if you switched between basic and advanced modes at System > Preferences > Settings while running in restricted mode.
- Incorrect IP address used for P2P
> Establishing a tunnel was slow or failed for clients on same LAN if the communication port was set only at System > Preferences > Settings > Advanced Settings > Peer Connections.
- Incorrect date format in notifications
> In some languages, the date was not displayed correctly in notification messages concerning planned maintenance..
- UPnP entries not removed from router
> UPnP entries were not removed from the router's settings when the Hamachi² client was not shut down properly (for example, due to system failure or network interruption).
- Incorrect client statistics
> In some cases, incorrect client statistics were displayed if the Hamachi² client was left running for a long time. To view client statistics, right-click on a client and select Details.
- Incorrect gateway DNS settings
> Secondary DNS server settings overwrote the primary DNS server settings of a gateway client.

* It contains a fix for the "Loss of Hamachi IP" issue.

* If a Gateway Node is established on a Server with Static IP Information, the Static IP will now correctly carry over to the Network Bridge.
* The Hamachi Adapter now has its Default Gateway set to 5.0.0.1 and its Metric to 9000.
* The Hamachi Adapter is noset to the lowest priority in the Adapter Binding list.

* Changed licensing model and according UI changes

* Changed the initialization sequence when the Hamachi is run
for the first time.