KeyStroke Spy and kdriver32.dll - Easily eliminate this problem
Let our support team solve your problem with KeyStroke Spy and repair kdriver32.dll right now!
Leave the detailed description of your problem in the form below. Our support team will contact you in several minutes and give a step-by-step instruction on how to solve your problem. Please be specific. Do your best describing the problem. This will help us recommend right and complete solution.
Describe your problem here and we'll contact you in several minutes:
Warning:
1) We hate spam as much as you do. We will not share your email with any third party or publish it anywhere. Your email is used only to contact you and give you the solution of your problem.
2) All fields of this form are obligatory.
Threat's profile
|
Name of the threat: KeyStroke Spy |
| Command or file name: kdriver32.dll |
| Threat type: Spyware\trojan |
| Affected OS: Win32 (Windows 9x, Windows XP, Windows Vista) |
Intrusion method
This threat copies its file(s) to your hard disk. Its typical file name is KeyStroke Spy. Then it creates new startup key with name KeyStroke Spy and value kdriver32.dll. You can also find it in your processes list with name kdriver32.dll or KeyStroke Spy.
If you have further questions about this threat, please fill in the form below and we'll contact you shortly.
» Download program for kdriver32.dll removal (True Sword Threat Remover)
Recommended Solution
If you are not sure what to delete, use our award winning program - True Sword. True Sword will find and fully remove KeyStroke Spy and 339 280 other dangerous threats including trojans, spyware, adware, riskware, problemware, keyloggers, dialers, viruses and other kinds of malicious programs in several seconds. Fast, easy, and handy, True Sword protects your computer against malicious programs that do harm to your computer and break your privacy. True Sword scans your hard disks and registry and destroys any manifestation of such malicious programs. Standard anti-virus software can do nothing against privacy breakers and malicious programs like that. Get rid of trojans, spyware, adware, trackware, dialers and keyloggers in one click now!
» Download True Sword now for free
How to fix KeyStroke Spy
This problem can be solved manually by deleting all registry keys and files connected with this software, removing it from starup list and unregistering all corresponding DLLs. Additionally missing DLL's should be restored from distribution in case they are corrupted by KeyStroke Spy. To fix this threat, you should:
1. Kill the following processes and delete the appropriate files:
• kdriver32.dll
• keystroke spy help documentation.url
• keystroke spy.lnk
• kimg.dll
• remove keystroke spy.lnk
• spysplash.dat
Warning: you should delete only those files which checksums are listed as malicious. There may be valid files with the same names in your system. We recommend you to use True Sword for safe problem solution.
2. Delete the following malicious folders:
• C:\Program Files\ksysconfig\
• %autostart% \keystroke spy\
3. Delete the following malicious registry entries and\or values:
• Key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Keystroke Spy Value: DisplayName
• Key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Keystroke Spy Value: UninstallString
Warning: If value is listed for some registry entries, you should only clear these values and leave keys with such values untouched. We recommend you to use True Sword for safe problem solution.
Here are the descriptions of problems connected with KeyStroke Spy and kdriver32.dll we received earlier:
keystroke spy error on kimg.dll
Problem Summary: keystroke spy error on kimg.dll
installed the software, had input password on initial setup...then logged in as other user to test.. it asked me to input the password to use (not quite stealthy??).
done some stuff after 'start logging'
rebooted to make sure..relogged on as both user and admin - get error saying cannot locate kimg.dll - after ok to this message I get smss.exe has stopped working
Our support has contacted the author of this message, ang, and helped to solve his problem.
Next threat: keywordmax cookie »
« Back to catalog |