I recently downloaded the procmon tool. I've noticed that after stopping it a subsequent attempt to run a privileged program gets an error dialog saying that a system monitor is running and to remove it. This prevents the privileged program execution. Rebooting cures the problem. The two times that I've run procmon, this has happened. Has anyone else seen this behavior?
📎 AI Summary:
A user reports that running and then closing Procmon causes an error when launching privileged programs, suggesting a lingering system monitor or driver remains. Despite others' assurances that Procmon's driver unloads upon exit, the user observes persistent issues and suspects residual kernel-mode components, possibly impacting certain applications like PokerTracker. The discussion highlights uncertainty about whether the problem originates from Procmon or specific software interactions, with some evidence pointing to lingering drivers detected by security tools.
A user reports that running and then closing Procmon causes an error when launching privileged programs, suggesting a lingering system monitor or driver remains. Despite others' assurances that Procmon's driver unloads upon exit, the user observes persistent issues and suspects residual kernel-mode components, possibly impacting certain applications like PokerTracker. The discussion highlights uncertainty about whether the problem originates from Procmon or specific software interactions, with some evidence pointing to lingering drivers detected by security tools.
Solution
Ok. Another data point. I tried running a different program requesting privilege and didn't get the error dialog. So there must be something about the program itself (PokerTracker) that is generating this error. So unless you play poker, you're not likely to encounter this, I suspect. I will report this to the PokerTracker developers and see what they say.
I will experiment a little further. It has occurred to me that perhaps I clicked the "X" to close it rather than using its "exit" function. This could possibly result in procmon not cleaning up as it should. I will post results after I try this.
Ok. Another data point. I tried running a different program requesting privilege and didn't get the error dialog. So there must be something about the program itself (PokerTracker) that is generating this error. So unless you play poker, you're not likely to encounter this, I suspect. I will report this to the PokerTracker developers and see what they say.
Searching the internet has provided other users with similar problems. According to some reports, these tools load a "kernel mode driver" which remains after the program (in this case procmon) exits. WinLicense is apparently a tool used by some developers to manage their software distributions. It apparently detects this driver somehow. I'm not sure who should fix this.
Similar threads
- Replies
- 2
- Views
- 496
- Article
- Replies
- 0
- Views
- 5K
- Replies
- 1
- Views
- 1K
- Replies
- 0
- Views
- 580
- Replies
- 1
- Views
- 4K