Common Issus with the new SwyxIt!

The information in this article applies to the following products:

• SwyxIt! ab Version 14
• SwyxIt! Classic

SUMMARY

This article describes some known issues that have been observed in the context of the ‘new’ SwyxIt! from Swyx version 14 onwards and suggests possible solutions.

COMMON ISSUES

Why is the new UI sometimes missing on terminal server environments?

• The app creates a registry key at Computer\HKEY_CURRENT_USER\Software\Swyx\SwyxIt!.Modern, enabling the ComSocket to verify that the interface versions of ComSocket and new SwyxIt! match. Since the key follows the user to a new session (configurable), while the installation directory %LocalAppData%\Local\Programs\SwyxIt! does not, the app is not automatically reinstalled in the new session.
  Note: This behaviour has been corrected in SwyxIt! 14.25 R1. If the registry key is validated positively when ComCocket is started and the installation directory is still empty, SwyxIt! will be reinstalled.

Why am I not being offered the automatic update?

• If the update dialog does not appear despite an available update, consider the following reasons:

  • The update service (https://service.update.swyx.net) is unreachable.

  • The update cannot download to %LocalAppData%\Local\swyxit!-updater due to AppLocker or group policy restrictions.

Why does the update installation fail?

• The installation unpacks and executes DLLs in the user's temporary directory. If AppLocker or group policy restrictions prevent DLL execution, the installation will fail.

Additional background information for a better understanding of the dependencies within the architecture of the new SwyxIt! can be found here: 5 Questions to the SwyxIt! Architects