Securom detects Filemon and won’t run

This seems almost offensive.  I purchased a game and happened to have run Filemon within the time since I last rebooted my PC (usually measured in months).  Now it demands I reboot my machine before it will allow me to run the software I've purchased.

Anyway - thought Mark or the other guys at Sysinternals may be interested in knowing they've been directly targetted by Securom and their customers are being harmed as a result.

Sorry for the duplicate post in that case.

No issue with Process Monitor at the moment, but you can bet they'll have it in the next update of their software.  I just hate the assumption that people who use these sorts of tools are "hackers".  If anything, it drives the more sophisticated users away from endorsing their products and finding ways to remove the offensive code.

Originally posted by Karlchen Thanks for reporting this issue: Securom refuses to run if it sees the Filemon/Regmon drivers in memory. (Guess it is their type of tamper protection.) By the way, it has been reported before: Filemon vs TR:Legend’s SecuROM

As mentioned in the refered to thread, even after Filemon is exited, Secrom is detecting something in memory that Filemon leaves behind.

Is Filemon perhaps leaving a file handle/thread/mutex/whatever behind and not cleaning up after itself?

This is a real annoying "feature" of Securom. According to Securom, the "fix" for this "error message" of theirs is to run their "System Analysis" program that probes your system and produces a very large, encrypted "analysis file" that you are supposed to e-mail to them.