Damasta

I know I might be flamed for this, but does any of you actually have the EULA and/or purchasing agreement and/or claim that says "lifetime license, INCLUDING all future upgrades"? When software companies offer "lifetime licenses" (sometimes called "perpetual use rights") that typically only applies to the version you just bought - NOT to future versions. So yes, we all bought V5 licenses (I did too), but I'm willing to bet that that did not include rights to new/major releases, such as V6. That being said, if anyone could find some clear licensing statements to this effect and post them here - that'd be awesome! :-)

Did you ever use the V5 universal app? Personally, I thought that was awesome. A great implementation of UWP. Slick, simple, uncluttered and accessible - worked great on phone, tablet and PC (mouse). The new UI is not as accessible: Too much whitespace and/or objects are too small. Plus, it looks stone-age to me as a Windows user. Fluent design is awesomely beautiful ans accessible when used properly. "Accessibility" to me means: everybody (and i mean everybody!) understands how it works, how to use it, it is easy to read and operate. The new UI has to accommodate too much new stuff and the black theme is full of dark grey on black. Can you please read some accessibility guidelines? Apple, Google and Microsoft all have them and it seems you read none. I also realize you are trying to make a UI that works on all platforms and therefore ought to be as generic as possible. But we all chose our platforms for a reason - last but not least how it looks and feels. So i understand that Apple users are frustrated with the user experience - but so am i as a Windows user. No offence to Android (i have two myself), but nothing feels consistent on those devices anyways, so Enpass' UI looks perfectly at home there. Personally, I'd pay extra (platinum?) to get the real UWP / Fluent design back to Enpass. And by the looks of it, so would the Apple crowd.

+1 As a long-time, very satisfied Enpass user, I'd like to echo the sentiments here. To be clear: I'm not upset that you made a major upgrade to V6, I'm upset HOW you did it. Personally, I am tech savvy, so I was able to help myself and my partner to upgrade to V6. However, my partner had NO CHANCE at all to upgrade herself and had already started to panic (passwords missing, devices not syncing), when she asked for help. In short: the upgrade experience was catastrophic. 1. Because I loosely followed the beta program for V6, I remembered reading that V6 vaults aren't compatible with V5 and that the upgrade from V5 to V6 is a "one-way" operation with no backward compatibility to V5. I thought that was a beta-issue only and would be solved in the release. That incompatibility caused my and my partner's devices to literally break apart, because sync just stopped. No message, no error, no warning, no instructions, no announcements. In our case, my partner lost a few passwords during the upgrade and broke sync between her devices. She had added new passwords to her Android V5 over the last couple of days. Then the upgrade automagically happened through Google Play. When she opened the new version, the passwords were imported to V6, breaking backward compat with V5 still on our Windows devices (no auto-upgrade on Windows!). So when she opened Enpass V5 on Windows, the new passwords were missing, because they didn't get moved to V6 on Windows yet. So as far as she could see, passwords were inconsistent at best or lost at worst. 2. We use Windows 10 Pro, Windows 10 Mobile and Android Oreo and Pie in our household. The upgrade experience was different for each platform. I realize you don't control the platforms, but could you at least have provided some clear upgrade guidance for each platform? Android upgraded itself, Windows 10 Pro didn't and had to upgraded/migrated manually, Windows 10 Mobile … just ended without comment. 3. At no time were we made aware of a coming upgrade and/or its consequences - much less an opt out. Microsoft is better at this, and that's saying something! 4. There is no obvious way to roll-back and recover from a failed upgrade. Really?! That is essential! Again, even Microsoft handles their Windows feature upgrades better - the roll-back actually works. If something goes wrong, users MUST be able to roll back. Do you realize that some people have access to their ENTIRE DIGITAL LIVES stored in Enpass? Breaking that could literally ruin someone. Managing passwords and access is more critical than managing data - you have a bigger responsibility than Microsoft or Amazon, who run the world's cloud services. What saved us was that we had all kinds of different platforms and each one failed differently, which luckily meant that at least one Enpass still worked, in order to get at our master passwords. PLEASE DONT DO THAT AGAIN.

+1 Agreed - this is ultra-annoying. I need to get my Android Enpass to get my master password to get my Windows Enpass. And the extra click on the face icon is plain unnecessary. Off-topic: why didn't this thread show up when did a global search for "hello" in this forum?

+1

Hi, I'm not sure what you mean by "full-time Windows Hello support" … Are you talking about the fact that Enpass needs the master password once after a restart? If yes: I have that on my Surface Book 2 too. That is ultra-annoying. V5 UWP didn't do that. So I need to get my Android Enpass to get the Enpass master password before Windows Hello works again. That being said, after unlocking Enpass with the master password once, Windows Hello seems to work fine for me.

+1 (same on Windows!)

If Windows Hello is enabled, please use Hello as the default authentication method. Currently, I need to tap the little face icon first - one step too many. Thanks!

My setup: Surface Book 2, Windows 17763.195, all updates (Firmware etc.) installed. Enpass 6.0.0 (218) syncs to OneDrive, connected to three other devices. After a restart, Enpass requires me to enter my master password once despite Windows Hello being enabled in the settings. Hello seems to work from then on. Please fix! Dom

This was a different thread that was closed - due to "windows wont let us do this". In fact, you are incorrect and have been at least since Windows 10 Version 1709. For proof, please see the app "Ear Trumpet", which is a brilliant volume control app that replaces the windows built-in volume control. It totally opens and minimizes back to the system tray. It auto-starts on boot. In fact, I think Enpass should work just like it. @Akash: Please revisit your answer to that closed thread? Please stop using Windows as an excuse why things don't work. ;-)

6 Months later and still no Windows Hello or decent touch support on the bridge version... Why not just cave in and dev plugins and extensions that connect to the local vault file and/or the cloud? I don't see the need to connect the extension to Enpass app.

Sorry Akash, that answer doesn't even come close to it. 1. The UWP version is... Universal. It works on PC, Phone and HoloLens and always looks and feels the same. The w32 Bridge/Desktop version doesn't. 2. The UWP version is great for touchscreens, the w32 Bridge/Desktop version is from the stone-age and is horrible for touch screens. 3. The UWP version supports Windows Hello biometric (un-)lock with fingerprint, face, iris and soon with palmvein recognition. Forget your password - literally! 4. The UWP version does not support browser extensions. IMHO that is a bad excuse tho… I don't see why a browser extension can't just connect to my cloud or local vault file and extract passwords from there. I understand that the UWP model will not allow apps to communicate directly to localhost - which, from a security standpoint - is a good thing. But if the UWP can connect to a cloud or a local vault file, why can't a browser extension? Other extensions certainly do... Do I sound like a bitter UWP user? Absolutely. I've tried both versions and I'll rather have the UWP version any time - hands down. Check the store - the UWP version even has better reviews, too.