However, the service will also report "NOT_STOPPABLE" and will refuse any stop attempts.Īdditionally, PROCMON23 now registers itself as a filesystem minifilter driver through the Filter Manager (FltDrv). It is possible to manually re-add the service, with type 2 (kernel FS driver) and it will immediately show up as already running. You can see this by monitoring ProcMon with itself. In earlier Process Monitor versions (probably pre-2.3, when it still had Windows XP support), it would install a "legacy" device driver that was visible via sc, Device Manager, etc.Ĭurrent versions of Process Monitor appear to remove the driver/service configuration from registry immediately after starting the driver. (For example, take a look at sc query beep – stopping the 'beep' driver is a common way to shut up the internal PC speaker.) Standard drivers are services and you can indeed control them via net and sc. My question is about unloading the driver without rebooting. My question is not a duplicate of this question, which is about a similar issue where the driver persists after a reboot. I can't delete the driver file, as it's not actually present on the filesystem ProcMon stores the file in its executable and extracts it as needed. I've also tried looking in Device Manager and enabling 'Show hidden devices', but none of the entries appear related to ProcMon. Several other questions have answers about unloading drivers using net stop or sc stop, but the ProcMon driver isn't a service, so this doesn't work. The driver remains loaded after closing Process Monitor, and there doesn't appear to be an option to have it unload. Some of these games use BattlEye anti-cheat software, which refuses to allow the game to run after Process Monitor has been started on the system, showing this in the log: 08:06:46: Starting BattlEye Service.Ġ8:07:07: Disallowed driver: "\?\C:\Windows\system32\Drivers\PROCMON23.SYS".
I sometimes use Process Monitor for debugging software, and also play games online.
0 kommentar(er)
