WSUS (Windows 2012 R2) - Windows 10 V1809 Clients Not Pulling Updates

Question

Hello,

I’ve recently set up our first WSUS server on ‘Windows 2012 R2’.

I know that clients are being pointed to the server correctly by our ‘Group Policy Object’ because they are slowly registering in the console.

However, the ‘Windows 10’ computers don’t seem to be reading/pulling updates from the WSUS server.

I have not approved any updates in WSUS relating to ‘Windows 10 Version 1903’ yet.

Any help gratefully received.

Kind regards,

Glen

Answer 1

Hi GlenV-4078,

Thanks for your posting on Q&A.

First, I noticed that your client's reporting status was incorrect. To be sure, the updates detected by the client do not come from WSUS. We could check the client's default update source with the following script.

Open the PowerShell as an administrator and enter the following scripts:

$MUSM = New-Object -ComObject "Microsoft.Update.ServiceManager"  
   
$MUSM.Services | select Name, IsDefaultAUService  

 

In addition, we could apply the following policy on the clients to prevent getting updates from Windows Update. After the client applies the below group policy, the client default update source is WSUS.

[Do not allow update deferral policies to cause scans against Windows Update]
(Location: Group Policy Management Editor\Policies\Administrative Templates\Windows Components\Windows Update)

Reference picture:

Here is a link about the dual scan for your reference:
https://learn.microsoft.com/en-us/archive/blogs/wsus/demystifying-dual-scan

Regards,
Rita

Answer 2

Sounds like dual scan - https://www.ajtek.ca/wsus/dual-scan-making-sense-of-why-so-many-admins-have-issues/

You should also visit my 8 part blog series on How to Setup, Manage, and Maintain WSUS.