Forum Discussion
Thanks for the update.
Folks,
FYI: A fix is on its way. It will be released on the 12th of March.
- SOSCOMP2 years agoNew Contributor
We updated LMI manaully and rebooted. Problem still exists. It can be triggered by looking at properties>details of the lmiinfo.sys file (which are blank) or by opening LMI control Panel and going to About>Check for updates, among other triggers. But that is easiest way to see if update worked. When LMI is uninstalled and reinstalled, the properties>Details of the lmiinfo.sys file are not blank -shows version info etc and cannot trigger ESET.
- SOSCOMP2 years agoNew Contributor
We did that last week when we found out about the release-it did not help. Please see all of my previous posts in htis thread. So far the only thing working is to uninstall and reinstall LogMein.
2 out 140 PCs done 😞 Please help.
- ProCentPM2 years agoGoTo Contributor
Hey!
Last Tuesday we released a new host version that is slowly being deployed to customers. You can update manually to this latest version that contains the fix of the issue detected by ESET. - SOSCOMP2 years agoNew Contributor
Hi-just checking to see if you kn ow if the LMI team is working on a fix -thanks!
- SOSCOMP2 years agoNew ContributorAlso cannot do ad hoc support when LMI is already installed -in case we wanted to uninstall LMI and reinstall it to mimick the fresh install test we did
- SOSCOMP2 years agoNew ContributorWe took a Windows10 PC with just ESET on it and installed LogmeIn (never on system before) and ESET did not detect anything-ran a custom scan on hte LMI directory too. The LMIinfo.sys in this new install is 11.1.0.3236. When we check the properties for the systems with LMI already installed and updated there is no version information listed. Odd. Could it be we have to uninstall and install LMI on the systems? Hard to do remotely I guess unless we do an ad hoc session to the systems, then uninstall and reinstall LMI?
- SOSCOMP2 years agoNew Contributor
We manually updated one to the new LMI version as a test. Didn't help. Like I said we don't have any issue on one that has a fresh LMI installation and has ESET. I sent a reply on this earlier too
- GlennD2 years agoGoTo Manager
SOSCOMP When we deploy new versions only a small number of systems receive it in the beginning, did you manually updated all of your computers to the new Host software 4.1.0.15410? The computers that ESET is reporting an issue with may not have updated yet, have you confirmed that they are all running v4.1.0.15410 of the Host software?
- SOSCOMP2 years agoNew Contributor
We took a Windows10 PC with just ESET on it and installed LogmeIn (never on system before) and ESET did not detect anything-ran a custom scan on hte LMI directory too. The LMIinfo.sys in this new install is 11.1.0.3236. When we check the properties for the systems with LMI already installed and updated there is no version information listed. Odd. Could it be we have to uninstall and install LMI on the systems? Hard to do remotely I guess unless we do an ad hoc session to the systems, then uninstall and reinstall LMI?
- SOSCOMP2 years agoNew Contributor
The LMI update did not fix the issue for us. We use ESET endpoint Security. What Antivirus are you using? Any resolution for you yet?
- SOSCOMP2 years agoNew Contributor
Hi -Windows 10 Pro and Windows11 Pro
- 2ARM52 years agoActive Contributor
Interesting. Users have reported, and I myself experienced, an update prompt without manually checking for an update. I've now reviewed the installed version on all systems, about 12% are up to date. Guess we'll give it some time.
Thanks
- GlennD2 years agoGoTo Manager
SOSCOMP What version of Windows is being used? We tested all supported Windows versions and only identified an issue with Windows 7 x64 and Server 2008 R2 x64 as they have issues validating the signature of the updated driver. According to Microsoft this Windows update should help with that: https://catalog.update.microsoft.com/search.aspx?q=kb4474419
- 2ARM52 years agoActive Contributor
Hi Glenn,
All of our systems are set to update automatically, but the update is prompting users for admin. credentials.
Our users don't have admin. rights. Is there a way to run this update programmatically?
- SOSCOMP2 years agoNew Contributor
Hi we are having same issue and with our endpoint security and LMI. We have ran the LMI update today (version.15410 installed) and rebooted. Our ENDpoint product is upto date as well.
"A potentially unsafe application (Win64/LogMeIn.A) found in a file (the filename is random)" tried to access."
Please help-pop-ups occurring often!
- GlennD2 years agoGoTo Manager
Hi,
We have begun deploying the update to accounts and systems will begin auto updating over the coming days.
- lmiuser122 years agoNew Contributor
thanks for the update