Manual Removal Guide for WinFixer

The following instructions have been created to help you to get rid of "WinFixer" manually.
Use this guide at your own risk; software should usually be better suited to remove malware, since it is able to look deeper.

If this guide was helpful to you, please consider donating towards this site.

Threat Details:

Categories:

• malware

Description:

advertising:
Aggressive advertising using flash to bypass popupblockers. Advertising LIES about the users computer beeing infected and/or corrupted.

installation:
during installation of the trial version, there is absolutely no display of any license or user agreement. An encrypted connection is being established to reliablestats.com without any notice nor question for user consent.

systemscan with winfixer shows more than 100 "severe Threats" on a clean test system , the "scans" are usually completely overexaggerated.

subsequent scans may show a difference in scanresults, without changes made to the system.

trial version does not allow fixing, instead a connection to trial.updates.winsoftware.com is established without any notice nor question about user consent.

uninstallation also causes a connection to reliablestats.com again with no user consent nor notice.

Supposed Functionality:

supposed to fix various system malfunctions in windows, such as corrupt files, registry entries and so on

Removal Instructions:

Autorun:

Please use Spybot-S&D, RunAlyzer or msconfig.exe to remove the following autorun entries.

• Entries named "WinFixer 2005".

Installed Software List:

You can try to uninstall products with the names listed below; for items identified by other properties or to avoid malware getting active again on uninstallation, use Spybot-S&D or RunAlyzer to locate and get rid of these entries.

• Products that have a key or property named "WFX5_is1".

Files:

Please use Windows Explorer or another file manager of your choice to locate and delete these files.

• The file at "<$SYSDIR>\birdihuy32.dll".
• The file at "<$COMMONPROGRAMS>\WinFixer 2005\Contact customer support.lnk".
• The file at "<$COMMONPROGRAMS>\WinFixer 2005\Uninstall WinFixer 2005.lnk".
• The file at "<$COMMONPROGRAMS>\WinFixer 2005\WinFixer 2005 on the Web.lnk".
• The file at "<$COMMONPROGRAMS>\WinFixer 2005\WinFixer 2005.lnk".
• The file at "<$COMMONPROGRAMFILES>\WinSoftware\CrXML.dll".
• The file at "<$PROGRAMFILES>\WinFixer 2005\compcln.dll".
• The file at "<$PROGRAMFILES>\WinFixer 2005\df_fixer.dll".
• The file at "<$PROGRAMFILES>\WinFixer 2005\df_kmd.sys".
• The file at "<$PROGRAMFILES>\WinFixer 2005\df_proxy.dll".
• The file at "<$PROGRAMFILES>\WinFixer 2005\ffCom.dll".
• The file at "<$PROGRAMFILES>\WinFixer 2005\FFWraper.dll".
• The file at "<$PROGRAMFILES>\WinFixer 2005\FileTypeRecognizer.dll".
• The file at "<$PROGRAMFILES>\WinFixer 2005\FixCore.dll".
• The file at "<$PROGRAMFILES>\WinFixer 2005\Install.exe".
• The file at "<$PROGRAMFILES>\WinFixer 2005\MMFix.dll".
• The file at "<$PROGRAMFILES>\WinFixer 2005\OEDrop.dll".
• The file at "<$PROGRAMFILES>\WinFixer 2005\sr.exe".
• The file at "<$PROGRAMFILES>\WinFixer 2005\StrRes.dll".
• The file at "<$PROGRAMFILES>\WinFixer 2005\Updater.exe".
• The file at "<$PROGRAMFILES>\WinFixer 2005\WFX5.exe".
• The file at "<$DESKTOP>\WinFixer 2005.lnk".
• The file at "<$LOCALSETTINGS>\Temp\WinFixer2005ScannerSetup.exe".
• The file at "<$SYSDIR>\df_kme.exe".
• The file at "<$SYSDIR>\drivers\df_kmd.sys".

Make sure you set your file manager to display hidden and system files. If WinFixer uses rootkit technologies, use our RootAlyzer or our Total Commander anti-rootkit plugins.
You will have to use a global search for files without a name specified. Be extra careful, because just the name might not be enough to identify files!

Important: There are more files that cannot be safely described in simple words. Please use Spybot-S&D to remove them.

Folders:

Please use Windows Explorer or another file manager of your choice to locate and delete these folders.

• The directory at "<$PROGRAMFILES>\WinFixer 2005".

Make sure you set your file manager to display hidden and system files. If WinFixer uses rootkit technologies, use our RootAlyzer or our Total Commander anti-rootkit plugins.
You will have to use a global search for files without a name specified. Be extra careful, because just the name might not be enough to identify folders!

Registry:

You can use regedit.exe (included in Windows) to locate and delete these registry entries.

• Delete the registry key "ApiMon" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\".
• Delete the registry key "ApiMon" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\".
• Delete the registry key "{AE65FF9D-47BA-9840-D610-4314AD1A6BA4}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{25A3C995-10C8-474B-A167-99460AB4AB2B}" at "HKEY_CLASSES_ROOT\AppID\".
• Delete the registry key "{287A2BAD-6590-4EFF-9BBC-494385664A73}" at "HKEY_CLASSES_ROOT\AppID\".
• Delete the registry key "{290B5B73-4963-4BA1-9D2D-07CB566CB7FA}" at "HKEY_CLASSES_ROOT\AppID\".
• Delete the registry key "{E8928E69-C050-42A9-8884-94DE85E888A2}" at "HKEY_CLASSES_ROOT\AppID\".
• Delete the registry key "compcln.dll" at "HKEY_CLASSES_ROOT\AppID\".
• Delete the registry key "FFWraper.DLL" at "HKEY_CLASSES_ROOT\AppID\".
• Delete the registry key "FixCore.DLL" at "HKEY_CLASSES_ROOT\AppID\".
• Delete the registry key "MMFixCtrl.DLL" at "HKEY_CLASSES_ROOT\AppID\".
• Delete the registry key "{08C71FB1-1E66-4D22-9F32-4C045A451306}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{1CDEB41B-905A-4183-AA20-26E075419B46}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{38EDB9E2-D7C4-4575-8905-FE65414FFEAD}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{48349992-1402-4C67-B45B-2E619E641FDB}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{538BC8F3-2E1E-4D2D-A261-158DF6E9B407}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{53ABACCB-434C-4756-A02B-8C2A3F29FB7D}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{66A9C4D0-BC54-4841-8FAA-DB98CBB77BAD}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{84C43108-013C-4513-8578-F50080B9C9D0}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{9CC1BE04-3B42-4442-9A46-77E8BC1108F9}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{AA69BBFC-1D28-4960-8061-93C1BB156238}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{B096A483-0ABD-4AF0-856A-CAD36145AF5C}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{B5E427F9-AB38-4348-9076-86870C2BE860}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{C0BC364F-AB33-4778-8047-5A2148E0ECDA}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{CAE8A9B1-ABBD-4159-A485-1DA045A5D4A1}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{F41C1430-CFDE-4AD3-B38D-7890F0843E47}" at "HKEY_CLASSES_ROOT\CLSID\".
• A key in HKEY_CLASSES_ROOT\ named "CompCleanCore.AppCleaner", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "CompCleanCore.AppCleaner.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "CompCleanCore.CCQuickScan", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "CompCleanCore.CCQuickScan.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "CompCleanCore.FileCleaner", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "CompCleanCore.FileCleaner.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "CompCleanCore.InetCleaner", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "CompCleanCore.InetCleaner.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "CompCleanCore.RegCleaner", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "CompCleanCore.RegCleaner.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "CompCleanCore.SystemCleaner", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "CompCleanCore.SystemCleaner.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "df_fixer.Fixer", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "df_fixer.Fixer.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "df_proxy.DriverManipulate", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "df_proxy.DriverManipulate.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "FFCom.FlFixer", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "FFWraper.FFEnginWraper", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "FFWraper.FFEnginWraper.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "FixCore.MMFixCore", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "FixCore.MMFixCore.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "MMFixCtrl.CoFixEngine", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "MMFixCtrl.CoFixEngine.1", plus associated values.
• Delete the registry key "{08C71FB1-1E66-4D22-9F32-4C045A451306}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{1CE1C25B-F8B4-4974-99D2-5D4AE96B9900}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{35096C29-3507-4ABE-B6D8-C7CC881BE020}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{38F743A2-210F-49DE-9B79-DCD501CED284}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{3EEC290D-FC13-4C83-803D-4802651EEB61}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{41A5BBF6-3C9D-4CF9-9A99-32DD37CC290B}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{4E4F38D9-8736-41AE-B192-E829AE194398}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{66484903-09F4-4330-927D-1F6C214221AC}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{7FA14AD6-D8E5-465F-9BD1-A37E26C1A74F}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{9E984934-CD94-4763-9DBC-618E483D4B7F}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{B115BD8E-B008-46F4-B8B6-3405EB325C3C}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{B9DFCF32-B679-4CAD-B7FC-518A48CE3922}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{CAE8A9B1-ABBD-4159-A485-1DA045A5D4A1}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{CBEEF194-EBC5-4758-9B51-AC34FC135E70}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{CD3604CC-2B95-43EE-AFC9-E7444C21BE1C}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{D21040FE-0A57-4FAB-8ED2-F0E653E55809}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{D7A2488E-53E4-4EDD-AEAA-F24778BEB100}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{D7A6DF8D-B6CF-4C27-8E99-ECA2CE370EA7}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{F41C1430-CFDE-4AD3-B38D-7890F0843E47}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{F6C1582E-B11C-4724-B8F6-240457EF1D2A}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{FB787D5E-0C7C-4BAB-B45D-20325FB886DB}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{0E9F6AC0-A21A-4591-910F-E2C6F3CA094C}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{4DCEEA42-794D-4855-9ECC-20DCF5F4FEA7}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{6A077841-5016-42C8-92C8-F2D6B865BCD1}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{AD70AC89-F460-4E7E-B5A5-7EAF7E207736}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{B6625280-8CD8-4632-97C0-83CEC12A49A3}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{F458ADAE-D53B-4859-B99F-9FA127791278}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{FC76A5B8-DB35-4F3E-8B9A-BF0EEA098D64}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "df_kmd.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\".
• Delete the registry key "df_kmd.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\".
• References to the file "<$COMMONPROGRAMFILES>\WinSoftware\CrXML.dll" at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls\.

If WinFixer uses rootkit technologies, use our RegAlyzer, RootAlyzer or our Total Commander anti-rootkit plugins.

Final Words:

If neither Spybot-S&D nor self help did resolve the issue or you would prefer one on one help,

1. Please read these instructions before requesting assistance,
2. Then start your own thread in the Malware Removal Forum where a volunteer analyst will advise you as soon as available.