Fixed issue in 2507 LTSR CU2

When Profile Management attempts to delete the local cached profile at logoff, the operation might fail with "Error 0x91: The directory is not empty" because reparse points created for streamed folders are not cleared.

After upgrading a Windows 10 image to Windows 11, applications might fail to auto-launch because the sessioninfo registry key is not cleared by the mid-session synchronization thread.

The User Profile Manager service (UserProfileManager.exe) might exit unexpectedly because of a race condition on the mid-session synchronization thread parameters.

The Profile Management service might crash on servers when the just-in-time profile context is released during logoff while the security processing thread is still using it.

Directories that you add to the exclusion list might still be synchronized by Profile Management when nested exclusions are configured.

When a duplicate session exists for the same user, sign-in might fail with the error "The Group Policy Client service failed the sign-in. Access is denied."

On Windows Server 2019, the local profile might not be cleaned up after a VDA upgrade, because the msteams folder cannot be deleted while Profile Management reparse points remain on it.

Profile Management might delete Windows system files at random over time, because the ProfileLoadTimeout event is global rather than per user and can trigger a local profile deletion with an empty profile path.

The server might experience a blue screen crash when multiple file cleanup operations occur simultaneously in the Profile Management streaming driver.

Profile data might be shown as offline in Director when the user store contains profile containers, because impersonation fails for container-based stores that have no junction point.

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

After upgrading from VDA 2203 CU2 to VDA 2402 CU3, mirrored folders located under a wildcard exclusion path might not be saved to the user store at logoff.

Winlogon notification registration might fail when the existing notification registry value exceeds the fixed buffer size that Profile Management uses.

The User Profile Manager service might crash with an access violation during mid-session container synchronization, when a disk interface query fails and the returned pointer is used without validation.

After upgrading the VDA from 2402 CU2 to 2507, random users might experience slow logons because Profile Management verifies the folder redirection path while resolving it during logon.

After upgrading UPM to 2507, users might experience slow logons because Profile Management sets ACEs on redirected folders during every logon.

Director and the Profile Management WMI diagnostics class might show the mounted container volume path instead of the SMB user store path as the Profile Path, when the entire profile container with local cache is enabled.

The Reset Profile option might be unavailable in Director, because Profile Management reports an incorrect profile type when the FSLogix Office container is enabled without the FSLogix profile container.

In rare cases, logon might hang while Profile Management is creating legacy profile junction points under the user profile, because the result of deleting the reparse tag is not checked when concurrent threads process the same folder.

After upgrading to 2402 CU3, the AppData\Local\Packages folder might not be created in the user store for new profiles, because a mirrored folder under an excluded path is copied with an incorrect parameter.

Outlook search might not work when Outlook search index roaming is enabled, because Profile Management cannot hook the search service on Windows 11 and Windows Server 2025.

Registry exclusion policies might not exclude keys whose names contain a forward slash, such as "PL/SQL Developer".

Microsoft Teams might be missing for new users after you upgrade the VDA to 2507 CU1, because Teams is not deployed to a fresh profile when App Layering is used.

The UPMACTION.sys driver might cause a blue screen crash in UPMACTION_EnsureSourceKey because of an incorrect parameter passed to the registry key creation routine.

Profile container compaction might not be replicated correctly, because the wrong destination path is used.