Failed To Find Updates With Error Code 800b0001 Windows 8
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 15:00:21 GMT by s_ac15 (squid/3.5.20)
Pro Computer I have number of Windows 8 joined to a domain that also has a WSUS (Windows Server Update Services) to manage all internal Windows updates. All ran well except for one thing, none of these Windows 8 machines windows update error 800b0001 windows 7 x64 were able to run Windows Updates. They were all getting the same message with an
800b0001 Windows 7
error code 800B0001. Since the update went through fine if I go with the option "check online for updates from Windows Update", I felt windows update 800b0001 wsus that the problem should reside on the server side instead of on these Windows 8 machines. Turns out, it failed because Windows 8 uses a new version of Windows update agent that's not supported by WSUS 3.0 SP2. http://answers.microsoft.com/en-us/windows/forum/all/windows-update-fails-with-code-800b0001-when/380996d7-0087-4bd4-883f-038d5f2f9798 It requires a special update (KB2734608) that lets WSUS server to provide the updates to computers that are running Windows 8 or Windows Server 2012. Download the update (about 30MB) and install it on WSUS. It doesn't require a reboot but to be safe, reboot the server if possible. Once it's all set, run the Windows updates again on these Windows 8 computers. In my case, it all went well after the update. If for some reason it still http://www.nextofwindows.com/fix-windows-update-error-800b0001-on-windows-8-pro-computer doesn't fix your problem, you can try the following Group Policy to bypass WSUS when it comes to Windows Update. Run gpedit on a command prompt window, navigate down to Computer Configuration / Administrative Templates / System Double-click "Specify settings for optional component installation and component repair", click Enable radio, and check the option "Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS)" Click OK to save all settings. Next time when you run Windows Update, it will bypass internal WSUS server and go talk to Microsoft Update directly. During the troubleshooting and research to fix this specific problem, I came across a few other things that I thought it would be good to share at the same time. If Windows Updates are not through WSUS or still failed even with the option "Check online for updates from Windows Update", that's probably because Windows Update service is having difficulty determining the cryptography service provider on your computer or simply a file required by Windows Update is corrupted. First, run the command sfc to quickly repair any corrupted Windows system files, if any. sfc /scannow If it didn't resolve the problem, try these following commands to repair the cryptography store. net stop wuauserv rd /s %SystemRoot%\SoftwareDistribution net start wuauserv cd %SystemRoot%\system32 net stop cryptsvc rename catroot2 catroot2.old net start cryptsvc Then, run dism /online /cleanup-image /restorehealth I
caused by Windows 8 using a newer update client than WSUS SP2 is aware of, consequently the client doesnt trust the server. Despite having KB2720211-x64 installed, still see this error on Windows 8 and Windows 2012 machines in my SCCM lab. Seems this recent https://ccolonbackslash.com/2012/09/13/code-800b0001-windows-update-ran-into-a-problem-on-windows-8-and-2012-when-using-wsus-or-wsus-with-sccm/ KB solves the issue: http://support.microsoft.com/kb/2734608 If I understand it correctly the issue is to related to the signing of the updates with a certificate that is not approved by Win8/2012 update client. This issue is corrected during the WSUS resync/reindex after the above update is applied. Once the sync is complete, before you try to apply the updates to any new clients be sure to stop the local wu service client on the windows8/2012 client and delete the software distribution windows update folder in C:\Windows. Be sure to start the Windows Update service again before you try to check for updates and then run the update installation again. Instructions below: Open an administrative command prompt on the affected computer Type the following: net stop wuauserv rd /s %windir%\softwaredistribution\ net start wuauserv In my case i'd already tried to publish the SCCM client before i did the update and before i applied the SP1/CTP for SCCM and ran into problems even after the windows update error above because the SCCM client is not resigned during the WSUS update. As i had not yet published the latest version of the SCCM client that came with SCCM SP1/CTP to WSUS, i published it AFTER applying KB2734608, to do this you go to Sites, Client Installation Settings and Software Update-Based Client Installation and it will tell you there is a new client available, agree, then apply and it will be correctly signed and will install on Server 2012 and Windows 8. SO if you publish a version of the client through WSUS before you do the KB update and resync, it doesnt get re-signed, only if you distribute it AFTER the update. ( I think…..) Phew. Like this:Like Loading... Related Uncategorized SCCM, Server 2012, Windows 8, WSUS ← Cannot install Server 2012 - The file may be corrupt or missing. Errorcode:0x80070570 HA Exchange 2010 two All-In-One servers in a DAG, CAS arrays, Windows NLB….. - confusion andsolution → 5 responses to “"Code 800B0001 Windows update ran into a problem" on Windows 8 and 2012 when using WSUS or WSUS withSCCM” Pingback: Windows 8 / Server 2012 Updates from WSUS fail with Code 800B0001 Pingback: How To Fix Code 800b0100 Windows Update Surface Errors - Windows Vista, Windows 7 & 8 Pingback: How To Fix Error Code 800b0001 Wsus Errors - Windows Vista, Windows 7 & 8 Pingback: How To Fix 800b0001 2012 Errors - Win