Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
KB12819689 is a historical hotfix for Configuration Manager current branch 2111—not a general fix for every Microsoft Connected Cache (MCC) problem. Its main purpose is to address MCC not being used as expected for Intune Win32 app downloads on co-managed devices. Before applying it, check your Configuration Manager version and confirm that the symptom matches the hotfix. Later Configuration Manager branches have their own MCC updates.
What KB12819689 fixes
KB12819689 addresses a case where MCC is enabled on a Configuration Manager distribution point, but a co-managed client downloading a Win32 app through Microsoft Intune does not use the cache as expected. In IntuneManagementExtension.log, the download may be associated with an internet-based DownloadURL rather than the expected cache-server path. That symptom is a useful lead, but it does not by itself prove the hotfix is the right remedy: client policy, cache reachability, content behavior, and Delivery Optimization fallback can produce similar outcomes.
The KB is also the successor to KB5001600, an earlier fix for MCC component installation failures following CDN changes. That earlier issue could cause installation retries to stop, with details recorded in DoincSetup.log. The two problems are related to MCC but are not the same symptom. See Microsoft’s KB12819689 article and the KB5001600 article.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Check the Configuration Manager version first
Do not select a hotfix based only on the words “Connected Cache.” Match it to the installed Configuration Manager branch and the observed failure.
#1 Best Overall
| Configuration Manager release or range | Relevant update | How to interpret it |
|---|---|---|
| 1910–2010 | KB5001600 | Earlier MCC component installation issue; superseded by KB12819689. |
| 2111 | KB12819689 | The version-specific hotfix discussed here. Its prerequisite wording says it can be applied when using versions 1910 through 2111; that does not mean every such version has the same defect or should receive it without checking applicability. |
| 2103–2207 | KB14978429 | Later replacement path for these branches; use the documentation for the installed version. |
| Newer releases | Use the matching MCC update or product guidance | Microsoft’s MCC version history lists later component updates, including KB33247081 for versions 2409, 2503, 2509, and 2603. |
KB12819689 was released on January 21, 2022, and supplies DoincInstall.exe version 1.5.5.9002. It is a product hotfix, not a security update or a universal MCC update. If you can move an old site to an appropriate supported Configuration Manager release, use that release’s update path rather than treating this historical KB as current for all environments.
Confirm that the issue matches before changing the site
- Identify the site version. Check the installed Configuration Manager current branch version and compare it with Microsoft’s MCC version history.
- Check the distribution point setting. In the distribution point properties, confirm whether Enable this distribution point to be used as Microsoft Connected Cache server is selected.
- Separate a client-use problem from an installation problem. For an Intune Win32 app that appears to bypass MCC, inspect
IntuneManagementExtension.log. For an MCC installation failure, inspectDoincSetup.logon the distribution point andDistMgr.logon the site server. - Check whether installation work is still active. Microsoft identifies status message 9522 from
SMS_DISTRIBUTION_MANAGERas indicating MCC installation is no longer being retried. Do not start another uninstall/reinstall cycle while an earlier operation is still running.
A successful app installation does not prove MCC served the content: Delivery Optimization can fall back to the original cloud source after an HTTP failure. Conversely, an internet-based URL in a log is not enough to diagnose every cause. Correlate timestamps across the client, site server, distribution point, and IIS logs.
Apply KB12819689 to an applicable 2111 environment
Follow Microsoft’s documented sequence. Use your normal change controls and verify the hotfix package and file version against Microsoft’s KB before deploying it. The file is copied to site-server locations, and an already-installed MCC component must be removed and installed again to use the updated installer.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRank #2
- Made in USA - Proudly produced in Ohio by a Veteran-owned business
- This Wire-O book contains spaces for managers to keep track of shift notes, employees, etc
- There are spaces to keep lists of top level items as well as daily to-do lists
- You can track your comps, sales, payments, and customer behavior
- 100 Pages, Wire-O, 8.5" x 11" Reorder SKU: LOG-100-7CW-PP(ManagerNotebook)
- Wait until MCC installation is no longer in progress. Check the relevant status message and
DistMgr.log; status 9522 indicates installation is no longer being retried. - Replace
DoincInstall.exe. Copy the updated version1.5.5.9002to{SMSInstallDir}binx64on every site server in the hierarchy, including the Central Administration Site if present and passive site servers. - Disable MCC on the affected distribution point. In its properties, clear Enable this distribution point to be used as Microsoft Connected Cache server. Allow the component uninstall to finish before continuing.
- Verify the uninstall. Look for status message 9152 and the corresponding entry in
DistMgr.log. Microsoft’s example successful entry is:Finished waiting for DoincInstall. InvocationState: UninstallCompleted. InvocationExitCode: 0. InvocationMessage: . - Re-enable MCC. Select the same distribution point option again and allow installation to complete using the updated installer. Check
DoincSetup.log,DistMgr.log, and status messages for the result.
For a site with many distribution points, Microsoft’s KB documents an alternative trigger: create an empty file named resetdps.trn in {SMSInstallDir}inboxesdistmgr.box. This causes the site’s distribution points to be reinstalled using the newer DoincInstall.exe. Use this deliberately: it is a site-wide distribution-point action, not a substitute for confirming the correct hotfix or monitoring the resulting work.
The KB says a computer restart is not required. That does not mean the change has no operational impact: allow for distribution point, IIS, and client deployment activity, and schedule the work accordingly.
Prove whether the cache is being used
Test from an affected client and check both reachability and actual byte counts. Microsoft’s Configuration Manager troubleshooting guide recommends an elevated, 64-bit PowerShell session for its tests. A successful HTTP response with StatusCode : 200 and StatusDescription : OK shows that the tested request received a successful response; it does not prove that a particular Intune app was delivered from MCC or that the full file was cached.
Rank #3
- EASY TO USE - The manager notebook is easy-to-use that help you keep track of shift notes, employees, etc.
- MONITOR YOUR DATAS - Using a project manager notebook to store all your data, you can track your comps, sales, payments, and customer behavior,consult your records whenever needed.
- HIGH QUALITY - The manager office supplies is used to high quality 100gsm pure white paper, elastic band and a back pocket for extra space. Make sure you have enough space for all manager plan
- UNIQUE DESIGN & A4 SIZE - Manager log book cover is lovely, golden spiral bound design, size of 8.2" x 10.5". Just the perfectly size to fit in your backpack, purse or laptop case. Without taking up your space and always helping you keep track of your small business
- THE PERFECT GIFT - Management logbook as gift for woman & man. Use it to improve your management efficiency, make efficient adjustments whenever needed
Microsoft’s guide includes an MSIX download example, such as:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsAdd-AppxPackage "https://installer.teams.static.microsoft/production-windows-x64/25177.2002.3761.5185/MSTeams-x64.msix"The versioned URL is an example from Microsoft’s documentation and may change. Use a current, appropriate test resource rather than assuming that exact URL will remain available.
After a download, query Delivery Optimization:
Get-DeliveryOptimizationStatus |
Select-Object DownloadMode, TotalBytesDownloaded, BytesFromCacheServerBytesFromCacheServer greater than zero means at least some reported bytes came from the cache server. It does not mean all bytes came from MCC. Microsoft’s troubleshooting guidance also describes comparing CDN and DOINC byte counts: equal CDN and DOINC counts indicate all reported bytes came from cache; a DOINC count of zero indicates all reported bytes came from the CDN; and CDN bytes greater than DOINC bytes indicate a partial cache contribution. Treat these as Delivery Optimization counters for the reported download, not proof that every request took the same route.
Some Intune content may not be cached until the third request because an Intune CDN VARY header can prevent earlier requests from being cached immediately. Repeat the same content request, then inspect the counters and logs. One unsuccessful test is not enough to declare the cache broken.
Where to look when the test fails
| Location | What it can help establish |
|---|---|
Client IntuneManagementExtension.log |
Whether the Intune Win32 app is associated with an internet-based download URL. |
Site server DistMgr.log |
Distribution point MCC install/uninstall activity and DoincInstall.exe invocation. |
Distribution point SMS_DP$Ms.Dsp.Do.Inc.SetupDoincSetup.log |
MCC setup progress and setup errors. |
%temp%arr_setup.log |
ARR dependency installation details. |
IIS logs under %SystemDrive%inetpublogsLogFiles |
Requests, HTTP status codes, and server-side request behavior. |
C:DoincProductInstallLogs |
MCC operational and cloud-connectivity details. |
HKLMSOFTWAREMicrosoftDelivery Optimization In-Network Cache |
Server-side MCC configuration values. |
Microsoft’s Configuration Manager MCC troubleshooting guide documents setup errors including IIS missing (0x00D00001), Default Web Site missing (0x00D00002), PowerShell not elevated (0x00D00005), non-64-bit PowerShell (0x00D00006), Default Web Site not using port 80 (0x00D0001E), cache allocation exceeding free space (0x00D00020), and IIS failing to stop (0x00D00029). The guide covers other codes and remediation; use it rather than treating KB12819689 as a fix for missing IIS, an ARR problem, insufficient disk space, or a setup environment error.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →If MCC installs but clients still download from the internet
- Check the branch and component version. The old hotfix may not match the site. For 2103–2207, review KB14978429; for newer branches, use the version-specific MCC history.
- Check client configuration and reachability. A healthy cache node may still be unreachable from clients because of firewall rules, network segmentation, DNS, proxy, TLS inspection, or (for newer deployments) WSL port forwarding.
- Check client cache discovery. For newer MCC deployments, DHCP Option 235 may not be retrieved in environments affected by
LocalPolicyMerge. Microsoft’s Enterprise and Education troubleshooting guidance describes directly configuring theDOCacheHostpolicy as an alternative in relevant environments. - Check for normal fallback or delayed caching. Delivery Optimization falls back to the original cloud source when the cache returns an HTTP failure. Also repeat the same test enough times to account for the documented third-request behavior.
- Check proxy-specific defects separately. KB33247081 addresses a later case where MCC cannot be installed behind proxy servers requiring absolute URLs. That is not the KB12819689 defect.
Configuration Manager MCC and the newer Connected Cache for Enterprise and Education are related but distinct deployment contexts. The latter has its own Windows/Linux node, client discovery, WSL, firewall, proxy, and TLS troubleshooting paths; do not apply the Configuration Manager 2111 reinstall procedure to it by default.
When to use a different fix
Use KB12819689 when the site is on the relevant historical branch, MCC is enabled on distribution points, and the observed behavior matches the documented Intune Win32 app/co-management issue—or when repairing the associated legacy MCC installer issue according to the KB. Prefer the later version-matched hotfix or a product upgrade when running a later branch. Investigate setup prerequisites, proxy behavior, client discovery, network reachability, and content caching separately when those are the actual failure points.
For authoritative version mapping and full procedures, consult Microsoft’s MCC version history, Configuration Manager troubleshooting guide, and, for standalone newer nodes, the Enterprise and Education troubleshooting guide.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
