- Apr 5, 2015
- 3
I believe the above information may be sufficient, particularly the log, in resolving any issues I think I may have. However, if not..
The original infection was Pro Optimizer and I believed MBAM had cleaned it. During this reinfection, I have found there is a dll still within the source folder(c:\program files (x86)\pro optimizer 3.56\abc.dll). I was able to rename the file abc.dll through the standard rename option, but unable to rename in command prompt with disabled explorer.exe. It is also resistant to being deleted via both options, and claims to be running via "pro optimizer crash manager", which I am unable to locate anywhere on the system.
Reinfection began as ads on Netflix, and was sourced to adware and a plugin for Firefox. MBAM scanned and quarantined, plugin deleted, restart, then another threat scan. MBAM read clean.
If any questions on processes or programs that you may be unaware of, as many are directly linked to games and game servers, I'll respond as quickly as I can.
Thank you for your time!
The original infection was Pro Optimizer and I believed MBAM had cleaned it. During this reinfection, I have found there is a dll still within the source folder(c:\program files (x86)\pro optimizer 3.56\abc.dll). I was able to rename the file abc.dll through the standard rename option, but unable to rename in command prompt with disabled explorer.exe. It is also resistant to being deleted via both options, and claims to be running via "pro optimizer crash manager", which I am unable to locate anywhere on the system.
Reinfection began as ads on Netflix, and was sourced to adware and a plugin for Firefox. MBAM scanned and quarantined, plugin deleted, restart, then another threat scan. MBAM read clean.
If any questions on processes or programs that you may be unaware of, as many are directly linked to games and game servers, I'll respond as quickly as I can.
Thank you for your time!