What is SecurityCheck (2).exe?
SecurityCheck (2).exe is usually located in the 'c:\documents and settings\%USERNAME%\my documents\downloads\' folder.
Some of the anti-virus scanners at VirusTotal detected SecurityCheck (2).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 [?]
SecurityCheck (2).exe does not have any version or vendor information.
Digital signatures [?]
SecurityCheck (2).exe is not signed.
VirusTotal report
5 of the 54 anti-virus programs at VirusTotal detected the SecurityCheck (2).exe file. That's a 9% detection rate.
| Scanner | Detection Name |
|---|---|
| Antiy-AVL | Trojan[:HEUR]/Win32.Unknown |
| Jiangmin | Trojan/Generic.birzy |
| Kingsoft | VIRUS_UNKNOWN |
| Qihoo-360 | HEUR/Malware.QVM06.Gen |
| Symantec | WS.Reputation.1 |
SecurityCheck (2).exe removal instructions
The instructions below shows how to remove SecurityCheck (2).exe with help from the FreeFixer removal tool. Basically, you install FreeFixer, scan your computer, check the SecurityCheck (2).exe file for removal, restart your computer and scan it again to verify that SecurityCheck (2).exe has been successfully removed. Here are the removal instructions in more detail:
- Download and install FreeFixer: http://www.freefixer.com/download.html
- Start FreeFixer and press the Start Scan button. The scan will finish in approximately five minutes.
- When the scan is finished, locate SecurityCheck (2).exe in the scan result and tick the checkbox next to the SecurityCheck (2).exe file. Do not check any other file for removal unless you are 100% sure you want to delete it. Tip: Press CTRL-F to open up FreeFixer's search dialog to quickly locate SecurityCheck (2).exe in the scan result.
c:\documents and settings\%USE..ME%\my documents\downloads\SecurityCheck (2).exe 
- Scroll down to the bottom of the scan result and press the Fix button. FreeFixer will now delete the SecurityCheck (2).exe file.
- Restart your computer.
- Start FreeFixer and scan your computer again. If SecurityCheck (2).exe still remains in the scan result, proceed with the next step. If SecurityCheck (2).exe is gone from the scan result you're done.
- If SecurityCheck (2).exe still remains in the scan result, check its checkbox again in the scan result and click Fix.
- Restart your computer.
- Start FreeFixer and scan your computer again. Verify that SecurityCheck (2).exe no longer appear in the scan result.
Hashes [?]
| Property | Value |
|---|---|
| MD5 | 042d33514b393a595323085ea96aceef |
| SHA256 | 5ee1641bc11f578bccd9271f16cf957e597715af2f4773f46890eceaceb275a5 |
Error Messages
These are some of the error messages that can appear related to securitycheck (2).exe:
securitycheck (2).exe has encountered a problem and needs to close. We are sorry for the inconvenience.
securitycheck (2).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.
securitycheck (2).exe has stopped working.
End Program - securitycheck (2).exe. This program is not responding.
securitycheck (2).exe is not a valid Win32 application.
securitycheck (2).exe - Application Error. The application failed to initialize properly (0xXXXXXXXX). Click OK to terminate the application.
What will you do with the file?
To help other users, please let us know what you will do with the file:
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.