Re: Error Message: 0x8024D007 as of 04/05/2009 - present
- From: gregzhrh <gregzhrh@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 22 Apr 2009 16:46:06 -0700
Dell Green OS CD's, XP SP3
I have attempted the /wuforce switch after stopping BITS and WU/AU
No prompt for reboot
We disable Windows Firewall as part of GP, and as I mentioned I do not
install AV software until after all Microsoft Updates are complete.
I don't personally understand why it is looking at those specific URL's
either and I can't help but wonder if that is part of the problem.
"MowGreen" wrote:
gregzhrh wrote:.
No anti-virus software installed on any of these PC's until Microsoft updates
are complete so to eliminate that possibility.
Intial installations are being done from CD with full format to the hard
drive during the CD setup process.
When trying to manually install latest version of WU Agent, with or without
"/wuforce" switch, returns same error (0x8024D007)
Are these XP RTM CD's ? If not, what is their SP level ?
Have you attempted to install the WUA from a Command Prompt with the
/wuforce switch after stopping the WU and BITS services ?
BITS is set to Manual by Default but it may have been started in this
situation -
net stop wuauserv
net stop bits
Was there ever a prompt to reboot after AU attempted to install the WUA?
If there is infact a permission issue, which I have also thought might be
occuring somewhere in the background, where would it be happening, and why
would a fresh batch of PC's work for a few hours last night with updates, and
then a clean installation the next day fail.
The fastest way to determine where a possible Perm issue is occurring is
to run Process Monitor. But, unless there's a firewall issue happening
here since there's no security software involved, there *should* not be
any Perm issues.
0x8024D007 WU_E_SETUP_REGISTRATION_FAILED is usually associated with
incomplete downloads and/or Perm issues, or missing files [0x80070002],
or interference by sec software [0x80070005].
Since I have no system to compare logs with due to the manual install of
the WUA vs. automatic installs done via AU, the URL shown in the WU.log
for the source of the .cab files is puzzling for an XP system:
http://download.windowsupdate.com/v8/windowsupdate/b/selfupdate/WSUS3/x86/Other
Also, the error seems to occur on PC's even without a CD installation. We
have tried just taking a Dell out of the box, pre-loaded with XP Pro, and
begin to run updates, same failure. We have also tried using our RIS server,
with an image of XP Pro SP3, drivers added for the specific machine, same
error when attempting to run updates. How could I trace/track down the
permission problem details?
Suggest you take a freshly installed system that is *not* connected to
the net, transfer the WUA to it, then manually run install from a
Command Prompt using /wuforce after stopping the AU service, and then
reboot, just to see what happens.
MowGreen
==============
*-343-* FDNY
Never Forgotten
===============
- Follow-Ups:
- Re: Error Message: 0x8024D007 as of 04/05/2009 - present
- From: MowGreen
- Re: Error Message: 0x8024D007 as of 04/05/2009 - present
- References:
- Error Message: 0x8024D007 as of 04/05/2009 - present
- From: gregzhrh
- Re: Error Message: 0x8024D007 as of 04/05/2009 - present
- From: MowGreen
- Re: Error Message: 0x8024D007 as of 04/05/2009 - present
- From: gregzhrh
- Re: Error Message: 0x8024D007 as of 04/05/2009 - present
- From: MowGreen
- Error Message: 0x8024D007 as of 04/05/2009 - present
- Prev by Date: Re: Net framework 1.1 service pack 1
- Next by Date: Re: KB956572 fails to install on SBS 2003 server
- Previous by thread: Re: Error Message: 0x8024D007 as of 04/05/2009 - present
- Next by thread: Re: Error Message: 0x8024D007 as of 04/05/2009 - present
- Index(es):
Relevant Pages
|
