Windows 10 WSUS – 1709 to 1803 Feature Update Missing from WSUS Clients

windows 10wsus

How do I get my 1709 windows 10 agents to upgrade to 1803?
What is the KB of the "April 2018 Feature upgrade to 1803"?

I've got two wsus servers, 2012 R2 that's been servicing out network for a while now, and 2016 fresh. Both of them have updated clients to Windows 10 1709 without an issue, however I cannot seem to get 1803 to show up. If I connect the windows 10 computer to the internet directly, it finds the update.

I'm also unable to find the "Feature Upgrade to 1803" on the windows catalog site

Best Answer

For receiving the Feature Update(s) as update(s), you need to ensure that "Upgrade" category is selected in the classification tab of WSUS Server. Once done, you'll be able to see the feature update after next successful synchronisation.

Upgrade: Specifies an upgrade for Windows 10 features and functionality. Your software update points and sites must run a minimum of WSUS 4.0 with the hotfix 3095113 to get the Upgrade classification. ------------// taken from "Configure classifications and products to synchronize".

Regarding your point that 1709 was available without this being checked, I highly doubt it. Maybe, those client systems were by default installed with Windows 10 version 1709. I'd request you to check with the concerned IT Team to verify this.

Also, just for your information, you can decline those updates (~upgrades from 7/8/8.1 to 10), and you can also set the option to download updates in WSUS only when you approve them. This would probably reduce the disk-space problem on the WSUS server.

Related Solutions

Windows – WSUS clients can’t find updates

As I see a cookie warning, please follow the step there to resync; http://support.microsoft.com/kb/903262 (cloned machine ?)

Quoted from the KB;

Click Start, click Run, type cmd in the Open box, and then click OK.
At the command prompt, type net stop wuauserv, and then press ENTER.
Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
In the details pane of Registry Editor, delete the following registry entries:
    PingID
    AccountDomainSid
    SusClientId
    SusClientIDValidation
Note Windows Update Agent 3.0 adds the SusClientIDValidation value. This value was released in May 2007. The other registry entries
exist in both Windows Update Agent 2.0 and in Windows Update Agent 3.0. Exit Registry Editor. At the command prompt, type net start wuauserv, and then press ENTER. At the command prompt, type wuauclt.exe /resetauthorization /detectnow, and then press ENTER. Wait 10 minutes for a detection cycle to finish. Start the WSUS console to make sure that the clients appear in the WSUS console.

Windows 10 Update Failing On Previous WSUS Client

It sounds like you need to change Group Policy settings; that's usually how clients are pointed at the WSUS server in the first place, instead of Microsoft for updates.

Edit GP and look in Comp Config -> Admin Temp -> Win Comp -> Win Update. Start by making sure Specify Intranet... is disabled. Disabled == clients will look to MS for updates.

If GP isn't specifying an intranet updates server, then perhaps someone manually configured the clients' reg keys. Check a client's HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate to confirm.

Best Answer

Related Solutions

Windows – WSUS clients can’t find updates

Windows 10 Update Failing On Previous WSUS Client

Related Topic