Deploying software and updates using Configuration Manager
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.