New Winupdate v5

The "new and improved" windows updates is a nightmare!
We have mostlt winXP pro workstations.Automatic updates do
not work at our site since changing from v4 to v5. Always
get the 0x800A0046 error, no matter what. Tried
Knowledgebase article 883821 Method 1 and 2, no success
and Method 3 does not work/unable to test as the darn
policy isnt there and cant find out how to get it in the
policy list.

Anyone have an idea what I can do to fix this?
I see win2003 server still uses v4 update, not v5, just
hope they don't switch because not being able to update
pc's or servers are a nightmare with all the security
loopholes found in Windows OS's.

Morne wrote:

> The "new and improved" windows updates is a nightmare!
> We have mostlt winXP pro workstations.Automatic updates do
> not work at our site since changing from v4 to v5. Always
> get the 0x800A0046 error, no matter what. Tried
> Knowledgebase article 883821 Method 1 and 2, no success
> and Method 3 does not work/unable to test as the darn
> policy isnt there and cant find out how to get it in the
> policy list.
>
> Anyone have an idea what I can do to fix this?
> I see win2003 server still uses v4 update, not v5, just
> hope they don't switch because not being able to update
> pc's or servers are a nightmare with all the security
> loopholes found in Windows OS's.
Hi

Reset the security settings on the BITS and Windows Update services
and see if it helps:

http://groups.google.com/groups?selm...TNGP12.phx.gbl

(the "sc sdset ..." part for the two services in the link above)



If tha above doesn't work, see if the tip from Karl B/Melvin Salazar
works for you:

<quote>

From: "Karl B" <>
Subject: Possible solution to the windows update 0x800A0046 problem
Date: Sun, 30 May 2004 12:03:39 +0100
Newsgroups: microsoft.private.xpsp2.general

Firstly, I take no credit for this I was going though the network
newsgroup because my dialup network settings had vanished and a guy
named Melvin Salazar suggested the following which WORKED!

'You can also try doing the following, it worked for me:

Go to Services under the Administrative Tools folder.

Notice that the logon account is set to a NT/User account under the RPC
(remote procedure call) service. Change it to Local System account,
under the Logon tab, and restart the computer. Many of these services
depend on the RPC, but there was an error when it came to configuring
this paticular service.'

Now once I made these changes I was able to get my network icons back
as well as use Windows Update.

Thanks
Karl

</quote>


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

I can't get v5 update to work. I've tried all the tips
I've found here and at MS. Is there any way to go back to
v4 that worked? Or is there any other way to download sp2?
Is ordering and waiting for the CD the only option?

(I get either 0x80240030 or 0x800A01AD depending on proxy
settings.)
>-----Original Message-----
>Morne wrote:
>
>> The "new and improved" windows updates is a nightmare!
>> We have mostlt winXP pro workstations.Automatic updates
do
>> not work at our site since changing from v4 to v5.
Always
>> get the 0x800A0046 error, no matter what. Tried
>> Knowledgebase article 883821 Method 1 and 2, no success
>> and Method 3 does not work/unable to test as the darn
>> policy isnt there and cant find out how to get it in
the
>> policy list.
>>
>> Anyone have an idea what I can do to fix this?
>> I see win2003 server still uses v4 update, not v5, just
>> hope they don't switch because not being able to update
>> pc's or servers are a nightmare with all the security
>> loopholes found in Windows OS's.
>Hi
>
>Reset the security settings on the BITS and Windows
Update services
>and see if it helps:
>
>http://groups.google.com/groups?selm=O4yhAYjdEHA.996%
40TK2MSFTNGP12.phx.gbl
>
>(the "sc sdset ..." part for the two services in the link
above)
>
>
>
>If tha above doesn't work, see if the tip from Karl
B/Melvin Salazar
>works for you:
>
><quote>
>
>From: "Karl B" <>
>Subject: Possible solution to the windows update
0x800A0046 problem
>Date: Sun, 30 May 2004 12:03:39 +0100
>Newsgroups: microsoft.private.xpsp2.general
>
>Firstly, I take no credit for this I was going though the
network
>newsgroup because my dialup network settings had
vanished and a guy
>named Melvin Salazar suggested the following which WORKED!
>
>'You can also try doing the following, it worked for me:
>
>Go to Services under the Administrative Tools folder.
>
>Notice that the logon account is set to a NT/User account
under the RPC
>(remote procedure call) service. Change it to Local
System account,
>under the Logon tab, and restart the computer. Many of
these services
>depend on the RPC, but there was an error when it came to
configuring
>this paticular service.'
>
>Now once I made these changes I was able to get my
network icons back
>as well as use Windows Update.
>
>Thanks
>Karl
>
></quote>
>
>
>--
>torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
>Administration scripting examples and an ONLINE version of
>the 1328 page Scripting Guide:
>http://www.microsoft.com/technet/scr...r/default.mspx
>.
>

I found a way to download SP2 (from this forum) and
installed it. v5 update still won't work. (error 80240030)
The tips listed here to date haven't helped. Any chance MS
will fix it or go back to v4 that worked? Are there any
new tips? (Note: Domain is behind MS Proxy server 2.0)

>-----Original Message-----
>I can't get v5 update to work. I've tried all the tips
>I've found here and at MS. Is there any way to go back to
>v4 that worked? Or is there any other way to download
sp2?
>Is ordering and waiting for the CD the only option?
>
>(I get either 0x80240030 or 0x800A01AD depending on proxy
>settings.)
>>-----Original Message-----
>>Morne wrote:
>>
>>> The "new and improved" windows updates is a nightmare!
>>> We have mostlt winXP pro workstations.Automatic
updates
>do
>>> not work at our site since changing from v4 to v5.
>Always
>>> get the 0x800A0046 error, no matter what. Tried
>>> Knowledgebase article 883821 Method 1 and 2, no
success
>>> and Method 3 does not work/unable to test as the darn
>>> policy isnt there and cant find out how to get it in
>the
>>> policy list.
>>>
>>> Anyone have an idea what I can do to fix this?
>>> I see win2003 server still uses v4 update, not v5,
just
>>> hope they don't switch because not being able to
update
>>> pc's or servers are a nightmare with all the security
>>> loopholes found in Windows OS's.
>>Hi
>>
>>Reset the security settings on the BITS and Windows
>Update services
>>and see if it helps:
>>
>>http://groups.google.com/groups?selm=O4yhAYjdEHA.996%
>40TK2MSFTNGP12.phx.gbl
>>
>>(the "sc sdset ..." part for the two services in the
link
>above)
>>
>>
>>
>>If tha above doesn't work, see if the tip from Karl
>B/Melvin Salazar
>>works for you:
>>
>><quote>
>>
>>From: "Karl B" <>
>>Subject: Possible solution to the windows update
>0x800A0046 problem
>>Date: Sun, 30 May 2004 12:03:39 +0100
>>Newsgroups: microsoft.private.xpsp2.general
>>
>>Firstly, I take no credit for this I was going though
the
>network
>>newsgroup because my dialup network settings had
>vanished and a guy
>>named Melvin Salazar suggested the following which
WORKED!
>>
>>'You can also try doing the following, it worked for me:
>>
>>Go to Services under the Administrative Tools folder.
>>
>>Notice that the logon account is set to a NT/User
account
>under the RPC
>>(remote procedure call) service. Change it to Local
>System account,
>>under the Logon tab, and restart the computer. Many of
>these services
>>depend on the RPC, but there was an error when it came
to
>configuring
>>this paticular service.'
>>
>>Now once I made these changes I was able to get my
>network icons back
>>as well as use Windows Update.
>>
>>Thanks
>>Karl
>>
>></quote>
>>
>>
>>--
>>torgeir, Microsoft MVP Scripting and WMI, Porsgrunn
Norway
>>Administration scripting examples and an ONLINE version
of
>>the 1328 page Scripting Guide:
>>http://www.microsoft.com/technet/scr...er/default.msp
x
>>.
>>
>.
>