Jump to content
wmc

Please Withdraw Version 6

Recommended Posts

  1. There are too many universally experienced bugs for a small support / development team to chase in an organized fashion that will not result in a much degraded product that will be much harder to maintain and upgrade going forward.
  2. Many of the bugs create security issues (e.g. the failure of Enpass browser extensions to block access to web login sites until the Enpass master password is entered, then subsequent failure to load the info from the vault for the page with the login controls (UID, password).
  3. A number of bugs impact stored data integrity and reliability.  E.g., browser extensions seem to "forget" Enpass has been installed and working fine in with a particular "Master Password" in the past, and reports it has not completed set-up, needs a master password to be created, or previous data restored.  However, despite selecting auto-backup creation in version 6, no backups get created, and attempts to restore from the local computer lead to a Google login page. (?!?)  Further, the database form, format and location used to store the "vault" has changed from v 5 so that the process of "rolling back" will be tedious with many manual actions required by the user while understanding it is highly likely that v5 will not be able to use a v6 vault for its data.
  4. Version 6 install / uninstall make a mess of the Windows registry leaving multiple entries with duplicate information that is incorrect.  For example, after installing v 6.0.2 the registry contains no entries referencing this version but does have entries referencing the previously installed 6.0.1 (239) referenced as 6.1.239.0.  There are multiple keys in HKCR that contain the exact same info.  HKCR\.enpass_card should reference one of the subsequent classes in HKCR from its "OpenWithProgids" key, but there are at least EIGHT OTHER Progids in HKCR all for same "@{SinewSoftwareSystems.EnpassPasswordManager_6.1.239.0_x86__fwdy0m65qb6h2?ms-resource:...".   Thus the uninstaller needs to be fixed so that it cleans up all the entries it leaves behind when the software is uninstalled since this splattering of multiple keys with duplicate data may be at the source of some worsening issues each time a new v6 install / uninstall / re-install is attempted.

Although I haven't attempted it, I believe this shotgun blast of Enpass version 6 registry entries left behind after its uninstall will make a rollback to version 5 problematic especially for Windows users not versed in registry editing and the subtleties of changes in Enpass database form, format and location.

For these reasons the Enpass development team needs to withdraw all version 6 releases and provide A FULLY TESTED UTILITY TO COMPLETELY REMOVE TRACES OF VERSION 6 FROM THE REGISTRY / SYSTEM FILE STORES, AND CONVERT THE V 6 DATABASE BACK TO A VERSION 5 COMPATIBLE "WALLET" SO USER CAN THEN SUCCESSFULLY RE-INSTALL AND OPERATE WITH VERSION 5.  This will then give the developers and Enpas QC engineers time to re-engineer v6 from top to bottom with REAL unit testing AND REAL THOROUGH in-house use case testing BEFORE releasing to beta testing or the "stable release" channel.

  • Like 5
  • Thanks 1

Share this post


Link to post
Share on other sites

...your lucky your post is still here.!!..My post from yesterday has been totally removed along with a few other different title threads...JUST GONE!!

Share this post


Link to post
Share on other sites

As a former software engineer,  technical lead and software architect for major aerospace software systems, I know a thing or two about what happens when proper design, development test and release procedures get short-cutted and this appears to be what happened here. The result is a product which can either go forward with lots of band-aids, bailing wire and spit holding it together (making maintenance a nightmare with limited reliability and success) OR a product that can be withdraw, reworked without the pressure of dealing with multiple daily reports of wide-ranging and serious bugs.

I am attempting to be constructive based on my experience with software development in both types of environments - when development followed a sound set procedure through the process from design to release, and when shortcuts were taken to satisfy political, management, or marketing desires.  I'm merely asking Sinew Software to withdraw a release that was clearly "not ready for prime time", and redo the effort properly with the technical process, issues and progress dictating release schedules rather than whatever pushed this one out the door before it was finished.  Other major software development organizations have done this in the past, and users who see a company ready to admit a mistake then take proper action to fix it generally end up with higher regard and satisfaction with the developer than for those developers who "press on" with a bug-laden product, trying to pretend all is copacetic.  In the end, the latter decision hurts the bottom line and ends up defeating whatever management / marketing decision drove the "pre-mature" release.

I have downgraded to version 5, turned off auto-update for the extensions in the various browser that allow that, instead of having purchased the prime option on v 6 which was my intention though I did not  need the features, but more as a reward for a an application and browser extensions I used and found perfectly met my need.  But now, unless they take the proper action to fix ALL the issues in version 6 (withdraw, re-work, re-release being the proper way instead of endless little ad-hoc patches), I will be done with any / all products related to Sinew Software an use one of the password managers built into my internet security suites or available from another vendor at a reasonable price.

 

  • Like 2
  • Thanks 1

Share this post


Link to post
Share on other sites

Has anyone found the tray icon sometimes becomes non-responsive?
When it happens, I have to close it down and re-open it.

Share this post


Link to post
Share on other sites
On 1/6/2019 at 1:22 AM, wmc said:

For these reasons the Enpass development team needs to withdraw all version 6 releases and provide A FULLY TESTED UTILITY TO COMPLETELY REMOVE TRACES OF VERSION 6 FROM THE REGISTRY / SYSTEM FILE STORES, AND CONVERT THE V 6 DATABASE BACK TO A VERSION 5 COMPATIBLE "WALLET" SO USER CAN THEN SUCCESSFULLY RE-INSTALL AND OPERATE WITH VERSION 5.  This will then give the developers and Enpas QC engineers time to re-engineer v6 from top to bottom with REAL unit testing AND REAL THOROUGH in-house use case testing BEFORE releasing to beta testing or the "stable release" channel.

+10000000

simply: the upgrade to 6.0 is the worst what happened to both: Customers (us) and probably developers (if, I am not sure actually)

both financially and usability (or lets say: disability) 

  • Like 1

Share this post


Link to post
Share on other sites
3 hours ago, xarlatan said:

can somebody please provide a link to the latest v5 version? That would be great! Or just tell me what the latest version Number was.

Go to the downloads page.  Near the bottom in smaller type find the link in the line,

Looking for an older version of Enpass? Get it from here.

That will take you to instructions for downloading the last working version 5.x.x application and extensions.  NOTE: you need to follow instructions carefully for the Chrome extension install.  And in Firefox you have to, on the "Add-ons Manager" tab (from the "Tools->Add-ons" menu) click on Enpass, and in the resulting pane disable auto-update or it will put you right back at version 6 for the extension.  Note also, there appears no way to downgrade the extension in Edge since it relies on Microsoft Store, just one more indication that Sinew Software should withdraw version 6, including extensions available in various vendors app stores.

BTW, the Enpass 6 data file is not backward compatible with Enpass 5 and I know of no conversion tool to make it so.  However, one thing Enpass 6 appears to have gotten right is that it renamed your last Enpass 5 file "walletx.db.backup" when it replaced it with the "vault.enpassdb" file buried deeper in your Enpass documents folder.

Edited by wmc
Added Para
  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

ah ok. Thanks a lot, somehow i was blind and didn't see this.

Luckily I made a Backup of my wallet just before i did the upgrade. I will stick to version 5 until i find a better password manager. It was annoying enough that the v6 did not find the external file just because the filename extension changed and it said there is no file on my WebDAV path....

Share this post


Link to post
Share on other sites

It is really strange that you guys are facing so many problems... 

I'm using Enpass 6 on both Windows 10 (with Edge browser extension) and Android since it was made available as Beta in Windows Store, and I haven't experienced any severe or functionality breaking issue so far. The communication with Edge extension even works much better with v6 compared to v5. Not for one second I thought about downgrading to the previous version.

Looks more like compatibility issues which needs to be fixed for you, and not as if Enpass 6 itself is broken. 

Share this post


Link to post
Share on other sites
7 hours ago, tox1c90 said:

It is really strange that you guys are facing so many problems... 

I'm using Enpass 6 on both Windows 10 (with Edge browser extension) and Android since it was made available as Beta in Windows Store, and I haven't experienced any severe or functionality breaking issue so far. The communication with Edge extension even works much better with v6 compared to v5. Not for one second I thought about downgrading to the previous version.

Looks more like compatibility issues which needs to be fixed for you, and not as if Enpass 6 itself is broken. 

I totally agree with your assessment of Enpass 6. I've read about the problems that Enpass 6 users claim to face on these forums and on the Google Play store. However, I don't feel them. The communication with browser extensions such as Edge, Chrome, and Firefox on Windows 10 works much better with version 6 than with previous versions. It is working great on Android.fThere are those who complain that they had to use the master password again after installing version 6, but they forgot the master password and had saved it to their Enpass. It is unfair to blame Enpass for users forgetting their master password and a master password should not be stored on Enpass since it should be stored on paper. Storing a master password on Enpass is like storing my house keys in my house when I'm outdoors, so I would not be able to open the door to my house.

Share this post


Link to post
Share on other sites

It appears that you (GeoLuz and tox1c90) are in the "exception" rather than "rule" category for Enpass v6.  It also appears you are primarily Edge and smartphone users of Enpass, both of which are incredibly castrated environments compared to the full-function desktop experience we have with Enpass v5 in full-function browsers like Firefox, Safari, Chrome on a desktop.

As for compatibility issues, if version 5 ran reliably and flawlessly, then as soon as v6 installed by Enpass's auto update and completely blew up (extension can't reliably connect with the application, can't find the data store, and when it does hook up, can't auto-invoke the credentials for the log-in page you have invoked - the most basic reliable function of version 5) then the onus is on Sinew Software, NOT users, to fix the problems.  The sheer volume of problems indicate this was an update to please Enpass, and the fancy Windows messaging version (so Microsoft can insert itself into your machine security situation and try to force you into OneDrive client-hood).  There was apparently no or little attention paid to impacts of design and coding changes to the "Traditional" version and interfaces with non-Microsoft extensions.

The fact that Sinew Software remains silent, provides no updates to address all these issues and no help to those they apparently ignored in the beta test / release cycle indicates that their roadmap is a Microsoft / Edge / Window phone / OneDrive centered plan so that users of non-Microsoft browsers can just fall to the wayside, live with the problems or find other products that actually work with non-Microsoft browsers and cloud services.  The Sinew Software silence, their lack of effort to address these issues is the coward's way out - they should just tell Firefox, non-MS cloud service users etc. that they will no longer support these browsers / services and make a clean break with those users who have been forced back to version 5 with all the SERIOUS functionality and reliability downgrades the auto-update to version 6 inflicted upon them.

But I'm happy that those who are enamored of Edge and OneDrive, Microsoft Store app versions etc. have a product that works for them.  It is still no help for the rest of us who swallowed the Sinew Software "good will" based on experience through version 5 on other browsers. 

Edited by wmc
grammar correction
  • Like 1

Share this post


Link to post
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

×