Re: Stuck on "Checking for the latest updates for your computer...

Tech-Archive recommends: Fix windows errors by optimizing your registry


--
Everything that can brake down - brakes down, everything that can`t - brakes
down either.


"Robert Aldwinckle" wrote:

"Tempest" <Tempest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E5267F1C-0EFC-4C66-90CD-4D208FB28E2A@xxxxxxxxxxxxxxxx
Hey, thanks for the help,

I cannot seem to register one of the DLL's

regsvr32 qmgr.dll

it dosent seem to work, it gives me:

qmgr.dll was loaded, but the DllRegisterServer entry point was not found.
The file cannot be registered

Any other thoughts ??????


What version of that module do you have?

Tip: you can use DependencyWalker to check both the properties
of that module and whether there is an external entry point of
DllRegisterServer in it.

If you do have the right version of the module and it does appear
to have that entry point a possible explanation for your symptom
would be that the error message is bogus and represents an attempt
to explain a different unexpected symptom.

To test that idea you can also use DependencyWalker,
using its profiler tool. In this case what you would do is
get it to execute the regsvr32.exe command with the operand(s)
that you were using. It will then generate a trace of modules and
intermediate return codes. Somewhere in there before the line
you see with the prompt for the error message would be a better
clue for why you can't register that module. E.g. perhaps there
is a permissions problem, missing module, unregistered dependent
module, etc.

Oh. One more thing. Is BITS running? It would already be using
that module if it was and that could perhaps prevent the module from
being re-registered while it was in use. It would probably be a good
idea to stop BITS before trying the regsvr32 command.

After you stop BITS you can check (from a cmd window)
if any other task is using that module with:

tasklist /fi "Modules eq qmgr.dll"

I just did that and that's how I reminded myself about BITS
because what that turned up was this:

<example>
Image Name PID Session Name Session# Mem Usage
========================= ====== ================ ======== ============
svchost.exe 860 Console 0 8,804 K
</example>

Then using the PID from that result I found

<example>
tasklist /svc /fi "PID eq 860"

Image Name PID Services
========================= ====== =============================================
svchost.exe 860 AudioSrv, BITS, Browser, CryptSvc, Dhcp,
....
</example>


An alternative diagnostic/repair would be to use bitsadmin's
new options under the /util category:


<extract>

/UTIL /VERSION [/VERBOSE]
Displays the version of BITS currently active on the system.
The switch /VERBOSE prints additional information useful for
troubleshooting purposes.

/UTIL /REPAIRSERVICE [/FORCE]
Attempts to repair a malfunctioning BITS service by inspecting some of the
service configuration settings. The switch /FORCE indicates that the BITS
service should be deleted and re-created if repairing the settings does not
clear the errors in starting the BITS service. Use this command with caution
as it is not possible to revert the changes.

</extract>


Note: I have never tried the /RepairService option
and I have never seen a report from anybody trying it either.
You could be a trailblazer... <w>


Good luck

Robert Aldwinckle
---





I had the same problem - and i were battling it for the last 4-5 hours. For
me, none of the solutions i have found, worked. And i have just figured it
out - this whole thing is only due to one reason - windowsupdate activex
searches not only for software updates, but also for hardware updates as well
(drivers & etc.) The solution that helped me out - is after i have updated my
video driver (intel integrated) - everything began working, all of a sudden.
So i do believe that the problem is that windowsupdate activex incorrectly
handles certain driver definitions, and due to that the whole process "hangs"
.

Relevant Pages