The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.

Forum Discussion

DaveFox's avatar
DaveFox
New Member
6 years ago

Legacy Versions for OSX

Hi,

 

Today I have been auto-updated to a version of LogMeIn Pro that now renders the application unusable. On reading the minimum system requirements it states OSX 10.12. I am maxed out on this machine at 10.11, so there is the reason.

 

Is there any way of taking a backwards step to a legacy version?

 

I would have liked to ask this via the trouble ticket process but that appears to be broken.

 

Any pointers are gratefully received.

 

Many Thanks

 

Dave

 

 

15 Replies

  • webmaster265's avatar
    webmaster265
    New Member
    6 years ago

    You must provide legacy version of the client app.  I have over 30 employees that as of today will begin working from home due to coronavirus.  Mac laptops were located overnight and all are Mac OS 10.11

  • AshC's avatar
    AshC
    Retired GoTo Contributor
    6 years ago

    I apologize for the frustrations.  While it is possible to keep an older Mac system such as 10.11 available as a Host computer, the LogMeIn desktop application has no way to revert back to an older version.

     

  • PLogic's avatar
    PLogic
    Visitor
    6 years ago

    SAME! Please share the last version so we can downgrade.

  • Mappy's avatar
    Mappy
    New Member
    6 years ago

    Same issue for me.

    Logmein Client Version: 4.1.7343 (4.1.0.7343) keeps crashing (SIG ABORT)
    because of my Mac being at 10.11.6 ...
    Can't use it anymore ... :(

     

    Crashed Thread: 0 TLMIApplicationMain Dispatch queue: com.apple.main-thread

    Exception Type: EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Exception Note: EXC_CORPSE_NOTIFY

    Application Specific Information:
    abort() called
    application requires at least OS X version 10.12.0 (10.12), but is being run on 10.11.6 ( 10.11.6/15G22010), and so is exiting