SCCM Updates Post Scan Error: 0x80248009

Question

Hello All

Request your help with the following

Env: - MECM - 2303 On-prem - Single Primary with DB hosted on Win Server 2019 - 1 SUP hosted on Primary - clients - win10 22h2 - SCCM client: 5.00.9106.1022 - WUA: 10.0.19041.3031

Issue: While testing Sep-2023 patches (Rollup/.Net/Office/AdobeReader) on a few Win10 PCs (~10), wuahandler logs successful install for all patches with Reboot Pending for the rollup/.Net as expected However, immediately following the above, it logs 'Scan failed with error: 0x80248009' The data store is missing info or has a reference to missing license terms, file, localized property or linked row

No reboot is triggered

<<wuahandler.log Update 1 (3165a6a3-cf72-41d1-8e9c-7a3627f7835e) finished installing (0x00000000), Reboot Required? No WUAHandler 9/15/2023 10:27:06 PM 9452 (0x24EC) Update 2 (409ff616-4aa5-4331-876a-1a973831e1ed) finished installing (0x00000000), Reboot Required? No WUAHandler 9/15/2023 10:29:29 PM 13712 (0x3590) Update 3 (4aec4d66-a06c-4544-9f79-55ace822e015) finished installing (0x00000000), Reboot Required? Yes WUAHandler 9/15/2023 10:50:42 PM 15308 (0x3BCC) Update 4 (531c5576-e0bb-4755-9ead-d69759d8c57c) finished installing (0x00000000), Reboot Required? No WUAHandler 9/15/2023 10:52:16 PM 16996 (0x4264) Update 5 (54b3c433-6f79-4071-b910-e2ab8aea984b) finished installing (0x00000000), Reboot Required? No WUAHandler 9/15/2023 10:53:56 PM 18900 (0x49D4) Update 6 (56fa2bf8-49fa-4d76-a6f0-652b6f975c84) finished installing (0x00000000), Reboot Required? No WUAHandler 9/15/2023 10:55:15 PM 19504 (0x4C30) Update 7 (6088844a-be5d-4f1d-82de-cffe7cf0b91d) finished installing (0x00000000), Reboot Required? No WUAHandler 9/15/2023 10:56:42 PM 22032 (0x5610) Update 8 (b4808387-8020-4685-8d60-30eadf344849) finished installing (0x00000000), Reboot Required? Yes WUAHandler 9/15/2023 10:58:07 PM 19936 (0x4DE0) Update 9 (b894a74c-dae2-4603-8a8b-120e9dd48f55) finished installing (0x00000000), Reboot Required? No WUAHandler 9/15/2023 10:59:12 PM 17140 (0x42F4) Async install completed. WUAHandler 9/15/2023 10:59:12 PM 17140 (0x42F4) Installation of updates completed. WUAHandler 9/15/2023 10:59:12 PM 9484 (0x250C) Scan results will include all superseded updates. WUAHandler 9/15/2023 10:59:12 PM 9484 (0x250C) Search Criteria is ((DeploymentAction=* AND Type='Software' AND CategoryIDs contains '25AED893-7C2D-4A31-AE22-28FF8AC150ED') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'B3C75DC1-155F-4BE4-B015-3F1A91758E52') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains '2DBD670B-6EB7-92BF-A93E-C273CB3B19BF')) WUAHandler 9/15/2023 10:59:12 PM 9484 (0x250C) Async searching of updates using WUAgent started. WUAHandler 9/15/2023 10:59:12 PM 9484 (0x250C) Async searching completed. WUAHandler 9/15/2023 10:59:14 PM 13476 (0x34A4) OnSearchComplete - Failed to end search job. Error = 0x80248009. WUAHandler 9/15/2023 10:59:14 PM 10252 (0x280C) Scan failed with error = 0x80248009. WUAHandler 9/15/2023 10:59:14 PM 10252 (0x280C)

I have attempted the following for it to make progress after the above: Re-Scan Cycle does not help

Revaluate SU Deployments does not help

Of the Sep-2023 patches, I created another SUG with only office patches. Same error, but upon rescan the error cleared and Compliant reported

Did not help -> SCCMUpdatesStore.RefreshServerComplianceState()

Software Center shows both Rollup/.Net in Failed state

To test SU component health, I pushed the latest Edge patch and it installed fine on all 10

What works: After 0x80248009, if I remove PC from collection, pull machine policy, then add back the PC to collection, the PC then progress immediately and prompts for the usual reboot and post reboot, reports 'Compliant', as expected

• Recent changes
  • upgraded to 2303 3 weeks ago; including clients
  • migrated SCCM to new Server 2019 server (using backup/restore) 2 weeks ago
  • health check is fine
    • software distribution
    • Edge patch deployment is fine as tested today
    • this is the first Patching cycle post upgrade / migration to Server 2019 (all was good with Aug-2023 patching)

Please advise - Thanks

Answer 1

Hi, @sccm72

Thank you for posting in Microsoft Q&A forum.

Clients locate and use SUP based on boundaries and boundary groups.

So double check if your boundaries and boundary groups are misconfigured?

And make sure the SUP is healthy, we may check WCM.log and WSUSCtrl.log to see if there any error?

---

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 "Add comment".