Repository navigation
Containerized Azure Data Factory Self-Hosted Integration Runtime works on Server Core ltsc2019 build 17763.8511 but not 17763.9020 #641
Description
Summary
We build a Windows container image FROM mcr.microsoft.com/windows/servercore:ltsc2019 that installs and runs the Azure Data Factory Self-Hosted Integration Runtime (SHIR), based on Microsoft's reference sample (Azure/Azure-Data-Factory-Integration-Runtime-in-Windows-Container).
An image built while the base resolved to 10.0.17763.8511 works — the SHIR node registers and reports Online in Data Factory. An image built while the base resolved to 10.0.17763.9020 does not — the SHIR node does not come online. The Dockerfile, scripts, and SHIR installer are unchanged between the two builds; the base OS build is the only difference.
We have not determined the underlying cause and are not attributing it to any specific component — reporting the observed difference in case it is a known change or expected behavior.
Environment
| Value | |
|---|---|
| Base image | mcr.microsoft.com/windows/servercore:ltsc2019 |
| Base build where it works | 10.0.17763.8511 (KB5078752) |
| Base build where it does not work | 10.0.17763.9020 (KB5099538) |
| Host | Azure App Service for Containers (Windows) |
| Workload | Azure Data Factory Self-Hosted Integration Runtime, installed via IntegrationRuntime.latest.msi |
Observed behavior
- Image built on base 17763.8511 → SHIR node registers and shows Online.
- Image built on base 17763.9020 (identical Dockerfile, scripts, and SHIR installer) → SHIR node does not come online.
Steps to reproduce
- Build a Windows container image
FROM mcr.microsoft.com/windows/servercore:ltsc2019that installsIntegrationRuntime.latest.msiand registers a SHIR node (per the reference sample above). - Run it with a valid SHIR auth key on base build 17763.9020 and observe the node does not come online.
- Build the identical image on base build 17763.8511 and observe the node comes online.
Notes
Happy to provide container logs or any other details on request.
Activity
github-actions commentedon Jul 16, 2026
Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub.
linliu-msft-git commentedon Aug 11, 2026
Hi, Mark,
A relevant bug fix was made in the August 2026 Windows Server 2019 update (KB5120238, OS Build 17763.9113). The fix applies to the container host, not the image. It takes effect when an image layer is pulled on a patched host.
Steps
Install KB5120238 on the container host and reboot.
docker pull the ltsc2019 image.
If you already pulled this image before patching, remove it first so it re-imports (a plain re-pull reuses the cached, still-broken layer):
docker rmi
docker system prune -f
Build/run as normal. Verify: vc_redist.x64.exe /install /quiet finishes in seconds.
Please let us know if this fix your issue
MarkFGarner commentedon Aug 24, 2026
This was resolved by Azure/Azure-Data-Factory-Integration-Runtime-in-Windows-Container#37, thank you for your reply!