We have published own created updates using wsus. The updates was
automatically signed by an certificate, which was created explicit for the
server. The root certificate is published on the computer as "trusted root".
Now we have digital signature errors on some computers(Windows Vista) like
the following:
2008-02-26 18:13:38:942 1020 cf4 DnldMgr BITS job
{92E46536-BB95-468B-8C4A-4129FAF413B3} completed successfully
2008-02-26 18:13:39:021 1020 cf4 Misc Validating signature for
C:\Windows\SoftwareDistribution\Download\4c04a18e468da1078fbeccdba67fe55f\15702aee91a845bedac5f000dad241cacef96f77:
2008-02-26 18:13:39:036 1020 cf4 Misc Microsoft signed: No
2008-02-26 18:13:39:036 1020 cf4 Misc Trusted Publisher: No
2008-02-26 18:13:39:036 1020 cf4 Misc WARNING: Digital Signatures on file
C:\Windows\SoftwareDistribution\Download\4c04a18e468da1078fbeccdba67fe55f\15702aee91a845bedac5f000dad241cacef96f77 are not trusted: Error 0x800b0004
2008-02-26 18:13:39:036 1020 cf4 DnldMgr WARNING: File failed
postprocessing, error = 800b0004
2008-02-26 18:13:39:036 1020 cf4 DnldMgr Failed file: URL =
'http://server.local.net/Content/77/15702AEE91A845BEDAC5F000DAD241CACEF96F77.cab',
Local path =
'C:\Windows\SoftwareDistribution\Download\4c04a18e468da1078fbeccdba67fe55f\15702aee91a845bedac5f000dad241cacef96f77'
2008-02-26 18:13:39:036 1020 cf4 DnldMgr Error 0x800b0004 occurred while
downloading update; notifying dependent calls.
Now the question is: Which kind of error is it? I tried to validate the
signing of the file using "signtool /verify" and it was successful.