Jump to content

Search the Community

Showing results for tags 'startup'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General discussion
    • Hot topics
    • Enpass Support & Troubleshooting
    • Autofilling and Desktop Browser Extensions
    • Data Security
    • Announcements
  • Help us improving Enpass
    • Feature requests
    • Enpass Beta
    • Localization
  • General discussion

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 6 results

  1. Hi ever since upgrading I have noticed that when Enpass starts up in the background upon logging into my Win 10 workstation .. the process is ridiculously slow relative to the previous version. It seems to take a full 5 seconds vs. less than 1 second to 1 second in the previous version. During the startup process a modal window pops up in the background of my monitor .. so for example if i just logged in and I am in the process of logging into to my vpn client for remote work, my login process is interrupted. Please fix this .. the enpass program should start quickly and seamlessly in the background causing very little delay in the boot/login process - just quickly start and the icon appears in the notification/icon area next to the clock in the lower right hand corner.
  2. The latest version freezes for a few seconds on startup. Whilst this is not a bug as such, it is slightly annoying
  3. The open automatically at startup option isn't working properly. #1 I have the option unchecked yet the program starts automatically (so this feature seems to be broken completely) ? #2 in previous version you had the option to open at startup BUT to open minimized to the icon area (this option seems to be missing) ?
  4. I have two machines that I switched from the Windows Desktop Native App to the new Windows 10 Store App that has the Edge Browser plugins. On both machines when I reboot and log in for the first time after a reboot, I get a pop-up that says, "Unexpected Error: Enpass has stopped working because of some unexpected error. " (Attached) The strange thing is. Enpass actually opens up behind it. And seems to be fine, I can actually use it. But if I click OK on the pop-up then Enpass closes and I have to start it again. I checked Task Manager startup and there is only one copy of Enpass listed there. The old version of Enpass is completely uninstalled. When it happened on my first machine I thought it was a fluke. But now it is happening on both machines. I am not sure where to check next to troubleshoot? Thanks, Eric
  5. Hi, Description Enpass crash on open from chrome the first time. Steps to reproduce Open computer or reboot. Open chrome. Go to a website with login. Use the shortcut to autocomplete with enpass. Enter master key. Current result Enpass crashes and chrome integration does not work until we open the enpass app again. Expected result That the enpass is unlocked correctly and the login fields are autocompleted. If I can help sending any data, let me know. Thanks
  6. Enpass on desktops should be split into two separate programs: EnpassCore.exe: This executable file constitutes the core Enpass service that browser plugins communicate with. It should have no window-based-UI whatsoever. This is also what users (and/or the installer) would add to the boot sequence. On boot, adding an icon to the tray (on Windows) or the menu bar (on OSX) would be the only clue it is running. EnpassUI.exe: This executable file constitutes the windowed UI. If EnpassCore isn't running, launching the EnpassUI would automatically launch EnpassCore as well. From any browser plugin, EnpassUI should never be more than a single click away. Benefits: EnpassCore has no windowed UI, so we could launch it as part of the boot sequence without having to deal with the annoying Enpass window being opened on every boot. A UI window should be in in one of the following states: opened, minimized, maximized, or closed. Since EnpassCore is always represented in the tray and EnpassUI is independent of that, there would be absolutely no need for the additional and unusual "minimized but in the tray" state Enpass currently employs. By separating what should be purely a background process from the front-end UI, we can eliminate the need for the quirky "minimize to tray" option and also say goodbye to the bothersome "Click here to restore Enpass" message that is shown every time Enpass is minimized to the tray on Windows 10. In a nutshell, how and when we require the UI for data lookup or data entry should have no affect on whether or not the Enpass service is running in the background. Because EnpassCore has no windowed UI, it could be very "lean and mean", thereby not noticeably impacting boot performance (assuming it's implemented as a native C/C++ application). For those people who are used to (or like) the way Enpass works now, there is no difference. Users can still add EnpassUI to the boot sequence and have the Enpass Window opened on boot if that is their preference. Technical thoughts: Architecturally, browser plugins and the EnpassUI would just be different clients of the same EnpassCore application. In the interest of a shared code base and developer productivity, EnpassCore would ideally be implemented as a C/C++ program that can be compiled on any of the platforms Enpass supports. I chose the filenames EnpassCore.exe and EnpassUI.exe only as a way to more clearly communicate their purpose. Nothing more. The filenames are not part of this suggestion. It would probably be best if EnpassUI is named enpass.exe, so that launching enpass.exe would open the windowed UI as it always has. In this way, people who don't know about, care, or want this change wouldn't be impacted by it at all.
×
×
  • Create New...