Server 2012 R2 no Updates via MECM Software Center

Philipp 21 Reputation points
2022-07-29T10:11:36.793+00:00

Hi all,

Updates are not offered in software center it says: "No items found".

ScanAgent.log says

CScanAgent::ScanCompleteCallback - failed at OnScanComplete with error=0x87d00631 ScanAgent 7/27/2022 4:21:50 PM 7540 (0x1D74)

The error code suggests sfc /scannow or dism could repair this (according to https://answers.microsoft.com/en-us/windows/forum/all/i-get-error-0x8024401c-when-trying-to-update/07ea1f0e-e1fe-4431-9392-253d2a94a68e). But neither do, unfortunately. I was able to resolve "CBS Manifest Corruption: 161", by downloading the KB files mentioned in the log files and pointing dism to it. But one corruption still won't repair: Repair failed: Missing replacement payload.

CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-wpfcorecomp.resources_31bf3856ad364e35_6.3.9600.17226_nl-nl_5c2110e7ed1cde21, file PresentationCore.resources.dll from any local source

It seems to have something to do with the dutch Language Pack. I installed this LP on a different Server 2012 R2 System and copied the files over to use with dism to no avail. Can someone
help me out maybe by gathering the necessary files to resolve this single left corruption?

Any help is much appreciated

Kind Regards

Microsoft Security | Intune | Configuration Manager | Updates
Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

Accepted answer
  1. AllenLiu-MSFT 49,316 Reputation points Microsoft External Staff
    2022-08-02T06:45:15.607+00:00

    Hi, @Philipp

    Thanks very much for your feedback. We're glad that the problem is solved now. Here's a short summary for the problem, we believe this will help other users to search for useful information more quickly.

    Problem/Symptom:
    Server 2012 R2 updates not offered in software center, it shows: "No items found".
    ScanAgent.log says:
    CScanAgent::ScanCompleteCallback - failed at OnScanComplete with error=0x87d00631
    WUAHandler.log says:
    OnSearchComplete - Failed to end search job. Error = 0x8024401c.

    Solution/Workaround:
    1, stop the Windows Update service by running the following command: net stop wuauserv
    2, Rename the C:\Windows\SoftwareDistribution folder to C:\Windows\SoftwareDistribution.old
    3, Start the Windows Update service by running the following command: net start wuauserv
    4, Start a software update scan cycle


    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.

    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. AllenLiu-MSFT 49,316 Reputation points Microsoft External Staff
    2022-08-01T06:59:23.467+00:00

    Hi, @Philipp

    Thank you for posting in Microsoft Q&A forum.

    Have we also checked WUAhandler.log?
    Is this a specific issue with server 2012 R2?


    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.

    0 comments No comments

  2. Philipp 21 Reputation points
    2022-08-01T08:04:16.827+00:00

    It's specific to this machine as other machines do not have this issue. Is there a way for someone to upload the files this machine is missing so I can point dism to it so it can repar this corruption?

    WUAhandler.log is not much help:
    Its a WSUS Update Source type ({71A45E99-1083-4CBA-BA3A-8170E0E7EB96}), adding it. WUAHandler
    7/31/2022 5:00:19 PM 9148 (0x23BC)
    Enabling WUA Managed server policy to use server: https://*****.**:8531 WUAHandler
    7/31/2022 5:00:19 PM 9148 (0x23BC)
    Waiting for 120 seconds for Group Policy to notify of WUA policy change... WUAHandler
    7/31/2022 5:00:19 PM 9148 (0x23BC)
    Waiting for 30 secs for policy to take effect on WU Agent. WUAHandler
    7/31/2022 5:00:27 PM 9148 (0x23BC)
    Added Update Source ({71A45E99-1083-4CBA-BA3A-8170E0E7EB96}) of content type: 2 WUAHandler
    7/31/2022 5:00:57 PM 9148 (0x23BC)
    Scan results will include all superseded updates. WUAHandler
    7/31/2022 5:00:57 PM 9148 (0x23BC)
    Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler
    7/31/2022 5:00:57 PM 9148 (0x23BC)
    Async searching of updates using WUAgent started. WUAHandler
    7/31/2022 5:00:58 PM 9148 (0x23BC)
    Async searching completed. WUAHandler
    7/31/2022 5:01:02 PM 7080 (0x1BA8)
    OnSearchComplete - Failed to end search job. Error = 0x8024401c. WUAHandler
    7/31/2022 5:01:02 PM 9148 (0x23BC)
    Scan failed with error = 0x8024401c. WUAHandler
    7/31/2022 5:01:02 PM 9148 (0x23BC)

    0 comments No comments

  3. Philipp 21 Reputation points
    2022-08-01T13:00:34.48+00:00

    Replacing this file amd64_microsoft-windows-wpfcorecomp.resources_31bf3856ad364e35_6.3.9600.17226_nl-nl_5c2110e7ed1cde21\PresentationCore.resources.dll under winsxs folder got rid of the last corruption but that didn't change anything with the updates missing issue.

    Afterwards this resolved the issue of not getting updates:

    Stop the Windows Update service by running the following command:

    net stop wuauserv
    Rename the C:\Windows\SoftwareDistribution folder to C:\Windows\SoftwareDistribution.old.

    Start the Windows Update service by running the following command:

    net start wuauserv
    Start a software update scan cycle.

    0 comments No comments

  4. Limitless Technology 39,931 Reputation points
    2022-08-02T07:22:34.347+00:00

    Hi there,

    Try to uninstall SCCM client and reinstall it and initiate the Machine policy & Retrieval cycle. Check after sometime if you can see any improvements.

    Examine ClientIDManagerStartup.log, ClientLocation.log, LocationServices.log and ccmmessaging.log.

    Check if the client can find your ConfigMgr server by running nslookup against it.

    I hope this information helps. If you have any questions please let me know and I will be glad to help you out.

    ------------------------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept it as an answer--

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.