- Seeing the DLLRegisterserver failed error implies that the DLL file could not be registered.
- To start fixing this the entry point DLLRegisterserver was not found error, you have to edit permissions for the TypeLib registry key.
- You can also disable the antivirus utilities to make sure you resolve the conflict with regsvr32.
- Another solution is to edit registers. To make sure you don't do anything wrong, check the correct steps in the guide below.
DLLRegisterserver failed errors can arise on various Windows platforms. They arise when users try to register DLL or OCX files with the regsvr32 command-line utility.
These are two examples of DLLRegisterserver failed error messages:
The module <file> was loaded but the call to DLLRegisterServer failed with error code 0x8002801c.
The module <file> was loaded but the call to DLLRegisterServer failed with error code 0x80070005.
Those regsvr32 error messages are very similar, albeit with different codes. So, the fixes for those DLLRegisterserver failed errors are much the same.
If you need to fix one of the above, or similar, DLLRegisterserver errors, check out these resolutions.
What to do if the DLLRegisterserver was not found?
1. Open an elevated Command Prompt
- DLLRegisterster failed errors often arise when users aren’t utilizing regsvr32 within an elevated Command Prompt. Press the Windows key + S hotkey.
- Type Command Prompt in the text box to search for it.
- Right-click Command Prompt to select a Run as administrator option for it, which will open an elevated Prompt window.
- Try registering the OCX or DLL file within the elevated Command Prompt.
2. Copy the OCX into the SysWow64 folder
- If the DLLRegisterserver error arises for an OCX file, try copying that file into the SysWow64 folder. To do so, open File Explorer.
- Open this folder in File Explorer:
- Type OCX file the DLLRegisterserver error arises for in the search box.
- Right-click the OCX file found, and select Copy.
- Then open the Windows, and select the SysWow64 folder.
- Right-click an empty space within the SysWow64 folder, and select Paste.
- Open an elevated Command Prompt as outlined for resolution one.
- Run the regsvr32 command for the OCX file you pasted into the SysWow64 folder.
3. Edit the registry
- Adjusting permissions for the TypeLib registry key might also fix your DLLRegisterserver error. To do so, press the Windows key and R at the same time.
- To open the Registry Editor, type regedit in Run and click OK.
- Open this registry key:
- Right-click TypeLib, and select Permissions.
- Select your user account on the Security tab if it’s listed.
- Click the Full Control option for your account if it’s not selected.
- If your user account isn’t listed, click the Add button. Then enter your user account title.
- Make sure Full Control/Allow is selected for the newly added user account.
- Select the Apply option.
- Click OK to exit the window.
4. Disable third-party antivirus utilities
Third-party antivirus utilities can also conflict with regsvr32. So, try disabling third-party antivirus software before running a regsvr32 registration command.
To do that, right-click the system tray icon for your antivirus software to open a context menu. You can usually select a disable option of some kind on most antivirus utilities’ context menus.
Select to disable the antivirus software for about 30 minutes to an hour if you can, and then check if the problem still occurs.
The above fixes can resolve the DLLRegisterserver 0x8002801c and 0x80070005 errors. Just remember that you always need admin rights to utilize the regsvr32 command-line utility for registering system files.
Which of the above solutions did you use? Leave us your answer and other suggested solutions in the comment section below.
Frequently Asked Questions
To get a precise answer, check out our detailed fix guide to resolve the error 0x80020009, and solve it in no time.
This error is caused by the fact that the file doesn’t have a DllRegisterServer. To see this for yourself, run the command dumpbin /exports comdlg32.dll.
You can paste a into the System32 folder the same way you would any other file. Also, if you encounter a System32.exe failure error in Windows 10, fix it no time with our help.