Finding in the Wild | PVS + Secure Boot – A Small CU2 Feature That Could Become Important in 2026

Citrix Provisioning 2507.1 LTSR CU2 is here. Among the usual fixes is a change that I find much more interesting for PVS environments than the version number suggests: 👉 Support for Microsoft Windows UEFI CA 2023 Why is

Citrix Provisioning 2507.1 LTSR CU2 is here.

Among the usual fixes is a change that I find much more interesting for PVS environments than the version number suggests:

👉 Support for Microsoft Windows UEFI CA 2023

Why is this important?

Microsoft is currently renewing the certificate chain behind UEFI Secure Boot. Some existing Secure Boot certificates date back to 2011, and Microsoft is gradually migrating Windows to the new 2023 certificates.

This is exactly where it becomes interesting for Citrix PVS.

PVS must understand the new Secure Boot world

With PVS 2507.1 LTSR CU2, Citrix now supports Secure Boot with images signed using the new Windows UEFI CA 2023 certificate.

Initially, this sounds like a small compatibility fix.

But it is not necessarily.

Anyone familiar with PVS knows:

💥 If the boot chain is wrong, there is no Citrix session.

We are no longer discussing logon duration, profiles or HDX performance.

The target simply does not boot.

Another interesting change

When a target device starts, PVS now automatically detects whether the system booted using:

BIOS or UEFI

.

This information is saved in the device record and is also available through farm telemetry.

I find this particularly useful in larger or long-established PVS farms.

Different firmware and boot configurations are surprisingly common there.

What would I check now?

Anyone using PVS + Windows 11 or Windows Server 2025 + Secure Boot should definitely keep CU2 on their radar.

Before a rollout, I would test in particular:

👉 Secure Boot + Windows UEFI CA 2023
👉 Target device boot
👉 PXE / BDM
👉 Existing vDisks
👉 Hypervisor firmware / UEFI configuration
👉 Boot after promoting a vDisk version
👉 Failover to a second PVS server

With changes like these:

The vDisk has worked for years is no guarantee that the future Secure Boot chain will also work.

My takeaway

For me, PVS 2507.1 CU2 is therefore more than just:

Another cumulative update with a few bug fixes.

Support for Windows UEFI CA 2023 is a classic future-readiness topic.

Microsoft is changing the Secure Boot trust chain.

Citrix is following suit with PVS.

And once a target fails to start after a Windows/Secure Boot update, an inconspicuous release-note entry suddenly becomes an important feature. 😎

Finding in the Wild | XenServer 9 + Windows Server 2025 – When a Boot Storm Becomes a Problem

An interesting detail from the current XenServer 9 known issues that may be particularly relevant to larger Citrix environments: XenServer documents a Windows Server 2025 issue under CP-51655. If many Windows Server 2025 VMs start simultaneously on the

An interesting detail from the current XenServer 9 known issues that may be particularly relevant to larger Citrix environments:

XenServer documents a Windows Server 2025 issue under CP-51655.

If many Windows Server 2025 VMs start simultaneously on the same XenServer host, some VMs may fail to start.

Why do I find this especially interesting in a Citrix context?

Because this scenario is completely normal there.

Citrix Power Management starts several workers in the morning.

An MCS catalog starts after a maintenance window.

Or PVS boots numerous targets almost simultaneously following a reboot schedule.

Initially, the symptoms may look like this:

Some of my Citrix workers will not start.

Troubleshooting will probably begin with MCS, PVS, the master image or the Delivery Controller.

But the cause may be one layer lower.

XenServer explicitly states that the issue can occur when a larger number of Windows Server 2025 VMs start simultaneously on a single host.

This also makes acceptance testing for new Server 2025 Citrix environments interesting.

A test with two or three VDAs may not be sufficient.

For XenServer 9 + Windows Server 2025, I would therefore also plan a realistic boot-storm test:

Start 5 VMs → 10 VMs → 20 VMs → 30+ VMs simultaneously.

Do not check only whether the VDAs are registered afterwards. Already at the XenServer layer, observe whether individual VM starts fail.

With Windows Server 2025 as a future multi-session platform in particular, this is a small detail with potentially significant consequences.

Known issue: CP-51655

Finding in the Wild | Windows Update Breaks Domain Trust – Experienced Firsthand at a Customer

The September 2026 update brings another surprise. This time, I experienced it directly in a customer environment. After the Windows update, certain domain-joined Windows 11 systems suddenly lose their trust relationship with Active Directory. ❌ Domain trust failure

The September 2026 update brings another surprise. This time, I experienced it directly in a customer environment.

After the Windows update, certain domain-joined Windows 11 systems suddenly lose their trust relationship with Active Directory.

❌ Domain trust failure
❌ Logon fails despite valid credentials
❌ Secure channel to the domain controller is broken

The cause: Machine Identity Isolation

With KB5124008, Windows honors existing Machine Identity Isolation settings. The problem: this feature requires an AD environment at the Windows Server 2025 domain functional level.

If the feature is already enabled through GPO, Intune or the registry even though that requirement is not met, the trust relationship may be lost.

What helps?

1. Check Machine Identity Isolation and the existing policies.
2. In an unsupported AD environment, disable the feature through the original management method.
3. Restart affected systems.
4. Then repair the secure channel.

PowerShell:

⚠️ Important: disabling the feature alone does not repair an already broken trust relationship.

My learning from practice:

If domain trust issues suddenly occur after the September patch, do not immediately remove the computer from the domain and join it again.

Check Machine Identity Isolation first!

Another example of how a security feature can become an operational issue when its infrastructure prerequisites are not met.

Finding in the Wild | Windows Server 2025 – Published App Closed, Session Remains

In a current Citrix Virtual Apps setup on Windows Server 2025 , I encountered some interesting behavior: The user closes the published application normally, but the Citrix session does not log off. Sometimes the session remains active for

In a current Citrix Virtual Apps setup on Windows Server 2025, I encountered some interesting behavior:

The user closes the published application normally, but the Citrix session does not log off.

Sometimes the session remains active for another 1–2 minutes.

So I investigated more closely what was still preventing logoff.

The actual application had already exited, but several processes continued running inside the user session. One stood out:

ShellAppRuntime.exe

The decisive test:
Terminate ShellAppRuntime.exe → the session logs off immediately.

That at least gave me a concrete lead.

🔍 Where did I look?

For seamless/published application issues, it is worth checking:

HKEY_USERS\<User-SID>\Software\CitrixVolatile\Seamless\Sessions\<Session-ID>\

This shows which processes still play a role within the seamless session.

That is much more useful than randomly terminating processes in Task Manager.

This becomes particularly interesting on Windows Server 2025: the behavior can also be observed with different VDA versions. On comparable Server 2022 systems, logoff occurs within a few seconds.

This is particularly inconvenient in combination with FSLogix or profile containers:

Published app closed

→ Session remains active
→ Profile container remains mounted
→ User starts the next application
→ VHDX may still be locked

I have therefore added a new test for Windows Server 2025 Citrix environments:

Check not only that a published application launches correctly, but also that the session actually ends cleanly after the application is closed.

Whether ShellAppRuntime.exe itself is the underlying cause or merely a symptom of deeper Windows Server 2025 behavior requires further investigation.
But for troubleshooting, the registry path was the decisive clue to understanding why logoff does not occur.

🔎 Finding from the field: closing an app does not automatically mean the session has ended.

Finding in the Wild | Windows October Update Breaks Citrix VDA Registration

A new Patch Tuesday, a new surprise. This time, Citrix VDA registration is affected. After installing Windows 11 security update KB5127648 (October 2026), Citrix Virtual Delivery Agents may suddenly fail to register with the Delivery Controller. The interesting

A new Patch Tuesday, a new surprise. This time, Citrix VDA registration is affected.

After installing Windows 11 security update KB5127648 (October 2026), Citrix Virtual Delivery Agents may suddenly fail to register with the Delivery Controller.

The interesting part: the VDA is reachable and RDP works, but Citrix remains stuck at Registering.

🔍 The symptoms
– Citrix Studio: Trying to re-register
– VDA status remains at Registering
– Published desktops cannot be launched
– RDP to the affected machine still works

Citrix officially documents the issue under CTX697231 for Windows 11 24H2/25H2, reported with VDA 2511. Other VDA versions may also be affected.

🔬 The decisive clue is in the event log

On the Delivery Controller:
Event ID 131075
Process: BrokerService.exe
Exception:
System.ServiceModel.Security.SecurityNegotiationException
Error message:
The caller was not authenticated by the service.
Affected operation:
Citrix.Cds.Protocol.Worker.IQueryAgent.Test()

This is where it gets interesting: the problem is not basic Controller connectivity, but authentication during communication between the Broker Service and VDA.

🛠️ The workaround

Citrix has already published a tested mitigation:

Then restart the affected VDA.

The registry value switches from the new Windows Administrator Protection to classic Admin Approval Mode.

Citrix confirms that affected VDAs register successfully again afterwards.

⚠️ Important: this is a temporary workaround that rolls back an additional Windows security feature. Apply the change in a controlled manner and reassess it after a permanent fix becomes available.

💡 What can we learn?

A VDA that fails to register after Patch Tuesday does not necessarily have a Citrix issue.

And working RDP does not mean that Citrix Broker authentication is working too.

Before reinstalling VDAs, repairing Delivery Controllers or dismantling the Active Directory configuration:

Check KB5127648, Event ID 131075 and TypeOfAdminApprovalMode.

Citrix and Microsoft continue to investigate the underlying cause together.

📚 Source: