Month: June 2006

Wsus won’t download updates

Had a customer whose wsus box wouldn’t download updates from microsoft with event id 364 – Content download failed. Reason: Access is denied. Source File &lt snip &gt destination File: d:\wsus\wsuscontent……
It looks like the permissions on the root of d: (in this case) are not correct – Network Service needs read access – unfortunately Network Service does not appear in the list of users to add to the drive (and you can’t right click d: to assign permissions).
Fortunately by using cacls you can change permissions – note that cacls is very powerful and you need to understand what you are doing before running this – take it from me, cacls going wrong can really mess with your system and your sanity and your job security!

If you are still with me, you need to do the following:
From a dos prompt:-
d:
cd\
calcs . <--- this provides you with the current state before you change it cacls . /e /g "NT AUTHORITY\NETWORK SERVICE":r cacls . Then in wsus console, double click a client that needs an update, click on the status, click on an update that has failed. Click retry download. Look at the eventvwr and you should see event id 361 - Content synchronization started. A quick glance back at your wsus homepage should show the files being downloaded.

error 0x80096001 when trying to run windows updates.

I had a problem trying to run Windows Updates on a machine, getting an error “Windows Update has encountered an error and cannot display the requested page. You may find the following resources helpful in resolving the problem…’Error Number: 0x80096001”

Several kb articles (ie kb822798) mentioned the need to edit security settings and reregister dll’s and/or remove the %windir%softwaredistribution directory but unfortunately this didn’t work.
Part of the troubleshooting for this involves going in and looking at the certificate status within internet explorer. When I tried to double click on the certificate it gave me the error message “system-level error occured while verifying trust” on any of the certificates.

A post on the microsoft.public.windowsupdate newsgroup gave me a clue and by logging on as another administrator it all worked – my certificates are ok and windows updates runs through successfully.
Update It turns out that the problem in this case was partially caused by having a readonly profile – for some reason the desktop folders etc were all redirected to a share that didn’t exist. By searching for this entry in the registry and editing it to point to a share that did exist I was able to get the profile (and windows update) working again.