Logos 4.2a Beta 1 (v4.21.4.8168) is available for testing.
To upgrade from a shipping version, such as 4.1 SR-4 or 4.2, enter "set update channel to beta" command to begin download, or "update now" if you've already switched to the beta channel. To install Beta 1 from scratch, see the notes and download link at http://community.logos.com/forums/t/8883.aspx.
For Release Notes, see http://wiki.logos.com/Logos_4.2a_Beta_1.
Logos 4.2a Beta 1 (v4.21.4.8168) is available for testing. To upgrade from a shipping version, such as 4.1 SR-4 or 4.2, enter "set update channel to beta" command to begin download, or "update now" if you've already switched to the beta channel. To install Beta 1 from scratch, see the notes and download link at http://community.logos.com/forums/t/8883.aspx. For Release Notes, see http://wiki.logos.com/Logos_4.2a_Beta_1.
Avast (version 5.0.677) is blocking this, reporting that it has a trojan infection. It is identified by Avast as Win32:Unruy-K (Trj]
Now I can't install via the installer either, since it shows that Logos4 is up to date.
However, I could open Logos from the C:\Users\[name]\AppData\Local\Logos4\System folder directly, and it seems to be running okay.
This seems strange, but I'm reporting it, in case someone else runs into this issue.
Avast (version 5.0.677) is blocking this, reporting that it has a trojan infection. It is identified by Avast as Win32:Unruy-K (Trj] Now I can't install via the installer either, since it shows that Logos4 is up to date. However, I could open Logos from the C:\Users\[name]\AppData\Local\Logos4\System folder directly, and it seems to be running okay.
Just to be sure, I rescanned all the files from the download server with ESET NOD32 Antivirus 4, and found no threats.
There should be a %LOCALAPPDATA%\Logos4\Logos4.exe file (not in the "System" folder) that is the normal entry point for the program. (Or is that the specific file that Avast is blocking?). As a workaround, you can run the "Logos4\System\Logos4.exe" file directly, but it would be preferable to be able to use the "Logos4\Logos4.exe" file. (Once Avast is updated to not detect a false positive, you should be able to restore that file by Repairing the Logos4.msi package.)
Someone else reported trouble with Avast reporting a false positive in a Logos installer file: http://community.logos.com/forums/t/26090.aspx. I've also read elsewhere on the web that Avast has been having lots of problems with false positives.
I suggest you give Avast a rest for a while and try a different anti-virus program. I use AVG and it's pretty well respected and free. And there are plenty of other good ones out there.
I just reported the same problem too - same virus detected. Reported it here.
Roise,
I've been using Microsoft Security Essentials & it seems to work very well. It's free too.
Roise, I've been using Microsoft Security Essentials & it seems to work very well. It's free too.
It may be coincidence but I had trouble getting the download notification (Autodownload = NO) eg. 2 x Update Now, restart, Update Now. When I turned off Real-time protection I got the notification immediately and the installer is slowly downloading (with Real-time back ON).
OK, installed with no virus warnings from MSE, and re-indexing!
Melissa,
For the last several beta releases (including this one), I've had to manually (Task Manager) kill the COM Launcher so installation could continue. Is anyone else having that issue?
AVG doesn't report any warning. Beta installed without any problems.
FWIW Kaspersky Internet Security never blinked, it's definitely an AVAST issue.
Maybe, but not totally. On my daughter's copy of Logos (different account), she is running an old Avast (4.8) which did not flag the problem. BUT, she has Windows Defender on there, and it popped up a screen asking to send Logos4.exe to Microsoft for analysis; so it must have seen something suspicious also. It did not block usage of the program though.
I use Avast but am so trusting of Logos that I have it excluded from protection. In Avast exclusions I put in C:\Users\<user>\AppData\Local\Logos4
Melissa, For the last several beta releases (including this one), I've had to manually (Task Manager) kill the COM Launcher so installation could continue. Is anyone else having that issue?
Bill ~ This is due to the Logos Smart Tag for Word. There a couple of ways around this: 1) close Word before updating Logos (and Outlook, too, if it's uses Word as the email editor); or 2) open Task Manager, click on the Processes tab, and End Process on LogosCom.exe before updating.
Hi Melissa,
Mystery solved, and THANKS! Outlook is open, though Word isn't. And I have Outlook set up to use Word as its editor. I have been doing exactly as you suggested in 2), I just couldn't figure out why I was having to. Now I understand... Thanks for repeating what I'm sure you already told us... I have vague recollection that this is a repeat... Thanks, again, for clearing up the mystery...
Blessings!
Just to be sure, I rescanned all the files from the download server with ESET NOD32 Antivirus 4, and found no threats. There should be a %LOCALAPPDATA%\Logos4\Logos4.exe file (not in the "System" folder) that is the normal entry point for the program. (Or is that the specific file that Avast is blocking?). As a workaround, you can run the "Logos4\System\Logos4.exe" file directly, but it would be preferable to be able to use the "Logos4\Logos4.exe" file. (Once Avast is updated to not detect a false positive, you should be able to restore that file by Repairing the Logos4.msi package.)
Thanks Bradley,
I reported this to Avast as a false positive last night, and haven't heard back yet.
I did exclude the Logos4 directory (and all subdirectories) from on access scanning by Avast and was able to restore and run Logos4 from the location you prefer. (I had the Logos4/System directory excluded before.)
Out of curiosity though, what can you tell us about why it's preferable to use the Logos4/Logos4.exe file than to use the Logos4/System/Logos4.exe file (and why are there two such files?)
Someone else reported trouble with Avast reporting a false positive in a Logos installer file: http://community.logos.com/forums/t/26090.aspx. I've also read elsewhere on the web that Avast has been having lots of problems with false positives. I suggest you give Avast a rest for a while and try a different anti-virus program. I use AVG and it's pretty well respected and free. And there are plenty of other good ones out there.
I've tried both AVG and Avast and prefer Avast's user interface (but to each his/her own). As far as doing my research, I've found AVG and Avast pretty much on par in terms of catching viruses, though AVG has a few more users than Avast.
Any anti-virus is going to give some false-positives from time to time (including the paid subscription ones), since they don't look for viruses, but virus signatures. I've had them on every anti-virus program I've used. Occasionally legitimate code includes a sequence of commands that parallels the part of the virus the anti-virus program looks for. That's when false positives happen, and why reporting them is as necessary as reporting problems and bugs on these forums.
The Logos4\Logos4.exe is a lightweight C++ app that displays the splash screen quickly, then determines if it should launch a new instance of Logos 4, or activate an existing instance. It also dispatches the logos4:, logosref:, etc. protocols, improves support for Windows 7 taskbar pinning, prompts you to install an update if one was downloaded in the last session, and some other minor (and non-essential) tasks.
Running System\Logos4.exe will get the same end results (Logos 4 up and running) but a) it doesn't display a splash screen, so you might not know it's loading; b) its startup time is longer, so if you already have Logos 4 running, it will take longer to activate the existing instance; c) there may be some other minor details I've forgotten.
Out of curiosity though, what can you tell us about why it's preferable to use the Logos4/Logos4.exe file than to use the Logos4/System/Logos4.exe file (and why are there two such files?) The Logos4\Logos4.exe is a lightweight C++ app that displays the splash screen quickly, then determines if it should launch a new instance of Logos 4, or activate an existing instance. It also dispatches the logos4:, logosref:, etc. protocols, improves support for Windows 7 taskbar pinning, prompts you to install an update if one was downloaded in the last session, and some other minor (and non-essential) tasks. Running System\Logos4.exe will get the same end results (Logos 4 up and running) but a) it doesn't display a splash screen, so you might not know it's loading; b) its startup time is longer, so if you already have Logos 4 running, it will take longer to activate the existing instance; c) there may be some other minor details I've forgotten.
Thanks for the explanation. I'll change my desktop shortcut to point back the correct place.
