Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I just recently installed Windows 8 Pro on a computer at work. The computer runs Windows Update fine while its not joined to the domain. However, once I join it to the domain it cannot perform windows update.

I get the following error code 800B0001 when it tries to update.

Also in the WindowsUpdate.log I see that I get the following error.

Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\wuident.cab:
Microsoft signed: Yes
Infrastructure signed: No
WARNING: Digital Signatures on file C:\WINDOWS\SoftwareDistribution\SelfUpdate\wuident.cab are not trusted: Error 0x800b0001
WARNING: SelfUpdate check failed to download package information, error = 0x800B0001
FATAL: SelfUpdate check failed, err = 0x800B0001
WARNING: Skipping scan, self-update check returned 0x800B0001
WARNING: Exit code = 0x800B0001

We have a Windows SBS Server 2008 running WSUS. All other Windows 7 machines are working just fine. I notice that it can't verify the signature of the .cab. Do I need to manually accept a server certificate somewhere?

EDIT 1

Oddly enough I went and spun up a new Windows 8 machine and joined the domain. It was able to receive updates from

Control Panel->Windows Update

but was not able to receive updates from

(Win + i) -> Change PC Settings -> Windows Update.

share|improve this question
    
After you joined the Domain, can it still list the updates with the KB hotlinks for manual download or does it fail to even get that far? I'm not asking just to hint that I know your answer, this is for myself to help me and others avoid the time consuming precaution of imaging my box, joining a domain just to realize there is no more way to even dowload the fixes that I'm willing to individually click and load or if WindowsUPdate is just ruined until I restore my image. –  user189950 Jan 14 '13 at 22:03
    
not really sure on this one I will have to check tomorrow and get back to you. –  meanbunny Jan 14 '13 at 23:00

2 Answers 2

up vote 3 down vote accepted

This could be that WSUS needs to be updated to manage Windows 8 clients. This was an issue with Windows 7 clients and WSUS and an update fixed the issue. A. Not sure that there is an update to support Windows 8 at this point but one MS forum indicates that KB2734608 addreses the issue. Later it indicates that fix is not available but points to other updates. WSUS Discussion

share|improve this answer
    
Finally got the chance to update WSUS, thanks for the tip! –  meanbunny Feb 16 '13 at 4:51

protected by slhck Jul 1 '14 at 12:21

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.