Problem registering a '.dll' with Command Prompt

Question

I'm trying to register a '.dll' file (ntdll.dll) with Command Prompt.

Whenever I enter the command 'regsvr32 ntdll.dll' in command prompt, I get the error:

'The module "ntdll.dll" was loaded but the entry-point DllRegisterServer was not found. Make sure that "ntdll.dll" is a valid DLL OR OCX file and then try again later.'

How can I fix it?

Answer 1

Just because a file has a .dll extension doesn't mean it is registerable (sorry Microsoft engaged Support Engineer "experts").

If the DLL does not have inside it the DllRegisterServer() (and also DllUnRegisterServer()) functions the regsvr32 program does not know what to do with it - it does not make sense to register it so hence the error message:

the entry-point DllRegisterServer was not found

It was not found because it is not inside the DLL you are trying to register.

Once it was suggested that the message should be changed to something like:

"Why are you trying to register this DLL? It's an ordinary Windows DLL, there's nothing to be registered"

You can use something like DLL Export Viewer and search to see if you can find DllRegisterServer anywhere in that file (and you won't) then the "expert" can explain why they suggested the idea in the first place.

Repeat the process on a DLL that is regsiterable like jscript.dll and you WILL find those functions inside so therefore the jscript.dll file is registerable - no error message there.

So if somebody gives you advice to register ntdll.dll you immediately know a few things:

1.  They don't know what they are talking about

2.  They have not recreated your issue themselves and solved it by registering the ntdll.dll file

3.  They have not attempted their own advice to register ntdll.dll on their own system to see what happens or they would know it doesn't work

Instead of referring you to another topic with more impossible to work advice, what Microsoft engaged Support Engineer "expert" Jayant Gupta should to is take 10 seconds and see what happens whey they try to register the ntdll.dll file on their own system and when they see that it doesn't work don't suggest that you do it because it isn't going to work for you either.

Then when it doesn't work explain why it doesn't work and give you a solution for how to register ntdll.dll but that will never happen because it is impossible.

What you should do about your problem with AC3SP.EXE is look out in the UBI or Steam community where your error message is discussed and not follow the impossible to work advice from the Microsoft engaged Support Engineer "expert" to register a DLL that is impossible to register.

Now you have multiple Microsoft engaged Support Engineer "experts" giving you impossible to work advice - register the ntdll.dll file...  it just won't work.

This advice from the "experts" will not magically make the ntdll.dll file registerable::

Register the ntdll.dll (impossible)

sfc  /scannow  (not the problem = I have no idea what the problem is or how to fix it)

Clean boot (will not make the missing function magically appear in ntdll.dll)

New User Account (will not make the missing function magically appear in ntdll.dll).

How will any of those things make a missing function appear in ntdll.dll?

How much time have you wasted on that advice from the "expert"?

The error you see for AC3SP.exe "The procedure entry point RtlUnsubscribeWnfStateChangeNotification" means that AC3SP3.exe is looking inside the ntdll.dll file looking for that function called RtlUnsubscribeWnfStateChangeNotification and not finding it (and it is not there on Windows 7 32-but at least):

So you have a mismatch of files somewhere, you have the wrong or incompatible version of AC3P3 installed or are missing some Windows update where that function is in the ntdll.dll file (and I don't know what that is).

Answer 2

Hi Sarvesh,

As per the description, you are trying to register a “.dll” file (ntdll.dll) using command prompt and getting error message: The module “ntdll.dll” was loaded but the entry-point DllRegister Server was not found. Make sure that “ntddll.dll” is a valid Dll or OCX file and then try again later on the system.

I certainly understand your concern.

I would suggest you to refer to the suggestions provided by “Shivam Kesarwani” replied on October 1, 2014 in the following Microsoft Community link given below and check if that helps.

http://answers.microsoft.com/en-us/windows/forum/windows\_7-performance/how-to-register-dll-and-ocx-files/0b2af90d-7c65-4fae-9303-d557e9faa9e8

I hope this information is helpful.

Please do let us know if you need any further assistance, we will be glad to assist you.

Thank you.

Answer 3

Thank you for the information.