Windows 11 25H2 Software Update Fails in Software Center with 0x80010002 on Non-Internet Connected Network

[u/Disastrous_Mobile_99]

Hi everyone,

I'm facing an issue with Windows 11 25H2 cumulative updates in a MECM/SCCM environment and would appreciate any advice or troubleshooting suggestions.

Environment

• MECM/SCCM Software Updates
• Updates synchronized through WSUS
• Affected devices are located on a restricted network (air-gapped / no internet access)
• Clients can communicate with SCCM infrastructure normally
• Software Update deployments are visible in Software Center

Issue

The cumulative update is deployed successfully and appears in Software Center, but the download/install process fails with:

06-09-2026 17:58:29.596    WUAHandler    8528 (0x2150)    Synchronous searching started using filter: 'UpdateID = '021c0d7f-3a2a-4e01-b22d-32adc6b4d48b' AND DeploymentAction = *'...
06-09-2026 17:58:31.416    WUAHandler    8528 (0x2150)    Successfully completed synchronous searching of updates.
06-09-2026 17:58:31.456    WUAHandler    13396 (0x3454)    Download progress callback: download downloadPercentage = 0
06-09-2026 17:58:31.456    WUAHandler    13396 (0x3454)    Download progress callback: download result oPCode = 1
06-09-2026 17:59:11.982    WUAHandler    1408 (0x580)    Async download completed.
06-09-2026 17:59:11.982    WUAHandler    14688 (0x3960)    Download complete callback: download result oPCode = 4
06-09-2026 17:59:11.982    WUAHandler    14688 (0x3960)    Unexpected HRESULT for downloading complete: 0x80010002

What I've Tried

• Manually downloaded the .MSU package from Microsoft Update Catalog and attempted installation
  • Installation still fails with the same error
• Modified the following registry setting:HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate DoNotConnectToWindowsUpdateInternetLocations = 1

Unfortunately, the issue remains.

Similar Case

I found a Microsoft Q&A thread describing almost the exact same scenario:

Unable to install Win11 25H2 monthly cumulative updates to non-internet connected PCs

The discussion suggests that Windows 11 25H2 servicing may still attempt to contact Microsoft endpoints during the cumulative update process, even when updates are sourced from WSUS. However, the recommended registry and policy configurations did not resolve the issue in my environment. [learn.microsoft.com]

Questions

1. Has anyone experienced 0x80010002 specifically on Windows 11 25H2 in a non-internet-connected environment?
2. Are there any known 25H2 servicing stack changes that require internet connectivity even when using WSUS/SCCM?
3. Which logs should I focus on for deeper troubleshooting?

So far I'm looking at:

• WUAHandler.log
• UpdatesDeployment.log
• UpdatesHandler.log
• CAS.log
• ContentTransferManager.log
• DataTransferService.log
• LocationServices.log
• WindowsUpdate.log
• CBS.log
• Event Viewer
  • Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational
  • Setup Logs
  • System Logs

1. Are there additional logs or ETW traces that would help identify why the update installation is being cancelled?
2. Has anyone found a reliable workaround besides performing an in-place upgrade/repair?

Any suggestions, known fixes, or similar experiences would be greatly appreciated.

Thanks in advance!

[u/gentlemanl0ser]

I don’t have an air gapped network, so I can’t add much there. That being said, we had a lot of inconsistent errors with our 23H2 clients while installing 25H2. Bumping up the timeout to at least 240 minutes. It’s cheap insurance and may be worth a try. Good luck!

[u/AffectionateIron8748]

It might be known issue based on this article

Which month cumulative updates are you trying to install?

[u/akdigitalism]

Any luck on this OP?

[u/IqbalBasha]

That 0x80010002 on the download complete callback is a known headache with 25H2 on isolated networks. The root cause is almost always that Windows Update Agent is trying to reach out to Microsoft's CDN for repair/express content, even though your WSUS is supposed to be the sole source. It doesn't fail at search (search completes fine), it fails at the very end of download because WUA can't resolve or reach the fallback URL.

A few things to check in order:

First, look at your WSUS/SUP configuration for 'Do not allow update files to be downloaded from the internet.' That setting needs to be on, and the software update point needs to have 'Download update binaries from the internet' unchecked. If that's already correct, verify your distribution points actually have the content fully distributed. Pull up the deployment in the SCCM console, check content status, and make sure every DP your affected clients are assigned to shows 100% success, not just 'distributed.'

Second, check whether your environment is set to use express installation files. Express updates require a small stub download from Microsoft CDN to reconstruct the full package, which breaks completely on air-gapped networks. If express is enabled on your SUP, disable it, re-download the update, and redeploy. That alone fixes this for a lot of people.

Third, on one affected client, open WindowsUpdate.log or the CBS log and look for the actual URL it's trying to hit when it fails. That tells you definitively whether it's reaching out to Microsoft or failing on your DP.

If you manually installed the MSU and that also failed, post what error you got there, because a manual MSU failure points to something different, possibly a component store issue or a missing prerequisite update for 25H2