Bug Fixes

Ivanti Automation tasks are not executed after configuring them to run as Notification type from the Workspace Control Console.

Link to KB article

Microsoft Windows Firewall service becomes unresponsive and results in a black screen when logging into Workspace Control sessions.

Link to KB article

During logon, if the printer creation process takes too long to complete, it prevents Workspace Control from establishing a connection between the VDX Plugin and the VDX Engine.

Link to KB article

After new Workspace Control Agent installations, Agent cache synchronization takes an unexpectedly long time to complete.

Link to KB article

When attempting to delete zones configured for global authorized files under their Access Control tab > Locations and Devices, it results in error message: The selected Locations and Devices cannot be removed because it is still referenced by the following objects.

Link to KB article

New Workspace Control managed applications disappear from the Workspace Control Console, under Composition > Applications, if their title contains Unicode characters.

Link to KB article

Workspace Control configures the screensaver timeout interval even when the screensaver is disabled from the Workspace Control Console under Composition > Desktop > Screensaver.

Link to KB article

Microsoft Exchange Online (Office 365) e-mail template no longer works.

Link to KB article

When the Workspace Control Shell is used, Microsoft Teams cannot be closed during log off.

Link to KB article

Execute Commands that use PowerShell scripts are carried out, but result in error message: (2) - The system cannot find the file specified.

Link to KB article

Long Desktop Background file names are truncated in the Workspace Preferences menu, under Background > Select.

Link to KB article

Pixelated icons are displayed for Citrix XenApp published application on the Citrix StoreFront website.

Link to KB article

When FSLogix is configured to run, it creates a new path: \Users\local_%username%. Writing data to this directory is blocked when Read-Only Blanketing is enabled in Workspace Control managed sessions on Windows Server 2019 machines. This is enabled in Workspace Control Console, under Security > Data > Read-Only Blanketing > Settings tab.

Link to KB article

Triggering a Relay Server force cache update from the Workspace Control Console results in error: Windows can not access the specified device, path, or file. You may not have the appropriate permissions to access the item.

Link to KB article

Under specific conditions, the results of Maintenance Actions are not reported correctly. These actions are configured in the Workspace Control Console under Administration > Maintenance.

Link to KB article

User settings are not synchronized if a Workspace refresh is performed when users log into Workspace Control managed sessions and then establish a VPN connection.

Link to KB article

Citrix Private VM hosted applications are not intercepted by Workspace Control.

Link to KB article

White lines at the end of digitally signed PowerShell scripts are removed, resulting in invalid digital signatures and the scripts failing to execute.

Link to KB article

The Windows desktop background is not always set in Workspace Control managed sessions.

Link to KB article

In the Workspace Control Console, under Security > Applications > User Installed Applications or Administration > Performance > CPU Optimization, entries in the Log tab can be displayed in incorrect order under the Time column.

Link to KB article

In the Workspace Control Console, under Composition > User Settings, if the Show all User Settings option is checked, the Load Policy column displays incorrect default settings.

Link to KB article

After configuring User Settings Capturing for a managed application, starting another managed application occurs only after the capture is complete.

Link to KB article

Profile Containers status not updating in local cache after enabling the Microsoft Profile Containers Integration.

Link to KB article

Checking the Do not show this message again option does not prevent further Network Security notifications from displaying.

Link to KB article

Disabling the Microsoft Profile Containers Integration triggers dialog box: Not all required parameters are filled in. Would you like to continue?

Link to KB article

After installing Workspace Control, an incomplete Workspace Control Agent cache causes user sessions to contain unmanaged shortcuts and generate multiple errors of type out-of-memory.

Link to KB article

In the Workspace Control Console, under Composition > Actions By Event > At Logon, managed applications launched through execute commands using %respfdir%\pwrgate.exe %application ID% as the command line can result in the application intermittently not starting.

Link to KB article

Workspace Control does not correctly restore user settings with Value=(Default) if their Data field is empty.

Link to KB article

Creating Building Blocks using the following command does not generate the corresponding XBB files:

pwrtech.exe /export path\<file path> /guid={<GUID>}

Link to KB article

When ImgGuard filter-driver is active, Surpass Viewer application is not displayed after being started. This occurs on Workspace Control version 10.4.50.0 or higher.

Link to KB article

Under Administration > Agents > Agents tab, no Workspace Control Agents are displayed upon request using the Search button. This occurs on Workspace Control 2021.1 (version 10.6.0.0 or 10.6.10.0) with MySQL as the database type.

Link to KB article

Differences between Building Blocks created from the Workspace Control Console and Building Blocks created using the pwrtech.exe command-line tool.

Link to KB article

Microsoft FSLogix configuration made in the Workspace Control Console is not applied correctly to VMware Horizon environments when Access Control is based on Active Directory membership.

Link to KB article

Microsoft Edge Chromium managed shortcut is removed from the taskbar upon starting a new Workspace Control session. This occurs on Workspace Control 2021.2 (version 10.6.10.0) running on Windows 10 build 20H2.

Link to KB article

When the UseStoreBrowse registry setting is configured to Yes, the Instant Passthrough zone membership configuration is not applied to published applications.

Link to KB article

When using the Workspace Control Shell, the taskbar is not visible when Windows exits the screensaver.

Link to KB article

Executing res.exe /config commands with additional parameters from Ivanti Automation or the Windows Task Scheduler, results in failure.

Link to KB article

Workspace Control Console 10.6.0.0 MSI file can trigger a virus alert.

Link to KB article

Workspace Control Management Portal 10.6.10.0 MSI file can trigger a malware alert from Symantec Endpoint Protection.

Link to KB article

When Citrix XenApp Publishing is used, the Remote Access Connection Manager service cannot start if the Secure Socket Tunneling Protocol Service is disabled on the Citrix server.

Link to KB article

Importing a connection file in the Workspace Control Agent using the command line, results in message: Ivanti Workspace Control Agent - Configure connection. Please enter a Cloud Relay Server Account Id.

Link to KB article

pwrcache.exe generates error: ProfileContainerConfigurationFactory.CreateConfiguration - Input String was not in a correct format. This occurs when configuration changes are made to Location and Devices or Workspace Containers in Workspace Control environments where the Microsoft Profile Container Integration was never enabled.

Link to KB article

Registry setting MonitorEndProgram does not work when Workspace Control is configured to use French or Norwegian languages.

Link to KB article

When a Workspace Control managed session is started, duplicate entries are created for User Registry settings of type string with Name={Default}.

Link to KB article

After upgrading from Workspace Control 10.0.400.0 to version 10.1.100.0, User Installed Applications are not visible in the Start Menu.

Link to KB article

Workspace Control Agent cache do not update successfully when the Microsoft TS RemoteApp integration is enabled.

Link to KB article

Windows 10 template for capturing taskbar settings causes Workspace Control to become unresponsive while loading.

Link to KB article

In the same Workspace Control managed session, starting second instances of Citrix published applications takes a minute before the instance starts.

Link to KB article

Opening PDF files from Workspace Control managed App-V applications takes over a minute before the file opens.

Link to KB article

After upgrading to Workspace Control 10.6.30.2, App-V applications configured as Workspace Control managed applications do not start.

Link to KB article

After upgrading to Workspace Control 10.6.30.2, managed applications configured with dynamic privileges do not start.

Link to KB article

After upgrading to Workspace Control 10.6.30.2, Folder Synchronization does not work on Windows Server operating systems. This option is found in the Workspace Control Console under Composition > Actions By Type > Files and Folders > Folder Synchronization.

Link to KB article

After upgrading to Workspace Control 10.6.30.2, user settings with Value=(Default) are restored with empty Data fields.

Link to KB article

The TCPIP.sys driver causes BSOD during Workspace Control managed sessions. The following error message is displayed: DRIVER IRSQL NOT LESS OR EQUAL failed tcpip.sys.

Link to KB article

When File Certificate Security is enabled, the Workspace Control splash screen does not load past 90% (Composing Data Sources) during session logon. This prevents the session logon to complete and prevents other users from logging into the same server.

Link to KB article

In a specific scenario where multiple Microsoft Windows Active Directory domains are configured in the Workspace Control Console, a delay occurs during the start of the Workspace Control managed session. The delay happens during Preparing Applications when users log on from an external domain.

Note: Refer to the KB article for the specific details of this scenario.

Link to KB article

After renaming the folder where a UWP package resides, the list of UWP applications is not properly populated when creating a new Workspace Control managed UWP application. This is done from the Workspace Control Console, under Composition > Applications > Start Menu tab.

Link to KB article

In the Workspace Control Console, under Administration > Agents > Agents tab, if the Filter is set to another option than the default (All Workspace Containers), it remains active even after switching to other node. This can cause Workspace Control Agents to not be visible under User Context > Workspace Containers.

Link to KB article

After upgrading to Workspace Control 10.6.40.0, under Composition > Applications, creating a new application using New Application (using wizard) results in an empty application after completing the wizard. The Edit application window appears, but all fields are empty and the new application cannot be saved without filling in the required fields.

Link to KB article

After upgrading Workspace Control Agents to version 10.6.30.2, Workspace Control Composer CPU usage is increased. This occurs when Workspace Control is used to manage Citrix published applications. The CPU usage increases with each Composer process (pfwsmgr.exe) running on the host of the published application.

Link to KB article

After upgrading to Workspace Control version 10.6.50.0, duplicating an application results in the creation of a copy without appending Copy of before the original application title. This occurs in the Workspace Control Console, under Composition > Applications > Start Menu tab. Right-click on an application and then select Duplicate from the context-menu.

Link to KB article

The text of the drop-down menu options for Setup > Integration > Ivanti Products > Ivanti Neurons for Edge Intelligence > Settings tab is editable.

When using Ivanti Cloud Relay, Workspace Control Agents sometimes create duplicate copies of the Agent.

Link to KB article

When users log into Workspace Control managed sessions configured to use the Workspace Control Shell as the default desktop shell, three instances of Microsoft Edge can be opened in the taskbar and cannot be closed. This behavior prevents users from logging off.

Link to KB article

In the Workspace Control Console, under Administration > Agents, configuring Run Workspace Composer to either Automatic or Manual does not work correctly for Workspace ControlAgents that are configured to connect to the Cloud Relay.

Link to KB article

A locally authenticated user with low privileges can leverage an unspecified attack vector to bypass Files and Folders Security. This makes it possible to start unapproved applications with elevated privileges.

Link to KB article

When setting up Ivanti Cloud Relay in new Workspace Control environments, the ConnectorId and ConnectorKey registry keys are not updated.

Link to KB article

When using the Ivanti Neurons for Edge Intelligence integration for Workspace Control, the Export to CSV option did not save the files to the Downloads folder on Windows machines. The CSV files were instead saved to the Windows temp directory.