Troubleshooting Regsvr32 Error 0x80004005

Until software vendors get totally Vista compatible, having to manually register DLL files is going to be a pretty common task. Here is how to troubleshooting one of the most common errors received while doing this.

A common sight when trying to get older software to work with Windows Vista is having to manually register DLL/OCX files using Regsvr32. There has been countless times where I have been working along in a piece of software and then all of a sudden it gives me an error about a DLL that it can’t access. The typical response to this is to run regsvr32 dllname.dll to register the DLL.

Occasionally, I run into Error 0x80004005 when registering these files. This error sounds highly complicated, but what it all boils down to is a rights issue. This error basically means that you don’t have the permissions to register the file you are trying to register.

This usually brings about the questions, “Wait! I’m logged in as an administrator?!”

Under previous versions of Windows, being logged in as an administrator is enough, but in Windows Vista there is a little thing called User Account Control (UAC) that prevents programs from running administrative tasks without first specifying that they are running as the administrator. This applies for the command prompt the same as it does for any other program.

This being the case, right-click on the command prompt icon, and select “Run as Administrator”, and then try to register your DLL. This is a mistake that is usually frustrating enough that, once you figure it out, you won’t make too often.



**

Comments

Popular posts from this blog

VMware PSOD Purple Screen of Death - Debugger waiting (world 2078) -- no port for remote debugger. "Escape" for local debugger

The Windows Time Service terminated with the following error - Event ID 7023 & 46

IBM x3650 M4 Series Server Model - Activation Keys Backup to be taken for IMM Moduel II, why?