Jump to content

tox1c90

Members
  • Content Count

    13
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by tox1c90

  1. Looks like it is only happening when Enpass is launched automatically and minimized together with Windows. I was not able to reproduce it after closing Enpass and starting it manually.
  2. 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.
  3. @Hemant Kumar I have to re-open that case. With the update it seems to be partially fixed. In the state when Enpass application is fully opened (see upper screenshot "Enpass main window.jpg") the problem is fixed and Platform Timer Resolution is at default now, so Windows energy report does not show a warning anymore. In the state when Enpass is running in extension mode (see lower screenshot "Enpass taskbar.jpg"), that means when left-clicking the Enpass icon just pop-outs a small Enpass window docked to the taskbar, the Platform Timer Resolution is still increased to 1ms by Enpass and Windows is showing the warning.
  4. Hello! If Enpass 6 is running minimized in the background / tray icon and the vault is locked, the Windows Platform Timer resolution is increased from the default 15.6ms to 1ms by Enpass process, which causes significantly lower CPU C state usage and thus less battery life. Steps to reproduce: 1. Let Enpass 6 start automatically with Windows, or start it and minimized it to the system tray, but do not unlock the vault yet 2. Run "powercfg /energy" within Windows PowerShell and let Microsoft power diagnostics generate an energy report 3. The report will show a warning, that Enpass.exe is requesting a non-standard Windows Platform Timer resolution that causes lower battery life (see attached screenshot). You can also confirm with tools like "ThrottleStop" that there is significantly less CPU package C state usage / power saving when Enpass is waiting for the vault to be unlocked. This almost doubles idle power draw of my CPU. 4. Unlock the Enpass vault by typing your password into Enpass window 5. Run "powercfg /energy" again 6. You will notice that when vault is unlocked, there is no Windows Platform Timer warning anymore and C state usage increases immediately. It should not be necessary for Enpass to increase Windows Platform Timer resolution when just running IDLE in the background with the vault still locked! The fact that the Platform Timer resolution goes back to its default value as soon as Enpass vault is unlocked, is a clear indication for that behavior to be a bug!
  5. Hi! I was using Enpass UWP for Windows 10 with full-time Windows Hello enabled, because my computer fulfills all necessary requirements (TPM 2.0, UEFI Secure Boot). So Enpass UWP successfully detected that the machine is secure enough to store the keys in hardware/TPM and use Windows Hello directly on the first launch even after a computer restart or when Enpass UWP was completely closed. Now with Enpass 6, it is only using the fallback solution of asking for the master password the first time after restart, and using Windows Hello only for subsequent unlocks. I think Enpass 6 is great and a big improvement in many things, but in this particular aspect it feels like kind of a stepback. So my question is: Will full-time Windows Hello be supported in Enpass 6 again like it was in Enpass UWP for computers which fulfill the necessary requirements for hardware/TPM-based security?
  6. What is about full-time Windows Hello, when the computer fulfills all the requirements needed for it to work in the Enpass UWP app? I have UEFI boot with Secure Boot, TPM 2.0 module, Windows Hello working with TPM, and was already successfully using full-time Windows Hello with Enpass UWP. Will it also be supported by Enpass 6? Or is it already for people that fulfill said requirements?
  7. Hello! It looks like Autofill is not working when using the Samsung Internet browser which is the preinstalled and default internet browser on newer Galaxy smartphones (S7, S8,...). Because it has a lot of optimizations for Samsungs Galaxy phones it's the preferred browser on Samsung devices and much faster and less battery consuming than Chrome. So it would be really great if you could give us autofill support for the Samsung Browser. Are there any plans? They even have some built in extension capabilities that allow third-party plugins to access the web page content (meant for adblockers and stuff like that..). Maybe Enpass could even integrate with that?
  8. Unfortunately even with latest version of Enpass, this is still the case Doesn't seem to depend on the browser extension though (same problem with Chrome and FF), it also happens sometimes when I click on Enpass icon in system tray, but only when extension support is enabled. Small Enpass box only appears briefly and I have to click a second time on the icon.
  9. It would already help a lot if it wouldn't be necessary to re-enable the extension every single time you restart Edge. That is what makes it totally unusable for me. I could live with having the loopback stuff enabled.
  10. I'm also experiencing this kind of crash. But only sometimes, which makes it really hard to reproduce. When it happens, it happens when trying to open Enpass window. Thereby it doesn't matter if I'm already logged into my vault or not. Last version of 5.3 was fine, problems started since 5.4. My cloud sync provider is Onedrive. Event log entry (unfortunately only in German): Name der fehlerhaften Anwendung: Enpass.exe, Version: 0.0.0.0, Zeitstempel: 0x0538bc38 Name des fehlerhaften Moduls: libstdc++-6.dll, Version: 0.0.0.0, Zeitstempel: 0x00000000 Ausnahmecode: 0x40000015 Fehleroffset: 0x0001f11d ID des fehlerhaften Prozesses: 0x17c8 Startzeit der fehlerhaften Anwendung: 0x01d25d316fc38744 Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Enpass\Enpass.exe Pfad des fehlerhaften Moduls: C:\Program Files (x86)\Enpass\libstdc++-6.dll Berichtskennung: 43891490-3a23-43c3-82b1-c3e2a24502d1 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: I'm using Windows 10 x64 (Anniversary update 1607) and browser extension for Firefox.
  11. Hello! Since Firefox 50 (which got released today) the browsers multiprocess architecture "e10s" is supporting extensions, too. However, Enpass is being reported as "Not compatible with multiprocess" by the Addon Compatibility Reporter and is thus preventing e10s from being enabled. Do you have an update in the pipe for giving us multiprocess support? That would be great, because right now Enpass is the only extension which I'm using that prevents me from using FF in multiprocess mode
  12. Hello! I have the following problem: Whenever I click the Enpass extension icon for the first time after starting Chrome (doesn't matter if Enpass is already unlocked or not), the small Enpass box is just flashing up for a few milliseconds. I have to click it for a second time to make it stay visible. After that everything is fine until I restart Chrome -> same thing again. Any suggestions?
  13. Hello! I'm new to Enpass (switched from Lastpass ) and so far everything was working really well, but now I have a problem with the Enpass extension for Google Chrome. Extension support is enabled in Enpass Desktop, connection to localhost / 127.0.0.1 is not blocked by any firewall application or AV software, but whenever I try to use the extension it shows me "Enpass connection error" and sometimes the following: If I disable the "Verify browsers" setting in Enpass, it starts working, but I think that could be security risk... The error "There where something wrong to find executable path" seems important to me, maybe that is connected to the problem? It's working on another PC of mine, so I looked for the differences between the computers. The computer where it is NOT working has Windows 7 x64 Pro (instead of W10) and a multi-user configuration, so the installer of Google Chrome didn't use the user folder where it usually puts the Chrome binaries. Instead it was automatically installed to "C:\Program Files (x86)\Google\Chrome\Application" (despite it's the x64 version of Chrome. I don't know why they are installing it to (x86) folder...) Could it be that Enpass doesn't expect the browser executable at this path?
×
×
  • Create New...