September month update showing expired in SCCM

Md. Rubiat Haque 151 Reputation points
2022-09-27T13:24:52.44+00:00

Hello everyone,

I have a SCCM server and all the roles are installed in one server. Recently 3-4 days ago, when I was going to deploy current month security update, I saw that maximum number of current month update showing expired. Then I checked the superseded rules and I saw that Immediately option was on. Then I changed it and run synchronization updates. But, still the console is showing that particular updates is expired. So, how to fix it that means I want to deploy these updates so how to recover these updates and make it normal from expired? Thanks in advance.

Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
1,000 questions
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
923 questions
0 comments No comments
{count} votes

7 answers

Sort by: Most helpful
  1. AllenLiu-MSFT 42,026 Reputation points Microsoft Vendor
    2022-09-28T02:37:00.81+00:00

    Hi, @Md. Rubiat Haque

    Thank you for posting in Microsoft Q&A forum.

    We may recover the expired updates with the steps:

    1. In the WSUS administrative console, click Updates and then click All Updates.
    2. Change Approval to Declined and click Refresh.
    3. In the list of updates, select one or more declined updates that you want to reinstate or recover.
    4. Right click on the update and select Approve. In the Approve Updates dialog, click OK to re-apply the default Not Approved approval status. The update will show in the list as Not approved instead of Declined.
    5. In SCCM console, navigate to \Software Library\Overview\Software Updates, right-click on the All Software Updates node, select Synchronize Software Updates to initiate a manual WSUS sync, click on OK to start the sync.
    6. Let’s wait for WSUS sync to complete so that you can see all the expired updates back in the SCCM admin console.

    For more details, you may refer to the article:
    https://www.anoopcnair.com/sccm-learn-how-to-recover-expired-updates-confi/
    (Please Note: Since the website is not hosted by Microsoft, just for your reference.)


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    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.

    1 person found this answer helpful.
    0 comments No comments

  2. Sarfraz Aslam 166 Reputation points
    2022-09-29T06:48:32.303+00:00

    Hi,
    My query is same as stated in the question, however by following @AllenLiu-MSFT comment, i have successfully reinstated declined updates from WSUS console, now Sep-2022 superseded updates are showing in All Updates -> Any Except declined, secondly i have changed the Supersedensce Rules also. After that Resync Software updates manually through SCCM console.
    Now i am able to view only one superseded update i.e.
    2022-09 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5017308)

    but not the remaining updates, i can see remaining updates in WSUS console but not in SCCM console
    2022-09 Cumulative Update for Windows 10 Version 21H1 for x64-based Systems (KB5017308)
    2022-09 Cumulative Update for Windows 10 Version 20H2 for x86-based Systems (KB5017308)
    2022-09 Cumulative Update for Windows 10 Version 20H2 for x64-based Systems (KB5017308)

    The difference i noticed in WSUS console is in snapshot.

    245839-wsus1.jpg
    245951-wsus2.jpg
    245933-wsus3.jpg

    0 comments No comments

  3. AllenLiu-MSFT 42,026 Reputation points Microsoft Vendor
    2022-09-29T09:01:39.17+00:00

    Hi, @Sarfraz Aslam

    That's interesting. But in my test lab, I did the same thing, the four updates recover to the console without any issue, you may try to search the KB like me to see if you can get the result:
    245917-1.png

    But since the KB5017308 is replaced by KB5017380, why do we deploy the KB5017380 directly?
    By the way, the superseded update can not deploy to clients by SCCM.


  4. Sarfraz Aslam 166 Reputation points
    2022-09-30T05:48:42.037+00:00

    Hi,

    Just to update. Today i found those missing updates in SCCM console automatically. Didn't do any thing except above steps.

    Thanks @AllenLiu-MSFT for assistance.


  5. Wayne Jones 1 Reputation point
    2022-09-30T18:07:15.153+00:00

    From Reddit....this is the fix that worked for me. WSUS ---> Move update to Not Approved in WSUS ---> Make sure SUP in SCCM is set to not expire superseded updates immediately ---> Sync SCCM SUP.

    246488-udatesrestored.jpg