Jump to content
Enpass Discussion Forum


  • Content Count

  • Joined

  • Last visited

  • Days Won


wmc last won the day on February 5 2019

wmc had the most liked content!

Community Reputation

21 Excellent

About wmc

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Garima, Great news! Thanks for keeping us informed.
  2. Matis, >> Just change the theme and you have the former size again. With 6.5.1 they just made "classic" theme as default and it has small letter. "modern" still has big letters. << This does not work for version 6.5.1 (723) on the latest version of Windows 10 whereas the environment variable addition does.
  3. Garima, The same thing happened when I updated via the Enpass update alert to version 6.5.1 (723). I followed the FAQ and it did the trick with one modification: you have to restart / reboot the machine before the new environment variable will take effect.
  4. If you went back to 5.6.10, it is likely that you did not restore your wallet file. Enpass 6 uses a different database organization and file format. So look in your SYS:/Users/<your UID>/ Documents/Enpass folder (AKA "My Documents/Enpass" folder) for a file called "Enpass_Backup_yyyy-mm-dd_hh-mm-ss.walletx" where "yyyy-mm-dd_hh-mm-ss" are numerals of a date_time when you first installed Enpass 6. I think that file is the last walletx.db file that your Enpass 5.6.10 was using before the update. Rename a copy (just to be safe) of "Enpass_Backup_yyy...." to "walletx.db" and you sho
  5. Since some reported version 6.0.4 fixed all the bugs, I decided to try it. BIG MISTAKE! It is as buggy (only without the text display issues) as 6.0.0. Just some of the issues: BUGS: 1. Interface on desktop app locks if Enpass is idle even when “Settings->Security->Enpass is idle for” remains unchecked. 2. Enpass “forgets” the browsers with which it has been authorized by entering the matching code each time the system is cold-start booted even when “Settings->Browser->Ask for Browser Authorization Every Time is unchecked. 3. This difficulty
  6. You only need the windows store version if you intend to use Edge as a browser. I do not know if you can still use OneDrive for sync as I do not use any cloud services. (As a former software engineer I know how insecure ANYTHING you put on the Internet is, so I tend not to use cloud services, social media, online banking / bill pay etc. If I need to sync I use "sneaker net".) I downgraded to 5.6.10 for the desktop app, and the last version of browser extensions for Firefox and Chrome a few days after the initial 6.0.0 release. I briefly upgraded to 6.0.2 to see if things were fixed and
  7. I tried all updates through v6.0.2. The latter fixed the misaligned / blurry text but nothing else. I can't auto-load credentials when you open a browser page for which you previously stored credentials in Enpass. More than half the time, after one successful invocation of Enpass from the browser's tool bar, the extension can't find the application and says that you have to finish installation and activate browser extensions (no matter how many times before you've done this). The "Search" doesn't work right. You have to key in an exact and complete "word" that falls betwee
  8. 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
  9. You may not have scrolled low enough on the page for downloading older versions (https://www.enpass.io/support/where-can-i-download-older-version-of-enpass/) There are listings for the rev 5.x versions of extensions for Firefox, Chrome and Safari. As mentioned above, there is no way to rollback Edge since its extension comes exclusively from the Microsoft Store and they only support the "latest" version absent Sinew Software withdrawing Versions 6.x from release.
  10. My Post of Jan 5 is not entirely correct. You CAN DOWNGRADE, but with caveats: Windows 10 Edge Browser cannot be rolled back (you would have to do that through the Microsoft Store, and it is not equipped for roll-backs). You have to disable auto-update of the Enpass desktop application. You have to disable auto-update of browser extensions. (I found a way to do that in Firefox, but not in Chrome) otherwise the browsers will update the extensions to 6.x.x and not be able to hook-up with the desktop application. I've been running with the versions from the link posted by
  11. 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
  12. You can. On the downloads page there is a link near the bottom of the page to older versions. You have to download the application, and the extensions separately. You have to remove the Enpass 6 extensions from your browsers (NOTE: Special instructions for installing from .zip package in Chrome, no option to downgrade Edge). In Firefox after removing the 6.0.x extension and installing the Firefox extension from the .xpi file you have to click the Enpass entry in the add-ons list, and disable auto-update or it will put the 6.0 extension back right away. I haven't figured out how to disable
  13. 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.
  14. I have the identical error when trying to roll back from Enpass 6.0.x installs to enpass_chrome-5.5.3 (unpacked in "Developer Mode"). I had uninstalled version 6.0.2, the extensions, and gone through the registry manually cleaning Enpass and Sinew software entries (and there are a TON of them). I noticed that the manifest.json file contains one very curious entry: "version": "", I wonder if this line is trying to tell the extension to hook up with the application version 6.0.0 in order to force an update to Enpass 6 when the roll-back version installed is actually 5.6.10.
  15. 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. 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). A number of bugs impact stored data integrity and reliability. E.g., browser e
  • Create New...