I have only used the new app once, so I'm not very familiar with it. I don't recall any errors though. I'll try to test it out again after hours.

Meanwhile, is there anything special about the way you run Firefox that might affect interprocess communication with the LogMeIn software? For example, if Firefox were running in a browser/security sandbox or virtual machine, or if you used startup switches to run multiple Firefox sessions simultaneously.

Nothing that I am aware of that I am doing with Firefox is non-standard.

Incidentally, IE11 did show the exact behaviour advertised by LogMeIn documentation. I clicked to connect to my remote host PC and a pop-up immediately lead me through the process of installing the necessary active-x or whatever it is in IE11.

Firefox until today had an earlier module installed, but after it failed to work any more, I removed it, but Firefox seems to assume it is still there and does not offer a reinstall of the latest version.

It may be that if I totally scrubbed Firefox from my system and reinstalled it, that would work, but I am reluctant to lose all my settings, bookmarks, add-ons, stored sign-ons and so forth.

Hi gbhall, before taking any drastic action, try this two-minute experiment.

Create a new Firefox profile

A new profile will have your system-installed plugins (e.g., Flash) and extensions (e.g., security suite toolbars), but no themes, other extensions, or other customizations. It also should have completely fresh settings databases and a fresh cache folder. This profile should be blissfully unaware of your earlier LogMeIn add-on, unless there is a lingering registry entry for it.

Exit Firefox and start up in the Profile Manager using Start > search box (or Run):

firefox.exe -P

Any time you want to switch profiles, exit Firefox and return to this dialog.

You'll click the Create Profile button. I recommend using the default location suggested, and NOT choosing your own folder. Then start Firefox in the new profile you created.

Does the LogMeIn push download work any better in the new profile?

When returning to the Profile Manager, you might be tempted to use the Delete Profile button. But... it's a bit too easy to accidentally delete your "real" profile, so I recommend resisting the temptation. If you do want to clean up later, I suggest making a backup of all your profiles first in case something were to go wrong.

Regarding the registry entry, if you are familiar with regedit.exe, you could search for LogMeIn and if you find it under any Mozilla-related key, that might explain Firefox's confusion.

Thank you for your advice. On starting the LogMeIn process, there was unfortunately no change, and the push download appeared, was installed but would not start - just as before. I do have a logmein app in the firefox setup config now, that describes it as an app, so that is a step forward.

Looking in the registry also gave me a clue, it told me where the push download had stored that app, and found it in users\david\appdata\local\logmein Client\ (no choice given at any stage).

It is named logmein client.exe and now I know why it 'does not start' - it is because I have win 7 pro, which enabled me to set a group policy preventing execution of anything in appdata\local except what I allow. As soon as I managed to rediscover how I did that (!!) and allowed logmein client.exe, the app now works.

Sadly it is not as it used to be, and lacks certain 'pro' features that I have paid for, so the easy answer is to use IE11 and the active-x extension which is fine.

After much testing and trying, I figured out what the problem is. The logmein client installs itself with a cookie. Very important. My FF was set up to delete cookies upon exit. When I leave the cookies alive for the next session, it doesn't require the reinstalling of the logmein client.

Thanks #gallicbear2, but it was not cookies preventing app start, it was a self-imposed group policy on where the app is installed. I can now run the app, only to find it no longer seems to support the pro features - one of which, file transfers - is vital to me. Very, very irritating.

Sorry, gbhall. I've always used the free version. And my Windows does not even support group policy. So I wouldn't have an answer for that.

Hi gbhall, yes, due to some recent malware attacks, many organizations blocked EXEs from launching out of the TEMP folder. So their users will definitely run into that problem on managed devices. (I think the typical LogMeIn user is on a non-managed device, or LogMeIn support would have recognized your problem right away.)

I'm surprised their app doesn't support the Pro features. Does this mean all Pro users will need to use IE for remote connections now?

You might think the temp folder, but much more important lately is the user appdata folder - usually at C:\users\<name>\AppData\local\LogMeIn (in this case). Now it is becoming increasingly used by malware, because more or less by definition, any application has unrestricted access to %appdata% without having to know where that is, and can drop exe's there and execute them, with full rights of the local user.

About IE11 and Firefox etc, my IT assistant has found this for me http://blog.logmein.com/it-management/logmein-impending-death-browser-plugins If you want a good laugh, read the dozens of highly critical customer posts that are on there. LMI has shot both feet, but is blaming Firefox.

I'm not yet sure what the app pro options do - it may be that rather than the previous side-menu buttons, there is now another way to do it. For file transfer, you might for instance, map a remote drive and simply drag-n-drop to and from your local drives. Still to be researched.

Thanks, gbhall; good observation. I guess Mozilla knows what they are doing, although they drop their changes on you without a warning and then people don't know how this affects them in their daily routines.

Ref the pro features. LogMeIn now has two parts to it. The traditional browser-based interface is still used to initiate the session, and still carries the side menu, from which the pro features like file transfer, interactive talk and so forth are still available in exactly the same way.

The app now replaces the previous 'Remote control' menu item. So apart from the small irritation of having two screens to close at the end of a session instead of one, there is no real difference. Thank goodness.

But for some people who regularly have remote sessions open to control many host PC's at the same time, they are quite annoyed because it used to be multiple tabs in one browser session, but is now one browser session but multiple applications open on the desktop. This complicates control quite a bit.