WORD TO THE WISE: In some cases, after you install this latest LogMeIn update, it will completely fail to work until you restart the computer.

I discovered this after having various problems on my desktop (Mac Pro running 10.8.5), including not being able to connect to it from other computers on my same local network AND noticing literally hundreds of log messages about something going wrong.

A restart stopped all of this from happening.

Here's why they are eliminating free mode and going to pay only.

Q: Why are you making this change?
A: In order to address the evolving needs of our customers, we will be unifying our portfolio of free and premium remote access products into a paid-only offering. We believe this offering to be the best premium desktop, cloud and mobile access experience available in the market today.

Make any sense of this? They could at least give us a straight answer.

I'm using client version 4.1.0.3257 from May 17, 2013. (note this is later than the one posted here on MacUpdate). Since installing this on boot up I receive a OS X pop up confirmation EVERY time at boot asking to allow incoming connections to LogMeIn. Yes, LogMeIn is already Allowed in Firewall, and always has been.I have researched this, steps I've already taken:

1) Yes, LogMeIn is already Allowed in the OS X Firewall, and always has been.
2) LogMeIn is Allowed all connections in Little Snitch, and always has been.
3) Per an old thread from 2010 about the exact same problem, the recommendation in that thread was to uninstall and reinstall. I have uninstalled and resinstalled 3 times. After each reinstall, the pop up stops for a few boots, and then reappears.

Due to this problem, I can't boot up remote unattended because user input is required at the host to confirm the pop up, otherwise the connection is blocked.

I opened a ticket #02971799, after a few email exchanges, Support promptly closed the ticket with no other explanation other than due to my not being a Pro user, support was not provided (ignoring the fact that if this is a bug, it probably exists in the Pro version too).

Anyone else having this issue? There are some references on the web that some other people who have looked into this feel it is an issue with the client not being signed properly relative to Gatekeeper/Sandbox, etc, hence on startup, OS X feels it isn't trusted, despite the Firewall setting, and wants reconfirmation. I'm running 10.8.5.

this didn't start until I upgraded to 4.1.0.3257, but even after trying to downgrade back to 4.1.2324, the problem persists, so something is not being cleared.

With out a doubt the best support system out there for a tech. As someone who spend a lot of time working on "OPN" (Other Peoples Networks) I could not live with out this useful tool.

I have also spent a lot of time comparing the other products like ARD, Timbuk2 and Go2MyPC and with out any hesitation I can tell you it's the best. While I use ARD when I need some additional Apple related feature I mostly use LMI because I can work on any type of machine (Windows. Mac and soon Linux) from my Mac, iPad or even iPhone.

This is with just the "Free" version of the client. If I were willing to pat for the Pro version I would also be able to do file transfers; and the pro client is still cheaper the paying for TB2. As a work around if I need to transfer a file I just boot up iChat or Google Docs and then use that as a go between, not a real headache.

Now let's talk about the security of the product... LMI uses a full 256bit AES encrypted tunnel between my machine and the "target". They also offer 2 factor authentication when I log in to my account.

For this and many more reasons I don;t have time to add here I recently upgraded my account to the LMI Central service which I would recommend to any tech or someone who has a lot of machines to support on many OPN.

Just my $0.02

Now up to version 4.00.1940