Manual Removal Guide for ErrorSafe

The following instructions have been created to help you to get rid of "ErrorSafe" 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:

ErrorSafe pretends to be an antivirus programm. It mainly appears in connection with a Smitfraud-C infection and is praised on a blue screen. Having installed the software one has to accept an insufficient Privacy. There is no button to deny this privacy. A scan with ErrorSafe reveals several problems that allegedly need to be removed urgently in order to rescue the computer. At this point the user is requested to buy the whole program for an unacceptable price.

Removal Instructions:

Desktop:

Please remove the following files from your desktop.
To check where they are pointing to, right-click them and choose "Properties" from the context menu appearing.

• Shortcuts named "Error Safe.lnk" and pointing to "<$PROGRAMFILES>\Error Safe Free\ERS.exe".

Autorun:

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

• Entries named "ErrorSafeFree" and pointing to "<$PROGRAMFILES>\ErrorSafe Free\uers.exe /scan".
• Entries named "Error Safe Free" and pointing to "<$PROGRAMFILES>\ErrorSafe Free\uers.exe?/scan".
• Entries named "UERScw" and pointing to "<$PROGRAMFILES>\ErrorSafe Free\UERScw.exe?-c".
• Entries named "Error Safe" and pointing to "?<$PROGRAMFILES>\Error Safe FreeERS.exe? /scan".
• Entries named "drin" and pointing to "*inrh9500.exe".
• Entries named "ErrorSafe" and pointing to "<$PROGRAMFILES>\ErrorSafe\ers.exe /scan".

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 "UERSU_is1".
• Products that have a key or property named "ErrorSafe Additional Feature".
• Products that have a key or property named "UERS_is1".

Files:

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

• The file at "<$PROGRAMFILES>\ErrorSafe Free\dcres.sys".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\wsres.sys".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\activate.dat".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\appupdate.dat".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\bnlink.dat".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\DataBase.sav".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\dcres.sys".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\EmtERSF.exe".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\ESSPChck.dll".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\flash.ini".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\FlFxr15.dll".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\FRec.dll".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\FWraper.dll".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\FxCore.dll".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\InstHelp.exe".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\lapv.dat".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\license.rtf".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\lock.dat".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\MMFx.dll".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\Program.sav".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\pv.dat".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\resource.xml".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\sr.log".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\support.url".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\uers.exe".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\uers.url".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\UERScw.exe".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\unins000.dat".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\unins000.exe".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\up.dat".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\updater.dat".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\Updater.exe".
• The file at "<$PROGRAMFILES>\ErrorSafe Free\wsres.sys".
• The file at "<$DESKTOP>\Error Safe.lnk".
• The file at "<$LOCALSETTINGS>\Temp\ErrorSafeScannerSetup.exe".
• The file at "<$LOCALSETTINGS>\Temp\ICD3.tmp\UERSU_9999_N91S2009NetInstaller.exe".
• The file at "<$LOCALSETTINGS>\Temp\ICD3.tmp\UERSU_9999_N91S2009NetInstaller.inf".
• The file at "<$LOCALSETTINGS>\Temp\NI.UERSU_9999_N91S2009\settings.ini".
• The file at "<$WINDIR>\Downloaded Program Files\UERSU_9999_N91S2009NetInstaller.exe".
• The file at "<$LOCALSETTINGS>\TempNI.UERSU_0001_N91M2407\settings.ini".
• The file at "<$LOCALSETTINGS>Temp\NI.UERSU_0001_N91M2407\setup.exe".
• The file at "<$LOCALSETTINGS>Temp\NI.UERSU_0001_N91M2407\setup.len".
• A file with an unknown location named "ErrorSafeScannerInstallDE.cab".
• A file with an unknown location named "ERS.exe".
• A file with an unknown location named "esPCheck.dll".
• A file with an unknown location named "FFWraper.dll".
• A file with an unknown location named "FlFxr5.dll".
• A file with an unknown location named "FTRec.dll".
• A file with an unknown location named "Install.exe".
• A file with an unknown location named "sr.exe".
• A file with an unknown location named "StrRes.dll".
• The file at "<$LOCALSETTINGS>\Temp\~ErrorSafeScannerSetup.exe".

Make sure you set your file manager to display hidden and system files. If ErrorSafe 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>\ErrorSafe Free\Download".
• The directory at "<$PROGRAMFILES>\ErrorSafe Free".
• The directory at "<$PROGRAMFILES>\ErrorSafe Free\Backup".
• The directory at "<$PROGRAMFILES>\ErrorSafe Free\Mp3DB".
• The directory at "<$PROGRAMFILES>\ErrorSafe Free\MpegDB".
• The directory at "<$PROGRAMFILES>\ErrorSafe Free\Repaired".
• The directory at "<$PROGRAMFILES>\ErrorSafe Free\Tasks".
• The directory at "<$PROGRAMFILES>\ErrorSafe Free\WaveDB".
• The directory at "<$LOCALSETTINGS>\Temp\NI.UERSU_9999_N91S2009".
• The directory at "<$COMMONPROGRAMS>\ErrorSafe".
• The directory at "<$PROGRAMFILES>\ErrorSafe".
• The directory at "<$PROGRAMFILES>\ErrorSafe\Backup".
• The directory at "<$PROGRAMFILES>\ErrorSafe\Mp3DB".
• The directory at "<$PROGRAMFILES>\ErrorSafe\MpegDB".
• The directory at "<$PROGRAMFILES>\ErrorSafe\Repaired".
• The directory at "<$PROGRAMFILES>\ErrorSafe\Tasks".
• The directory at "<$PROGRAMFILES>\ErrorSafe\WaveDB".

Make sure you set your file manager to display hidden and system files. If ErrorSafe 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!

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

Registry:

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

• A key in HKEY_CLASSES_ROOT\ named "Sb6.StrangeBho", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "Sb6.StrangeBho.1", plus associated values.
• Delete the registry key "{3ED808D8-9119-4757-B7BE-40C463452F87}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{580EB069-9905-4A04-A20C-AD6598D8C0A3}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{55149956-1A81-44F8-A00A-F9CF7CA03329}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{0B9B7B2E-30E3-4C5D-AD2C-C38724979B4B}" at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects\".
• Delete the registry key "ErrorSafe" at "HKEY_CURRENT_USER\Software\".
• Delete the registry key "{0BA379C6-0EFD-4a28-932C-D20469052FD9}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{0BC09FC7-473D-4f9c-B49B-F4E3E244B47A}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{196C80CB-20A7-4cf9-9C98-9322FB1E35FB}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{1E6CE4CD-161B-4847-B8BF-E2EF72299D69}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{24834631-B8A4-4B39-9466-DEFD2FB0F3A2}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{356AF2E9-8874-4c60-A3D8-0CB516C9E747}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{35BA68DA-A9F5-4374-8B97-1183D93846A4}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{51F2E6BE-22EF-40D3-AEB0-E6E20DF78FB8}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{5284AC2A-EF00-4750-9B82-B5B907D26536}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{5E19DEE2-8D2F-4a9c-A66D-76BBEEDD15CB}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{6AE7418B-229F-4A2C-AE1B-D5962888F02D}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{77CA442A-0C72-492b-804A-82611E558142}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{7E73C9DB-69FB-4580-8E8E-194B34A2306C}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{8815A3DB-0C23-4200-84DF-D49EBDDED63A}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{965A8D33-AE18-4c17-8011-FE42D81E0758}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{C033567C-68FE-419b-BCC4-135DB7FAF8EB}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{C85A4AFD-FF76-4661-B76A-3E9BB2CE2DAB}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{E73E3959-FB15-44d7-ACB9-3A75377006FC}" at "HKEY_CLASSES_ROOT\CLSID\".
• A key in HKEY_CLASSES_ROOT\ named "ESCompCleanCore.ESAppCleaner", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESCompCleanCore.ESAppCleaner.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESCompCleanCore.ESCCQuickScan", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESCompCleanCore.ESCCQuickScan.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESCompCleanCore.ESFileCleaner", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESCompCleanCore.ESFileCleaner.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESCompCleanCore.ESInetCleaner", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESCompCleanCore.ESInetCleaner.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESCompCleanCore.ESRegCleaner", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESCompCleanCore.ESRegCleaner.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESCompCleanCore.ESSystemCleaner", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESCompCleanCore.ESSystemCleaner.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESdf_fixer.ESFixer", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESdf_fixer.ESFixer.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESdf_proxy.ESDriverManipulate", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESdf_proxy.ESDriverManipulate.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESFFWraper.ESFFEnginWraper", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESFFWraper.ESFFEnginWraper.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESFixCore.ESMMFixCore", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESFixCore.ESMMFixCore.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESMMFixCtrl.ESCoFixEngine", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESMMFixCtrl.ESCoFixEngine.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESSPCheck.ESSPCheck", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "ESSPCheck.ESSPCheck.1", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "FlFxr5.FlFixer5", plus associated values.
• A key in HKEY_CLASSES_ROOT\ named "newhttpsibdll6screener.CBrowserHelper", plus associated values.
• Delete the registry key "{04392304-5221-4022-9300-BE4128FB25B2}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{14A5F3E7-B235-4D98-9264-5C67D2657BC4}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{49F9FFB5-514D-4B69-B31D-2AE5A7D30AE6}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{68BC55E9-4D3E-4C89-89AC-7559763C98B8}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{692CA430-32C8-470D-BA1F-7E15E21E7043}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{6BD7E052-306E-497A-AD23-601BC6BFC305}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{77DC6558-60E0-4644-A3DF-B31F29D113BD}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{9DD86CF2-8AC0-4FE0-B55A-601A302B5FD8}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{A73973AB-95A6-4ABE-A046-DE3BAB2BE448}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "ErrorSafe" at "HKEY_LOCAL_MACHINE\SOFTWARE\".
• Delete the registry key "drsmartload" at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\".
• Delete the registry key "ERSU_is1" at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\".
• Delete the registry key "erssdd.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Minimal\".
• Delete the registry key "erssdd.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Network\".
• Delete the registry key "erssdd" at "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\".
• Delete the registry key "erssdd.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\".
• Delete the registry key "erssdd.sys" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\".
• Delete the registry key "erssdd" at "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\".

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

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

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.