Coverage chart / LogMeIn Client
How to update LogMeIn Client on your Mac
LogMeIn Client is published as the Homebrew cask logmein-client. Below is how to run that update yourself, then how Floodtide does it for you, alongside every other app on the Mac. Homebrew describes LogMeIn Client as "Remote access tool".
Update LogMeIn Client by hand
- Upgrade the Homebrew cask. If you installed LogMeIn Client with Homebrew, open Terminal and run
brew upgrade --cask logmein-client. Homebrew downloads the current build and replaces the app in your Applications folder. - Or download it from logmein.com. Otherwise get the current build from logmein.com, which is the same download Homebrew points at. Quit LogMeIn Client, open the download and put the new LogMeIn Client in Applications in place of the old one: a disk image is dragged across, an installer package runs its own steps. Your settings and documents live outside the app and are kept.
brew upgrade --cask logmein-clientThat is one app. The same walk, through a different menu or page each time, is what every other app on the Mac asks of you, which is where Floodtide comes in.
The shorter route: one click in Floodtide
Floodtide reads the same Homebrew record for LogMeIn Client that the brew command above does, without needing Homebrew installed, to learn which version is current. When yours is behind, the row appears under Updates with the version it will move to and the download size. Pressing Update, or Update All, does the rest:
- The vendor's own build is downloaded, several apps at a time, with real progress.
- The download is verified against the developer signature of the installed copy; Gatekeeper must accept it before anything is replaced.
- LogMeIn Client is asked to quit politely if it is open, and never forced.
- The bundle is swapped and the old version kept for seven days, so Undo Last Update always works.
- The replacement's code signature is checked; a build signed worse than the one you had is rolled back automatically.
LogMeIn Client's publisher does not publish a checksum, so Floodtide verifies each download by requiring the same developer signature as the copy already installed, and Gatekeeper has to accept it before anything is replaced.
If LogMeIn Client lives in a folder macOS protects, the swap asks for your administrator password once for the whole batch, exactly as the Finder does when you install anything by hand.
What Floodtide knows about LogMeIn Client
- Floodtide reads
- the Homebrew cask logmein-client
- Developer
- logmein.com
- Version the source named on 18 October 2026
- 4.1.8100
- Downloads come from
- secure.logmein.com
- Installed by Floodtide
- Yes, in one click, with the rest of your apps.
- Each download is checked against
- the developer signature already on the installed copy, and Gatekeeper
Read from the source on 18 October 2026. The app reads it live.
Questions about LogMeIn Client
Does Floodtide update LogMeIn Client?
Yes. LogMeIn Client is in the Homebrew catalog that Floodtide reads, so it appears in your update list automatically when a newer version is published, with no configuration.
How does Floodtide install a new version of LogMeIn Client?
It downloads the vendor's official build, verifies it carries the same developer signature as the copy already installed and passes Gatekeeper, quits LogMeIn Client if it is running, swaps the bundle, and keeps the previous version for seven days so the update can be undone.
Will updating LogMeIn Client lose my settings?
No. Floodtide replaces the application only. Preferences, licences and documents live outside it and are untouched.
More apps like this
Other apps people ask about, each with its own page of steps and its own source.
Next to LogMeIn Client in the list