Stuck on "Checking for the latest updates for your computer..." sc

HI,

Im trying toupdate my windows XP, and when i go into the site it first asked
me to install the new updateing software, and that was fine, then it takes me
to a page where it asks me to choose expess or custom, after i click on
either button, it says "Checking for the latest updates for your computer..."
and the little progress bar with the green boxes keep sliding back and forth
for over 6 hours when i left it over night, but it just does not progress any
further ??????

Any thoughts ???

you may need to re-registered some files:

1. Click Start.
2. Choose Run.
3. In the Run box, type (pressing okay after each one) :-

net stop wuauserv

Repeat for the following:
regsvr32 wuapi.dll
regsvr32 wups.dll
regsvr32 wuaueng.dll
regsvr32 wuaueng1.dll
regsvr32 wucltui.dll
regsvr32 wuweb.dll
regsvr32 MSXML3.dll
regsvr32 qmgr.dll
regsvr32 qmgrprxy.dll
regsvr32 jscript.dll

net start wuauserv



"Tempest" wrote:

> HI,
>
> Im trying toupdate my windows XP, and when i go into the site it first asked
> me to install the new updateing software, and that was fine, then it takes me
> to a page where it asks me to choose expess or custom, after i click on
> either button, it says "Checking for the latest updates for your computer..."
> and the little progress bar with the green boxes keep sliding back and forth
> for over 6 hours when i left it over night, but it just does not progress any
> further ??????
>
> Any thoughts ???

"TaurArian" wrote:

> you may need to re-registered some files:
>
> 1. Click Start.
> 2. Choose Run.
> 3. In the Run box, type (pressing okay after each one) :-
>
> net stop wuauserv
>
> Repeat for the following:
> regsvr32 wuapi.dll
> regsvr32 wups.dll
> regsvr32 wuaueng.dll
> regsvr32 wuaueng1.dll
> regsvr32 wucltui.dll
> regsvr32 wuweb.dll
> regsvr32 MSXML3.dll
> regsvr32 qmgr.dll
> regsvr32 qmgrprxy.dll
> regsvr32 jscript.dll
>
> net start wuauserv
>

I'm having exactly the same problem on two W2K servers (both running SQL
Server, incidentally), and I tried this and it still doesn't work. Also
tried reinstalling the windows update agent, which won't install as it's
already present. Installing from WSUS server also fails -- it will download
updates, just won't install them. Any ideas?

thanks,
Casper.

Why not try the WSUS Newsgroup

http://www.microsoft.com/technet/com...pdate_services


"Casper Gasper" wrote:

> >
> I'm having exactly the same problem on two W2K servers (both running SQL
> Server, incidentally), and I tried this and it still doesn't work. Also
> tried reinstalling the windows update agent, which won't install as it's
> already present. Installing from WSUS server also fails -- it will download
> updates, just won't install them. Any ideas?
>
> thanks,
> Casper.

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 ??????

"Casper Gasper" wrote:

> "TaurArian" wrote:
>
> > you may need to re-registered some files:
> >
> > 1. Click Start.
> > 2. Choose Run.
> > 3. In the Run box, type (pressing okay after each one) :-
> >
> > net stop wuauserv
> >
> > Repeat for the following:
> > regsvr32 wuapi.dll
> > regsvr32 wups.dll
> > regsvr32 wuaueng.dll
> > regsvr32 wuaueng1.dll
> > regsvr32 wucltui.dll
> > regsvr32 wuweb.dll
> > regsvr32 MSXML3.dll
> > regsvr32 qmgr.dll
> > regsvr32 qmgrprxy.dll
> > regsvr32 jscript.dll
> >
> > net start wuauserv
> >
>
> I'm having exactly the same problem on two W2K servers (both running SQL
> Server, incidentally), and I tried this and it still doesn't work. Also
> tried reinstalling the windows update agent, which won't install as it's
> already present. Installing from WSUS server also fails -- it will download
> updates, just won't install them. Any ideas?
>
> thanks,
> Casper.

Try using the full path:
regsvr32 C:\windows\System32\qmgr.dll


"Tempest" wrote:

> 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 ??????
>
> "Casper Gasper" wrote:
>
> > "TaurArian" wrote:
> >
> > > you may need to re-registered some files:
> > >
> > > 1. Click Start.
> > > 2. Choose Run.
> > > 3. In the Run box, type (pressing okay after each one) :-
> > >
> > > net stop wuauserv
> > >
> > > Repeat for the following:
> > > regsvr32 wuapi.dll
> > > regsvr32 wups.dll
> > > regsvr32 wuaueng.dll
> > > regsvr32 wuaueng1.dll
> > > regsvr32 wucltui.dll
> > > regsvr32 wuweb.dll
> > > regsvr32 MSXML3.dll
> > > regsvr32 qmgr.dll
> > > regsvr32 qmgrprxy.dll
> > > regsvr32 jscript.dll
> > >
> > > net start wuauserv
> > >
> >
> > I'm having exactly the same problem on two W2K servers (both running SQL
> > Server, incidentally), and I tried this and it still doesn't work. Also
> > tried reinstalling the windows update agent, which won't install as it's
> > already present. Installing from WSUS server also fails -- it will download
> > updates, just won't install them. Any ideas?
> >
> > thanks,
> > Casper.

"Tempest" <> wrote in message
news:E5267F1C-0EFC-4C66-90CD-...
> 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
---

"Robert Aldwinckle" wrote:

> "Tempest" <> wrote in message
> news:E5267F1C-0EFC-4C66-90CD-...
> > 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
> ---
>
>
>

All this is real nice, and it's great to see folks trying to help one
another. I REALLY wish I had something to offer to help troubleshoot or
resolve this problem, but alas, it's beyond me.... at this point in time.

BUT, speaking of points, I have one that everyone everywhere seems to be
overlooking. I haven't yet figured out whether it's overlooked because people
are used to sloppy programming, whether they EXPECT shoddy service, or they
really don't care how MS treats their customers after they already have their
money.

The fact of the matter is that THIS issue should never have existed. It is
purely the result of sloppy progamming and said programming is directly
related to Micro$oft's overzealous efforts to curb piracy. They're willing to
F**K every legitimate user of their software to pursue the (maybe) 2% who
have illegal copies. At $179 per copy of XP Pro, my own feeling is that THAT
cost is figured in..... so what it amounts to is MS is rendering our systems
useless (at least temporarily, while they make us run 100% CPU), all so they
can squeeze a dime until it sh**s pennies. WAY TO GO UNCLE BILL!!!!

You're one terrific geek, pal, but your marketing and PR really sucks.
Betcha we can find a law firm to do a class action suit. Doesn't matter to me
that I'll never see a dime.... I just want M$ and all their shareholders to
pay for being idiots.

If you're gonna be dumb, you better be tough.

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


"Robert Aldwinckle" wrote:

> "Tempest" <> wrote in message
> news:E5267F1C-0EFC-4C66-90CD-...
> > 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"

I fixed this problem twice by repairing boot record. Boot on cd R for repair
and type fixboot. I didn't try fixmbr.