Cisco AnyConnect User Interface has stopped working

[jhonsberger]

So I have an MS Surface Pro (Windows 8.1 x64) has been running AnyConnect 3.1.04066 for several months without incident.  All of a sudden a couple of weeks ago, when you load the software and then click 'Connect' a pop-up stating that "Cisco Any Connect User Interface has stopped working" with an app crash.  Have attempted:

- Uninstall & Reinstall

- Install of latest release, v3.1.05182

- Install back to v2.5.2019

No change in behaviour with any of these (just the v2 crashes with a different error message).  We have several hundred other people connecting to our corporate VPN system without issue, so I know our VPN connectivity is good.  I have 2 other MS Surface's out and both of those are working fine.  Machine has all MS updates installed, nothing has been installed or changed during the time period between when it was working to where it was not working.  Computer appears to be virus\malware free.  I've smacked my head against this for a while and I'm completely stumped.  Any direction would be appreaciated.

Here's the app error log:

Log Name:      Application

Source:        Application Error

Date:          2014-10-14 2:17:26 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Computer.domain.com

Description:

Faulting application name: vpnui.exe, version: 3.1.5160.0, time stamp: 0x5320c86f

Faulting module name: vpnapi.dll, version: 3.1.5160.0, time stamp: 0x5320c746

Exception code: 0xc0000005

Fault offset: 0x0000e359

Faulting process id: 0x1114

Faulting application start time: 0x01cfe7db1ab77104

Faulting application path: C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnui.exe

Faulting module path: C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnapi.dll

Report Id: 594fe6e1-53ce-11e4-be98-281878489656

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

   <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-10-14T18:17:26.000000000Z" />

    <EventRecordID>9949</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Computer.domain.com</Computer>

    <Security />

  </System>

  <EventData>

    <Data>vpnui.exe</Data>

    <Data>3.1.5160.0</Data>

    <Data>5320c86f</Data>

    <Data>vpnapi.dll</Data>

    <Data>3.1.5160.0</Data>

    <Data>5320c746</Data>

    <Data>c0000005</Data>

    <Data>0000e359</Data>

    <Data>1114</Data>

    <Data>01cfe7db1ab77104</Data>

    <Data>C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnui.exe</Data>

    <Data>C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnapi.dll</Data>

    <Data>594fe6e1-53ce-11e4-be98-281878489656</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

[Satya Gone]

We received request to install “Cisco AnyConnect Secure Mobility Client” (VPN Client) on Azure 2012 VM and while installing we received below error: “cisco any client user interface has stopped working”.  I could find workaround for Windows 7, 8 and 8.1 but not for Server 2012 VM. Could anyone please help to find the cause of the issue.

[rfreytag]

I installed a new .xml profile on both my Windows 8 laptop and Windows 10 desktop. Each has a different version of the AnyConnect client.  I put the same .xml profile in each computer, and they both gave me the error Cisco AnyConnect User Interface has stopped working.

I removed the .xml, which is located here:
%ProgramData%\Cisco\Cisco AnyConnect Secure Mobility Client\Profile
... and the clients started working again. I think it is a formatting error in my .xml

It is not recommended to edit the .xml manually, which is what I did.  Per Cisco:

use the VPN Profile Editor instead. It is also recommended that both XML profiles, the one located on your client machine and the one located on your headend be the same ones.