Error number: 0x800A0046 Windows 2000 SP4 Critical Update Issue

I am having an issue with about 25 Windows 2000 SP4 computers. The
automatic updater 'wuauclt.exe' shows up and then disappears when you click
it. The updater icon is fuzzy with the red/green/blue/yellow When examining
the Task Manager, the 'wuauclt.exe' shows up and then disappears when you
click it. The PID of 'wuauclt.exe' changes every time.

When you attempt to go to the Windows Update site you are greeting with the
following error and message:

[Error number: 0x800A0046]
Please change your Internet Explorer security settings
To save changes to your settings for this website, you need to enable
userdata persistence for Internet Explorer. Complete the steps below, and
then click Change settings to the left and try saving your changes again.
In Internet Explorer, on the Tools menu, click Internet Options.
Click the Security tab, click the Internet security zone icon, and then
click Custom Level.
In the Settings dialog box, scroll to the Miscellaneous section.
Under Userdata persistence , select Enable.
Click OK and when the security warning dialog box appears, click Yes.

This solution doesn't work and doesn't appear to address the problem.

I found a Windows 2000 SP4 system that hadn't applied the updates from last
week. I went through the process and it appears that Microsoft changed the
way Windows Update works. The previous version was 'V4' and the new version
you are updated to is 'V6'. The 'V6' update modifies the 'wuauclt.exe' and
adds a new 'wuacuclt1.exe'. I assume 'V6' to be aimed at the Windows XP
world and has broken functionality in Windows 2000 SP4 workstations.

I looked in the \system32\ directory of the clean Windows 2000 SP4 system
and noticed that 'wuauclt.exe' and 'wuaucpl.cpl' modified 2/9/2004. There is
also a 'wupdmgr.exe' modified 12/7/1999.

However, when I look at the \system32\ directory of the updated Windows 2000
SP4 system I find that 'wuauclt.exe' and 'wuaucpl.cpl' to be modified
5/26/2005. There is also a new 'wuauclt1.exe' with the same modification
date of 5/26/2005. The 'wupdmgr.exe' still has the same modification date of
12/7/1999.

I am hoping that Microsoft realizes the situation and offers a solution for
the Windows 2000 user base. If they don't, my short term solution will be
to turn off the automatic update.

Randy

Randy wrote:

> I am having an issue with about 25 Windows 2000 SP4 computers. The
> automatic updater 'wuauclt.exe' shows up and then disappears when you click
> it. The updater icon is fuzzy with the red/green/blue/yellow When examining
> the Task Manager, the 'wuauclt.exe' shows up and then disappears when you
> click it. The PID of 'wuauclt.exe' changes every time.
>
> When you attempt to go to the Windows Update site you are greeting with the
> following error and message:
>
> [Error number: 0x800A0046]
> Please change your Internet Explorer security settings
> To save changes to your settings for this website, you need to enable
> userdata persistence for Internet Explorer. Complete the steps below, and
> then click Change settings to the left and try saving your changes again.
> In Internet Explorer, on the Tools menu, click Internet Options.
> Click the Security tab, click the Internet security zone icon, and then
> click Custom Level.
> In the Settings dialog box, scroll to the Miscellaneous section.
> Under Userdata persistence , select Enable.
> Click OK and when the security warning dialog box appears, click Yes.
>
> This solution doesn't work and doesn't appear to address the problem.
> (snip)
Hi,

See if any one of the 3 different suggestions here fixes it:

http://update.microsoft.com/windowsu...cleid=20&ln=en



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

Thank you for the suggestion. I did try all three of those suggestions
previous to posting.

1. Doesn't have this setting in Windows 2000 SP4.
2. Running this command does nothing.
3. Doesn't apply to Windows 2000 SP4.

I truly think that the 'V6' version of windows update breaks the
functionality of windows update in Windows 2000.

I am going to venture a guess that since Microsoft released Windows 2000
Service Pack 4 Update Rollup 1 on 6/28/2005 and that Mainstream Support for
Windows 2000 Professional expired on 6/30/2005 Microsoft is pushing people to
the Windows XP platform.

While I have no problem with that, we are an K-12 educational environment
that don't always have the econcomic resources to upgrade to the support
version of OS.

Randy

"Torgeir Bakken (MVP)" wrote:

> Randy wrote:
>
> > I am having an issue with about 25 Windows 2000 SP4 computers. The
> > automatic updater 'wuauclt.exe' shows up and then disappears when you click
> > it. The updater icon is fuzzy with the red/green/blue/yellow When examining
> > the Task Manager, the 'wuauclt.exe' shows up and then disappears when you
> > click it. The PID of 'wuauclt.exe' changes every time.
> >
> > When you attempt to go to the Windows Update site you are greeting with the
> > following error and message:
> >
> > [Error number: 0x800A0046]
> > Please change your Internet Explorer security settings
> > To save changes to your settings for this website, you need to enable
> > userdata persistence for Internet Explorer. Complete the steps below, and
> > then click Change settings to the left and try saving your changes again.
> > In Internet Explorer, on the Tools menu, click Internet Options.
> > Click the Security tab, click the Internet security zone icon, and then
> > click Custom Level.
> > In the Settings dialog box, scroll to the Miscellaneous section.
> > Under Userdata persistence , select Enable.
> > Click OK and when the security warning dialog box appears, click Yes.
> >
> > This solution doesn't work and doesn't appear to address the problem.
> > (snip)
> Hi,
>
> See if any one of the 3 different suggestions here fixes it:
>
> http://update.microsoft.com/windowsu...cleid=20&ln=en
>
>
>
> --
> 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
>

"Randy" <> wrote in message
news:74E1168A-87E3-4502-AC2E-
....
> "Torgeir Bakken (MVP)" wrote:
>> See if any one of the 3 different suggestions here fixes it:
>>
>> http://update.microsoft.com/windowsu...cleid=20&ln=en


> Thank you for the suggestion. I did try all three of those suggestions
> previous to posting.
>
> 1. Doesn't have this setting in Windows 2000 SP4.

Be more specific about what you are seeing.
Is the problem just the menu descriptions?
In XP they are apparently running secpol.msc under them.
Do you have that tool? At which point do the instructions fail?


> 2. Running this command does nothing.

<quote>
At the command prompt, type sc sdset wuauserv
....
</quote>

So, perhaps you should do instead

sc sdshow wuauserv

and copy and paste the results


> 3. Doesn't apply to Windows 2000 SP4.

Be specific. Where are the instructions failing?
FWIW in XP the command being run is compmgnt.msc


>
> I truly think that the 'V6' version of windows update breaks the
> functionality of windows update in Windows 2000.



>
> I am going to venture a guess that since Microsoft released Windows 2000
> Service Pack 4 Update Rollup 1 on 6/28/2005 and that Mainstream Support for
> Windows 2000 Professional expired on 6/30/2005 Microsoft is pushing people to
> the Windows XP platform.
>
> While I have no problem with that, we are an K-12 educational environment
> that don't always have the econcomic resources to upgrade to the support
> version of OS.


Perhaps you should try posting in a newsgroup which specializes
in your OS in order to get a more accurate analogy of the instructions.


Good luck

Robert Aldwinckle
---

Randy wrote:

> "Torgeir Bakken (MVP)" wrote:
>
>>
>>See if any one of the 3 different suggestions here fixes it:
>>
>>http://update.microsoft.com/windowsu...cleid=20&ln=en
>>
>
> Thank you for the suggestion. I did try all three of those
> suggestions previous to posting.
>
> 1. Doesn't have this setting in Windows 2000 SP4.

I do on my Win2k SP4 computer, and so should you.

My "Impersonate a client after authentication" policy setting had
SERVICE already in place, but not the "Administrator" account.


> 2. Running this command does nothing.

SC.exe doesn't come builtin with Win2k. You can download it from here:
ftp://ftp.microsoft.com/reskit/win2000/


> 3. Doesn't apply to Windows 2000 SP4.

Yes it does.


> I truly think that the 'V6' version of windows update breaks the
> functionality of windows update in Windows 2000.
>
> I am going to venture a guess that since Microsoft released Windows 2000
> Service Pack 4 Update Rollup 1 on 6/28/2005 and that Mainstream Support for
> Windows 2000 Professional expired on 6/30/2005 Microsoft is pushing people to
> the Windows XP platform.
>
> While I have no problem with that, we are an K-12 educational environment
> that don't always have the econcomic resources to upgrade to the support
> version of OS.
>>


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

Okay, here is what I did to resolve my issue in Windows 2000 SP4.

I visited this link:
http://update.microsoft.com/windowsu...cleid=20&ln=en that Torgeir Bakken supplied for me.

I originally said the following:
1. Doesn't have this setting in Windows 2000 SP4.
2. Running this command does nothing.
3. Doesn't apply to Windows 2000 SP4.

I typed the above answers from memory, so it was no wonder I was incorrect
with my recollection from memory.

Here are the steps I performed with respects to the support link above.
1. The workstations already had 'Service and Administrator' were part of
"Impersonate a client after authentication" security policy. So this one
didn't work.

2. I downloaded the 'SC' security descriptor from the provided link by
Torgeir Bakken. Once I copied the 'SC' application to the root of the c: and
typed the long commands I was greeted with the following:
SetServiceObjectSecurity SUCCESS.

I then attempted to try the Windows Update site again, no luck, still 'Error
number: 0x800A0046'.

3. I went to the Local User Account settings and went to the 'Member Of'
tab and noticed the account was a member of the following groups:
Administrators, Backup Operators, Guests, Power Users, Replicator and Users.
I removed everyone but 'Administrators' from this Local User Account.

I then attempted to try the Windows Update site again, no luck, still 'Error
number: 0x800A0046'.

So I decided to restart the workstation and voila Windows Update worked
again and let me download the updates from the site and it also automatically
downloaded critcal updates.

I decided to go one step further to determine if step 2 or step 3 combined
fixed the issue or if it was just step 2 or step 3 separately. I picked a
couple of different workstations and upon testing step 2 by itself and the
'Error number: 0x800A0046' was still present. I restarted the workstation to
see if the restart fixed step 2 and it didn't.

I then tested step 3 by itself and the 'Error number: 0x800A0046' was still
present. I followed logic and restarted the workstation. The Windows Update
worked again and let me download the updates from the site and it also
automatically downloaded critcal updates.

So, from my testing, I concluded that step 3 was the real solution by
removing all the groups but 'Administrator'. You can probably just remove
'Guests' and 'Users' and get the same result.

I will be venturing ahead and performing just step 3 to fix the issue I am
experiencing with 'Error number: 0x800A0046' on Windows 2000 SP4.

Thank you for all the suggestions and assistance.
Randy

Randy,

I also have all the same issues you are reporting on about 8 machines here
in my department. I have previously posted the same issue last week.
Nothing seems to fix the problem. I'm considering trying to figure what
patches these machines may need and downloading them separately and
installing them manually. It's too bad windows update no longer works in
Windows 2000

Dave


"Randy" <> wrote in message
news:74E1168A-87E3-4502-AC2E-...
> Thank you for the suggestion. I did try all three of those suggestions
> previous to posting.
>
> 1. Doesn't have this setting in Windows 2000 SP4.
> 2. Running this command does nothing.
> 3. Doesn't apply to Windows 2000 SP4.
>
> I truly think that the 'V6' version of windows update breaks the
> functionality of windows update in Windows 2000.
>
> I am going to venture a guess that since Microsoft released Windows 2000
> Service Pack 4 Update Rollup 1 on 6/28/2005 and that Mainstream Support
for
> Windows 2000 Professional expired on 6/30/2005 Microsoft is pushing people
to
> the Windows XP platform.
>
> While I have no problem with that, we are an K-12 educational environment
> that don't always have the econcomic resources to upgrade to the support
> version of OS.
>
> Randy
>
> "Torgeir Bakken (MVP)" wrote:
>
> > Randy wrote:
> >
> > > I am having an issue with about 25 Windows 2000 SP4 computers. The
> > > automatic updater 'wuauclt.exe' shows up and then disappears when you
click
> > > it. The updater icon is fuzzy with the red/green/blue/yellow When
examining
> > > the Task Manager, the 'wuauclt.exe' shows up and then disappears when
you
> > > click it. The PID of 'wuauclt.exe' changes every time.
> > >
> > > When you attempt to go to the Windows Update site you are greeting
with the
> > > following error and message:
> > >
> > > [Error number: 0x800A0046]
> > > Please change your Internet Explorer security settings
> > > To save changes to your settings for this website, you need to enable
> > > userdata persistence for Internet Explorer. Complete the steps below,
and
> > > then click Change settings to the left and try saving your changes
again.
> > > In Internet Explorer, on the Tools menu, click Internet Options.
> > > Click the Security tab, click the Internet security zone icon, and
then
> > > click Custom Level.
> > > In the Settings dialog box, scroll to the Miscellaneous section.
> > > Under Userdata persistence , select Enable.
> > > Click OK and when the security warning dialog box appears, click Yes.
> > >
> > > This solution doesn't work and doesn't appear to address the problem.
> > > (snip)
> > Hi,
> >
> > See if any one of the 3 different suggestions here fixes it:
> >
> >
http://update.microsoft.com/windowsu...cleid=20&ln=en
> >
> >
> >
> > --
> > 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
> >

Randy wrote:

> Okay, here is what I did to resolve my issue in Windows 2000 SP4.
>
> I visited this link:
> http://update.microsoft.com/windowsu...cleid=20&ln=en that Torgeir Bakken supplied for me.
>
> I originally said the following:
> 1. Doesn't have this setting in Windows 2000 SP4.
> 2. Running this command does nothing.
> 3. Doesn't apply to Windows 2000 SP4.
>
> I typed the above answers from memory, so it was no wonder I was incorrect
> with my recollection from memory.
>
> Here are the steps I performed with respects to the support link above.
> 1. The workstations already had 'Service and Administrator' were part of
> "Impersonate a client after authentication" security policy. So this one
> didn't work.
>
> 2. I downloaded the 'SC' security descriptor from the provided link by
> Torgeir Bakken. Once I copied the 'SC' application to the root of the c: and
> typed the long commands I was greeted with the following:
> SetServiceObjectSecurity SUCCESS.
>
> I then attempted to try the Windows Update site again, no luck, still 'Error
> number: 0x800A0046'.
>
> 3. I went to the Local User Account settings and went to the 'Member Of'
> tab and noticed the account was a member of the following groups:
> Administrators, Backup Operators, Guests, Power Users, Replicator and Users.
> I removed everyone but 'Administrators' from this Local User Account.
>
> I then attempted to try the Windows Update site again, no luck, still 'Error
> number: 0x800A0046'.
>
> So I decided to restart the workstation and voila Windows Update worked
> again and let me download the updates from the site and it also automatically
> downloaded critcal updates.
>
> I decided to go one step further to determine if step 2 or step 3 combined
> fixed the issue or if it was just step 2 or step 3 separately. I picked a
> couple of different workstations and upon testing step 2 by itself and the
> 'Error number: 0x800A0046' was still present. I restarted the workstation to
> see if the restart fixed step 2 and it didn't.
>
> I then tested step 3 by itself and the 'Error number: 0x800A0046' was still
> present. I followed logic and restarted the workstation. The Windows Update
> worked again and let me download the updates from the site and it also
> automatically downloaded critcal updates.
>
> So, from my testing, I concluded that step 3 was the real solution by
> removing all the groups but 'Administrator'. You can probably just remove
> 'Guests' and 'Users' and get the same result.
>
> I will be venturing ahead and performing just step 3 to fix the issue I am
> experiencing with 'Error number: 0x800A0046' on Windows 2000 SP4.
>
Hi,

Glad you got it fixed :-)

The reason for that it didn't start to work before you did a reboot is
that changes in group membership isn't "seen" by the system before you
do a new logon.

So the article is really missing one step in the procedure, it should
have stated that after doing any changes to group memberships, you
would need to log off and on again (a reboot isn't really necessary,
but it will do the job of course).


--
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 tried these fixes but I'm still seeing the problem. Could you suggest
where I may be going wrong...

My User acount is only a member of the Administrators group. I have run the
"SC" command and received a "Success" message. I have checked the
impersinate a client after authorisation contains the administrators group
and have even added my account to it as well. and finally, in internet
options, I have checked that Persist user data is enabled. I'm a bit at a
loss as to what else I can do...



"Torgeir Bakken (MVP)" wrote:

> Randy wrote:
>
> > Okay, here is what I did to resolve my issue in Windows 2000 SP4.
> >
> > I visited this link:
> > http://update.microsoft.com/windowsu...cleid=20&ln=en that Torgeir Bakken supplied for me.
> >
> > I originally said the following:
> > 1. Doesn't have this setting in Windows 2000 SP4.
> > 2. Running this command does nothing.
> > 3. Doesn't apply to Windows 2000 SP4.
> >
> > I typed the above answers from memory, so it was no wonder I was incorrect
> > with my recollection from memory.
> >
> > Here are the steps I performed with respects to the support link above.
> > 1. The workstations already had 'Service and Administrator' were part of
> > "Impersonate a client after authentication" security policy. So this one
> > didn't work.
> >
> > 2. I downloaded the 'SC' security descriptor from the provided link by
> > Torgeir Bakken. Once I copied the 'SC' application to the root of the c: and
> > typed the long commands I was greeted with the following:
> > SetServiceObjectSecurity SUCCESS.
> >
> > I then attempted to try the Windows Update site again, no luck, still 'Error
> > number: 0x800A0046'.
> >
> > 3. I went to the Local User Account settings and went to the 'Member Of'
> > tab and noticed the account was a member of the following groups:
> > Administrators, Backup Operators, Guests, Power Users, Replicator and Users.
> > I removed everyone but 'Administrators' from this Local User Account.
> >
> > I then attempted to try the Windows Update site again, no luck, still 'Error
> > number: 0x800A0046'.
> >
> > So I decided to restart the workstation and voila Windows Update worked
> > again and let me download the updates from the site and it also automatically
> > downloaded critcal updates.
> >
> > I decided to go one step further to determine if step 2 or step 3 combined
> > fixed the issue or if it was just step 2 or step 3 separately. I picked a
> > couple of different workstations and upon testing step 2 by itself and the
> > 'Error number: 0x800A0046' was still present. I restarted the workstation to
> > see if the restart fixed step 2 and it didn't.
> >
> > I then tested step 3 by itself and the 'Error number: 0x800A0046' was still
> > present. I followed logic and restarted the workstation. The Windows Update
> > worked again and let me download the updates from the site and it also
> > automatically downloaded critcal updates.
> >
> > So, from my testing, I concluded that step 3 was the real solution by
> > removing all the groups but 'Administrator'. You can probably just remove
> > 'Guests' and 'Users' and get the same result.
> >
> > I will be venturing ahead and performing just step 3 to fix the issue I am
> > experiencing with 'Error number: 0x800A0046' on Windows 2000 SP4.
> >
> Hi,
>
> Glad you got it fixed :-)
>
> The reason for that it didn't start to work before you did a reboot is
> that changes in group membership isn't "seen" by the system before you
> do a new logon.
>
> So the article is really missing one step in the procedure, it should
> have stated that after doing any changes to group memberships, you
> would need to log off and on again (a reboot isn't really necessary,
> but it will do the job of course).
>
>
> --
> 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'm still having the same issues myself. Only difference is that its on a
Windows 2000 Server DC. Doesn't allow you access to the local user accounts,
only domain accounts.

Any suggestions?

"Buggrit" wrote:

> I tried these fixes but I'm still seeing the problem. Could you suggest
> where I may be going wrong...
>
> My User acount is only a member of the Administrators group. I have run the
> "SC" command and received a "Success" message. I have checked the
> impersinate a client after authorisation contains the administrators group
> and have even added my account to it as well. and finally, in internet
> options, I have checked that Persist user data is enabled. I'm a bit at a
> loss as to what else I can do...
>
>
>
> "Torgeir Bakken (MVP)" wrote:
>
> > Randy wrote:
> >
> > > Okay, here is what I did to resolve my issue in Windows 2000 SP4.
> > >
> > > I visited this link:
> > > http://update.microsoft.com/windowsu...cleid=20&ln=en that Torgeir Bakken supplied for me.
> > >
> > > I originally said the following:
> > > 1. Doesn't have this setting in Windows 2000 SP4.
> > > 2. Running this command does nothing.
> > > 3. Doesn't apply to Windows 2000 SP4.
> > >
> > > I typed the above answers from memory, so it was no wonder I was incorrect
> > > with my recollection from memory.
> > >
> > > Here are the steps I performed with respects to the support link above.
> > > 1. The workstations already had 'Service and Administrator' were part of
> > > "Impersonate a client after authentication" security policy. So this one
> > > didn't work.
> > >
> > > 2. I downloaded the 'SC' security descriptor from the provided link by
> > > Torgeir Bakken. Once I copied the 'SC' application to the root of the c: and
> > > typed the long commands I was greeted with the following:
> > > SetServiceObjectSecurity SUCCESS.
> > >
> > > I then attempted to try the Windows Update site again, no luck, still 'Error
> > > number: 0x800A0046'.
> > >
> > > 3. I went to the Local User Account settings and went to the 'Member Of'
> > > tab and noticed the account was a member of the following groups:
> > > Administrators, Backup Operators, Guests, Power Users, Replicator and Users.
> > > I removed everyone but 'Administrators' from this Local User Account.
> > >
> > > I then attempted to try the Windows Update site again, no luck, still 'Error
> > > number: 0x800A0046'.
> > >
> > > So I decided to restart the workstation and voila Windows Update worked
> > > again and let me download the updates from the site and it also automatically
> > > downloaded critcal updates.
> > >
> > > I decided to go one step further to determine if step 2 or step 3 combined
> > > fixed the issue or if it was just step 2 or step 3 separately. I picked a
> > > couple of different workstations and upon testing step 2 by itself and the
> > > 'Error number: 0x800A0046' was still present. I restarted the workstation to
> > > see if the restart fixed step 2 and it didn't.
> > >
> > > I then tested step 3 by itself and the 'Error number: 0x800A0046' was still
> > > present. I followed logic and restarted the workstation. The Windows Update
> > > worked again and let me download the updates from the site and it also
> > > automatically downloaded critcal updates.
> > >
> > > So, from my testing, I concluded that step 3 was the real solution by
> > > removing all the groups but 'Administrator'. You can probably just remove
> > > 'Guests' and 'Users' and get the same result.
> > >
> > > I will be venturing ahead and performing just step 3 to fix the issue I am
> > > experiencing with 'Error number: 0x800A0046' on Windows 2000 SP4.
> > >
> > Hi,
> >
> > Glad you got it fixed :-)
> >
> > The reason for that it didn't start to work before you did a reboot is
> > that changes in group membership isn't "seen" by the system before you
> > do a new logon.
> >
> > So the article is really missing one step in the procedure, it should
> > have stated that after doing any changes to group memberships, you
> > would need to log off and on again (a reboot isn't really necessary,
> > but it will do the job of course).
> >
> >
> > --
> > 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
> >