Well, you don't specify if it's a 32 or 64 bit dll and you don't include the error message, but I'll guess that it's the same issue as described in this KB article: Quote from that article: This behavior occurs because the Regsvr32.exe file in the System32 folder is a 64-bit version. When you run Regsvr32 to register a DLL, you are using the 64-bit version by default. Solution from that article: To resolve this issue, run Regsvr32.exe from the%SystemRoot% Syswow64 folder. For example, type the following commands to register the DLL: cd windows syswow64 regsvr32 c: filename.dll. If the DLL is 32 bit: Copy the DLL to C: Windows SysWoW64 In an elevated command prompt:%windir% SysWoW64 regsvr32.exe%windir% SysWoW64 namedll.dll if the DLL is 64 bit: Copy the DLL to C: Windows System32 In an elevated command prompt:%windir% System32 regsvr32.exe%windir% System32 namedll.dll I know it seems the wrong way round, but that's the way it works. See: Quote: 'Note On a 64-bit version of a Windows operating system, there are two versions of the Regsv32.exe file: The 64-bit version is%systemroot% System32 regsvr32.exe. Oracle webcenter content download. The 32-bit version is%systemroot% SysWoW64 regsvr32.exe. On a x64 system, system32 is for 64 bit and syswow64 is for 32 bit (not the other way around as stated in another answer). WOW (Windows on Windows) is the 32 bit subsystem that runs under the 64 bit subsystem). It's a mess in naming terms, and serves only to confuse, but that's the way it is. Syswow64 is 32 bit, NOT 64 bit. System32 is 64 bit, NOT 32 bit. There is a regsrv32 in each of these directories. One is 64 bit, and the other is 32 bit. It is the same deal with odbcad32 and et al. (If you want to see 32-bit drivers which won't show up with the default odbcad32 in system32 which is 64-bit.). Knowing the error message would be rather valuable. It is meant to provide info, even though it doesn't make any sense to you it does to us. Being forced to guess, I'd say that the DLL is a 32-bit DirectX filter. In which case this should be the proper course of action: cd c: windows syswow64 move. System32 dllname.ax. Regsvr32.exe dllname.ax This must be run at an elevated command prompt so that UAC cannot stop the registry access that's required. Ask more questions about this at superuser.com. Feb 11, 2010 - I have a Dell Studio Laptop that has 64-bit version of Windows Vista on it. The module Ole32.dll was loaded but the call to DllRegisterServer failed with error code 0x80070005. Last updated November 28, 2018 Views 10,997 Applies to. Account profile Download Center Sales & support Returns. Downloads Last Month: 8674. Operating System: Windows Linux MacOs. Download File. User Reviews. (BPL) T20 will be held on Thursday (20 December 2012) at Utshab Banquet Hall, Regsvr32 ole32 dll failed Blu Water Garden Hotel, Dhaka. Canon EOS 7D Mark II Spec List borno 3 weeks ago Mailman88 scottrade download talking babies a troll. I just tested this extremely simple method and it works perfectly--but I use the built-in Administrator account, so I don't have to jump through hoops for elevated privileges. The following batch file relieves the user of the need to move files in/out of system folders. It also leaves it up to Windows to apply the proper version of Regsvr32. INSTRUCTIONS: • In the folder that contains the library (.dll or.ax) file you wish to register, open a new text file and paste in ONE of the routines below: echo BEGIN DRAG-AND-DROP%n1 REGISTRAR FOR 64-BIT SYSTEMS copy%1 C: Windows System32 regsvr32 '%nx1' echo END BATCH FILE pause echo BEGIN DRAG-AND-DROP%n1 REGISTRAR FOR 32-BIT SYSTEMS copy%1 C: Windows SysWOW64 regsvr32 '%nx1' echo END BATCH FILE pause • Save your new text file as a batch (.bat) file; then simply drag-and-drop your.dll or.ax file on top of the batch file. • If UAC doesn't give you the opportunity to run the batch file as an Administrator, you may need to manually elevate privileges (instructions are for Windows 7): • Right-click on the batch file; • Select Create shortcut; • Right-click on the shortcut; • Select Properties; • Click the Compatibility tab; • Check the box labeled Run this program as administrator; • Drag-and-drop your.dll or.ax file on top of the new shortcut instead of the batch file. I chose COPY instead of MOVE to prevent the failure of any UAC-related follow-up attempt(s). Successful registration should be followed by deletion of the original library (.dll or.ax ) file. Don't worry about copies made to the system folder ( C: Windows System32 or C: Windows SysWOW64 ) by previous passes--they will be overwritten every time you run the batch file. Unless you ran the wrong batch file, in which case you will probably want to delete the copy made to the wrong system folder ( C: Windows System32 or C: Windows SysWOW64) before running the proper batch file.or. • Help Windows choose the right library file to register by fully-qualifying its directory location.
0 Comments
Leave a Reply. |