Rick Brewster Posted October 15, 2007 Share Posted October 15, 2007 The problem is probably simple to figure out with a copy of Process Explorer. While the error dialog is up, right click on the rundll32 process (from within Proc. Exp.) and check out what command-line it was given, and also check out what the parent process is. There. Now you know (1) who started rundll32, and (2) what it's trying to do including what DLL it's probably trying to load and failing at. However, (1) may just say explorer.exe at which point you know it's something being launched at startup. So just jump into msconfig.exe and look for rundll32's. Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Nilks Posted October 17, 2007 Author Share Posted October 17, 2007 The problem is probably simple to figure out with a copy of Process Explorer. While the error dialog is up, right click on the rundll32 process (from within Proc. Exp.) and check out what command-line it was given, and also check out what the parent process is. There. Now you know (1) who started rundll32, and (2) what it's trying to do including what DLL it's probably trying to load and failing at. However, (1) may just say explorer.exe at which point you know it's something being launched at startup. So just jump into msconfig.exe and look for rundll32's. Rick, i am in Process Explorer while the error dialog is up, but i cant find where to look for the command-line it was given og what the parents process is. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.