From: Bitbug on
Fresh install of XP-Pro, SP-2 Manually installed from CD I got at work, now all updates from windows update give this message...
From: Robert Aldwinckle on
"Bitbug" <1@2> wrote in message
news:c7CdnUot78NF1YjfRVn-ig(a)rogers.com...
> Fresh install of XP-Pro, SP-2 Manually installed from CD I got at work,
> now all updates from windows update give this message...

Try a search?

http://groups-beta.google.com/group/microsoft.public.windowsxp.accessibility/browse_frm/thread/6fb6808976f443ab/5cb1a7bd549c7768?q=8009001A++OR++0x8009001A++MSFT+OR+MVP++group:microsoft.*&_done=%2Fgroups%3Fq%3D8009001A++OR++0x8009001A++MSFT+OR+MVP++group:microsoft.*%26&_doneTitle=Back+to+Search&&d#5cb1a7bd549c7768

(Google Groups search for
8009001A OR 0x8009001A MSFT OR MVP group:microsoft.*
)


---


From: Bitbug on
Thank you for the reply but the error I'm getting is whenever I try to use
windows update, not when the system is rebooting. I have googled this all
over the place and can only narrow it down to some type of VB error, "keyset
not registered", but as I am not familiar with VB, it's meaningless to me
and more important offers no solution...


From: Robert Aldwinckle on
"Bitbug" <brianpenhale(a)rogers.com> wrote in message
news:_eGdnRjVT4Xp9ILfRVn-qw(a)rogers.com...
> Thank you for the reply but the error I'm getting is whenever I try to use
> windows update, not when the system is rebooting.

I'm not sure that the suggested resolution only applies to that case.
I thought that you could try those two regsvr32 commands
just in case they worked.

I guess you will have to diagnose it then.

FWIW my guess is that the code is bogus and very likely your log
shows other codes before that which may be more meaningful.


Good luck

Robert
---