Flamer Removal Tool Log

rue_east

I'm wondering if someone could give me some insight into these findings for the FLAMER removal tool, here is attached a log

ERROR: Could not open file: C:\windows\system32\LogFiles\WMI\RtBackup\

HIDDEN: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTDiagLog.etl

ERROR: Could not scan file: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTDiagLog.etl

HIDDEN: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTEventLog-Application.etl

ERROR: Could not scan file: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTEventLog-Application.etl

HIDDEN: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTEventlog-Security.etl

ERROR: Could not scan file: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTEventlog-Security.etl

HIDDEN: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTEventLog-System.etl

ERROR: Could not scan file: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTEventLog-System.etl

HIDDEN: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTMsMpPsSession7.etl

ERROR: Could not scan file: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTMsMpPsSession7.etl

HIDDEN: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTUBPM.etl

ERROR: Could not scan file: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTUBPM.etl

HIDDEN: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTWDC.BE95A9B1-DE15-4B78-B923-A12AB70BE951.etl

ERROR: Could not scan file: C:\windows\system32\LogFiles\WMI\RtBackup\EtwRTWDC.BE95A9B1-DE15-4B78-B923-A12AB70BE951.etl

ERROR: Could not scan file: C:\windows\system32\catroot2\edb.log

ERROR: Could not scan file: C:\windows\system32\catroot2\{127D0A1D-4EF2-11D1-8608-00C04FC295EE}\catdb

ERROR: Could not scan file: C:\windows\system32\catroot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb

ERROR: Could not scan file: C:\windows\system32\config\COMPONENTS

ERROR: Could not scan file: C:\windows\system32\config\COMPONENTS.LOG1

ERROR: Could not scan file: C:\windows\system32\config\COMPONENTS.LOG2

ERROR: Could not scan file: C:\windows\system32\config\DEFAULT

ERROR: Could not scan file: C:\windows\system32\config\DEFAULT.LOG1

ERROR: Could not scan file: C:\windows\system32\config\DEFAULT.LOG2

ERROR: Could not scan file: C:\windows\system32\config\RegBack\DEFAULT

ERROR: Could not scan file: C:\windows\system32\config\RegBack\SAM

ERROR: Could not scan file: C:\windows\system32\config\RegBack\SECURITY

ERROR: Could not scan file: C:\windows\system32\config\RegBack\SOFTWARE

ERROR: Could not scan file: C:\windows\system32\config\RegBack\SYSTEM

ERROR: Could not scan file: C:\windows\system32\config\SAM

ERROR: Could not scan file: C:\windows\system32\config\SAM.LOG1

ERROR: Could not scan file: C:\windows\system32\config\SAM.LOG2

ERROR: Could not scan file: C:\windows\system32\config\SECURITY

ERROR: Could not scan file: C:\windows\system32\config\SECURITY.LOG1

ERROR: Could not scan file: C:\windows\system32\config\SECURITY.LOG2

ERROR: Could not scan file: C:\windows\system32\config\SOFTWARE

ERROR: Could not scan file: C:\windows\system32\config\SOFTWARE.LOG1

ERROR: Could not scan file: C:\windows\system32\config\SOFTWARE.LOG2

ERROR: Could not scan file: C:\windows\system32\config\SYSTEM

ERROR: Could not scan file: C:\windows\system32\config\SYSTEM.LOG1

ERROR: Could not scan file: C:\windows\system32\config\SYSTEM.LOG2

ERROR: Path does not exist: `

ERROR: Could not scan file: C:\windows\system32\Microsoft\Protect\Recovery\Recovery.dat

ERROR: Could not scan file: C:\windows\system32\Microsoft\Protect\Recovery\Recovery.dat.LOG1

ERROR: Could not scan file: C:\windows\system32\Microsoft\Protect\Recovery\Recovery.dat.LOG2

ERROR: Could not scan file: C:\windows\system32\Microsoft\Protect\Recovery\Recovery.dat{7ddbc2d4-b2e3-11e1-939f-9cb70d2fb3f8}.TM.blf

ERROR: Could not scan file: C:\windows\system32\Microsoft\Protect\Recovery\Recovery.dat{7ddbc2d4-b2e3-11e1-939f-9cb70d2fb3f8}.TMContainer00000000000000000001.regtrans-ms

ERROR: Could not scan file: C:\windows\system32\Microsoft\Protect\Recovery\Recovery.dat{7ddbc2d4-b2e3-11e1-939f-9cb70d2fb3f8}.TMContainer00000000000000000002.regtrans-ms

Anything to be worried about? The catroot2 entries are suspicious.

rootkit

Hello

Welcome to the forums!

Those entries appear in the log because they can not be scanned as the operating system is using those resources.

Anyway, if the malware is detected in the system, is not located in those folders.

Do you have Bitdefender installed? If not, would you like to try it for free for 3 months?

Take care.