*** Updated June 14, 2010 ***
It turns out that the Procexp64.exe exists ONLY while Process explorer is running. Don’t ask me why. So my registry entry instead now shows:
Otherwise you still get the “cannot find” message.
*** End June 14, 2010 Update ***
I recently was introduced to Windows’ Process Explorer and liked it enough to want to replace Window’s native task manager with it.
It *should* be as simple as clicking “Options > Replace Task Manager” in the Process Explorer window but then, when you try to invoke the Task Manager (now supposedly Process Explorer) you get a message indicating that
“Windows cannot find ‘C:\Window\System32\taskmgr.exe’. Make sure you typed the name correctly, and then try again.”
For me, going back in Process Explorer to uncheck the above option shows that it’s not checked, and clicking it again doesn’t do anything at all.
Not sure exactly why but what’s happened is that a registry key for task manager has now been created with a debugger key that has a garbage value. Mine showed something like ” ^ $ ^”.
Check it out under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\taskmgr.exe
To go back the way things were you just need to remove the “Debugger” key. Or, if you want to go forward and actually replace the task manager, then set the value of the debug key with the location of your process explorer executable. In my case it looks like “C:\bin\Procexp64.exe” “C:\bin\Procexp.exe”.
Funny, I deleted the debug key and then went back to process explorer and try “Options > Replace Task Manager” again and it works just fine now. Must be an initialization issue.
Posted under Tech Stuff
This post was written by Marc
on June 12, 2010 at 2:10 pm