What is dpupdchk.exe and Why Is It Running?
You are no doubt reading this article because you are wondering what on earth that dpupdchk.exe process is doing in your Task Manager window… there’s no description and it just keeps coming back. So what is it anyway?
In case you aren’t sure what we’re talking about, if you sort by “Image Name” you might see something similar to the screenshot below. And that’s what we’ll be explaining to you today.
So What Is It Anyway?
This process is some type of automatic update checker from Microsoft IntelliPoint (as far as we can tell), but here’s how we actually diagnosed it…
First, if you are using Vista you can right-click on the process and choose to Open File Location.
…which will open up the containing folder, so you can drill down into exactly what the file is by looking at the properties. Unfortunately, this process just has zero information in the properties dialog… shame on you, Microsoft!
Further investigation led me into the registry, and by using the Process Monitor utility from Sysinternals I was able to determine that the process was querying a registry key named “Intellipoint Pro Auto Update”… a clear giveaway that this process has to do with updating of some type.
Then there’s also the fact that in the start menu is a shortcut using a similar icon that says Check for Updates. It’s one of those special shortcuts that you can’t see the target for… one has to wonder why they bothered to make this so complicated.
Dear Microsoft: If you are reading this article, perhaps you might leave a comment and shed some light on what it’s really doing. Then you might want to start learning how to document things.
How Do I Get Rid of It?
Keep in mind that removing pieces of Microsoft software without fully understanding what they are is probably a bad idea and shouldn’t be attempted by anybody under any circumstances ever, even slightly, probably.
Now that the disclaimer is out of the way… here’s where we stand: You can take one of two routes to get rid of it:
- Uninstall IntelliPoint in Control Panel (losing extra mouse functionality)
- Replace the dpupdchk.exe file with a dummy file that does nothing.
A dummy file, you say? Whatever for?
The problem is that if you delete the dpupdchk.exe file, every single time you open the mouse panel you will get horrible errors. Since we like to avoid horrible errors, I’ve created a dummy executable that does nothing at all, which you can replace the current one with.
First, browse down to the following folder (adjusting if necessary for your install path).
C:\Program Files\Microsoft IntelliPoint
Now rename the existing dpupdchk.exe file to something else (using the handy Take Ownership script if necessary to gain access).
![image[5]](http://www.howtogeek.com/wp-content/uploads/2009/03/image51.png "image[5]")
Once you’ve renamed that file, replace it with this fake dpupdchk.exe file created by the fine folks here at How-To Geek. It’s a blank executable that does nothing, but feel free to scan it with at least 74 anti-virus engines if you’d like to make sure.
And thus ends the tale of the phantom dpupdchk process. But what about svchost.exe, jusched.exe, or dwm.exe? The journey continues!
Daily Email Updates
You can get our how-to articles in your inbox each day for free. Just enter your name and email below:
My email adress is confidential thanks.
I use XP Home with Service Pack 3.
After having the above problem once I installed an update (from FileHippo) for my Intellipoint mouse, I was fed up that “dpupdchek” running for no apparent purpose and using system resources. I uninstalled the mouse software entirely, (the mouse still worked but with less functionality), then I reinstalled the original driver that came with it and all is well again. I won’t be updating it in the future since it works just fine with the original driver, “dpupdchek” is now gone from my Task Manager window, and there are no security concerns whatsoever that I can determine. Other than Microsoft’s update (dpupdchek – which did nothing whatsoever to enhance useability, it just checked for software updates constantly), it really is a very good mouse.
I am using a logitech mouse, and do not find this process running in Task Manager. Apparently, installation of the logitech driver removed it automatically, if it was ever there. No problems with the logitech mouse, so I guess dpupdchek was not essential to anything in the OS.
Hey Spacegold, this article is about Microsoft Mice, not Logitech Mice. The Logitech mice have a similar process that continually checks for updates, but I disabled mine to not have useless tasks running.
Good article though, I’m going to have to use on my parent’s computer. They have a “Microsoft Wireless Laser Mouse 7000″, which is NOT a good mouse imo.
(Using anonymous email)
The solution is *much* less complex and is even provided by Microsoft. I currently use IntelliPoint / IntelliType 6.3 on Vista 64-bit but previously used it on XP 32-bit as well. On installation of either Intelli product, a shortcut is provided in the start menu named “Quality Settings”. This points to “qs.exe” in the IntelliPoint / IntelliType folder in Program Files. It is the same binary for both but takes a command line: “/DISPLAY_TYPE SETTING /PRODUCT_TYPE IP” for mouse and “/DISPLAY_TYPE SETTING /PRODUCT_TYPE ITP” for keyboard. This launches a dialog that lets you check for updates and opt in/out of automatically checking, or to join the customer experience improvement program. In the mentioned registry key “Intellipoint Intellitype Pro Auto Update”, the DWORD auKeyboardNeverShowAgain changes from 0 (automatically check=YES) to 1 (automatically check=NO) for keyboard; or same for auMouseNeverShowAgain for mouse. On system startup when “itype.exe” or “ipoint.exe” are loaded, “dpupdchk.exe” is loaded; it checks the au*NeverShowAgain settings and if both are 1 then it unloads. It’s that simple.
Using Vista Home Basic fought this for a long time. Finally after unchecking “hide system files and folders” in folder options was able to find the program. Renamed it dupupchkold.exe and inserted the dummy file.Good job Geek. Thanks
Paul and I used the same solution. Since there is a directly way to disable this process, I would recommend that you follow this method. Replacing files with dummy files can lead to further headaches and just isn’t worth it in this case.