Jump to content
Enpass Discussion Forum


  • Posts

  • Joined

  • Last visited

Aeropedia's Achievements


Newbie (1/14)

  • First Post
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges



  1. @Dizzy You're an absolute legend! I never would have suspected the Simulator. Thank you.
  2. I appreciate it takes time to release things sometimes, but having this released sooner rather than later would be great. I recommend Enpass to users of the SaaS product I work on, but it is actively introducing buggy behavior by cycling through- and sending focus events to all sorts of input fields in the system. This then clashes with a JS date picker library which auto-fills every empty field with a bogus date, messing up all the data. When they reach out for support I have to guide them through how to limit the extension's site access.
  3. Hi there, The "Touch ID" setting does not appear in the Security screen, and I am not quite sure why. It is not really mentioned anywhere what the requirements are, other than that it requires iOS 8. I've got: an iPhone 5s iOS 9.3.2 latest version of Enpass (trial) fingerprint definitely enrolled - I unlock my phone with it Any help would be appreciated
  4. I don't know if this was fixed before and came back, but I have been affected by this for the last few weeks. Online games became unplayable until I exited Enpass. Thank you for the solution. Works fine!
  5. I suddenly had the same issue today, so I figured I would share the cause in case somebody else runs into the same problem. In my case, Enpass crashed within a few seconds, caused by the OSD feature being turned on in my MSI Gaming App. This feature normally shows you graphics card statistics while you're playing games, but it appears it also tried to do it in Enpass - which it did not seem to appreciate. Turning the feature off in the MSI Gaming App allowed me to get to my passwords again. If your Enpass is crashing for different reasons, I suggest opening Event Viewer (which ships with Windows). Just typing "Event Viewer" in the start menu should bring it up. In Event Viewer, go to Windows Logs > Application. Find the most recent "Error" level activity and it will give you some technical details. In my case it was enough to hint at the cause: Faulting application name: Enpass.exe, version:, time stamp: 0x06925888 Faulting module name: MsiGamingOSD.dll, version:, time stamp: 0x5799965f Exception code: 0xc0000005 Fault offset: 0x00004906 Faulting process id: 0x15cc Faulting application start time: 0x01d20661c8ae701d Faulting application path: C:\Program Files (x86)\Enpass\Enpass.exe Faulting module path: C:\Program Files (x86)\MSI\Gaming APP\OSD\x86\MsiGamingOSD.dll Report Id: b09b3666-f7af-48ff-88ab-054fbac83950 Faulting package full name: Faulting package-relative application ID: Hope that helps someone.
  • Create New...