An entry in one of your event logs should indicate what the problem is. Download ProcMon from Unzip ProcessMonitor.zip Copy ProcMon. Here are some easy steps for starting, stopping, and saving a Procmon capture. Do you see procmon.exe appear briefly, then go red and/or disappear? If so, then “something” is preventing it from running and is killing it. ProcMon is an indispensable tool that zillions of people have used. Launch Process Monitor while carefully watching the other part of the screen. Procmon64.exe File Path: C:SysinternalsSuiteProcmon64. I can run Process Monitor under Windows 7 圆4 with no problems, and as suggested it does spawn a procmon64.exe process.ĭo you also have Process Explorer? Does it work? If not then Task Manager will do, but try splitting your screen so that you can run Process Explorer (or Task Manager) in one part, and have the command where you try to launch Process Monitor in the other part. This is an issue for those of us that have Software Restriction Policies in place that prevent executions from TEMP. Could also be the dreaded UAC getting in the way, so check your settings. The default behavior of Procmon on a 64 bit system seems to be that it extracts Procmon64 to TEMP then runs it from there. If you do not see your own user name in the list, add it in and give it “Full control”. The user (or group) that you are running under needs to have “Full control”. Process Monitor will tell you all the processes that are active on the system and which files they are accessing or linked to. Using Windows Explorer or similar, navigate to the executable file (I would guess C:Program FilesProcess MonitorProcmon.exe), right-click on it, then Properties, then Security. If you do not see the “Do you want to run” message when you run it as administrator, that suggests a security issue.
0 kommentar(er)
