Anthony

I've just enabled the new website icons feature in Enpass 6.2.0 (542) and in general it has done a good job of retrieving the favicons from the website. However, there is a small, very random, number of entries where it has gone and applied the same incorrect favicon which just happened the be the favicon for the 2nd entry in my wallet that it updated. In my case, it has used the favicon from https://9now.com.au which was the 2nd entry in my wallet that it updated with a favicon. However, it also used that exact same 9now.com.au favicon for entries such as http://www.asus.com.au https://www.auntbetty.com.au https://austpost.com.au http://avis.com.au https://www.bestpoolsupplies.com.au https://www.budgetpetproducts.com.au cashbackclub.com.au http://netbank.com.au http://davey.com.au ..and many many more. Any ideas why or how to investigate/troubleshoot?

I use OneDrive as my cloud sync. I'm currently using Enpass 6.1.2 (428) for Windows Desktop. I've just changed my Microsoft Account (MSA) password and so need to re-authenticate any apps that use my MSA/OneDrive. Am I correct in assuming that the way to do this in Enpass for Windows is Go into Vault Settings Click 'Disconnect' and confirm validation prompts Go back in and re-setup Sync using OneDrive from scratch. There is no 'cleaner' way to do this? I mean, it works.. but it isn't particularly neat. It would be nice if there was a 'reauthenticate' option on the Vault Settings tab that would go through the same MSA auth process as initial setup without having to do the whole disconnect/reconnect set of steps.

When manually creating a new Login entity in Enpass, almost all use the same email address (or a limited subset of 2-3 email addresses). It would be handy and save time when creating new entries for the Email address field to offer a default email address option (could be an option in settings, or could just be offered on the field like a MRU list).

A minor, but annoying, thing I've noticed of late is that whenever a new version of Enpass 6 is pushed through the Microsoft Store, it will update the app, but not restart the app after update (assuming it was open prior to update). Every other app that I have via the Store, including many 'classic' apps that have been bridged, all seamlessly update and restart in the background. With Enpass, I'll often discover it has updated because I go to use it and find it isn't running (I have 'Open Automatically at System Startup' enabled) Why doesn't Enpass 6?

+1 Since 6.0.1 (239) I'm seeing the exact same thing. I tried uninstalling and reinstalling but as you can see from the attached screenshots, the problem occurs right from the first post-install screens. I've only encountered this on one of my PCs; a Dell Latitude 7480 running Windows 10 1809 (17763.195), Intel HD Graphics 620 using driver 24.20.100.6286 and 150% text scaling. No problem on my other PC running same version of Enpass and Windows but with a nVidia GPU.

Having battled the insanity of the Enpass release process, once I got the current beta installed from the Store on my PCs, along with the beta on my Android phone, the OneDrive sync has worked without issue. As always, YMMV

FIXED now that the correct file has linked for the beta download...

There is a difference between using betas within a current version line and being forced up to a major new version of a product which is completely incompatible with the previous version (and to which they've botched up the upgrade). This morning I found my phone had been upgraded to Enpass 6. My PCs are all using Enpass 5. I'm now screwed. So, I did not have a choice in this matter. Please refrain from telling people how to feel when you really don't understand the full circumstances.

What does this even mean? It seems that the link in the article downloads a standalone enpass.exe There is no installer. How does this "come over the existing Enpass 5 application"? Do you copy it manually? What if you are using the bridged traditional desktop vesrion of Enpass 5? does this still apply?

Agreed. This is a mind-numbingly stupid architectural decision. Why on earth would I want to set up multiple cloud providers just so I can sync multiple vaults? Most *normal* people have settled on (or only ever been exposed to) one single cloud provider and Enpass *should* support base functionality like multiple vaults based on this premise.

I've just been forced to the Enpass 6 beta. I've installed Enpass 6.0.0.198 and during the setup when asking where to restore the database from I selected OneDrive. It took me to the Authorisation page which showed as successful, however, in the app it just sat there hourglassing. I gave up and restored from a local backup I made. I then when into the app to setup Sync, and again, OneDrive sync setup failed with the exact same symptoms as above. I then tried to setup Sync using Google and got the exact same symptoms as above.

I am REALLY pissed off at this. Honestly, how dare you force me into a beta situation. I RELY on my password vault across my PCs, tablets, and phone 10s of times per day and I need to working 100% reliably. Now, you decide to forgo the previous side-by-side beta experience (a good way to do it) and force everyone into your beta?? I appreciate you want to put out the best version of the product on release and thus it probably made sense in your minds to pull in more users to beta test, but FORCING us into your beta test program with no way to decline or opt-out is simply unforgivable. I had always been a strong advocate of Enpass over other solutions like Lastpass but this behaviour by you will make me never in good faith recommend your product again.

I am REALLY pissed off at this. Honestly, how dare you force me into a beta situation. I RELY on my password vault across my PCs, tablets, and phone 10s of times per day and I need to working 100% reliably. Now, you decide to forgo the previous side-by-side beta experience (a good way to do it) and force everyone into your beta?? I appreciate you want to put out the best version of the product on release and thus it probably made sense in your minds to pull in more users to beta test, but FORCING us into your beta test program with no way to decline or opt-out is simply unforgivable. I had always been a strong advocate of Enpass over other solutions like Lastpass but this behaviour by you will make me never in good faith recommend your product again.

I totally agree with this. While I love beta testing, my password vault is too important for me for day-to-day use. I can't afford issues. I was watching the v6 beta and liked the fact that it could run side-by-side with v5 as it was independent and ran its own upgraded database file. However, being forced into a beta scenario, which I on;y found myself because my phone app (Android) was upgraded this morning, is NOT OK. You say you Love your users. Not giving them a choice is a very strange type of Love.

I'm seeing this issue more and more often now across multiple PCs. All running: Windows 10 1803 (17134.254) Microsoft Edge 42.17134.1.0 Enpass 5.6.19 (5548) (Desktop App through Microsoft Store) Enpass Edge Extension 5.5.2 If I go into the Enpass App -> Tools -> Settings -> Browser and Toggle 'Enable Browser Extensions' OFF and then back ON, then the Enpass extension works immediately.