Additional note on KB 2734608 regarding WSUS, Windows 8 and Windows Server 2012

Artikel
09/05/2012

As we mentioned yesterday, the Windows Server Update Services (WSUS) team has released Knowledge Base article 2734608. This update lets servers running Windows Server Update Services (WSUS) 3.0 SP2 provide updates to computers that are running Windows 8 or Windows Server 2012.

If you have previously applied this update then there are no additional steps to take. Since this KB was taken offline due to backend issues, there are no changes to the download packages themselves. All customers though should be aware of the following steps described in the “Known Issues” section of this KB:

If you have Windows 8 or Windows Server 2012 clients that synchronized with WSUS 3SP2 before you applied this update, wait for the update to be applied to the WSUS servers, and then follow these steps:

On the affected client, open cmd.exe in elevated mode.
Type the following commands. Make sure that you press Enter after you type each command:

Net stop wuauserv
rd /s %windir%\softwaredistribution\
Net start wuauserv

For more details on what is included in this KB, please go to: https://support.microsoft.com/kb/2734608

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter :

The Forefront Server Protection blog: https://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : https://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : https://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: https://blogs.technet.com/b/isablog/
The Forefront UAG blog: https://blogs.technet.com/b/edgeaccessblog/

Comments

Anonymous
January 01, 2003
I'm having an issue with WSUS 4.0 and Hyper-V Server 2012. Maybe I'm way off base, but it seems like it could be related to this blog post. I've migrated my clients to WSUS 4.0 and all but two Hyper-V 2012 Servers are working great. These two server core based servers show up in WSUS, but then fail to report or obtain further updates. I've tried all the advice in this blog post and comments regarding stopping the service on the affected server, removing the directory and registry entries. When I start the service back up, it shows up in my WSUS server list, but never reports its list of updates.I see the following in the log files on the two affected servers:Windows Update Client failed to detect with error 0x8007000eI never had this issue running Hyper-V Server 2008 R2. It always obtained updates fine. I also have other full installations of Server 2012 with the GUI that are obtaining updates from the WSUS 4.0 server fine. Why doesn't the windows update function want to work properlly in server core?
Anonymous
January 01, 2003
Here is some PowerShell code, which achieves similar results:Stop-Service -Name wuauserv;Remove-Item -Path $env:windirsoftwaredistribution -Recurse;Start-Service -Name wuauserv;
Anonymous
September 06, 2012
Is it possible to update the WSUS-Console with this update? I always get error 1603. Without it i see all my Windows 8 Clients as Windows XP. On the Console on the WSUS-Server itself they show up correctly as Windows 8
Anonymous
September 11, 2012
The comment has been removed
Anonymous
October 17, 2012
Two quick things:Jurgen: Yes, you can apply this to console-only workstations (or servers) and it does indeed fix up the XP display issue you've mentioned.J.C.: What do you do when removing the softwaredistribution folder has no effect? Server Core 2012 is still throwing 0x80246003 errors, along with detecting a Silverlight hotfix that doesn't even apply to Server Core 2012. Is there a file and database version reference anywhere that one can use to determine if KB2734608 was even successfully applied?
Anonymous
October 17, 2012
Figured I'd answer my own question.The three commands listed above weren't enough. After the second command (the "rd /q /s"), use regedit to remove HKLMSoftwareMicrosoftWindowsCurrentVersionWindowsUpdate, then follow that with the "net start wuauserv". That resolved the 0x80246003 error on multiple Server Core 2012 hosts for us.Thus, the steps (in our case) were:net stop wuauservrd /q /s %windir%softwaredistribution Use regedit to delete HKLMSoftwareMicrosoftWindowsCurrentVersionWindowsUpdate net start wuauserv This only applies to Server 2012 (or Windows 8, most likely) hosts that had registered with the WSUS host prior to the KB2734608 patch having been applied.
Anonymous
October 29, 2012
When will KB2734608 provided in WSUS itself?
Anonymous
January 28, 2014
Lains post worked for me with exception, noted on step 2net stop wuauserv rd /q /s %windir%softwaredistribution ***** this errored out for me in powershell, I went to c:windows and manually deleted the softwaredistribution folder Use regedit to delete HKLMSoftwareMicrosoftWindowsCurrentVersionWindowsUpdate net start wuauserv wuauclt.exe /updatenow check the windows update log in c:windowswindowsupdate.txt to see if you are ok now
Anonymous
May 26, 2014
where should I enter these commands.On WSUS server or WIn 8 Clients ?
1. net stop wuauserv

2. rd /q /s %windir%softwaredistribution

3. Use regedit to delete HKLMSoftwareMicrosoftWindowsCurrentVersionWindowsUpdate

4. net start wuauserv

Any please give me answer as my win 8 clients not receiving updates.

Freigeben über

Additional note on KB 2734608 regarding WSUS, Windows 8 and Windows Server 2012

Comments

Zusätzliche Ressourcen