What is rsa64.dll?
rsa64.dll is usually located in the 'C:\ProgramData\Microsoft\Crypto\RSA64\' folder.
Some of the anti-virus scanners at VirusTotal detected rsa64.dll.
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.
Digital signatures [?]
rsa64.dll is not signed.
VirusTotal report
6 of the 50 anti-virus programs at VirusTotal detected the rsa64.dll file. That's a 12% detection rate.
| Scanner | Detection Name |
|---|---|
| Avast | Win64:Bot-A [Trj] |
| Baidu-International | Trojan.Win64.Sathurbot.A |
| Emsisoft | Trojan.Win64.Sathurbot (A) |
| ESET-NOD32 | a variant of Win64/Sathurbot.A |
| Malwarebytes | Trojan.Sathurbot.64 |
| TrendMicro-HouseCall | TROJ_GEN.F47V0222 |
rsa64.dll removal instructions
The instructions below shows how to remove rsa64.dll with help from the FreeFixer removal tool. Basically, you install FreeFixer, scan your computer, check the rsa64.dll file for removal, restart your computer and scan it again to verify that rsa64.dll 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 rsa64.dll in the scan result and tick the checkbox next to the rsa64.dll 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 rsa64.dll in the scan result.
C:\ProgramData\Microsoft\Crypto\RSA64\rsa64.dll 
- Scroll down to the bottom of the scan result and press the Fix button. FreeFixer will now delete the rsa64.dll file.
- Restart your computer.
- Start FreeFixer and scan your computer again. If rsa64.dll still remains in the scan result, proceed with the next step. If rsa64.dll is gone from the scan result you're done.
- If rsa64.dll 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 rsa64.dll no longer appear in the scan result.
Filename variants
rsa64.dll may also use other filenames. The most common variants are listed below:
- {7647FE2D-574A-4F8D-B580-B435816EC0FB}
- trz314C.tmp
- trz7637.tmp
- trzBB81.tmp
- trzE011.tmp
Folder name variants
rsa64.dll may also be located in other folders than C:\ProgramData\Microsoft\Crypto\RSA64\. The most common variants are listed below:
- c:\ProgramData\COMODO\Cis\Quarantine\data\
Hashes [?]
| Property | Value |
|---|---|
| MD5 | 55c94597a258d86acf61c951ed5c5062 |
| SHA256 | 51e580a54db96d38bf8d8a48f4839119ab05c2f2830442a86772b6e9fbdf624f |
What will you do with rsa64.dll?
To help other users, please let us know what you will do with rsa64.dll:
What did other users do?
The poll result listed below shows what users chose to do with rsa64.dll. 88% have voted for removal. Based on votes from 40 users.
NOTE: Please do not use this poll as the only source of input to determine what you will do with rsa64.dll.
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.
Scanned the PC and the software didn't find rsa64.dll cause avast was removing it for quarentine before I think... Then I restarted in safe mode, scanned PC, found rsa64.dll in two points, and fixed it!
Worked for me, thanks.
# 18 Mar 2014, 17:20
Abdul writes
Scanned and not found.. disabled Symantec Endpoint Protection and found 2.. checked and fixed and rebooted.. scanned again found 3.. checked and fixed and rebooted.. scanned again found 3.. and so on.. not fixed.. I don't know what to do.
# 23 Jun 2014, 20:12
Robson writes