clipped from forum.sysinternals.comProblems with PE ...
How do I see my Task Manager again??? Please read How do I see my Task Manager again???. |
(In short, delete the key [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\taskmgr.exe].)
Well.... I deleted the key you told me but still as i want to start PE
"Sysinternals Process Explorer has occurred a problem and has to be closed. We are sorry about the inconvenience. " (I have another lang O/S
Check the Application and System event logs in the Event Viewer (start -> run -> eventvwr -> OK).
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 70 72 6f ure pro
0018: 63 65 78 70 2e 65 78 65 cexp.exe
0020: 20 31 31 2e 32 31 2e 30 11.21.0
0028: 2e 30 20 69 6e 20 70 72 .0 in pr
0030: 6f 63 65 78 70 2e 65 78 ocexp.ex
0038: 65 20 31 31 2e 32 31 2e e 11.21.
0040: 30 2e 30 20 61 74 20 6f 0.0 at o
0048: 66 66 73 65 74 20 30 30 ffset 00
0050: 30 31 37 35 64 30 0d 0a 0175d0..
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 70 72 6f ure pro
0018: 63 65 78 70 2e 65 78 65 cexp.exe
0020: 20 31 31 2e 32 31 2e 30 11.21.0
0028: 2e 30 20 69 6e 20 70 72 .0 in pr
0030: 6f 63 65 78 70 2e 65 78 ocexp.ex
0038: 65 20 31 31 2e 32 31 2e e 11.21.
0040: 30 2e 30 20 61 74 20 6f 0.0 at o
0048: 66 66 73 65 74 20 30 30 ffset 00
0050: 30 31 37 35 64 30 0d 0a 0175d0..
and it tells me that the error is an application error and the adress is
0x000175d0...
| 0x000175d0 |
That's helpful.
First, exit PE, and then try executing the following commands from a CMD prompt:
unlodctr .NETFramework
unlodctr .NETFramework
lodctr c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\corperfmonsymbols.ini
lodctr c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\corperfmonsymbols.ini
unlodctr .NETFramework
lodctr c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\corperfmonsymbols.ini
Thank you very much!!! 
Now PE finally works! :) I suggest putting this topic in the F.A.Q so it can help other people with this strange error
Again, Thank you very much for your help I really appreciate that
Parts of the problem are in the FAQ. The particular crash address that is related to the problem will generally change for each version of procexp.exe. And this specific solution is not always guaranteed to solve the problem; sometimes, one must resort to uninstalling / reinstalling / repairing installations of the .NET Framework. But yes - the particular FAQ item relating to this certainly could use some augmentation.
Get Clipmarks - The easiest way to email text, images and videos you find on the web.
No comments:
Post a Comment