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 a 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 dll file
3. They have not attempted their own advice to register 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 "expert" should do is take 10 seconds and see what happens when they try to register the 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 dll but that will never happen because it is impossible.
What you should do about
your problem is look out in the community where your error message is discussed and not follow the impossible to work advice from the "expert" to register a DLL that is impossible to register.
Now you have multiple "experts" giving you impossible to work advice - register the dll file... it just won't work.
This advice from the "experts" will not magically make the dll file registerable::
Register the 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 dll)
New User Account (will not make the missing function magically appear in .dll).
How will any of those things make a missing function appear in .dll?
How much time have you wasted on that advice from the "expert"?