Fixed issues

Profile containers might fail to load when you enable Profile Management on Azure non-domain-joined VMs.

Profile Management versions 2209, 2212, and 2303 might cause user profile sync issues, such as failing to populate the Start menu icons.

Profile containers (VHDX files) might show an Access Denied error message when you upgrade Profile Management from a version earlier than 2009 to version 2009 or later.

After you upgrade a VDA to 2203 LTSR CU2 with Profile Management enabled, a PowerShell window might pop up for a short amount of time. The issue occurs during the desktop session logon,

Profile Management might reset the customized Outlook OST path during user logon.

With the profile container-based Profile Management enabled, a user might have access to the profile files and folders of other users.

After you upgrade Profile Management from version 2212 to version 2203 LTSR CU1, the profile containers might fail to load.

When configuring an app access control rule to hide an application from certain computers, in addition to those computers, you must configure at least one OU for the assignments. If not, the rule applies to all OUs—the application is invisible to all computers in your domain.

The same issue occurs when you configure rules to hide an app from certain OUs. In addition to those OUs, you must configure at least one computer for the assignments. If not, the rule applies to all computers—the application is invisible to all computers in your domain.