Sysinternals Homepage
Forum Home Forum Home > Sysinternals Utilities > Process Explorer
  New Posts New Posts RSS Feed: crashes on startup
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

crashes on startup

 Post Reply Post Reply Page  123 5>
Author
Message Reverse Sort Order
Karlchen View Drop Down
Senior Member
Senior Member
Avatar

Joined: 18 June 2005
Location: Germany
Online Status: Offline
Posts: 5121
Post Options Post Options   Quote Karlchen Quote  Post ReplyReply Direct Link To This Post Topic: crashes on startup
    Posted: 12 May 2007 at 6:54am
Originally posted by KaKTy3

Redownloading and reinstalling .NET framework [...] fixed it. [...] this should defintely be added to the FAQ.

Finally added:
17. Proccess Explorer won’t start... (.NET Framework Issue)

Karl
Back to Top
KaKTy3 View Drop Down
Newbie
Newbie


Joined: 21 April 2007
Online Status: Offline
Posts: 2
Post Options Post Options   Quote KaKTy3 Quote  Post ReplyReply Direct Link To This Post Posted: 22 April 2007 at 9:43am
Originally posted by molotov

Have you tried exiting PE, renaming / removing [HKEY_CURRENT_USER\Software\Sysinternals\Process Explorer], and restarting PE?

I should have mentioned I have tried that already as it was suggested earlier on in the thread.

Originally posted by molotov

 
Another thing that has helped for others is to repair installations of the .NET Framework on the affected system.

U R A STAR! Wink Redownloading and reinstalling .NET framework as per http://support.microsoft.com/kb/306160 fixed it. I have done both repairs sequentially, so cannot confirm whether it's v1.1 or v2.0 of the .NET framework that was the culprit, but this should defintely be added to the FAQ.

Thanks again! :)
Back to Top
molotov View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 October 2006
Online Status: Offline
Posts: 17492
Post Options Post Options   Quote molotov Quote  Post ReplyReply Direct Link To This Post Posted: 22 April 2007 at 9:06am
Have you tried exiting PE, renaming / removing [HKEY_CURRENT_USER\Software\Sysinternals\Process Explorer], and restarting PE?
 
Another thing that has helped for others is to repair installations of the .NET Framework on the affected system.
 
If neither of those work, you could try running PE from WinDbg or Dependency Walker to try to get more information about the crash.
Daily affirmation:
net helpmsg 4006
Back to Top
KaKTy3 View Drop Down
Newbie
Newbie


Joined: 21 April 2007
Online Status: Offline
Posts: 2
Post Options Post Options   Quote KaKTy3 Quote  Post ReplyReply Direct Link To This Post Posted: 21 April 2007 at 5:20pm
Hi,

I've decided to try Process Explorer after reading about it in one of the IT blogs, but unfortunately I am having the same problem as the original poster: the latest version (10.x) crashes on startup. That is using Windows XP SP3 on AMD Athlon XP 3700+ system.

Now, my PATH environment variable is fine (PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;), and I can't seem to get any drwtsn32.log created when it crashes (I've tried re-enabling Dr Watson with "drwtsn32 -i" command).

Is there anything else in your toolbox, guys? Many thanks!
Back to Top
iceburg View Drop Down
Newbie
Newbie


Joined: 23 November 2005
Online Status: Offline
Posts: 2
Post Options Post Options   Quote iceburg Quote  Post ReplyReply Direct Link To This Post Posted: 22 January 2006 at 11:56am
Thank you, Thank you, Thank you!! I had been following this thread for a while, then gave up. I returned today and re-read the entire thread, installed the debugging tools and symbols (unneccessary!)and just like kees continued to recieve the same error message. I ran dskchk and also got the same results as kees. Finally I reached the end of the thread and changed my environmental variables. They were set to Java something or other(don't know how), but once set to the ones you suggested "bam!" procexp is up and running! I hope at some point I can contribute to this forum.
Thanks guys!
Question: Should I uninstall the debugger tools and symbols?
thanks, Iceburg
Back to Top
Karlchen View Drop Down
Senior Member
Senior Member
Avatar

Joined: 18 June 2005
Location: Germany
Online Status: Offline
Posts: 5121
Post Options Post Options   Quote Karlchen Quote  Post ReplyReply Direct Link To This Post Posted: 23 December 2005 at 4:39pm
Incorrect assumption:

You may not have entered a set path=... or path ... statement since DOS days.

Yet, of course, the PATH environment variable has always been there, on all Windows systems. Only, starting with NT it moved from autoexec.bat to the registry.

But you might have seen and modified it as described by thks. And some setup programmes will certainly have changed the systemwide PATH variable.

CU and Merry XMas,
Karl
Back to Top
kees779 View Drop Down
Newbie
Newbie


Joined: 19 November 2005
Online Status: Offline
Posts: 18
Post Options Post Options   Quote kees779 Quote  Post ReplyReply Direct Link To This Post Posted: 23 December 2005 at 1:16am
Thanks for the replies. I have my path back. Still not a clue why it dissapeared in the first place though. I havent used PATH since DOS...
Back to Top
thks View Drop Down
Newbie
Newbie


Joined: 22 December 2005
Online Status: Offline
Posts: 1
Post Options Post Options   Quote thks Quote  Post ReplyReply Direct Link To This Post Posted: 22 December 2005 at 8:21pm
Same problem here.

I figure out why my ENVIRONMENT VARIABLE changed. I installed ActiveState Perl and it modified it. When I check my ENVIRONMENT VARIABLE, all that was there was PATH=C:\Perl\bin

now my Path=C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S ystem32\Wbem

Thanks......
-------
So, to fix:

Start>Setting>Control Panel>System>Advanced>Environment Variables

Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem


Back to Top
Karlchen View Drop Down
Senior Member
Senior Member
Avatar

Joined: 18 June 2005
Location: Germany
Online Status: Offline
Posts: 5121
Post Options Post Options   Quote Karlchen Quote  Post ReplyReply Direct Link To This Post Posted: 20 December 2005 at 1:45pm
Confirmed. Same on my machine (WinXP Prof Sp1), so it must be correct.

Karl

Edited by Karlchen
Back to Top
namrehto View Drop Down
Senior Member
Senior Member


Joined: 23 June 2005
Location: Scotland
Online Status: Offline
Posts: 3861
Post Options Post Options   Quote namrehto Quote  Post ReplyReply Direct Link To This Post Posted: 20 December 2005 at 12:37pm
Try Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Gil
Back to Top
 Post Reply Post Reply Page  123 5>

Forum Jump Forum Permissions View Drop Down