Archive. This is an archive of the Apple Support Community. Discussions are being restored and soon you will be able to read and post here again.

MacOs Ventura 13.7.8 (Intel x86 64) X CISCO Client VPN 5.1.20.333

I am experiencing issues opening the newly updated Cisco VPN Client (version 5.1.20.333) on my MacBook Pro running macOS Ventura 13.7.8 (Intel x86-64). The application installs without error messages and the process completes successfully, but when I try to launch it, the icon flashes briefly and the app fails to open.

3 replies

Hi,

Google AI says:


The most likely cause for Cisco Secure Client (version 5.1.20.333) crashing immediately upon launch on macOS Ventura is an issue with the background daemon (vpnagentd), orphaned preference files from the previous version, or blocked system/socket extensions.

Because the installer completed successfully, the underlying system binaries are present, but the GUI application is failing to handshake with the background service or is reading a corrupt preference file. Follow these structured steps to resolve the issue.


1. Reset Leftover Preferences and Cache

Upgrading Cisco clients on macOS frequently leaves behind conflicting application states. Clearing these often resolves instantaneous startup crashes.


  1. Completely quit the app if it's running in the background.
  2. Open Finder, press Cmd + Shift + G, and navigate to:
  3. /opt/cisco/secureclient/vpn/
  4. Delete any corrupted profile or preferences XML files (such as preferences.xml or custom .xml files). Note: You may want to back them up to your desktop first.
  5. Go to ~/Library/Preferences/ and look for any file containing com.cisco.Cisco-Secure-Client or com.cisco.anyconnect, then move them to the Trash.

2. Verify and Force Start the Background Daemon

The GUI client will instantly close or flash if the underlying macOS daemon (vpnagentd) is not active.


  1. Open the Terminal app.
  2. Check if the service is running by executing:
  3. bash
sudo launchctl list | grep cisco
  1. Be careful using code.
  2. If it is missing or not responding, force-load the daemon with the following command:
  3. bash
sudo launchctl load -w /Library/LaunchDaemons/com.cisco.secureclient.vpnagentd.plist
  1. Be careful using code.
  2. (For older upgrade paths, the path might still be /Library/LaunchDaemons/com.cisco.anyconnect.vpnagentd.plist).

3. Check System Extension Approvals

macOS Ventura strictly enforces security gates on Network Extensions. If the Socket Filter or Core VPN extension failed to prompt for administrative privileges during the installation, the client will immediately exit on launch.


  1. Go to Apple Menu  > System Settings > Privacy & Security.
  2. Scroll down to the Security section.
  3. Look for a message stating "System software from application 'Cisco Secure Client' was blocked from loading." 
  4. Click Allow and enter your macOS administrator password.
  5. Restart your MacBook Pro to allow the kernel extension to attach successfully.

4. Perform a Clean Reinstallation

If the steps above do not stop the flashing crash, the installation package might have misconfigured modules for your Intel architecture. Use the built-in uninstaller rather than dragging the app to the trash to completely purge system extensions.


  1. Navigate to /Applications/Cisco/ and double-click Uninstall Cisco Secure Client.
  2. Follow the prompt to remove all components and restart your Mac.
  3. Re-run the version 5.1.20.333 installer package. When selecting modules, ensure only the VPNcomponent and DART (Diagnostics and Reporting Tool) are selected if you do not use other Cisco services like Umbrella or ISE Posture


Connecting to a SAML VPN on macOS Ventura When Cisco Secure Client Crashes

If Cisco Secure Client crashes at startup on an Intel MacBook Pro running macOS Ventura 13.7.8, OpenConnect with openconnect-saml and an installed Microsoft Edge browser may provide an alternative.

This approach bypasses the Cisco interface. It does not repair it, and compatibility depends on the VPN server’s authentication and security requirements.

Prerequisites

  • Homebrew
  • Python and pipx
  • Microsoft Edge installed
  • Your organization’s official VPN server address
  • An account authorized to access that VPN

Follow your organization’s policy regarding third-party VPN clients.

1. Install pipx if needed

If Homebrew is already available:

brew install pipx
pipx ensurepath

Restart the terminal afterward.

2. Install OpenConnect

OpenConnect establishes the VPN tunnel:

brew install openconnect

Verify the installation:

openconnect --version

Homebrew may compile dependencies on older macOS versions. Wait for installation to finish before continuing.

3. Install the SAML authentication tool

pipx install "openconnect-saml[chrome]"
pipx install "openconnect-saml[chrome]==0.24.5"
This guide was tested with openconnect-saml 0.24.5.The command above installs the latest available
 version, which may behave differently.

Verify that Playwright is installed in the same environment:

pipx runpip openconnect-saml show playwright

The version above pins the authentication tool to a specific release. Future releases may behave differently.

4. Use an installed browser

Downloading Playwright’s bundled Chromium can fail on Ventura with:

Playwright does not support chromium on mac13

The tool supports selecting an installed Microsoft Edge browser instead:

--browser chrome --chrome-channel msedge

This avoids downloading bundled Chromium and does not require the optional PyQt6 browser backend.

5. Connect

Replace vpn.example.org with the official VPN address provided by your organization:

openconnect-saml connect --server "vpn.example.org" --browser chrome --chrome-channel msedge

Run the command without adding sudo at the beginning.

Complete the authentication in the browser window, including MFA if required.

If the terminal subsequently requests a password through sudo, enter your local Mac administrator password. Nothing appears while typing a terminal password; this is expected.

Authentication success alone does not confirm that the VPN tunnel is connected. Check the subsequent terminal output and test access to an authorized internal resource.

6. Disconnect

Keep the terminal open while using the connection.

To disconnect, press:

Ctrl + C

Troubleshooting

sudo: openconnect: command not found

Check whether OpenConnect is installed:

command -v openconnect
brew list --versions openconnect

If it is missing:

brew install openconnect

If it is installed but sudo cannot find it, investigate the executable path rather than reinstalling repeatedly.

PyQt6 installation fails because Xcode is required

The Edge method above uses the Playwright browser backend. PyQt6 is not required for this method.

A pipx environment path does not exist

Inspect the actual paths:

pipx environment

Do not assume pipx uses the same directory on every system. Enclose paths containing spaces in quotes.

Homebrew displays a “Tier 3” warning

This describes Homebrew’s support level for the configuration. It does not, by itself, mean installation failed. Check for an explicit error and verify that openconnect --version works.

Connection command

After installation, reconnect using:

openconnect-saml connect --server "vpn.example.org" --browser chrome --chrome-channel msedge

Never share passwords, MFA codes, authentication cookies, or session tokens in screenshots or troubleshooting logs.

References: OpenConnect · openconnect-saml · Homebrew

VPN:

A virtual private network, or VPN, is a private connection over the Internet from a device to a specific network.  VPN technology is widely used in corporate environments. If you need to be "present" on an institutional network, a VPN is a great tool for accomplishing this. It is generally issued and controlled by the institution.


Almost all other uses are a SCAM. There is generally no need for you to have a private (and almost always MUCH slower) connection to a VPN vendor's Network, except to make it easier for them to harvest your data to sell. If you are behind a Router you control or Trust, there is NO security advantage whatsoever in using a VPN. Your connections are already encrypted in most cases.


If VPN vendors just stopped there, it would be bad. But many of these packages also insist on scanning all your files, non-stop, -- nominally looking for viruses, but who knows for sure what data they are harvesting. Their non-stop file reading punishes your computer's performance in the process.


Some also break into your other secure connections so they can be FIRST to examine your data, often leaving your Mac MORE vulnerable to attack.


What VPN service to use?

DON'T use VPN services


https://gist.github.com/joepie91/5a9909939e6ce7d09e29