Is Scrubit compatible with other security products?
Yes, with some caveats. Scrubit works perfectly fine with
the active protection of most anti-virus programs. However, we highly
recommend using Repelit™ (realtime badware blocker) as the only threat
monitoring program (instead of process termination programs and active
monitoring by some spyware programs).
Repelit was specifically designed to compliment Scrubit's behavioral design.
If you wish to run a competitors monitoring process, it is recommended to shut
off the competitors monitoring product before running Scrubit. Some products
attempt to monitor in-memory processes and this may fight with one of
Scrubit's filters and can force Scrubit to identify the monitoring program as
badware. If the security product is not safelisted, Scrubit will clean off the
security program. You can restore the security product from Scrub'd
(quarantined items) if a mistake is made.
If you clean a system with these guidelines, Scrubit can co-exist with a
competitor’s product. Please note there are many products posing as FREE
malware (badware) cleaners, if you continue to have problems after following
these guidelines, do not shut off the suspect security product. It could very
well be badware pretending to be a FREE security application. Scrubit will
test it and clean it off, if its behavior tests as bad.
Scrubit compliments definition-based scanning programs, with no modifications.
It is recommended to run Scrubit first before any definition-based scanning
programs. This method allows Scrubit to remove polymorphic and unknown threats
and scanners to clean up any remaining non-running traces of badware listed in
their definitions.
Traces are not active processes, but are left over non-threatening files and
registry entries unable to run. The auto-running badware items which are the
real threats were identified and removed by Scrubit prior to running the
definition-based scanner.
NOTE:
In situations where badware has compromised your existing security products,
you may find that after running Scrubit, they are able to run once again and
update their definitions.
![]()