Need help with help errors lol

Protagonist. · Post by **Protagonist.** » Sun Jan 22, 2006 1:48 pm

I am getting the following error whenever I try to run diskeeper, services.msc, device manager, etc.

And I have done the exact same thing as I did with 2.01 update pack. Same nLite preset file and what not. Only thing I did differently was integrate the latest versions of the addons I use. So that is what leads me to believe it is something with the pack itself that changed.

Also here is my setuperr.log report.

Error:
Setup could not register the OLE Control C:\WINDOWS\system32\mmcndmgr.dll because of the following error:
LoadLibrary returned error 126 (the specified module could not be found).

***

I don't know if this is a compatibility issue or why it only occurs in this update pack. But anyways could someone please upload their apphelp.dll file so that I can see if that fixes the error?
Thanks

Post by **5eraph** » Sun Jan 22, 2006 1:57 pm

Known issue with Diskeeper 10. Known issue with XPize 4.2 beta2.

These occur due to the update from MMC2 to MMC3 in RVMUPv2.0.2a.

Protagonist. · Post by **Protagonist.** » Sun Jan 22, 2006 3:24 pm

Did you even read my post? This is not related to the diskeeper 10 problem or the xpize problem...

Post by **RyanVM** » Sun Jan 22, 2006 3:33 pm

Have you reproduced this problem when integrating with only the integrator like this post tells you to?

Protagonist. · Post by **Protagonist.** » Sun Jan 22, 2006 4:01 pm

I don't have time, this is my main system. Could you please spare your apphelp.dll or advise some way to fix? I can't even access device manager to install my drivers.

edit: I got apphelp.dll and put it in system32 but now the error is the class is not registered. I did regsvr32 apphelp.dll and it said "DllRegisterServer entry point was not found".

Am I doing this correctly?

Post by **5eraph** » Sun Jan 22, 2006 4:14 pm

Did you try to copy and register apphelp.dll in system32?

Protagonist. · Post by **Protagonist.** » Sun Jan 22, 2006 4:23 pm

Yea I tried that, see above.

Post by **5eraph** » Sun Jan 22, 2006 4:30 pm

Does mmcndmgr.dll exist in system32? If not you could try pulling the file out of RVMUPv2.0.2a and registering that first.

Failing that, you could try getting the very recently refreshed MMC3 (RC1) update from Microsoft's Download Center and installing it.

@RyanVM: I wasn't aware you started putting betas and release candidates into your Update Pack.

Protagonist. · Post by **Protagonist.** » Sun Jan 22, 2006 5:58 pm

Seraph, thanks for your help. and if it seemed like I snapped at you earlier I'm sorry lol

Fortunately mmcndmgr.dll I did find in system32 and when I tried to register it is suceeded and now I can access device manager and everything.

I'm still a bit worried though. Trying to register apphelp.dll before I got two blue screens. I haven't had a blue screen of death in like 2 years.

Post by **RyanVM** » Sun Jan 22, 2006 6:30 pm

5eraph wrote:Does mmcndmgr.dll exist in system32? If not you could try pulling the file out of RVMUPv2.0.2a and registering that first.

Failing that, you could try getting the very recently refreshed MMC3 (RC1) update from Microsoft's Download Center and installing it.

@RyanVM: I wasn't aware you started putting betas and release candidates into your Update Pack.

I didn't. It went final with Windows Server 2003 R2.

Post by **5eraph** » Sun Jan 22, 2006 11:38 pm

I went re-reading and researching and you're right. MMC3 is Pre-Release, but it is the final. You're definitely on top of things with this 0-day update.

On a weird note: Just how common is the letter combination "re?" It appears in this post eight times. Four in the first sentence alone.

dgelwin · Post by **dgelwin** » Mon Jan 23, 2006 12:35 am

isnt there a sticky at the top of this thread that explains what causes this error?

Post by **5eraph** » Mon Jan 23, 2006 12:46 am

The sticky describes only one of the conflicts with MMC3 (XPize). A second can be found in the 2.0.2a announcement (DK10). nLite is now a confirmed third conflict, depending on its usage I suppose.

Protagonist. · Post by **Protagonist.** » Mon Jan 23, 2006 1:58 am

dgelwin wrote:isnt there a sticky at the top of this thread that explains what causes this error?

no! lol

Why do people keep pointing me to the stickies, I already read them. This doesn't apply because the problem happened during windows setup. Before I would even have time to install diskeeper or xpize lol.

For some reason that one thing failed to register, you can see in my setuperr.log above. I have no idea why that happened. I started over fresh and redid everything and the same thing happened. I even took off most of the nlite options. Dunno what the deal is.

Siginet · Post by **Siginet** » Mon Jan 23, 2006 3:18 am

Well... we will have a hard time helping you if you do not have the time.
There obviously isn't much to indicate it is an error with the updatepack... or we would have the same bug posted everywhere. Try the same thing without useing NLite. Sorry... but we can't do much if you aren't willing to help us help you.

Darknite · Post by **Darknite** » Tue Jan 24, 2006 5:19 am

Protagonist. wrote:
dgelwin wrote:isnt there a sticky at the top of this thread that explains what causes this error?
no! lol

Why do people keep pointing me to the stickies, I already read them. This doesn't apply because the problem happened during windows setup. Before I would even have time to install diskeeper or xpize lol.

For some reason that one thing failed to register, you can see in my setuperr.log above. I have no idea why that happened. I started over fresh and redid everything and the same thing happened. I even took off most of the nlite options. Dunno what the deal is.

I had the same thing(see post here). all you need to do is add apphelp.dll to the keep box.

Post by **5eraph** » Tue Jan 24, 2006 5:32 am

Thanks for the linkage, Darknite. Maybe this conflict can be made sticky as well since nLite is still commonly used to integrate the Update Pack.

Summary:

nLite 1.0 RC5 users who remove Internet Explorer or other components from their source should add apphelp.dll to the keep box within nLite when integrating RVMUPv2.0.2a due to a possible MMC3 IE dependency to prevent problems with Device Manager.

[/thread]

Post by **RyanVM** » Tue Jan 24, 2006 9:55 am

Sure, I'll make note of that. Is that a confirmed fix?

Post by **5eraph** » Tue Jan 24, 2006 9:58 am

It was tested by shaggy in nuhi's forum, but MSFN is on the blink.

Protagonist. · Post by **Protagonist.** » Tue Jan 24, 2006 4:07 pm

I did not remove IE or any IE components...

Darknite · Post by **Darknite** » Tue Jan 24, 2006 4:49 pm

RyanVM wrote:Sure, I'll make note of that. Is that a confirmed fix?

Yes its mate if you use nlite but i dont no what takes the dll out.

@Protagonist
same here, take a look at my last session.ini in the post.