question

DarkMallard-0914 avatar image
0 Votes"
DarkMallard-0914 asked DarkMallard-0914 commented

SCCM - All Win 10 Software Updates Expired

It appears that Software Updates for Windows 10 (cumulative, dynamic, servicing stack, edge, .net framework) are showing in the ConfigMgr console as expired (icon with black X). However, other updates for other Microsoft OSes and products are showing a normal status and are published to Software Center as expected. What's also odd is that it is successfully downloading/publishing updates for Win 10 1507, but any updates for any Win 10 version after that is showing as expired. I'm not sure when this started. Possibly in the last few months (we have a separate process in PDQ that installs OS updates for Win 10 if SCCM "misses" the update, so this is why it is gone unnoticed). I'm not seeing any errors in the WCM.log or wsyncmgr.log, and if I look at the WSUS console itself, I do NOT see any of the Win 10 updates beyond version 1507. When I check SUP config settings: Update Files: Download full files for all approved updates is checked Classifications, all are checked. Products, all of the Window 10 options are checked, so I "should" be getting any version of them. Sync schedule is every 1 hour WSUS Maintenance tab: Decline expired updates in WSUS according to supersedence rules is checked (I tested unchecking it to see if made any difference after the next sync. It did NOT, unfortunately). Also, Remove obsolete updates from the WSUS database is checked. So, this just seems limited to Windows 10 updates that came after version 1507. Any suggestions are appreciated!

mem-cm-generalwindows-server-update-services
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

yannara avatar image
0 Votes"
yannara answered DarkMallard-0914 commented

What build are you looking for? Is there any chance that you utilize only a build which is actually expired already? I don't witness the same behavior. Maybe double check SUP properties and let updates go to expire in 6-12 months, and not immidiately? Also you might want to refresh your sup by disabling win10 products, sync, enable win10 products, and re-sync again. Check also that your wsus sync ends succesfully.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks, yannara. It was the simple refresh that I thought I had done already that fixed it: disabled Win10 products, let it sync, enable Win10 products, let it sync. Took hours, and all the updates came in. Thanks!

0 Votes 0 ·
Amandayou-MSFT avatar image
0 Votes"
Amandayou-MSFT answered

Hi @DarkMallard-0914,

What's also odd is that it is successfully downloading/publishing updates for Win 10 1507

Please check if the update product tab is windows 10 LTSB, if yes, LTSB CU update is supported at present, and we could download and deploy it to the LTSB client.

82331-3293.png

Based on my test, my environment could sync Windows 10 updates that came after version 1507.

82341-3294.png

Kindly check wsyncmgr.log again and synchronization status, refer to the following picture:

82323-3295.png
82324-3296.png



If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



3293.png (4.6 KiB)
3294.png (43.6 KiB)
3295.png (80.6 KiB)
3296.png (153.0 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.