You are here

Symantec isolates files - LO 4 not usable after update

8 posts / 0 new
Last post
kaum
Offline
Last seen: 9 years 9 months ago
Joined: 2008-07-16 11:18
Symantec isolates files - LO 4 not usable after update

Hi,
I upgraded to the LO 4 version today. Symantec Endpoint Protection isolates "unopkg.exe" and "unopkg.bin" as "Suspicious.MLApp".
LO does not start.

On my home computer Symantec has not isolated anything, although LO 4 is running there as well.
You may like to contact Symantec...

Marc

CatTech
Offline
Last seen: 1 month 1 week ago
Joined: 2010-06-29 02:27
VirusTotal Scan Results

Hi

FYI, the files (1)"unpkg.exe" and (2)"unopkg.bin" scanned by Virustotal are no longer flagged by Symantec as "Suspicious.MLApp" anymore:

BEFORE:

(1) https://www.virustotal.com/file/e7ae00c26a0d2cfaae0fcec010456c9ddb5ef594...

(2) https://www.virustotal.com/file/073dc24722dbe8f2ccadd6772fa5616d1780cbd6...

AFTER:

(1) https://www.virustotal.com/file/e7ae00c26a0d2cfaae0fcec010456c9ddb5ef594...

(2) https://www.virustotal.com/file/073dc24722dbe8f2ccadd6772fa5616d1780cbd6...

These files were submitted to Symantec for their re-evaluation via https://submit.symantec.com/false_positive/.

(Re: https://www.techsupportalert.com/content/how-report-malware-or-false-pos...)

Hope this helps.

Best Regards

potnoodles
Offline
Last seen: 6 years 1 month ago
Joined: 2012-02-21 07:08
LO 4.0.1 Symantec Endpoint

I never had the problem with 4.0 but I do after updating today to LO 4.0.1
unopkg.bin and unopkg.exe (both suspicious MLApp)got shunted into quarantine.
I have submitted both files to Symantec for re-evaluation via the application.

edforman7170@usa.net
Offline
Last seen: 5 years 4 months ago
Joined: 2008-12-08 13:20
Suspicious.Cloud.7.Fdetected in libxml2.dll in LO 4.0.1

When I installed LO 4.0.1 on Windows 7 my Norton Internet Security blocked libxml2.xml because it detected Suspicious.Cloud.7 malware. It also detected Suspicious.MLApp in both unopkg.exe and unopkg.bin as mentioned above.

Now LO won't work at all. I tried both versions (single and multi language)

This just happened last night and this morning. Is there any solution in sight?

John T. Haller
John T. Haller's picture
Online
Last seen: 4 min 30 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Report it to Norton

The issue is entirely with Norton/Symantec. Their current definitions are broken. It's a false positive. You'll need to keep reporting it to Norton until they fix their bug.

Sometimes, the impossible can become possible, if you're awesome!

DrAJAllen
Offline
Last seen: 7 years 11 months ago
Joined: 2005-12-09 08:00
4.01 work around with Norton

Not perfect, but in Norton you can configure Norton (under the settings menu) to exclude the two files from Auto-Protect, SONAR, and Download Intelligence Protections. Then download and reinstall the file manually. Seems to have worked for me. Meanwhile, report the problem to Norton.

sehlat
Offline
Last seen: 8 years 1 month ago
Joined: 2008-07-15 16:45
4.0.3.3 seems to be OK with Symantec

Ran a full scan of everything in my portableapps and Libre Office was left completely untouched.

Swwright
Offline
Last seen: 6 days 22 hours ago
Joined: 2008-07-17 20:25
LibreOffice 4.1.2 versus Symantec Endpoint Protection

Just updated my PortableApps including LibreOffice 4.1.2. As always, less than a minute after the update was installed, Symantec Endpoint Protection informed me that it had saved my computer from an infestation of "Suspicious.MLApp".

Fortunately, the PortableApps version of LibreOffice works without those files (unopkg.exe and unopkg.bin). However, it annoys me that Symantec has refused for over a year to deal with this "false positive" problem.

I have reported the incident to Symantec, including the information that this problem has remained unaddressed for at least a year.

Log in or register to post comments