Windows Fixed the Black-Screen Fault. Citrix Sessions Still Need Testing
Update, 31 October 2026: Microsoft now records the Windows black-screen and desktop-loading issue as resolved by updates released on 13 October and later. Install the latest applicable update before using an older workaround. The separate FSLogix entry remains in progress, so a successful patch deployment still needs a full session test.
Windows 11 24H2 Home and Pro reached end of updates on 13 October 2026; move those editions to a supported feature release. Enterprise and Education remain supported until 12 October 2027. A historical minimum repair does not justify leaving an unsupported edition in service.
Microsoft’s out-of-band Windows updates fixed the September failure that could make Remote Desktop Services stop accepting connections. They did not end every Citrix black screen problem associated with the same update cycle.
Citrix’s 25 September notice warned that some Citrix Virtual Apps and Desktops environments could still present users with a black screen after sign-in, even after the September Remote Desktop repair. That notice predates the later Windows desktop-loading fix. Microsoft’s separate FSLogix known-issues entry still lists an in-progress problem in which explorer.exe crashes while the Windows shell is starting.
The distinction matters. One incident prevents a session from being established because Remote Desktop Services becomes unstable. The other can allow sign-in to progress and then fail while loading the user’s desktop. Applying the fix for the first problem does not prove that the second one has been resolved.
Two failures arrived in the same update cycle
BlackTree reported earlier in September that the month’s Windows security updates could leave Remote Desktop users stuck at Connecting, make sign-ins fail and leave servers hanging while waiting for Remote Desktop configuration.
Microsoft has since resolved that RDS problem with cumulative out-of-band updates released on 14 September. Citrix lists updates for Windows client and server releases from Windows Server 2012 through Server 2025, alongside Windows 10 and Windows 11. Older platforms remain subject to their extended-support conditions.
The separate desktop-loading problem is different. Microsoft says it began with the August non-security preview update for Windows 11 and continued into later updates, including September’s security release. Reports have primarily involved virtual-desktop hosts using FSLogix, with the problem appearing more frequently for some existing user profiles.
Microsoft lists the following symptoms:
- A black screen appears after sign-in and the desktop does not load automatically.
- The user cannot reach the desktop until the Windows shell is started manually.
- Application logs may show
explorer.execrashes.
Citrix’s September notice says Desktop OS Virtual Delivery Agents can exhibit the black screen after installing KB5124008 or its preview predecessor KB5120998. It adds that environments combining Citrix Virtual Apps and Desktops with Citrix Profile Management or FSLogix can remain affected after the RDS out-of-band updates are installed.
The RDS repair is still necessary
Administrators should not read the remaining black-screen warning as a reason to skip the out-of-band Windows updates. They address a separate and serious service failure.
Citrix identifies three useful signatures for the resolved RDS condition:
TerminalServices-RemoteConnectionManagerevent 20498, reporting that Remote Desktop Services took too long to complete a client connection.Winlogonevent 6005, reporting that theSessionEnvnotification subscriber took too long to process a disconnect.- The
TermServiceservice remaining inStopPendinginstead ofRunning.
Microsoft says the failure could also make management tools, File Explorer and the Windows Update interface become unresponsive. The affected range was unusually broad, covering supported Windows 10 and Windows 11 releases as well as Windows Server 2012 through Windows Server 2025.
The out-of-band updates are cumulative and retain the security protections from the September releases. Organisations should install the newest applicable update rather than attempting to choose between the security fixes and the RDS repair.
Update first, then investigate remaining black screens
Microsoft now marks the Windows desktop-loading issue resolved by the 13 October updates and later releases. KB5127648 is the resolving package for Windows 11 24H2, 25H2 and 26H2; the separate 26H1 release-health record names KB5127646. Devices with that repair or a later applicable cumulative update do not need this issue’s workaround. The record lists these four Windows 11 client versions and no affected server platform.
For centrally managed devices still on an older affected build, administrators can install and configure the version-correct Known Issue Rollback Group Policy package, then restart. Follow its exact instructions rather than assuming a policy value. It suppresses the change causing the problem; it does not replace the available cumulative repair.
For a user on an older affected build already looking at a black screen, Microsoft documents a temporary way to regain the desktop:
- Open Task Manager with
Ctrl+Shift+Esc. - Select Run new task.
- Enter
explorer.exeand run it.
That action starts the shell for the current session. It is not a fleet-level repair and it does not remove the condition that caused the crash.
Microsoft’s separate FSLogix known-issues page says the condition affects FSLogix 2210 hotfix 4, version 2.9.8884.27471, and later. It classifies the work as in progress and says the black screen results from explorer.exe crashing during shell start-up. The entry was updated on 23 September and still promises a future FSLogix release or a coordinated Windows release. This open product entry does not overturn the newer, resolved Windows issue record or prove that every remaining black screen has the same cause.
Do not treat every Citrix black screen as the same failure
The following split is more useful than treating every post-update login complaint as one incident.
Connections hang before the desktop session is established
Check the RDS and Winlogon events, inspect TermService and confirm whether the platform has received its applicable 14 September out-of-band update or a later cumulative release.
Authentication succeeds but the Citrix black screen remains
Check for explorer.exe crashes, identify whether the VDA uses FSLogix or Citrix Profile Management, confirm the Windows build and whether it has the applicable 13 October repair or a later update. Assess the Microsoft Known Issue Rollback only for an older affected build. On a current build, preserve the evidence, inspect profile attachment and shell extensions, and seek Microsoft or Citrix support for a persistent failure. Test with both established and newly created profiles because Microsoft says some existing profiles appear more likely to trigger the problem.
The session works only after manually starting explorer.exe
Treat that as a diagnostic clue and temporary restoration step. It supports the shell-start failure hypothesis, but it does not demonstrate that the environment is safe to leave unchanged.
What infrastructure teams should do now
- Separate server VDAs from desktop OS VDAs. The RDS problem spans Windows Server and client systems. Microsoft’s current black-screen record lists Windows 11 client platforms and no affected server platform.
- Record the exact build, not only the update month. Determine whether
KB5120998,KB5124008, an out-of-band repair or a later cumulative update is installed on each affected machine. - Confirm profile technology and version. Record whether the host uses Citrix Profile Management, FSLogix or another profile solution. For FSLogix, capture the installed version and retain the profile logs from
C:\ProgramData\FSLogix\Logs\Profile. - Apply the RDS repair where required. Do not withhold the cumulative out-of-band update because a separate black-screen condition remains.
- Pilot the appropriate remedy on representative VDAs. Prefer the current applicable update. If an older affected build requires the KIR, pilot that separately. Use a small ring that includes existing profiles, multi-session behaviour where applicable and the applications users need immediately after sign-in.
- Plan the restart. Both the Windows out-of-band update and the enterprise KIR workflow require a controlled restart to complete the change.
- Validate the user journey. A healthy service status is not enough. Test connection establishment, authentication, shell start, profile attachment, application launch, sign-out and reconnection.
- Keep rollback state visible. Document which VDAs received the KIR and retire the temporary policy deliberately once the resolving update and full session recovery have been verified.
A green patch report is not the same as a healthy desktop
Citrix’s September validation report says the Windows security updates passed its testing on selected supported CVAD releases, but it also says the tests were not exhaustive and were conducted only on English-language environments. That is a useful boundary, not a contradiction.
Patch validation proves that a defined set of tests passed. It cannot reproduce every combination of Windows build, VDA release, profile technology, user history and application stack in production. The operational lesson is therefore not to distrust the security update. It is to validate the full service that depends on it.
The records now describe three boundaries: the September RDS service fault has a repair, the Windows desktop-loading issue has an October repair, and the separate FSLogix product entry remains in progress. Infrastructure teams need to establish the installed build and the stage that fails before declaring recovery complete.
Sources
- Citrix CTX697101, Issues with Microsoft Windows September 2026 Update
- Citrix CTX697098, Microsoft Security Update Validation Report September 2026
- Microsoft Windows 11 24H2 release health, black-screen and Remote Desktop records, current resolution and edition support, checked 31 October 2026.
- Microsoft Windows 11 26H1 release health, version-specific repair, checked 31 October 2026.
- Microsoft FSLogix known issues
- Microsoft KB5129195, Windows 11 24H2 and 25H2 out-of-band update


