Jump to content
Enpass Discussion Forum

URGENT: Last update to 6.110.1694.0 completely BROKE Arm64 support - Enpass crashes immediately on launch


Recommended Posts

Folks, the latest update will not launch on Arm64 Snapdragons anymore. This is A DISASTER, as all our work devices are Snapdragon based and we now can't access our vaults anymore!

Symptons and steps to repro:
1. Get a Snapdragon and install current Windows 11.
2. Get Enpass from the Store.
3. Run Enpass and observe the brief flash of the CMD box - then either nothing or a brief flash of the Enpass welcome screen. Silent close, no error.

We tested on both current Windows 11 Dev Preview as well as Release - both will not run Enpass.

The event log only provides this:

Faulting application name: Enpass.exe, version: 6.11.0.0, time stamp: 0x6659d5aa
Faulting module name: Enpass.exe, version: 6.11.0.0, time stamp: 0x6659d5aa
Exception code: 0xc000001d
Fault offset: 0x00088382
Faulting process id: 0x3178
Faulting application start time: 0x1DAB74A2F15B363
Faulting application path: C:\Program Files\WindowsApps\SinewSoftwareSystems.EnpassPasswordManager_6.110.1694.0_x86__fwdy0m65qb6h2\EnpassBridge\Enpass.exe
Faulting module path: C:\Program Files\WindowsApps\SinewSoftwareSystems.EnpassPasswordManager_6.110.1694.0_x86__fwdy0m65qb6h2\EnpassBridge\Enpass.exe
Report Id: 45823d69-3897-4c0a-9445-b9dc23173e1d
Faulting package full name: SinewSoftwareSystems.EnpassPasswordManager_6.110.1694.0_x86__fwdy0m65qb6h2
Faulting package-relative application ID: App

We can confirm it still works on x64, but those are not part of our production environment.

Please fix this ASAP! And in future, please make sure you test on Snapdragons before releasing, ok?

Edited by Damasta
Link to comment
Share on other sites

I am happy to report that the Enpass team identified the issue, fixed it, published it to the MSFT Store and the Store is now pushing the fix to our Snapdragons.

All within ~24 hours. (surprised the Store approved and pushed the updates so quickly!)

So while this shouldn't have happened in the first place, I am impressed how fast this got resolved. THANKS team!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...