Virus detection: False positive for Webroot SecureAnywhere 2012
Just to let everyone know that Webroot's SecureAnywhere 2012 product falsely identifies logos.documents.contracts.dll as a virus, at the default settings. I've reported it as a false positive, so hopefully they'll fix it. In the meantime, Webroot can quarantine that file which will cause Logos to crash on startup, and never start. You need to make sure you allow access to the file (in Webroot, go to PC Security, then the Quarantine tab, and choose Configure. If the file's already been quarantined, you can restore it from the View Quarantine button.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
Comments
-
Fair play, I just had an email from Webroot saying that they've updated their software so Logos is no longer identified. A ten-hour turnaround is very impressive.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Hi Mark,
I was on the phone with Logos Tech Support for almost three hours yesterday trying to figure out why Logos will not start. I just installed Webroot on Christmas Eve and I did not have the Logos problem until after I installed and used Webroot.
My problem is that I uninstalled and reinstalled Webroot, so I do not have the files you mentioned in Quarantine, and it does not seem that Webroot actually fixed the problem as they told you. Can you tell me what file/s I need to tell Webroot to allow? I don't see the one you have listed in your post.
Thanks for the help!
Blessings,
Tom
0 -
Hi Mark,
I installed Webroot on Christmas Eve and have not been able to open Logos since. I don't think they fixed the problem. I do not see the files in Quarantine because I uninstalled and reinstalled Webroot. I do not have the file you wrote in your post. Do you know of any other file names I can give Webroot to fix the issue?
Blessings,
Tom
0 -
Hi Mark,
I installed Webroot on Christmas Eve and have not been
able to open Logos since. I don't think they fixed the problem. I do
not see the files in Quarantine because I uninstalled and reinstalled
Webroot. I do not have the file you wrote in your post. Do you know of
any other file names I can give Webroot to fix the issue?Blessings,
Tom
0 -
Thomas P. Fox said:
I don't think they fixed the problem.
I've since discovered they only fixed it for one specific version. To restore the file:
- In Webroot, click on PC Security, then Quarantine. Now click View Quarantine.
- You'll see a Logos file in the list. Make a note of the filename, then tick it, the press Restore. It's likely to be c:\users\USERNAME\appdata\local\logos4\system\logos.documents.contracts.dll
- Now, under PC Security, click Configure under Detection Configuration.
- See if the file listed under (2) is also listed under Detection Configuration. If it is, make sure it's set to Allow.
- If it's not listed, click on Add File. Find the file, then click open. Then make sure it's set to Allow and click close.
I'll email Webroot again, and alert them to the ongoing issue.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Thomas P. Fox said:
. I do
not see the files in Quarantine because I uninstalled and reinstalled
Webroot.Sorry, I didn't see this bit. I would reinstall Logos first. The file will probably be quarantined again, in which case you can restore it with the method above.
http://downloads.logos.com/LBS4/Installer/4.30.0.1624/Logos4Setup.exe
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
I reinstalled Logos with their Techs yesterday and nothing. Do you know if that file in question is only installed if I reinstall only Logos and not my Library Resources? To save time, the Logos tech did not reinstall my Library Resources. I wonder if that is why that .dll file did not install.
Thanks for the help!
Tom
0 -
Thomas P. Fox said:
I reinstalled Logos with their Techs yesterday and nothing.
Did you reinstall Logos after reinstalling Webroot? That's what I'm suggesting you do.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Unless you're looking for something more out of Webroot SecureAnywhere than antivirus and malware protection, I'd recommend uninstalling it and getting a refund.
Microsoft Security Essentials is free, extraordinarily lightweight, and from my experience on numerous PCs does not have any interaction problems with Logos.
http://windows.microsoft.com/en-US/windows/products/security-essentials
My $.02 ...
Donnie
0 -
Yes! The Logos Tech reinstalled Logos after I reinstalled Webroot.
0 -
I've read some good things from Microsoft Essentials. I like Webroot for it's prevention, speed of scan, and that it is bundled with mobile phone security as well. I appreciate the thought!
0 -
Thomas P. Fox said:
Yes! The Logos Tech reinstalled Logos after I reinstalled Webroot.
OK. Does the file C:\Users\USERNAME\AppData\Local\Logos4\System\logos.documents.contracts.dll exist? If so, please do steps 3-5, above.
If not, you'll definitely need to reinstall Logos. If you need to reinstall Logos:
- first go to Webroot/PC Security/Shields and disable all the shields.
- Install Logos from the link given above.
- Run Logos, and make sure it works. Close Logos.
- Re-enable all the shields again.
- Run Logos again. If you now get the error message, follow steps 1-2 above.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
I asked the Logos techs for that .dll file you wrote about, but the tech does not have it in his Logos system. The Logos techs narrowed it down to a .NET problem, but we reinstalled .NET and nothing. I'm at a loss.
0 -
Thomas P. Fox said:
I asked the Logos techs for that .dll file you wrote about, but the tech does not have it in his Logos system.
I don't use Webroot and don't have any problems but wanted to confirm that this file does not exist anywhere on my computer either. I done a complete search including hidden and protected files.
0 -
Thomas P. Fox said:
I asked the Logos techs for that .dll file you wrote about, but the tech does not have it in his Logos system. The Logos techs narrowed it down to a .NET problem, but we reinstalled .NET and nothing. I'm at a loss.
I'm running the beta, so perhaps the file only exists there. I just checked my wife's 4.3 install, and you're right, the file doesn't exist there. That being the case, there's no certainty that the problem is being caused by Webroot. I think it would be best for you to create some logs (see 'How to ask for help', below) and create a new thread with the log uploaded.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0
