Last updated:
I’ve recently encountered the same issue at two of my customers:
After installing the November 2026 Windows updates, image preparation through Citrix Machine Creation Services (MCS) fails.
And apparently, I’m not the only one. Several administrators have reported similar issues in the comments on Günter Born’s blog.
⚠️ Windows Updates Under Investigation:
- Windows Server 2019 – KB5131085
- Windows Server 2022 – KB5131090
- Windows Server 2025 – KB5131080
🔍 The Issue
MCS image preparation fails with the following error:
Image preparation failed to rearm the copy of Windows installed on the master image.
As a result, the updated master image cannot be deployed successfully.
🔬 Technical Analysis
The failure occurs during the Windows rearm operation as part of the MCS image preparation process.
Whether this is caused by changes to the Windows Software Protection Service, Windows activation mechanisms, or the interaction between Windows and Citrix MCS remains unclear.
The timing strongly suggests a connection to the November Patch Tuesday updates, but correlation alone does not establish the root cause.
🛠️ My Recommendations
1️⃣ Install the November updates on test master images first.
2️⃣ Validate the complete MCS image preparation process — not just whether Windows boots successfully.
3️⃣ If preparation fails, investigate Citrix ProvTask details, preparation VM logs, and Windows activation events.
4️⃣ Keep the last known-good master image snapshot available for rollback.
5️⃣ Postpone production Machine Catalog updates until the updated image has been successfully validated.
I would also avoid manually modifying slmgr /rearm or Windows activation settings until the underlying cause has been identified.
❗ Current Status
I’ve reproduced this issue in two customer environments, and several similar reports have appeared in the community.
As of now, there is no official confirmation or documented fix from Citrix or Microsoft.
Has anyone identified a reproducible root cause or a working workaround?
I’m particularly interested in the CVAD versions and Windows activation methods (KMS, MAK, or ADBA) used in affected environments.
