KB5034203 and newer updates are causing caching issues in Windows 10 21H2 and 22H2
Systems with DHCP Option 235 are most likely to get affected
2 min. read
Updated on
Share this article
Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more
Microsoft recently updated the Windows 10 issue details page and talked about the newly spotted caching issues in the Windows 10 KB5034203 update released in January. It says that some Windows 10 devices within enterprise networks might face issues using Microsoft Connected Cache (MCC) nodes causing increased download traffic from the public internet.
Systems with DHCP Option 235 are likely to run into caching issues in Windows 10
The newly discovered bug reportedly affects devices with Windows 10 version 21H2 and 22H2 with KB5034203 or newer updates. Microsoft further confirmed that the systems with DHCP Option 235 are most likely to run into caching issues in Windows 10. As a result, enterprise users have no choice but to use networks outside of their companies to download updates and apps.
For those unaware, Microsoft Connected Cache is a feature currently available in preview that offers software-based caching. It allows delivering “Microsoft Content” across education and enterprise networks.
The tech giant says that Connected Cache for Enterprise and Education caters to customers looking to modernize the management away from Configuration Manager distribution points.
Microsoft also mentioned that the caching issue in Windows 10 KB5034203 and newer updates doesn’t affect home users. That’s because the affected feature only caters to the needs of ISPs, enterprises, and education networks.
Microsoft says workarounds are available to mitigate the problem
But, the company said it is working towards resolving the caching issue in Windows 10. And, mentioned that the fix could feature in the next updates. In the official documentation, Microsoft added two options that IT admins can try to resolve the problem at their end:
- Option 1: Configure Microsoft Connected Cache endpoint in DOCacheHost policy as indicated in Cache hostname. Additionally, DOCacheHostSource has to be set to 1 or removed as indicated in Cache hostname source. Note that by default, the DOCacheHost and DOCacheHostSource policies have no value.
- Option 2: This issue can also be mitigated using Group Policies available through our support channel. Organizations can request help through Support for business.
Are you also facing caching issues with Windows 10 KB5034203 or newer updates? Let us know if the solutions suggested by the company helped resolving it.
