Windows 11 25H2 black screen when the same FSLogix profile is used across different patch levels on non-persistent VDI

Arunkumar Durai 0 Reputation points
2026-11-19T03:52:24.34+00:00

We run Windows 11 25H2 non-persistent virtual desktops provisioned with Citrix MCS on VMware vSphere, with user profiles on FSLogix. Our September-patched 25H2 image is in production, using a newly provisioned FSLogix profile store path dedicated to 25H2. We are now testing a November-patched 25H2 image against the same profile store. When a user logs on to the November-patched image and then logs on to the September-patched image with the same profile, the second session gets stuck at a black screen. Is this related to using the same FSLogix profile across different patch levels of Windows 11 25H2? Is this a known issue, and what would you recommend as next steps?

Windows for business | Windows Client for IT Pros | User experience | FSLogix
0 comments No comments

2 answers

Sort by: Newest
  1. Xuan Nhu 1,700 Reputation points Independent Advisor
    2026-11-19T04:24:37.6433333+00:00

    Hello Durai,

    This may be related to FSLogix profile state or AppX package registration rather than simply having different Windows patch levels.

    I recommend testing the November image with a brand-new FSLogix profile first. If it works, investigate the existing profile for incompatible or stale package registration data.

    Also, review the FSLogix logs under C:\ProgramData\FSLogix\Logs\Profile and Windows AppX deployment logs for errors.

    There is no general requirement to use separate FSLogix containers for different patch levels of the same Windows 11 release. However, isolating profiles during testing can help identify the root cause.

    Xuan Nhu.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-19T03:52:47.2966667+00:00

    Yes. This matches a known Windows issue affecting Windows 11 25H2 desktop loading after sign-in on virtual desktop environments, primarily observed on Azure Virtual Desktop hosts using FSLogix, and it occurs more frequently with some existing user profiles. The documented symptoms include a black screen after sign-in, the desktop session not loading automatically, and Windows Explorer crashes in the Application event log.

    For Windows 11 25H2, Microsoft identifies the issue as originating after the August 2026 non-security preview update KB5120998 and subsequent updates. It was resolved by updates released October 13, 2026, specifically KB5127648 and later. If the September-patched image is still on a build before that resolution, using the same existing FSLogix profile with that older image can align with the behavior being seen when moving back from a newer image to the older one.

    Recommended next steps:

    1. Verify the patch level of both 25H2 images.
      • If the September image is earlier than the October 13, 2026 resolution update, update that image to KB5127648 or later.
      • If the November image is already later than that, keep both images on the resolved update level or newer.
    2. Avoid validating mixed patch levels against the same existing FSLogix profile until both images include the resolved update.
      • The issue is documented as occurring more often with some existing user profiles.
    3. If immediate testing must continue on a pre-resolution image, use one of the documented mitigations:
      • Manually launch explorer.exe from Task Manager with Ctrl+Shift+Esc > Run new task > enter explorer.exe > OK.
      • For enterprise-managed devices, apply the documented Known Issue Rollback (KIR) Group Policy for Windows 11 25H2 / 24H2.
    4. Check Application event logs on affected sessions for Windows Explorer crashes.
      • That is one of the documented indicators for this issue.
    5. If Microsoft Support for Business already provided an immediate workaround, that can be used instead of KIR or the special Group Policy.

    Based on the documented issue, this is best treated as a known Windows/FSLogix profile interaction with affected 25H2 builds rather than as evidence that FSLogix profiles are generally unsupported across minor patch levels. The priority action is to bring the older 25H2 image to the resolved update level and retest with the same profile.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.