Secure Client VPN upgrade not extracting UI folder

[Ollie8722]

I seem to be encountering an issue when upgrading Cisco Secure Client VPN from 5.1.5.65 to 5.1.6.103 where the UI folder does not extract the new UI version to the correct location  C:\Program Files (x86)\Cisco\Cisco Secure Client\UI.

Instead the shortcut UI file gets placed within C:\Program Files (x86)\Cisco\Cisco Secure Client\UI\Setup\5.1.5.1171 and breaks the shortcut.

Upgrade is being performed on a Win11 system via Intune and performing a restart after the upgrade.

[ccieexpert]

I would test this on a machine without intune and see if the same problem happens. if the problem happens, then you may want to open a TAC case ..also try as a test 5.1.7.80 which is the latest for isolation purposes and see if it is fixed in that version..

[Simperdy]

Our Intune packaging team has the same issue when installing Cisco Secure Client on Windows 11 with Intune. But today we also ran into this issue when updating the Cisco Secure Client with the webdeploy autoupdate on the ASA. The VPN Client establishes a connection, downloads the new version 5.1.12.146 and tries to install it over the old 5.1.7.80. The autoupdater then encouters an error during the update and the csc_ui shortcut is broken. It installs the new the new csc_ui "C:\Program Files (x86)\Cisco\Cisco Secure Client\UI\Setup\5.1.12.1179\csc_ui.exe" here but not in here "C:\Program Files (x86)\Cisco\Cisco Secure Client\UI\csc_ui.exe". I tested a manual update before this, where a colleague installed the predeploy .msi and it worked as expected.

[Simperdy]

Maybe it is a problem when installing the Cisco Secure Client in Windows 11 as "nt-authority\system" user. Looks like Intune and also the autoupdate process over the ASA are using this user.

[vivekshukla]

Did anyone found any solution for this issue. I am facing the same issue while deploying secure client via SCCM.