*Sitecore is sunsetting LTSC2019 container images for SitecoreAI-related images, which means anyone still pinned to that Windows base needs a migration plan now — not in March.*
Sitecore says it is retiring support for LTSC2019-based container images in the public ACR. The affected images are:
xmcloud/sitecore-xmcloud-cmxmcloud/sitecore-xmcloud-mssql-initxmcloud/sitecore-xmcloud-solr-init
What’s Changed
The practical change is pretty simple:
- The **final LTSC2019 image release** is scheduled for **15 September 2026**
- LTSC2019 images will stay in the public ACR until **31 March 2027**
- After 15 September 2026, those LTSC2019 images stop getting fixes and maintenance
- Sitecore recommends moving to **LTSC2022** or **LTSC2025**
In plain English, the images may still exist for a while, but they’re on borrowed time.
So, Why Does This Matter?
If you are still relying on LTSC2019, this affects your patching posture, your container host compatibility, and probably some of your build and deployment assumptions too. Once the release train stops, staying behind means choosing stale images on purpose.
Who Should Care
This is mainly relevant for:
- Teams running Sitecore container workloads on older Windows container baselines
- Anyone with build pipelines or environment templates still pinned to LTSC2019 tags
- Platform owners responsible for security patching and supportability
- Teams touching XM Cloud-related container setups that include these images
If you already standardized on LTSC2022, this is probably just a quick validation exercise.
If not, it deserves a proper review.
What To Look Out for Before Upgrading
The changelog note is short, so it does **not** spell out every migration detail. That means you should avoid guessing and validate the surrounding platform pieces in your own environment.
A few things I’d check first:
- Whether your Windows hosts fully support the target LTSC base image you plan to use
- Whether your CI/CD agents, build caches, or Dockerfiles still reference LTSC2019 implicitly
- Whether any downstream scripts, compose files, or internal templates are hard-coded to older tags
- Whether your testing covers image updates well enough to catch base-image-related surprises early
This is one of those changes that can be straightforward technically, but annoying operationally if old assumptions are scattered around the stack.
The Sensible Next Move
If you are on LTSC2019, the smart move is to plan the migration before September rather than treat March 2027 as the real deadline. That later date only tells you when the images disappear from the public registry. It does **not** mean they remain a healthy choice until then.
Short version: if these image names look familiar, put this on the platform backlog now.
