Fixed issues

A black screen with the error message "The Group Policy Client service failed the sign-in. Access is denied." might occur when a user launches a duplicate session on the same VDA machine.

The Profile Management service might crash when active write back is enabled.

A Blue Screen of Death (BSOD) might occur due to the upmjit.sys driver.

The local profile might not be cleaned up after logoff due to reparse points set by Microsoft applications (such as Microsoft Teams).

The local profile might not be cleaned up after logoff due to reparse points set by Profile Management.

The SessionInfo registry key might be incorrectly synced to the user store when active write back for the registry is enabled, which can affect application auto-launch behavior.

Profile data might be displayed as Offline on the Director Personalization page for container-based profiles.

The user might experience slow logons when Folder Redirection is enabled after upgrading the VDA.

Profile Management might fail to register its Winlogon notification during installation when the existing notification registry value is large. As a result, user profiles are not processed and local profiles are created instead of managed profiles.

The Profile Management service might crash during mid-session container synchronization when a disk interface query fails and the returned pointer is used without validation.

Windows Search and other per-user UWP apps might stop working at the first logon after an existing user's profile is reset.

Folders configured in Folders to mirror might not be saved to the user store during logoff when a parent folder is excluded using a wildcard (*).

User logons might hang when profile streaming is enabled, because Profile Management attempts a cache fill on a folder whose reparse point has already been removed by another thread.

Logon performance data for VDAs might not be displayed in Citrix Director when one of the Windows event logs that Profile Management watches cannot be read.

On the Citrix Director Personalization page, the Profile Path might still display the mounted container volume path instead of the SMB user store path when the entire Profile container with local caching is enabled. An earlier fix reported for this case in Profile Management 2603 was incomplete: it did not cover the WMI HealthCheck path, so the volume path could still be reported through that path. This release completes the fix.