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 | FSLogix – ODFC Container No Longer Mounts After an Update

An FSLogix update is intended to fix problems, but under certain conditions it can prevent Office containers from mounting.

Microsoft has confirmed this issue in FSLogix 26.01 (3.26.102.18413).

🔴 The symptoms

In environments using both FSLogix Profile Containers and ODFC Containers, creating or mounting the ODFC VHD(X) fails.

The key condition:

CleanupInvalidSessions = 1

This setting is intended to clean up orphaned sessions and prevent issues with locked containers.

🔬 Technical cause

The issue occurs in FSLogix 26.01 when the following conditions are combined:

• Profile Containers enabled
• ODFC Containers enabled
• CleanupInvalidSessions enabled

Microsoft has officially documented this problematic combination.

🛠️ Diagnosis

First, check the installed FSLogix version.

Then check the registry value:

Also review the FSLogix logs under C:\ProgramData\FSLogix\Logs for errors when creating or mounting the ODFC container.

✅ Workaround and fix

As a temporary workaround, Microsoft recommends disabling CleanupInvalidSessions.

The fix was released in FSLogix 26.01 CU1 (3.26.126.19110) on February 10, 2026.

Updating to a current FSLogix version approved for your environment is therefore the preferred solution.

⚠️ Important: Disabling CleanupInvalidSessions may prevent automatic cleanup of orphaned containers after sessions end unexpectedly.

💡 Takeaway

If ODFC containers suddenly stop mounting after an FSLogix update, storage or permissions are not necessarily responsible.

Sometimes the cause is simply the combination of a product version and an otherwise useful setting.

📚 Sources:

Microsoft FSLogix Known Issues:
https://lnkd.in/eU_ygcFg

Microsoft FSLogix Release Notes:
https://lnkd.in/eiMCtPqw

Finding in the Wild | Citrix & FSLogix – Outlook Only Works on the Second Launch!

While analyzing a Citrix multi-user environment, I encountered an interesting issue:

Outlook starts, but Microsoft 365 authentication does not work reliably. Sign-in only succeeds on the second attempt.

The FSLogix profile loads successfully, other applications work, and the Citrix VDA is registered.

⚠️ The symptoms

• Outlook repeatedly prompts for credentials.
• Microsoft 365 SSO fails intermittently.
• Relaunching Outlook sometimes allows sign-in to succeed.
• Profile and ODFC containers are mounted.
• The issue can also occur outside Citrix.

🔬 Possible causes

A mounted FSLogix container does not guarantee working Microsoft 365 authentication.

Outlook relies on components including Windows Web Account Manager (WAM) and Microsoft.AAD.BrokerPlugin.

Potential sources of failure include:

🔹 Incorrect WAM initialization
🔹 Issues with Entra device identity or the PRT
🔹 Roaming of device-bound authentication data
🔹 Timing issues during profile initialization
🔹 Third-party add-ins or security software

A root cause has not yet been confirmed.

🛠 My diagnostic steps

1️⃣ Check FSLogix

Review the Profile and ODFC logs under C:\ProgramData\FSLogix\Logs\ for mount failures and timeouts.

2️⃣ Check the WAM broker

Get-AppxPackage Microsoft.AAD.BrokerPlugin

3️⃣ Check Entra authentication

dsregcmd /status

In particular, check AzureAdJoined, DomainJoined and AzureAdPrt in the affected user’s context.

4️⃣ Correlate events

Compare WAM, Entra, AppModel and Office events with the timing of the Outlook launch.

5️⃣ Review the FSLogix configuration

Check ODFC policies, identity roaming and the FSLogix version.

⚠️ What I would avoid

Indiscriminately deleting all Microsoft 365 token caches or disabling WAM.

These measures may change the symptoms without addressing the underlying cause.

💡 My takeaway

A successfully loaded FSLogix profile does not automatically mean Microsoft 365 SSO is working.

What matters is the interaction between Windows device identity, WAM, profile management and Outlook.

📚 Sources

Microsoft – FSLogix Known Issues
https://lnkd.in/eU_ygcFg

Citrix – CTX695895
https://lnkd.in/eeAWVnQG

17:35

Finding in the Wild | Citrix PVS – Database Connection Drops Because the vDisk Version Is 20!

Sometimes the smallest details lead to surprisingly extensive troubleshooting.

I recently received a report of particularly unusual behavior in Citrix Provisioning Services (PVS):

⚠️ The symptoms

The PVS environment experienced repeated, brief database connection interruptions.

The following events appeared regularly in the event log:

• Event IDs 201 / 214 – PVS database connectivity issues
• SQL Error 8023 – Error processing a supplied value
• PVS loses its database connection for a few seconds and temporarily goes offline.

The strange part: not all targets were affected, only one specific group.

🔬 The cause – reproduced by Citrix in the lab

After extensive analysis, Citrix reproduced the issue in its lab using the supplied data.

The cause lies in the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL), which PVS uses to communicate with its SQL database.

The decisive trigger?

vDisk version number 20!

When a PVS target starts or stops, PVS writes a license usage record to the database. This record also includes the version number of the vDisk in use.

If that version number is exactly 20, the driver transmits the value incorrectly.

SQL Server rejects the operation with Error 8023.

PVS interprets this error as a loss of database connectivity and briefly goes offline.

In the investigated environment, exactly one active vDisk was running version 20. This also explained why only the associated targets were affected.

🛠 The workaround

The solution is surprisingly straightforward:

✅ Do not use vDisk version 20 in production.
✅ Deploy a newer version, 21 or higher.
✅ Alternatively, merge the vDisk versions as appropriate.
✅ For other vDisks, avoid keeping version 20 in use long-term.

Important: this is not a general SQL connectivity issue. Restarting SQL Server or adjusting network timeouts does not eliminate the underlying trigger.

📌 Vendor status

Citrix has reproduced the behavior in its lab.

A permanent fix is planned for a future PVS release.

💡 My takeaway

A single version number can be enough to cause brief PVS database connectivity failures.

If you see PVS Events 201/214 together with SQL Error 8023, check the vDisk versions in use as well.

The number 20 certainly would not have been my first suspect. 😉

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.