![]() ![]() "Working" message in Citrix environment after upgrading to CONNECTION Client 11.00.02.xx Possible Issue 5 - BeyondTrust Privilege GuardĪn incompatibility with Avecto's BeyondTrust Privilege Guard has been discovered that interferes with the Microsoft Edge WebView2 Runtime we use in CONNECTION Client 11.00.02.xx or later. If you are using a Citrix environment with API Hooks enabled, the Microsoft Edge WebView client may need to be added as an exception per the following article: Please ask your IT team to check for updates or changes to the environment Possible issue 4 - Citrix Environment In a few cases, there is a local change to the Firewall and/or Anti-Virus configurations done by the Organization. Possible issue 3 - Firewall / Antivirus rules Uninstall x86 Edge Chromium and install 圆4 Edge Chromium. A 64-bit release is required for CONNECTION Client 11.00.02.xx or later to function. If a 32-bit release is installed, contact your IT team for further assistance. Note whether a 32-bit or 64-bit release is installed.Click the three dots in the upper right corner, and select Help and Feedback > About Microsoft Edge from the contextual menu.To confirm, please perform the following steps: Problems arise when a 32-bit Edge Chromium is installed on a 64-bit OS. Possible issue 2 - 32-bit installation of Microsoft Edge ![]() Restart CONNECTION Client by opening the system tray, clicking on the CONNECTION Client icon, and selecting Exit.Find Microsoft Edge WebView2 Runtime in the list of installed products, and remove it.Right-click on the Windows Start menu, and select Apps & Features from the contextual menu.Scroll to the bottom, and click the Download button under Evergreen Bootstrapper in the lower left corner to obtain a standalone installer for Microsoft Edge WebView2 Runtime.To resolve the issue, perform the following steps: After doing so, it sometimes fails to load thereafter. Microsoft Edge WebView2 Runtime periodically updates itself. Possible Issue 1 - WebView2 automatic update failed In almost all cases, we have identified this issue as a problem caused by Microsoft's Auto-update of the Edge Webviewer. The CONNECTION Client says "Working" and never completes sign in ![]()
0 Comments
Leave a Reply. |