Share via

Problem downloading updates software update deployment(SCCM and ADR) specfiy Windows 11 build 25 H2

SSE@TUE 360 Reputation points
2026-06-05T07:58:30.3466667+00:00

Hi,

I'm in the process of deploying windows updates to Windows Clients (Windows 11 build 25H2) Windows servers(2019,2022,2025) in my environment with SCCM and ADRs and most of the client computers have installed updates just fine however around 50 or so client computers are not installing updates and the updates are not getting downloaded. When I click to install updates it just stays stuck at 0% downloading and never installs until eventually it times out

My Boundary and Boundary Groups

the updates have been distributed to the DP servers. The boundaries are configured to include the clients in the scope. All of my boundary groups are set up with the Active Directory site only.

We have the following IP Range

192.168.0.0, 172.20.0.0, 172.10.0.0. 172.40.0.0

But I set my My Boundary and Boundary Groups with the Active Directory site only.

Is that the my issue?

Should/Could I create or add some new Boundary with IP address Range(what we have see above IP Range) additionally to my Active Directory site?

Could you please help me?

Regards

Microsoft Security | Intune | Configuration Manager | Deployment
0 comments No comments

1 answer

Sort by: Most helpful
  1. Rayyan Fawad 0 Reputation points
    2026-06-05T09:54:20.6966667+00:00

    Yes, that is exactly your issue. When your Configuration Manager (SCCM) clients hit a 0% downloading snag, it means they are successfully talking to the Management Point to receive their policy, but they cannot find a valid Distribution Point (DP) to pull the actual Windows 11 build 25H2 update binaries from.

    Relying solely on an Active Directory site boundary frequently fails if your network subnets aren't perfectly mapped to your AD sites or if clients are using VPNs and remote subnets. Because you have distinct IP ranges (192.168.0.0, 172.20.0.0, etc.), you should immediately create explicit IP Address Range boundaries for each of them in your SCCM console. Once those boundaries are created, add them directly to your active Boundary Group and verify that your target Distribution Points are explicitly linked to that group under the References tab. This ensures that when the 50 failing machines request the content, SCCM can successfully map their current IP to a local DP hosting the package, which will instantly break the 0% download lock.

    Was this answer helpful?


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.