There are some posts about it on the m.p.windowsupdate newsgroup. It
seems you need to supply your update log to a support person.
The error 0x8009310B equates to "ASN1 bad tag value met"
It has to do with cryptography failure.
General suggestion:
Make sure these services are not disabled
( use MSCONFIG to review or run SERVICES.MSC):
Background Intelligent Transfer Service (BITS)
Cryptographic Services
Remote Procedure Call (RPC)
System Restore Service
Also, the next time you force (or visit) Windows Update, close your open user programs, and review the auto-loaded (auto-start) utilities beforehand.
Since you appear to be using the web-based interface, use this next link to Windows Update newsgroup:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windowsupdate&lang=en&cr=US
You may make a new post there, give all details, and "attach" your update log.
Post an *extract* from the log, but only for the very last date.
Use Wordpad and open & look at the Windows Update log file
C:\WINNT\WindowsUpdate.log
Scroll down all the way. Get / copy / paste /attach the set of lines for the last session.
N.B. Your Windows folder may be at \Windows
Be specific in your next post. Do mention which update item(s) failed (hopefully by update number; if not, then by description).
One more thing, all microsoft public newsgroups are peer-to-peer. Although MS Windows Update team monitors from time to time, and answer from time to time, at the Windows Update group, it is mainly peer support.
You may wind up having to really contact MS support. If so, visit this page
http://support.microsoft.com/ph/6527/
Review contents. If no joy, then there's a link to support at the top & at very bottom.
--
Maurice N
MVP Windows - Shell / User
-----
Nath wrote:
> Also...how do I supply my update log to a support person ?
>
Review the article. Do all the 'methods". Really focus on the certificates section (method 8).
I had hoped we'd hear of your status on this issue. If you are still stuck & having the same issue, try the following, which is basically to re-register some selected DLL files.
From main Windows Start menu, select RUN, type in
CMD <Enter-key>
type in
net stop wuauserv <Enter-key>
net stop cryptsvc <Enter-key>
(Now, re-register some DLL files)
At the command prompt, type the following lines and press Enter key after each line:
regsvr32 cryptdlg.dll
regsvr32 dssenh.dll
regsvr32 gpkcsp.dll
regsvr32 initpki.dll
regsvr32 rsaenh.dll
regsvr32 sccbase.dll
regsvr32 slbcsp.dll
regsvr32 softpub.dll
regsvr32 wintrust.dll
(Click OK when you receive the message that DllRegisterServer in FileName succeeded. )
(While still at command prompt, enter these to restart 2 Windows services).
net start cryptsvc <Enter-key>
net start wuauserv <Enter-key>
Type exit
(That closes out the command prompt window).
HTH
--
Maurice N
MVP Windows - Shell / User
-----
Nath wrote:
> Also...how do I supply my update log to a support person ?
To see what I mean, rename the folder of CatRoot to CatRootTest.
Download an update from Microsoft's site, not through Windows update
and run it. The "ASN1 bad tag" error changes to a directory not found
error. Change the directory back to it's original name to continue with
the fix.
Go through this directory and check all .CAT files by double clicking
on them to see if they are good. Any .CAT files that are bad (ie cannot
verify signature), simply append .old or whatever you like to them.
After I renamed the bad .CAT files, I ran Windows Update and it worked.
--
bellenberger
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message2208109.html