Finding in the Wild | Windows Server 2025 – KMS Activation Broken After the November Update!

While troubleshooting a Windows Server 2025 system, I encountered an issue that initially looked like a corrupted Windows licensing store or an incorrect KMS configuration.

However, every repair attempt failed.

⚠️ The symptoms

Windows activation stopped working. Even basic licensing management commands failed:

❌ slmgr.vbs /ipk – Install a product key
❌ slmgr.vbs /skms – Configure the KMS server
❌ slmgr.vbs /ato – Activate Windows

The error message:

0x80041008 – Invalid parameter (SWbemObjectEx)

What stood out: the issue affected not only KMS activation itself, but also local Windows licensing management.

🔬 The cause – confirmed by Microsoft

The November 2026 security updates introduced an issue in the Windows Software Licensing WMI Provider.

As a result, certain licensing management operations failed with 0x80041008.

This also explains why our previous repair attempts had no effect.

There was no confirmed corruption of the licensing store, nor was the issue caused by connectivity to the KMS host.

🛠 Microsoft provides the fix

On November 13, 2026, Microsoft released an out-of-band update:

✅ KB5136489 – Windows Server 2025
✅ OS Build 26100.33828

Here is how I would proceed:

1️⃣ Check the installed update:

Get-HotFix -Id KB5136489

2️⃣ Install KB5136489 and restart the server.

3️⃣ Then test licensing management again:

When installing manually, any required checkpoint updates must also be taken into account.

💡 My takeaway

Not every KMS error is a KMS problem!

If even /ipk and /skms fail with 0x80041008, check the Windows patch level first.

In this case, the cause was the Microsoft update.

A repair installation, deleting tokens.dat or making further changes to WMI was not required to resolve this confirmed issue.

📚 Source: Microsoft KB5136489
https://lnkd.in/e7JfT6hm

Finding in the Wild | Citrix MCS – Windows Rearm Failure After November 2026 Updates

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.

Finding in the Wild | Secure Boot 2026 – A Topic That Belongs in VDI Master Images

Microsoft continues preparing the transition away from expiring Secure Boot certificates. This is already relevant for conventional clients, but virtualized environments add another layer. Especially with Windows 11 and Windows Server 2025, I would therefore incorporate this topic

Microsoft continues preparing the transition away from expiring Secure Boot certificates.
This is already relevant for conventional clients, but virtualized environments add another layer.
Especially with Windows 11 and Windows Server 2025, I would therefore incorporate this topic into image and provisioning processes now.

A few basic checks:

In VDI environments, also check:
🔹 UEFI configuration
🔹 vTPM and hypervisor
🔹 Firmware level
🔹 BitLocker and recovery process
🔹 Master image and templates
🔹 MCS and PVS provisioning

The crucial point: with non-persistent and provisioned systems, examining only individual VMs is not enough.
When Secure Boot changes are required, it must be clear how those changes propagate through the master image, hypervisor and provisioning to the actual VDAs.

For new Windows 11 VDI and Windows Server 2025 environments in particular, I would therefore include this topic directly in the technical baseline.

Finding in the Wild | Citrix Printers Missing After a Windows Upgrade?

Citrix currently documents a known issue around CVAD 2603: After an in-place Windows upgrade on a system with Citrix VDA already installed, the Citrix Print Providers may disappear from the Windows execution order. Possible symptoms: – Client printers

Citrix currently documents a known issue around CVAD 2603:

After an in-place Windows upgrade on a system with Citrix VDA already installed, the Citrix Print Providers may disappear from the Windows execution order.

Possible symptoms:

– Client printers are no longer created
– The Citrix Universal Printer is missing
– Printing issues occur only on the upgraded VDAs
– Spooler and Citrix Print Manager nevertheless run without errors

According to Citrix, the cause lies in the Windows upgrade process: the registered Print Provider order is not fully retained.

Workaround:

Open the following registry path:

In the Order value, add the following entries before the other providers:

• Universal Printer
• Client Printer

Then restart the VDA.

My recommendation:

After every in-place upgrade of a VDA, check not only VDA registration and session launch, but explicitly test Client Printer, Session Printer and Universal Printer too.

A successful logon does not automatically mean anyone will be able to print afterwards.

Finding in the Wild | When Identical Machine SIDs Suddenly Become a Citrix Problem

For years, this was completely normal in Citrix environments: Create a golden image → use MCS or PVS to provision hundreds of VDAs → done. Machines from the same image may share the same local machine SID .

For years, this was completely normal in Citrix environments:
Create a golden image → use MCS or PVS to provision hundreds of VDAs → done.

Machines from the same image may share the same local machine SID.
Usually, that was not a major problem.

After all, each computer has its own Active Directory computer account with a unique domain SID.

With stricter Windows security hardening, however, this old architectural assumption becomes interesting.

What can happen?
When two cloned VDAs communicate, certain machine-to-machine connections may be blocked because their local identities are identical.

For example, this may affect:
❌ RDP between VDAs
❌ SMB / file sharing
❌ Printer sharing
❌ Certain NTLM/Kerberos scenarios

The Windows event log may show LsaSrv Event ID 6167.

And this is where it gets interesting:
The VDAs are correctly domain joined.
The AD computer accounts are unique.
DNS is correct.
Kerberos also initially looks fine.
Yet the connection is blocked.

Why?
Microsoft is increasingly tightening machine identity validation.
A design decision that was unproblematic for cloned Windows systems for years suddenly collides with more modern Windows security hardening.

This does not affect an obscure Citrix feature.

It affects one of the basic principles of:
MCS and PVS: creating many machines from a single golden image.

Citrix itself is now emphasizing the security of local persistent accounts in shared MCS/PVS images and explicitly recommends not creating such accounts in the master image.

What does this mean in practice?
If communication suddenly fails after Windows security updates between two VDAs in the same catalog:
Do not immediately dismantle firewalls, DNS or Citrix policies. 😉

Also check:
System event log →
LsaSrv
and particularly Event ID 6167.

For me, this is a good example of why golden-image architectures now need testing against more than just new Citrix versions.