What is SymErr.exe?

SymErr.exe is part of Symantec Shared Component and developed by Symantec Corporation according to the SymErr.exe version information.

SymErr.exe's description is "Symantec Error Reporting"

SymErr.exe is digitally signed by Symantec Corporation.

SymErr.exe is usually located in the 'C:\Program Files (x86)\Norton Internet Security\Engine\22.19.9.63\' folder.

None of the anti-virus scanners at VirusTotal reports anything malicious about SymErr.exe.

If you have additional information about the file, please share it with the FreeFixer users by posting a comment at the bottom of this page.

Vendor and version information [?]

The following is the available information on SymErr.exe:

PropertyValue
Product nameSymantec Shared Component
Company nameSymantec Corporation
File descriptionSymantec Error Reporting
Internal nameSymErr
Original filenameSymErr.exe
Legal copyrightCopyright © 2019 Symantec Corporation. All rights reserved.
Product version7.17
File version7.17.0.56

Here's a screenshot of the file properties when displayed by Windows Explorer:

Product nameSymantec Shared Component
Company nameSymantec Corporation
File descriptionSymantec Error Reporting
Internal nameSymErr
Original filenameSymErr.exe
Legal copyrightCopyright © 2019 Symantec Corporati..
Product version7.17
File version7.17.0.56

Digital signatures [?]

SymErr.exe has a valid digital signature.

PropertyValue
Signer nameSymantec Corporation
Certificate issuer nameVeriSign Class 3 Code Signing 2010 CA
Certificate serial number46735060c8d2436a20f7384996ec931b

VirusTotal report

None of the 71 anti-virus programs at VirusTotal detected the SymErr.exe file.

None of the 71 anti-virus programs detected the SymErr.exe file.

Sandbox Report

The following information was gathered by executing the file inside Cuckoo Sandbox.

Summary

Successfully executed process in sandbox.

Generic

[
    {
        "process_path": "C:\\Windows\\System32\\lsass.exe",
        "process_name": "lsass.exe",
        "pid": 476,
        "summary": {},
        "first_seen": 1575435184.34375,
        "ppid": 376
    }
]

Signatures

[
    {
        "markcount": 1,
        "families": [],
        "description": "This executable has a PDB path",
        "severity": 1,
        "marks": [
            {
                "category": "pdb_path",
                "ioc": "C:\\bld_area\\SymQualClient_7_17_0_56\\VS141\\Bin\\x64\\Release\\symerr.pdb",
                "type": "ioc",
                "description": null
            }
        ],
        "references": [],
        "name": "has_pdb"
    },
    {
        "markcount": 1,
        "families": [],
        "description": "The file contains an unknown PE resource name possibly indicative of a packer",
        "severity": 1,
        "marks": [
            {
                "category": "resource name",
                "ioc": "SYMPRO",
                "type": "ioc",
                "description": null
            }
        ],
        "references": [],
        "name": "pe_unknown_resource_name"
    }
]

Yara

The Yara rules did not detect anything in the file.

Network

{
    "tls": [],
    "udp": [
        {
            "src": "192.168.56.101",
            "dst": "192.168.56.255",
            "offset": 546,
            "time": 3.0631229877471924,
            "dport": 137,
            "sport": 137
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 5074,
            "time": 3.025428056716919,
            "dport": 5355,
            "sport": 51001
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 5402,
            "time": 1.023564100265503,
            "dport": 5355,
            "sport": 53595
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 5730,
            "time": 3.037790060043335,
            "dport": 5355,
            "sport": 53848
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 6058,
            "time": 1.5364830493927002,
            "dport": 5355,
            "sport": 54255
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 6386,
            "time": -0.09843206405639648,
            "dport": 5355,
            "sport": 55314
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 6714,
            "time": 1.5474610328674316,
            "dport": 1900,
            "sport": 1900
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 15396,
            "time": 1.0570709705352783,
            "dport": 3702,
            "sport": 49152
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 23780,
            "time": 3.110337018966675,
            "dport": 1900,
            "sport": 53598
        }
    ],
    "dns_servers": [],
    "http": [],
    "icmp": [],
    "smtp": [],
    "tcp": [],
    "smtp_ex": [],
    "mitm": [],
    "hosts": [],
    "pcap_sha256": "032f2fa85fe66c3dfab99452403db64ad390f834ed078e1b860b19f67427f22b",
    "dns": [],
    "http_ex": [],
    "domains": [],
    "dead_hosts": [],
    "sorted_pcap_sha256": "99d00f3085afa86abb819d11903a40a717b0890f34aa348c28d6509403c726a3",
    "irc": [],
    "https_ex": []
}

Screenshots

Screenshot from the sandboxScreenshot from the sandbox

Other files also named SymErr.exe

SymErr.exe (13 votes)

Hashes [?]

PropertyValue
MD52ac1a6936da4f33a6336f13db841c8be
SHA256e274464b27e593c97e31e9787779d34b777cd4c3dd9c4bb0e3db84e27aa39ff3

Error Messages

These are some of the error messages that can appear related to symerr.exe:

symerr.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

symerr.exe - Application Error. The instruction at "0xXXXXXXXX" referenced memory at "0xXXXXXXXX". The memory could not be "read/written". Click on OK to terminate the program.

Symantec Error Reporting has stopped working.

End Program - symerr.exe. This program is not responding.

symerr.exe is not a valid Win32 application.

symerr.exe - Application Error. The application failed to initialize properly (0xXXXXXXXX). Click OK to terminate the application.

What will you do with SymErr.exe?

To help other users, please let us know what you will do with SymErr.exe:



Malware or legitimate?

If you feel that you need more information to determine if your should keep this file or remove it, please read this guide.

Please select the option that best describe your thoughts on the information provided on this web page


Free online surveys

And now some shameless self promotion ;)

A screenshot of FreeFixer's scan result.Hi, my name is Roger Karlsson. I've been running this website since 2006. I want to let you know about the FreeFixer program. FreeFixer is a freeware tool that analyzes your system and let you manually identify unwanted programs. Once you've identified some malware files, FreeFixer is pretty good at removing them. You can download FreeFixer here. It runs on Windows 2000/XP/2003/2008/2016/2019/Vista/7/8/8.1/10. Supports both 32- and 64-bit Windows.

If you have questions, feedback on FreeFixer or the freefixer.com website, need help analyzing FreeFixer's scan result or just want to say hello, please contact me. You can find my email address at the contact page.

Comments

Please share with the other users what you think about this file. What does this file do? Is it legitimate or something that your computer is better without? Do you know how it was installed on your system? Did you install it yourself or did it come bundled with some other software? Is it running smoothly or do you get some error message? Any information that will help to document this file is welcome. Thank you for your contributions.

I'm reading all new comments so don't hesitate to post a question about the file. If I don't have the answer perhaps another user can help you.

No comments posted yet.

Leave a reply