The GoTo Community is currently experiencing some technical issues affecting new posts and comments. You may need to reload the page you are on before you can post a comment. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Ricardo369
8 years agoNew Contributor
Windows 10 1803 i cant install the logmein client
 i have tried installing on 3 computers with fresh installes and updates. every time i get Logmein Setup ended prematurley . is there a work around for this? 
- 8 years ago
The answer was just posted in another post that worked for me:
Try this, it worked for me. When downloading from the Add Computer within logmein central, it did not work. However, when downloading it from here, which I would have thought to be the same source, it worked:
https://secure.logmein.com/logmein.msi
It's either a different install package or they just fixed it and I happened to grab it right after.
But If I had to guess, the error has to do with the account association. The LogMeIn Central version ties the user to the installer. This version requires you log in after you install.
 
GlennD
8 years agoGoTo Manager
Hi,
We are working on a new release that will correct this issue, we hope to make available very soon. I will update this topic once a firm release date is confirmed.
aqua_jon
8 years agoActive Contributor
Hi Glenn
we appreciate the update, and hope it's coming soon.
This is not your fault, but perhaps you could suggest to QHSE that from a quality perspective it would be worth obtaining early previews of the next Windows 10 Build to perform some testing against, to make sure LMI isn't caught out again, your customers would appreciate that and probably be willing to be involved in the testing.
Thanks,
Jon.
- theaccuser8 years agoActive ContributorAny update on this?
- Sage_Eagle8 years agoActive Contributor
I too would like an update on this ASAP. We need our customized installers when deploying LMI to customer machines. We can't be giving credentials to customers in order to log in and associate their machines with our Central account. If we have to use another remote utility first so we can connect, install, and enter the login ourselves, then why are we paying so much for LogMeIn?
Here's our work-around for now. When I first ran into and troubleshot this issue, I tried some older custom installers I had to see if they worked. Some failed just like these newest ones, but I found that one of our older installers did work – one I created in February of 2017. So for now I I've posted that old installer on our website for customers to download. That old one properly associates the customer machine with our account and puts the PC into the correct group. Then the client detects that it has an update, the customer allows the update to be installed, and we're good to go. But that's still an extra step that of course shouldn't be needed, and it doesn't cover all situations in which we deploy customized LMI installers.
- Sage_Eagle8 years agoActive Contributor
I should've specified that the old customized installer I have that works does work on the April 2018 update to Windows 10, aka 1803.