rundll32.exe problem
Wednesday, November 11, 2009 by Richard Mohler | Discussion: Personal Computing
I noticed my dx meters quit working and noticed also in task mgr. that it doesn't list rundll32.exe anywhere. It used to but now it's gone. I tried DesktopX beta update and had nothing but troubles so I uninstalled it and put it back like it was only now rundll32.exe isn't in task mgr. anywhere. Any suggestions? When I got update to DesktopX I'd click on desktop and it said windows explorer quit working and I think that's when it disappeared from task mgr, anyway thanks for any help..
Reply #2 Wednesday, November 11, 2009 9:08 PM
yea it's rundll32.exe, I fixed it in post.. I'll try sme stuff & see what happens, thanks..
Reply #3 Wednesday, November 11, 2009 9:41 PM
executing rundll32.exe in and of itself will do nothing. Rundll32.exe is responsible for running dll's and placing their processes in memory. there are many things that can and will run under this.
Reply #4 Wednesday, November 11, 2009 10:38 PM
I don't think it's a problem with the rundll32.exe because on my mom's laptop it doesn't list any in task mgr. and I downloaded a DX gadget to it and cpu meter & memory meter worked fine.
Reply #5 Friday, November 13, 2009 4:53 PM
I think your problem may be more related with WMI. Which gadget are you attempting to run and on what OS?
Mike
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
Reply #1 Wednesday, November 11, 2009 8:41 PM
Hey Rich, I looked in my Task Manager and found rundll32.exe listed but not Run32.dll. Could it be that it's rundll32.exe? If so, try to restart it manually by typing the nmae of the .exe in New Task. If that doesn't work? You may have a corrupted system 32 .dll. I found this quick fix for it if you can:
Maybe someone else has another suggestion or better advise than I do...