I’m running into this exact same issue. It happens every time I use ProcMon even once during a Windows session. I did some digging to find out why the 'restart your PC' suggestion is often the only fix.
Even after closing the app, the PROCMON24 driver stays resident in the kernel. I tried manually unloading it via fltmc unload, but it fails with error 0x801f0010. As shown in my screenshots, Process Explorer reveals that the System process (PID 4) is holding a handle on ProcmonExternalLoggerEnabled.
This means the driver is essentially 'trapped' by the OS, and the user has no way to clear it without a reboot. The Anti-Cheat should recognize when the driver is dormant and the tool isn't actually active.
