JUly 2026 patches deployed workstation lastweek . but they are still showing an Unknown status in the SCCM server.

Ramesh Raju Nuni 0 Reputation points
2026-07-27T04:53:02.8133333+00:00

July patches deployed workstation 8 days back . but they are still showing an Unknown status in the SCCM server.

SCCM 2207 with SQL DB.-- All site component is green.

SCAN AGENT AND LOCATIONSERIVCE AND WUHNADLER ERROR IS BELOW

only three component is red:

SMS_SERVICE_CONNECTOR ( online) &SMS_AD_SYSTEM_DISCOVERY_AGENT ( offline) & SMS_AD_SYSTEM_DISCOVERY_AGENT ( online)

Log Error

SCANAGENT LOG:

ScanJob({DE9BBB65-3D01-45E3-83B0-3C6D31EE443E}): CScanJobManager::OnScanComplete- Scan has failed, scan request will be pending for scan retry cycle. ScanAgent 7/27/2026 10:30:23 AM 9840 (0x2670)

CScanAgent::ScanCompleteCallback - failed at OnScanComplete with error=0x87d00631 ScanAgent 7/27/2026 10:30:23 AM 9840 (0x2670)

WUAHHANDLER:LOG:

Added Update Source ({89ECECF3-6E08-46D1-BFB9-729ED6C31737}) of content type: 2 WUAHandler 7/27/2026 10:30:05 AM 13640 (0x3548)

Scan results will include all superseded updates. WUAHandler 7/27/2026 10:30:06 AM 13640 (0x3548)

Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 7/27/2026 10:30:06 AM 13640 (0x3548)

Async searching of updates using WUAgent started. WUAHandler 7/27/2026 10:30:06 AM 13640 (0x3548)

Async searching completed. WUAHandler 7/27/2026 10:30:23 AM 26852 (0x68E4)

OnSearchComplete - Failed to end search job. Error = 0x80244007. WUAHandler 7/27/2026 10:30:23 AM 13640 (0x3548)

Scan failed with error = 0x80244007. WUAHandler 7/27/2026 10:30:23 AM 13640 (0x3548)

ScanAgent.log 0x80244007 WSUS returned invalid/incomplete SOAP response Corrupt WSUS metadata, excessive updates, IIS/WSUS communication problems, malformed SOAP response. [learn.microsoft.com], [learn.microsoft.com]

WUAHandler.log 0x80244010 WSUS exceeded maximum server trips / too many updates returned WSUS catalog is too large, scan timeout, WSUS performance issues, clients making excessive round trips. [woshub.com], [thewindowsclub.com]

ScanAgent.log 0x87D00631 SCCM scan failed because WUA scan failed Secondary error; SCCM is reporting the underlying WUA/WSUS failure. [learn.microsoft.com], [learn.microsoft.com]

ScanAgent.log Sources are current, but Invalid. TTL is also invalid. Metadata from WSUS is corrupt or incomplete SUP/WSUS metadata synchronization issue.

ScanAgent.log No CatScan history exists

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Gupta, Nimit 0 Reputation points
    2026-07-29T08:07:44.6766667+00:00

    Below fix seems to do the trick for us

    Server-Side Fix (WSUS Limits)  Error = 0x80244007. WUAHandler

    • Open an elevated Command Prompt on your WSUS server and navigate to %programfiles%\Update Services\WebServices\ClientWebService.
    • Run takeown /f web.config and grant permissions using icacls web.config /grant administrator:(F).
    • Open web.config in Notepad and update the limits to higher values (e.g., maxInstalledPrerequisites to 800 and maxCachedUpdates to 44000).
    • Run IISReset in the command promp

    Was this answer helpful?

    0 comments
  2. Chen Tran 12,750 Reputation points Independent Advisor
    2026-07-27T06:27:19.5533333+00:00

    Hello Ramesh,

    Thank you for posting question on Microsoft Windows Forum!

    Based on the issue description as well as the provided logs. The plausible explanation to this symptom is that the SCCM client cannot communicate properly with the WSUS server, causing the software update scan to fail. Consequently, the installed patches are unable to report their status back to the SCCM server.

    Since the WUA scan is failing, SCCM cannot determine compliance. That is the reason of why your workstations still show Unknown even though patches were deployed 8 days ago. The suggestion is to check WSUS Synchronization. On the SCCM server, verify that the SUP (Software Update Point) sync is successful by looking at wsyncmgr.log for sync errors.

    Another suggestion is to verify WSUS health by running this command wsusutil.exe checkhealth . Then inspect Application Event Log for WSUS events.

    Another point worth mentioning here is to ensure the network connectivity between the client and the WSUS server, and verify that no firewalls or network devices are blocking SOAP communication on the relevant ports (usually 8530 or 8531).

    You can follow the below link to troubleshoot the error code 0x80244007.

    Hope the above information is helpful!

    Was this answer helpful?

    0 comments

Your answer

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