6 ms·

I use procmon heavily too. Good point about the mem usage. I find procmon especially helpful for diagnosing COM activation issues; being able to trace all the r

I use procmon heavily too. Good point about the mem usage. I find procmon especially helpful for diagnosing COM activation issues; being able to trace all the registry and file system accesses is invaluable in figuring why a specific DLL is or isn't loaded.

voltagex_ 10y ago
COM activation has eaten a week of mine. Any idea why procmon wouldn't load on a Server 2008 box as Admin? Gives me a driver error.
- j_s 10y ago
  Google says: * reboot * check anti-virus * requires 'Workstation' service * try a different/older version * verify other SysInterals utils can load their driver * extract the 64-bit version and run it directly http://superuser.com/questions/211759/process-monitor-fails-to-load http://superuser.com/questions/211759/process-monitor-fails-... Any further details on the error message?
  - voltagex_ 10y ago
    Unfortunately lowly devs are not allowed access to that particular server, but I'd bet it's the Workstation service. Thanks.
- osullivj 10y ago
  No idea on procmon refusing to load as Admin. But I would caution on using the System account to run services that use COM activation, which does ClassId & ProgId lookups via the HKCU hive. LocalSystem will go to HKCU\.Default [1], which is probably not what you need. [1] https://social.msdn.microsoft.com/Forums/vstudio/en-US/cef6584d-d05e-4510-a7c2-7ab529c303f9/setting-user-registry-keys-hkcu-from-a-local-system-account-service?forum=vcgeneral https://social.msdn.microsoft.com/Forums/vstudio/en-US/cef65...