JeffB

I had similar problem. Uninstalled Android app (Beta tester). Reinstalled and connected. All seems to be working now on Windows, Android and the Linux app.

I have been using Windows 10 QuickAssist the last couple of days to help a neighbor with a computer hacking problem. I have noticed that using Enpass during the session can cause a crash. And Enpass definitely crashes after QuickAssist is closed. I hope that this problem can be investigated and corrected. However, it is not something that I do regularly, and I don't feel this is a major problem. Thanks

Tahreem, I receive the update that was to address the failure of Autofill on Android (V6.4.0.320). The problem did change, but it is still failing. Originally on my phone, the app would stop working (crash) right away (just after the phone restarted). Now the app crashes while trying to Autofill. I am using an :LG Stylo 3 Plus running Android 7.0.

Autofill is not working in any condition or on any browser after the update this morning. I get a system message that it stops shortly after restart, etc. I assume the crash is causing the Autofill to fail. I have check all of the settings and they are the same as before the update. I have all of the Autofill options set.

Just received the Beta 6.4.0.317. Reconnected Sync to OneDrive. App crashes in background. No ability to use Autofill. Running on LG Stylo 3 Plus Android 7.0.

The Enpass extension from the Google Web Store is working very well on both the Dev and Canary release builds. I think the Enpass extension in the Microsoft Extension store is still V5, but I haven't checked in a couple of days.

Friends, The Enpass Chrome plugin was working on test (leaked) build of Edge on Chromium version 111 (which is often called Edgium). I just upgraded to 19H1 on the slow ring (presumably the Release Preview coming next week). Now I am getting an error as below. I will continue to test and hope that the Beta Edge on Chromium comes out soon, and I will go back to Brave with the Enpass extension until I can get the stable Edgium. Browser requesting the data is not code signed. You can share the following diagnostics with us at support@enpass.io. code : 3 origin : chrome-ex

I have been able to get the early (leaked) beta of the Chromium-based Microsoft Edge identified as x.107. As I have become dependent (and depend on) Enpass, it was great to see it works well out of the box. I have been using Google Web Store version, and that works well on the new Edge. There is a Extension in the new Microsoft Store for Enpass, but it is a 5.x version. Microsoft should be notified that the version of the extension should be updated to the latest 6.x version before the formal Beta starts. Thanks, JeffB

In addition to the changes to the Power Options noted above, I also had to use the Catalyst Control Panel for my Radeon adapter and set the Switchable Graphics for the Enpass app to Maximize Performance. If settings were other, the 1114 load library error would appear again. I am hoping that things are settling now. I have also have to work on settings for other applications that use DirectX graphics, including Brave browser and the Snip and Sketch tool.

It is now Enpass v6 that is not working. Let me know if there is specific information you might find useful. I am also loading up another system to see there is something about that installation.

Well, we are at build 18312 and the Password Manager app is not working, nor is the Edge Extension. I am not worried about the Edge extension because it's future is limited with the announced change for Edge to replace EdgeHTML with Chromium. So I assume the Chromium extension will work when it arrives. But the Password Manager app not working is more of a concern. It throws an error "LoadLibrary failed with error 1114: A dynamic link library (DLL) initialization routine failed." This has been going on for weeks now on these 19H1 builds. I am suspecting it is something missing from the build,

I am baffled by the discussions above on free Vs paid features. I was glad to pay for the Windows Hello integration and the templates. It is a one time charge of 6 USD. Almost all the other services are subscription and require much more than the 6 USD per year. For me, Enpass provides the best solution both technically and financially. Thanks

Sorry for posting this. After rebooting, Hello is now working as expected. Keep up the good work.

I used the Beta version for some time and I just purchased the Premium version to get the dark theme and Windows Hello. The Dark theme and Hello worked on the Beta, but stopped working a couple of days ago. I purchased the Features update, and now Dark theme is working again, but Hello isn't working even though it is selected. Is there something that needs to be enabled?

Today's update to the Edge Extension (6.0.4.0) greatly improved both performance and reliability. Thanks for your extra work to make this a solid update. Is there any time frame on when the V6 update might be generally available? Thanks, JeffB