Known issues in previous releases

Workspace Environment Management service 2507.1.0.1

• Logon analysis data might not be generated for Azure AD user logons on Azure AD-joined machines.

Workspace Environment Management service 2505.1.0.1

• When updating registry entries, the operation might time out during bulk updates. As a workaround, process the updates page by page.
• When deleting expired users, the service might hang or fail if the number of expired users is too large.

Workspace Environment Management service 2504.1.0.1

• Cloud Health check fails if PowerShell execution policy is set to RemoteSigned. The issue is caused when the customer sets the policy to RemoteSigned.
• WEM web console shows SIDs instead of user names in the Manage assignments window. Assignment targets only display SID in Manage assignments window.

Workspace Environment Management service 2501.1.0.1

• When the .zip file content of the imported GPO registry .zip file is not valid, an error prompt gets displayed whereas though the .zip file is valid, the conversion of content to the registry fails.
• When a customer configures process hierarchy control rules with a hash type, agents with versions before 2412 generate an error in the service log when retrieving the process hierarchy control rules.
• When the customer creates action groups and adds external tasks to them, the legacy console crashes while viewing the action group content under Legacy Console > Actions > Action Groups, or under Legacy Console > Assignments > Action Assignment while viewing the assignments associated with these action groups.
• When restoring a configuration site that includes action groups containing process hierarchy control rules, the process hierarchy control rules are lost in these action groups.

Workspace Environment Management service 2412.1.0.1

• The source profile path does not match the actual user store profile path for some profiles in Windows 10 machines.

Workspace Environment Management service 2410.1.0.1

• The source profile path does not match the actual user store profile path for some profiles in Windows 10 machines.

Workspace Environment Management service 2409.1.0.1

• The source profile path does not match the actual user store profile path for some profiles in Windows 10 machines.

Workspace Environment Management service 2408.1.0.1

• While creating Start menu shortcuts and pinning applications to the Start menu, shortcuts are generated in the root folder of the Start menu instead of being created in the path specified. This issue occurs only on Windows Server 2022/2019 but not on Windows Server 2016.

Workspace Environment Management service 2407.2.0.1

• When you create an application security rule and add publisher conditions, it is deleted when you open the legacy console. The publisher condition's file path value is null which is specified as an invalid rule by the legacy console.
• When you try to log in to the Workspace via Citrix Environment Tool Hub > Application assistance using your Active Directory and Token, you see a blank workspace window.
• While creating Start menu shortcuts and pinning applications to the Start menu, shortcuts are generated in the root folder of the Start menu instead of being created in the path specified. This issue occurs only on Windows Server 2022/2019 but not on Windows Server 2016.

Workspace Environment Management service 2403.1.0.1

• While creating Start menu shortcuts and pinning applications to the Start menu, shortcuts are generated in the root folder of the Start menu instead of being created in the path specified. This issue occurs only on Windows Server 2022/2019 but not on Windows Server 2016.

Workspace Environment Management service 2401.1.0.1

• While creating Start menu shortcuts and pinning applications to the Start menu, shortcuts are generated in the root folder of the Start menu instead of being created in the path specified. This issue occurs only on Windows Server 2022/2019 but not on Windows Server 2016.

Workspace Environment Management service 2311.1.0.1

Workspace Environment Management service 2310.1.0.1

Workspace Environment Management service 2309.2.0.1

Workspace Environment Management service 2309.1.0.1

• Certain applications of the "Citrix Workspace™ (StoreFront™) resource" type, for example, SaaS applications, might fail to start on the agent machine.
• When the WEM agent runs on Windows Server 2022, the memory usage limit you apply to specific processes might not work as expected.

Workspace Environment Management service 2307.1.0.1

• Certain applications of the "Citrix Workspace (StoreFront) resource" type, for example, SaaS applications, might fail to start on the agent machine.
• When the WEM agent runs on Windows Server 2022, the memory usage limit you apply to specific processes might not work as expected.
• When the WEM agent fails to retrieve the policy settings during startup, the intended SMB connections (as configured by the SMB share settings) are not immediately accessible. In this scenario, you must wait for the next connection refresh, which occurs every 15 minutes.

Workspace Environment Management service 2306.1.0.1

• Certain applications of the "Citrix Workspace (StoreFront) resource" type, for example, SaaS applications, might fail to start on the agent machine.
• You might see the following error that appears intermittently in the Windows Event Log: HostDirectoryServicesController.IsCurrentDomainReachable(): Checking domain status timed out. Each time WEM fails to check that the domain is reachable, the error is written in the Windows Event Log. The checks are necessary when WEM processes policies. This issue does not affect the functionality of the WEM agent.
• Attempts to restore a configuration set may fail if it contains too many (for example, 10,000) template-based GPOs.
• When the WEM agent runs on Windows Server 2022, the memory usage limit you apply to specific processes might not work as expected.

Workspace Environment Management service 2304.2.0.1

• Certain applications of the "Citrix Workspace (StoreFront) resource" type, for example, SaaS applications, might fail to start on the agent machine.

Workspace Environment Management service 2304.1.0.1

• Certain applications of the "Citrix Workspace (StoreFront) resource" type, for example, SaaS applications, might fail to start on the agent machine.

Workspace Environment Management service 2302.1.0.1

• Certain applications of the "Citrix Workspace (StoreFront) resource" type, for example, SaaS applications, might fail to start on the agent machine.

Workspace Environment Management service 2301.1.0.1

• In the legacy console, when you click the State column header to sort, items are not sorted as expected.
• In the legacy console, the Backup Actions button is not available when you use the backup wizard to back up Group Policy settings. The issue occurs even if the configuration set does not contain any resources created using the web console.

Workspace Environment Management service 2211.1.0.1

• When running in offline mode, the agent can't connect to the SMB shares you configured in Advanced Settings > File Shares. This issue does not affect the functionality of the agent.

Workspace Environment Management service 2210.2.0.1

• If you restore settings from a previous backup, you experience issues with user store-related credentials.
  • In the legacy console, you can't save changes made to the credentials.
  • In the web console, the restored credentials fail to appear in Advanced Settings > File Shares.
• On Mozilla Firefox browsers, the built-in scripted task Cloud Health Check fails to appear above custom scripted tasks.
• An application security rule fails to work when both of the following conditions are met:
  • It's an exception rule of the publisher type.
  • "And above" or "And below" is selected for the file version.

Workspace Environment Management service 2210.1.0.1

• If you restore settings from a previous backup, you experience issues with user store-related credentials.
  • In the legacy console, you can't save changes made to the credentials.
  • In the web console, the restored credentials fail to appear in Advanced Settings > File Shares.
• On Mozilla Firefox browsers, the built-in scripted task Cloud Health Check fails to appear above custom scripted tasks.

Workspace Environment Management service 2208.1.0.1

• In the web console, when you use the filter, Last logon, to refine results in Monitoring > Administration > User Statistics, the filter might not work as expected. The issue occurs when you leave the end date unspecified. As a workaround, specify an end date when using the filter.

Workspace Environment Management service 2207.2.0.1

Workspace Environment Management service 2207.1.0.1

Workspace Environment Management service 2206.2.0.1

• In the web console, attempts to add or edit registry operations of the following types might fail: REG_QWORD and REG_QWORD_LITTLE_ENDIAN. The issue occurs when you type a decimal value that exceeds 9007199254740991 or a hexadecimal value that exceeds 1FFFFFFFFFFFFF. As a workaround, use the legacy console instead.
  If you use the web console to edit registry operations of the two types whose value exceeds the limit, you see the following error message: Invalid value or format. You can dismiss the message.

Workspace Environment Management service 2205.1.0.1

• When you use VUEMRSAV.exe to view results about actions applied through an action group for the current user, the Applied Actions tab might display the incorrect source of the actions. Example: Two action groups (Group1 and Group 2) were assigned to the user and Group1 contains Application1. The Applied Actions tab might also show that Application1 is from Group2 even if Group2 does not contain Application1. (By default, VUEMRSAV.exe is located in the agent installation folder: %ProgramFiles%\Citrix\Workspace Environment Management Agent\VUEMRSAV.exe.)

Workspace Environment Management service 2204.2.0.1

• When you use VUEMRSAV.exe to view results about actions applied through an action group for the current user, the Applied Actions tab might display the incorrect source of the actions. Example: Two action groups (Group1 and Group 2) were assigned to the user and Group1 contains Application1. The Applied Actions tab might also show that Application1 is from Group2 even if Group2 does not contain Application1. (By default, VUEMRSAV.exe is located in the agent installation folder: %ProgramFiles%\Citrix\Workspace Environment Management Agent\VUEMRSAV.exe.)
• When you import your AppLocker rules exported from the Microsoft AppLocker console into WEM, rules of the hash type cannot be imported.
• When using Legacy Console > Assignments > Modeling Wizard, you might not be able to view the resultant actions for a user in a nested group. The issue occurs when the user does not reside in the top group to which the actions or action groups are assigned. Example: The top group is GroupA, GroupB is its member, and UserA is in GroupB. If you assign actions or action groups to GroupA, you cannot view the resultant actions for UserA by using Modeling Wizard.

Workspace Environment Management service 2204.1.0.1

• When you import your AppLocker rules exported from the Microsoft AppLocker console into WEM, rules of the hash type cannot be imported.
• With self-elevation or privilege elevation disabled, the WEM agent might write the following error to the Windows Event Log even if users experience no issues with their environment: System.ArgumentException: Cannot delete a subkey tree because the subkey does not exist.

Workspace Environment Management service 2203.2.0.1

• Attempts to restore self-elevation rules to a different configuration set might fail.

Workspace Environment Management service 2201.2.0.1

• On Windows 10 and Windows 11 machines, certain settings such as environment settings that you configured in the administration console might not work.
• Attempts to restore self-elevation rules to a different configuration set might fail.

Workspace Environment Management service 2201.1.0.1

• On Windows 10 and Windows 11 machines, certain settings such as environment settings that you configured in the administration console might not work.

Workspace Environment Management service 2110.2.0.1

• On Windows 10 and Windows 11 machines, certain settings such as environment settings that you configured in the administration console might not work.
• On the Administration Console > Policies and Profiles > Microsoft USV Settings > Folder Redirection tab, with both Redirect AppData (Roaming) and Delete Local Redirected Folders enabled, the WEM agent fails to apply the following settings:
  • Redirect Contacts
  • Redirect Downloads
  • Redirect Links
  • Redirect Searches
• After you upgrade to 2103 or later, the WEM agent might write errors to the Windows Event Log every five minutes even if users experience no issues with their environment.

Workspace Environment Management service 2110.1.0.1

• On Windows 10 and Windows 11 machines, certain settings such as environment settings that you configured in the administration console might not work.
• After Windows Update installs KB5005033 on an agent host, assigned printers do not work. The issue occurs because the update prevents the automatic start of the Windows Print Spooler service. As a workaround, start the service manually.
• After you upgrade to Windows Server 2022, the WEM infrastructure service might fail to respond. As a workaround, reinstall the infrastructure service and configure it to connect to the WEM database.
• After you upgrade to 2103 or later, the WEM agent might write errors to the Windows Event Log every five minutes even if users experience no issues with their environment.
• When you click Apply to save your environment settings, the administration console might exit unexpectedly. The issue occurs because the Style setting of Environmental Settings > Start Menu > Set Wallpaper is left empty. (If you previously set Style to Fill or Fit, the setting became empty after you upgraded the administration console to version 2109.) Workaround: Do not leave the Style setting empty.

Workspace Environment Management service 2109.2.0.1

• On Windows 10 and Windows 11 machines, certain settings such as environment settings that you configured in the administration console might not work.
• After Windows Update installs KB5005033 on an agent host, assigned printers do not work. The issue occurs because the update prevents the automatic start of the Windows Print Spooler service. As a workaround, start the service manually.
• After you upgrade to Windows Server 2022, the WEM infrastructure service might fail to respond. As a workaround, reinstall the infrastructure service and configure it to connect to the WEM database.
• When you click Apply to save your environment settings, the administration console might exit unexpectedly. The issue occurs because the Style setting of Environmental Settings > Start Menu > Set Wallpaper is left empty. (If you previously set Style to Fill or Fit, the setting became empty after you upgraded the administration console to version 2109.) Workaround: Do not leave the Style setting empty.

Workspace Environment Management service 2107.2.0.1

• When you apply privilege elevation to a 32-bit executable, the privilege of the executable can be successfully elevated on machines running a 64-bit Windows operating system. However, its child processes automatically inherit the privilege whether or not the Apply to Child Processes setting is selected in the executable rule.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2107.1.0.1

• If you use the [ADAttribute:objectSid] dynamic token to extract the objectsid attribute, the WEM agent fails to extract the attribute of the corresponding AD object.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2106.2.0.1

• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2105.1.0.1

• If you assign a printer to a user based on a filter and the assignment satisfies the filter criteria, the WEM agent assigns the printer to the user. However, the agent still assigns the printer to the user the next time the user logs on even when the assignment does not satisfy the filter criteria at that time.
• When you assign an action to a user or user group through an action group, the action still takes effect even if it is set to Disabled in the administration console.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2104.1.0.1

• If you assign a printer to a user based on a filter and the assignment satisfies the filter criteria, the WEM agent assigns the printer to the user. However, the agent still assigns the printer to the user the next time the user logs on even when the assignment does not satisfy the filter criteria at that time.
• If you assign a file system operations action and update the action later, the files or folders that were previously copied to the user environment might be deleted. The issue occurs because the WEM agent reverts the assignment made earlier after you update the action.
• With Agent Type set to CMD on the Advanced Settings > Configuration > Main Configuration tab, the Monitoring > Daily Reports > Daily Login Report tab might fail to display a summary of logon times across all users connected to the current configuration set.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2103.2.0.1

• You might experience performance issues such as slow logon or slow session disconnect when launching or disconnecting from published application sessions. The issue occurs with WEM agent 2005 and later.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2101.2.0.1

• For logging level changes to take effect immediately, the WEM agent might access certain registry keys frequently, thus affecting performance.
• With an action group assigned to multiple users or user groups, if you unassign it from a user or user group, the assignment might not work as expected. For example, you assign an action group to two user groups: Group A and Group B. If you unassign the action group from Group A, the action group is unassigned from Group B rather than Group A.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2101.1.0.1

• When using the application security feature, you see a green checkmark next to a user or user group in the Assigned column of the Assignments section in the Edit Rule or Add Rule window. The green checkmark icon does not necessarily indicate that the rule is assigned to that user or user group. Only a user or user group with a blue background is the one to which the rule is assigned.
• The privilege elevation feature might fail to work properly. The issue occurs with the following versions of the WEM agent: 2010.2.0.1, 2011.1.0.1, and 2101.1.0.1. The issue occurs because the certificate used to sign the Citrix WEM software has expired. To work around the issue, uninstall the relevant WEM agent, install the latest WEM agent, and then restart the agent host.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2011.1.0.1

• When using the application security feature, you see a green checkmark next to a user or user group in the Assigned column of the Assignments section in the Edit Rule or Add Rule window. The green checkmark icon does not necessarily indicate that the rule is assigned to that user or user group. Only a user or user group that has a blue highlight in the background is the one to which the rule is assigned.
• The privilege elevation feature might fail to work properly. The issue occurs with the following versions of the WEM agent: 2010.2.0.1 and 2011.1.0.1. The issue occurs because the certificate used to sign the Citrix WEM software has expired. To work around the issue, uninstall the relevant WEM agent, install the latest WEM agent, and then restart the agent host.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2010.2.0.1

• After you upgrade the WEM agent to version 1912, the memory consumption of Citrix WEM Agent Host Service might exceed 2G. If debug mode is enabled, you can see that the following messages appear many times in the Citrix WEM Agent Host Service Debug.log file:
  • Adding history entry to the DB writer queue
  • Initializing process limitation thread for process
• After you upgrade the WEM agent to version 2005, Citrix WEM Agent Host Service might consume between 10% and 30% of the total CPU resources, affecting the user experience.
• When using the application security feature, you see a green checkmark next to a user or user group in the Assigned column of the Assignments section in the Edit Rule or Add Rule window. The green checkmark icon does not necessarily indicate that the rule is assigned to that user or user group. Only a user or user group that has a blue highlight in the background is the one to which the rule is assigned.
• After you select a registry file in the Import from Registry File window, the Manage tab displays a black screen if you press ESC to exit the window and then click Yes.
• The privilege elevation feature might fail to work properly. The issue occurs with the WEM agent version 2010.2.0.1. The issue occurs because the certificate used to sign the Citrix WEM software has expired. To work around the issue, uninstall the relevant WEM agent, install the latest WEM agent, and then restart the agent host.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2010.1.0.1

• After you upgrade the WEM agent to version 1912, the memory consumption of Citrix WEM Agent Host Service might exceed 2G. If debug mode is enabled, you can see that the following messages appear many times in the Citrix WEM Agent Host Service Debug.log file:
  • Adding history entry to the DB writer queue
  • Initializing process limitation thread for process
• After you upgrade the WEM agent to version 2005, Citrix WEM Agent Host Service might consume between 10% and 30% of the total CPU resources, affecting the user experience.
• When using the application security feature, you see a green checkmark next to a user or user group in the Assigned column of the Assignments section in the Edit Rule or Add Rule window. The green checkmark icon does not necessarily indicate that the rule is assigned to that user or user group. Only a user or user group that has a blue highlight in the background is the one to which the rule is assigned.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2009.1.0.1

• After you upgrade the WEM agent to version 1912, the memory consumption of Citrix WEM Agent Host Service might exceed 2G. If debug mode is enabled, you can see that the following messages appear many times in the Citrix WEM Agent Host Service Debug.log file:
  • Adding history entry to the DB writer queue
  • Initializing process limitation thread for process
• After you upgrade the WEM agent to version 2005, Citrix WEM Agent Host Service might consume between 10% and 30% of the total CPU resources, affecting the user experience.
• The WEM administration console might fail to display the changes you made to the working directory for an installed application the next time you edit the application.
• In non-persistent environments, changes you make through the administration console might fail to take effect on the agent hosts. The issue occurs because the agent cache file in the base image might cause cache synchronization problems. As a workaround, users must first delete the cache on their agent hosts and then refresh the cache manually to synchronize the cache with the infrastructure services.
  The recommended best practice is to use a persistent location for the agent cache. If the agent cache resides in a non-persistent location, take these steps before sealing the base image:
  1. Stop Citrix WEM Agent Host Service.
  2. Delete these agent local database files: LocalAgentCache.db and LocalAgentDatabase.db.
• The following options are not mutually exclusive. However, the administration console does not allow you to configure them at the same time.
  • Hide Specified Drives from Explorer and Restrict Specified Drives from Explorer (on the Policies and Profiles > Environmental Settings > Windows Explorer tab)
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2008.1.0.1

• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2007.2.0.1

• When editing a default packaged rule, you are prompted to provide valid values on the Publisher tab of the Edit Rule window, with the OK button grayed out. However, the OK button remains grayed out even if you provide valid values on the Publisher tab later.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2007.1.0.1

• When you finish importing your Group Policy settings into WEM, the following message might appear even if you are the only administrator that is using the administration console:
  • Configuration Change Update: An administrator has made configuration-related changes. Click OK to reflect the changes in the current administration console.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2006.2.0.1

• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2006.1.0.1

• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2005.1.0.1

• In Transformer (kiosk) mode, and with Enable Window Mode enabled, the WEM agent might exit unexpectedly.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2004.1.0.1

• Attempts to start an application from the My Applications icon list in the agent UI might fail. The issue occurs with application shortcuts that are created using StoreFront URLs.
• Agents might fail to synchronize with the WEM service in Citrix Cloud. The issue occurs when you configure an HTTPS proxy to define how agents communicate with the service.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2002.1.0.1

• On the agent host, attempts to start a published application as an application shortcut might fail. The issue occurs with application shortcuts that are created using StoreFront URLs.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 2001.1.0.1

• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• Registry entries might not take effect if you assign them to a user or user group through an action group. However, they do take effect if you assign them directly. The issue occurs when you assign registry entries to be created in one of the following locations:
  • %ComputerName%\HKEY_CURRENT_USER\SOFTWARE\Policies
  • %ComputerName%\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies
• Workspace agent refreshes might take a long time to complete. The issue occurs when the current user belongs to many user groups and there are action groups or many actions for the agent to process.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 1911.1.0.1

• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• Registry entries might not take effect if you assign them to a user or user group through an action group. However, they do take effect if you assign them directly. The issue occurs when you assign registry entries to be created in one of the following locations:
  • %ComputerName%\HKEY_CURRENT_USER\SOFTWARE\Policies
  • %ComputerName%\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 1910.1.0.1

• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• The Restore wizard might take a long time to load the Active Directory (AD) objects after you select Machines as the type of AD objects you want to restore and click Next. The issue occurs when there are many OUs (for example, 4,000).
• Registry entries might not take effect if you assign them to a user or user group through an action group. However, they do take effect if you assign them directly. The issue occurs when you assign registry entries to be created in one of the following locations:
  • %ComputerName%\HKEY_CURRENT_USER\SOFTWARE\Policies
  • %ComputerName%\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies
• The Use Cache Even When Online option on the Administration Console > Advanced Settings > Configuration > Agent Options tab might not work.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 1908.2.0.1

• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• After you migrate your on-premises WEM database to the WEM service, you must reinstall the WEM service agent even if the latest version is installed on your machine. This is necessary because the agent cache cannot synchronize with the WEM service database unless you reinstall the WEM service agent.
• In Transformer (kiosk) mode, and with Log Off Screen Redirection enabled, WEM might fail to redirect the user to the logon page after logging off.
• The Restore wizard might take a long time to load the Active Directory (AD) objects after you select Machines as the type of AD objects you want to restore and click Next. The issue occurs when there are many OUs (for example, 4,000).
• Registry entries might not take effect if you assign them to a user or user group through an action group. However, they do take effect if you assign them directly. The issue occurs when you assign registry entries to be created in one of the following locations:
  • %ComputerName%\HKEY_CURRENT_USER\SOFTWARE\Policies
  • %ComputerName%\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 1908.1.0.1

• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• On the Active Directory Objects tab of the administration console, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management™ allows multiple objects to be identified and added without closing the dialog each time.)
• After you migrate your on-premises WEM database to the WEM service, you must reinstall the WEM service agent even if the latest version is installed on your machine. This is necessary because the agent cache cannot synchronize with the WEM service database unless you reinstall the WEM service agent.
• In Transformer (kiosk) mode, and with Log Off Screen Redirection enabled, WEM might fail to redirect the user to the logon page after logging off.
• The Restore wizard might take a long time to load the Active Directory (AD) objects after you select Machines as the type of AD objects you want to restore and click Next. The issue occurs when there are many OUs (for example, 4,000).
• Registry entries might not take effect if you assign them to a user or user group through an action group. However, they do take effect if you assign them directly. The issue occurs when you assign registry entries to be created in one of the following locations:
  • %ComputerName%\HKEY_CURRENT_USER\SOFTWARE\Policies
  • %ComputerName%\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 1907.2.0.1

• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• On the Active Directory Objects tab of the administration console, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management allows multiple objects to be identified and added without closing the dialog each time.)
• After you migrate your on-premises WEM database to the WEM service, you must reinstall the WEM service agent even if the latest version is installed on your machine. This is necessary because the agent cache cannot synchronize with the WEM service database unless you reinstall the WEM service agent.
• In Transformer (kiosk) mode, and with Log Off Screen Redirection enabled, WEM might fail to redirect the user to the logon page after logging off.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 1907.1.0.1

• Instances of Adobe Reader installed on Windows Server 2012 R2 prevent Workspace Environment Management from associating PDF files with other PDF reader applications. Users are forced to select the PDF reader application each time they open a PDF.
• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• On the Active Directory Objects tab of the administration console, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management allows multiple objects to be identified and added without closing the dialog each time.)
• After you migrate your on-premises WEM database to the WEM service, you must reinstall the WEM service agent even if the latest version is installed on your machine. This is necessary because the agent cache cannot synchronize with the WEM service database unless you reinstall the WEM service agent.
• In Transformer (kiosk) mode, and with Log Off Screen Redirection enabled, WEM might fail to redirect the user to the logon page after logging off.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 1906

• Instances of Adobe Reader installed on Windows Server 2012 R2 prevent Workspace Environment Management from associating PDF files with other PDF reader applications. Users are forced to select the PDF reader application each time they open a PDF.
• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• On the Active Directory Objects tab of the administration console, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management allows multiple objects to be identified and added without closing the dialog each time.)
• After you migrate your on-premises WEM database to the WEM service, you must reinstall the WEM service agent even if the latest version is installed on your machine. This is necessary because the agent cache cannot synchronize with the WEM service database unless you reinstall the WEM service agent.
• In Transformer (kiosk) mode, and with Log Off Screen Redirection enabled, WEM might fail to redirect the user to the logon page after logging off.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 1904

• Instances of Adobe Reader installed on Windows Server 2012 R2 prevent Workspace Environment Management from associating PDF files with other PDF reader applications. Users are forced to select the PDF reader application each time they open a PDF.
• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• On the Active Directory Objects tab of the administration console, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management allows multiple objects to be identified and added without closing the dialog each time.)
• After you migrate your on-premises WEM database to the WEM service, you must reinstall the WEM service agent even if the latest version is installed on your machine. This is necessary because the agent cache cannot synchronize with the WEM service database unless you reinstall the WEM service agent.
• In Transformer (kiosk) mode, and with Log Off Screen Redirection enabled, WEM might fail to redirect the user to the logon page after logging off.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 1812.1.0.1

• Instances of Adobe Reader installed on Windows Server 2012 R2 prevent Workspace Environment Management from associating PDF files with other PDF reader applications. Users are forced to select the PDF reader application each time they open a PDF.
• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• On the Active Directory Objects tab of the administration console, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management allows multiple objects to be identified and added without closing the dialog each time.)
• After you migrate your on-premises WEM database to the WEM service, you must reinstall the WEM service agent even if the latest version is installed on your machine. This is necessary because the agent cache cannot synchronize with the WEM service database unless you reinstall the WEM service agent.
• In Transformer (kiosk) mode, and with Log Off Screen Redirection enabled, WEM might fail to redirect the user to the logon page after logging off.
• When you click Apply Filter or Refresh Report on the Administration Console \> Monitoring \> User Trends \> Devices Types tab, you might not be able to view the report. Instead, you are returned to the Administration Console \> Actions \> Applications \> Application List tab.
• On Windows 10 version 1809 and Windows Server 2019, Workspace Environment Management fails to pin the applications to the task bar.
• After WEM upgrades to the latest version, if you still use the earlier versions of the agent, the agent fails to work properly in offline mode. This issue occurs because of the scope changes of the agent local cache file in the latest release. As a workaround, delete the old agent local cache file, and then restart the WEM Agent Host Service (Norskale Agent Host service).
• On the Security tab of the administration console, if you create an AppLocker rule for a file with an .exe or a .dll extension using a file hash condition, the rule does not work. This issue occurs because WEM calculates the hash code of that file incorrectly.
• On the Security tab of the administration console, if you create an AppLocker rule for a file using a publisher condition, the rule does not work. This issue occurs because WEM resolves the file name incorrectly.
• If you click Add OU on the administration console, WEM might not display anything on the Organizational Units window. The issue occurs when a forest (current or trusted) contains many OUs. As a workaround, you might need to click Cancel and then click Add OU multiple times.
• The Application Security feature does not work on Windows servers that use non-English Windows operating systems. This issue occurs because WEM fails to start the Application Identity service in non-English language environments.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 1812.0.0.1

• Instances of Adobe Reader installed on Windows Server 2012 R2 prevent Workspace Environment Management from associating PDF files with other PDF reader applications. Users are forced to select the PDF reader application each time they open a PDF.
• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• On the Active Directory Objects tab of the administration console, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management allows multiple objects to be identified and added without closing the dialog each time.)
• After you migrate your on-premises WEM database to the WEM service, you must reinstall the WEM service agent even if the latest version is installed on your machine. This is necessary because the agent cache cannot synchronize with the WEM service database unless you reinstall the WEM service agent.
• In Transformer (kiosk) mode, and with Log Off Screen Redirection enabled, WEM might fail to redirect the user to the logon page after logging off.
• When you click Apply Filter or Refresh Report on the Administration Console \> Monitoring \> User Trends \> Devices Types tab, you might not be able to view the report. Instead, you are returned to the Administration Console \> Actions \> Applications \> Application List tab.
• On Windows 10 version 1809 and Windows Server 2019, Workspace Environment Management fails to pin the applications to the task bar.
• After WEM upgrades to the latest version, if you still use the earlier versions of the agent, the agent fails to work properly in offline mode. This issue occurs because of the scope changes of the agent local cache file in the latest release. As a workaround, delete the old agent local cache file, and then restart the WEM Agent Host Service (Norskale Agent Host service).
• On the Security tab of the administration console, if you create an AppLocker rule for a file with an .exe or a .dll extension using a file hash condition, the rule does not work. This issue occurs because WEM calculates the hash code of that file incorrectly.
• On the Security tab of the administration console, if you create an AppLocker rule for a file using a publisher condition, the rule does not work. This issue occurs because WEM resolves the file name incorrectly.
• Attempts to map a network drive to users fail if you select the character # as the drive letter for that network drive in the Assign Filter & Drive Letter window. This issue occurs because WEM currently does not support assigning a random letter to a network drive by using "#."
• Attempts to migrate your WEM database into the WEM service can fail. The issue occurs when the entries in the VUEMTasksHistory table of your on-premises WEM database contain special characters. As a workaround, delete those entries from your on-premises WEM database, and then restart the migration process.
• If you click Add OU on the administration console, WEM might not display anything on the Organizational Units window. The issue occurs when a forest (current or trusted) contains many OUs. As a workaround, you might need to click Cancel and then click Add OU multiple times.
• The Application Security feature does not work on Windows servers that use non-English Windows operating systems. This issue occurs because WEM fails to start the Application Identity service in non-English language environments.
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 1811

• Instances of Adobe Reader installed on Windows Server 2012 R2 prevent Workspace Environment Management from associating PDF files with other PDF reader applications. Users are forced to select the PDF reader application each time they open a PDF.
• If you open the Workspace Environment Management service administration console using Internet Explorer 11 (IE11) or Microsoft Edge, and open the Developer Tools pane (F12), when you close the Developer Tools pane again the administration console does not redraw to full size. If this happens, refresh the browser window to redraw the administration console correctly.
• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• On the Active Directory Objects tab of the administration console, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management allows multiple objects to be identified and added without closing the dialog each time.)
• After you migrate your on-premises WEM database to the WEM service, you must reinstall the WEM service agent even if the latest version is installed on your machine. This is necessary because the agent cache cannot synchronize with the WEM service database unless you reinstall the WEM service agent.
• Attempts to access the administration console from the Workspace Environment Management service Manage tab fail. As a workaround, refresh your browser window and try again.
• Attempts to run the UpmConfigCheck script on Windows 7 Service Pack 1, Windows 2008 R2 Service Pack 1, or Windows Server 2008 Service Pack 2 fail. To run the script on those operating systems, you must manually install Windows Management Framework 3.0. If the UpmConfigCheck still does not work after you install Windows Management Framework 3.0, restart your WEM agent host service (Norskale Agent Host Service).
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.

Workspace Environment Management service 1807

• On Windows Server 2012 R2, if Adobe Acrobat Reader is installed, it prevents Workspace Environment Management from associating PDF files with other PDF reader applications. Users are forced to select the PDF reader application each time they open a PDF.
• On the Security tab, when you clear the option Process DLL Rules, the rule count reported next to the "DLL Rules" collection is set to zero, regardless of the actual number in the WEM database.
• If multiple session support is enabled on a Windows server OS machine, application security rules of previously logged on users are replaced by rules of more recently logged on users. For example, if a rule is assigned to user1 but not to user2, when user2 logs on, the rule is deleted from local AppLocker rules. Thus the rule cannot be enforced for user1 as well.
• If you open the Workspace Environment Management service administration console using Internet Explorer 11 (IE11) or Microsoft Edge, and open the Developer Tools pane (F12), when you close the Developer Tools pane again the administration console does not redraw to full size. If this happens, refresh the browser window to redraw the administration console correctly.
• Agent host machine names listed on the Active Directory Objects tab of the WEM service administration console do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again.
• The on-premises version of Workspace Environment Management (WEM) allows you to use Active Directory security groups as containers for WEM agents. However, the WEM service does not support using Active Directory security groups as agent containers. The on-premises infrastructure service also supports using direct and indirect OUs as agent containers. However, the WEM service does not support indirect OUs. For example, suppose WEM agent AGENT1 belongs to OU2, and OU2 belongs to OU1 (OU1>OU2>AGENT1). The on-premises infrastructure service recognizes AGENT1 as a member of both OU1 and OU2, but the WEM service only recognizes AGENT1 as a member of OU2.
• In the administration console Active Directory Objects tab, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management allows multiple objects to be identified and added without closing the dialog each time.)
• On Windows 10 machines, environment and certain other settings that you configured in the administration console might not work.