HitmanPro reports a few "suspicious" ocx-files in the C:\Windows\SysWOW64\ folder on my notebook (Dell Studio 1558, Windows 7 Home Premium 64 bit). The filenames are COMCT332.OCX, COMDLG32.OCX, ... PICCLP32.OCX, etc. (May be the files were installed there by Visual Basic 6.)
HitmanPro calls them suspicious because: "Program is code signed with a weak certificate. This is common to malware. Program is code self-signed. The file is located in a folder that contains core operating system files from Windows. This is not typical for most programs and is only common to system tools, drivers and hacking utilities."
Other malware scanners (MS security essentials, MS safety scanner, TDSSkiller, Malwarebytes) do not report a problem for these files.
- Is there an easy way to replace the files?
- Or should I ignore the warning?
HitmanPro calls them suspicious because: "Program is code signed with a weak certificate. This is common to malware. Program is code self-signed. The file is located in a folder that contains core operating system files from Windows. This is not typical for most programs and is only common to system tools, drivers and hacking utilities."
Other malware scanners (MS security essentials, MS safety scanner, TDSSkiller, Malwarebytes) do not report a problem for these files.
- Is there an easy way to replace the files?
- Or should I ignore the warning?
My Computer
At a glance
Windows 7 home premium, 64 biti3-330M
- Computer type
- Laptop
- Computer Manufacturer/Model Number
- Dell
- OS
- Windows 7 home premium, 64 bit
- CPU
- i3-330M
- Antivirus
- MS security essentials
- Browser
- IE9
