Unable to register dll using regsvr32

visual-studio-2005 dllregistration
SyncMaster picture SyncMaster · Dec 22, 2010 · Viewed 24.3k times · Source

My project generates a dll and when build in Debug mode the dll gets registered automatically by Visual Studio 2005. But when I try to register the same dll in command prompt using "regsvr32" I'm unable to register. I get the following error,

The module ".." failed to load. Make sure the binary is stored at specified path or debug it to check problems with the binary or dependent .DLL files.

But I have all the dependent dlls in place. What could be the reason for this issue.?

I tried registering and unregistering the dll using the following command,

regsvr32 dll_name.dll

regsvr32 /u dll_name.dll

Answer

WhatEvil picture WhatEvil · Feb 26, 2014

I just had the same issue.

If you're running 64-bit Windows and you've placed the 32-bit DLL in Windows\System32\ then it'll give you this error.

Simply place the DLL into Windows\SysWOW64\ and register it from there.

Here's where I found the fix:

http://csi-windows.com/blog/all/73-windows-64-bit/378-fixing-qregsvr32-the-module-failed-to-load-the-specified-module-could-not-be-foundq

Related questions

Unable to copy file - access to the path is denied

I am using Visual Studio 2005. After taking code from version control first, the c#.net application runs correctly. But, after doing some modifications, when I build I am getting the following error: Error 383 Unable to copy file "..\root\leaf\Bin\…

Read More
How to fix "Referenced assembly does not have a strong name" error?

I've added a weakly named assembly to my Visual Studio 2005 project (which is strongly named). I'm now getting the error: "Referenced assembly 'xxxxxxxx' does not have a strong name" Do I need to sign this third-party assembly?

Read More
The name 'controlname' does not exist in the current context

I have a web application that I'm working on (ASP.NET2.0 with C#, using VS2005). Everything was working fine, and all of a sudden I get the error: Error 1 The name 'Label1' does not exist in the current context …

Read More