While you work to fix this I need a link to download the previous version.

I'm "update averse", as nearly all software updates these days break software or degrade usability for the sake of changes, so I was scared to apply the update, seeing that Enpass was redesigned. I fully expected a disaster. I have to admit though, that I was not a complete disaster as this new Enpass improved the looks and the functionality without breaking too much.

Well, for the most part...

The main content screen is mostly nice, definitely an improvement over the old one, it's cleaner, looks better and I like the new dark mode, the old one was black, like the early Windows 10 dark mode. I like the addition of standard menus in the upper left too.

But, it's not all that good, I see few annoying issues.

I don't like that the notes field is now an eye scorching bright yellow and that it's folded by default. Can you please consider adding an option to make notes the same color as the window, the way it used to be, and not fold/hide it by default? I use notes a lot and it's now very uncomfortable to look at them when working in dark mode in a dimly lit room. It literally lights up the room when unfolded. And you missed the opportunity to make the notes field re-sizable in edit mode which would be more of an improvement than the painfully bright, yellow color. There is no need to associate "notes" with "yellow" any more, even Post-it started offering blue, white and gray stickies over a decade ago.

The new icons are also too bright, too colorful, this is unnecessary decoration that adds nothing but visual noise. Can we please have the option to go back to the old gray glyphs or hide them altogether as they are nearly as painful as the yellow notes?

Same for item icons, you increased the saturation. I use website icons whenever possible and the default icons do stick out.

I'm not too crazy about the new settings either. It looks and works too much like the dreaded Windows 11 Settings App, but I suppose I can get used to it. There is too much empty space and display density is low like on mobile devices. Now everything is too big and there is more scrolling required to access settings while the window can't be enlarged. This is a regression in usability. And for what? For the dozen of people who use Windows on mobile devices?

Overall, pretty decent update except for the few jarring color choices. Please consider adding options to address those annoyances. Thank you.

• Automatically sign in after filling in login details

• Autofill without prompting to select for single matching item

Both are translated as "O atalho de teclado preencherá automaticamente sem apresentar o Assistente do Enpass se houver apenas um Item correspondente". The error does not occur in English.



While we're at it... The addition of Brazilian Portuguese would also be very welcome.

I have a total of 450 entries and for all of them I created and saved custom icons myself (mostly based on the icons of the respective apps from the iOS App Store) so that everything looks clean and high-resolution (especially for websites whose favicons do not look good). I always used a resolution of 256x256 pixels (PNG files) to ensure the icons were high-resolution enough to also look good on high DPI displays such as my iPhone.

Until updating Enpass to version 6.12.0 on Windows, everything looked perfect and nothing was pixelated. With the new update, all of my custom icons are now very pixelated, which makes me suspect that a different scaling technique is now being used to scale the icons down (with my screen resolution of 1920x1080 pixels and normal 100% scaling in Windows, the icons are displayed at 40x40 pixels each). Unfortunately, this makes some of the text on the icons hard to read and overall does not look good anymore.

Here are some examples:

I hope this can be fixed soon.

• OS: Windows 11 (Kernel Version 26100, Build 10.0.26100.7920)

• Architecture: x64, 20 logical processors

• Enpass version: [insert your version]

• Crash date: April 20, 2026 — 15:32:59 UTC+2

Bug Description

Enpass.exe is causing a reproducible kernel-level crash (Blue Screen of Death) on Windows 11 with stop code DRIVER_IRQL_NOT_LESS_OR_EQUAL (bugcheck 0xD1).

The crash occurs inside NETIO.SYS at function StreamInvokeCalloutAndNormalizeAction+0x5c, triggered by a Windows Filtering Platform (WFP) callout registered by Enpass. The faulting process is explicitly identified as Enpass.exe in the minidump.

Minidump Analysis (WinDbg !analyze -v)

BUGCHECK_CODE: 0xD1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)
PROCESS_NAME: Enpass.exe
FAILURE_BUCKET_ID: AV_NETIO!StreamInvokeCalloutAndNormalizeAction
FAILURE_HASH: {c2ca2d1f-cfdc-88d5-c7bc-7693b8f0de04}

FAULTING_INSTRUCTION:
  NETIO!StreamInvokeCalloutAndNormalizeAction+5c
  fffff805`607c43a8 488b4808  mov rcx, qword ptr [rax+8]
  → Access Violation: reading address 0x0000000000000008 at IRQL 2 (DISPATCH_LEVEL)

STACK TRACE:
  nt!KeBugCheckEx
  nt!KiBugCheckDispatch+0x69
  nt!KiPageFault+0x468
  NETIO!StreamInvokeCalloutAndNormalizeAction+0x5c
  NETIO!StreamCalloutProcessingLoop+0x147
  NETIO!StreamProcessCallout+0x2f4
  NETIO!ProcessCallout+0x821
  NETIO!ArbitrateAndEnforce+0x5af
  NETIO!ArbitrateAndEnforceCallout+0x4d
  nt!KxSwitchKernelStackCallout+0x2e
  nt!KiSwitchKernelStackContinue

Root Cause Analysis

Enpass registers a WFP stream callout (via FwpsCalloutRegister) to inspect network traffic — likely for phishing protection or connection monitoring. The callout is passing an invalid or already-freed NET_BUFFER_LIST pointer to NETIO!StreamInvokeCalloutAndNormalizeAction. When the function attempts to dereference offset +0x8 of the returned pointer (rax+8), it reads from address 0x0000000000000008 — a near-null pointer, indicating a use-after-free or NULL dereference in the callout handler.

This is a kernel-mode bug: WFP callouts operate at DISPATCH_LEVEL (IRQL 2) and must not access pageable or invalid memory. The crash is 100% reproducible and consistently attributed to Enpass.exe across multiple minidumps.

Impact

• Severity: Critical — system crash (BSOD), data loss risk

• Frequency: Recurring (multiple crashes observed)

• Workaround: Uninstalling Enpass eliminates the crash entirely

Steps to Reproduce

The crash appears to trigger during active network usage while Enpass is running in the background. No specific user action in Enpass is required — simply having it running as a startup process is sufficient.

Suggested Fix

Review the WFP stream callout implementation (FwpsCalloutRegister / FwpsStreamInjectAsync). Ensure that:

1. NET_BUFFER_LIST references are validated before dereferencing at DISPATCH_LEVEL

2. Callout handlers properly handle NULL or freed buffer pointers

3. The callout is unregistered safely on process exit with FwpsCalloutUnregisterById

Reference: Microsoft WFP Stream Callout documentation

042026-19312-01.dmp

Da es keiner von Enpass für nötig empfindet, bei Problemen und Fehlern per Mail und hier im Forum einzugehen, hoffe ich, dass jetzt endlich jemand zahlende Anwender hilft. Nur zu Info, durch euer neustes Update kann Enpass weiter genutzt werden. Wie bereits in einen anderen Beitrag erwähnt, ist nach dem Update keine Synchronisierung möglich. Alle Tipps der Hilfeseite wurden befolgt, dennoch keine Verbesserung. Es liegt nicht an unseren Einstellungen oder Systemen, denn dort hat sich nichts verändert. Es liegt difinitiv an Enpass, denn bei einer Neuinstallation bekommt man die Fehlermeldung "Es konnte keine Verbindung zum Server hergestellt werden", daher ist eine Aktivierung auch nicht möglich. Das wurde auf verschiedenen Computer versucht, überall funktioniert die neuste Version nicht. Ich kann nur jeden von der Installation des Updates 6.11.19 (2205) abraten. Der Beweis, die alte Version Enpass_5.6.10_Setup von der offiziellen Enpass Seite funktioniert und synchronisiert auch einwandfrei.

Wann reagiert mal jemand von den Entwickler und/oder behebt das Problem, schliesslich haben bzw zahlen (6 Lizenzen) wir für Enpass. So langsam sind wir ziemlich verärgert.

Forum Eintrag

Forum Eintrag

If I Quit Enpass and then relaunch it, then it starts working again immediately.

I don't need to reboot Windows or anything. Just Quit Enpass and relaunch.

First I want to say thank you: For the last couple of years, enpass crashed quite often on my notebook and since a few month it seems to be very stable. Thanks for that!

Now to my little issue:
When I activate autostart on windows start, every time enpass launches, it also launches a console window, that quickly after that closes. This by itself is no issue. But this also launches my Windows Terminal app, which after than stays open. As soon as I disable enpass autostart, this does not happen anymore. BTW this also happens when I don't auto start enpass but then manually open enpass. So it seems that this is an issue with enpass altogether and not the autostart function. It's very annoying that my windows terminal opens every time I restart windows.

Can you please look into that and maybe avoid the opening of the terminal window altogether? 

Information:

• Enpass 6.8.5 (1238)
• Windows 11 Pro 22H2 (22623.1255)

Thanks!
Regards,

Florian

How can I restore the full Windows Hello functionality? I tried deleting and re-registering Face ID in Windows Settings, but this didn't help.

Windows Store version 6.11.19

ich habe das Problem nach der Installation des Updates version 6.11.19 (2205) mit Google Drive mit der Fehlermeldung „Bitte überprüfen Sie Ihre Internetverbindung oder versuchen Sie es später erneut.“, oder "Etwas hat nicht funktioniert"..

Alle Anweisungen der Hilfeseite habe ich befolgt, auch automatische Uhrzeiten ist eingestellt und stimmen überein. Das Problem besteht nur bei der Version 6.11.19 (2205)! Ich habe alle verfügbaren Versionen die älter sind installiert, bei denen besteht das Problem nicht. Somit hat es nichts mit unseren System oder Uhrzeit zu tun. Bitte behebt das Problem, wir können so unsere Passwörter nicht mehr nutzen.

Hello, I'm having trouble with Google Drive after installing update version 6.11.19 (2205). I'm getting the error message "Please check your internet connection or try again later," or "Something went wrong." I've followed all the instructions on the help page, and the automatic time settings are correct. The problem only occurs with version 6.11.19 (2205)! I've installed all older versions, and the problem doesn't occur with them. Therefore, it's not related to our system or the clock. Please fix this issue; we can no longer use our passwords.

Please give us back version 6.11.17, at least everything works with that one. Or tell us where we can download this version.

Then, I noticed my most recent backup was only 1kb in size. Looking at previous monthly backups I'm seeing a wide variety of size differences. If anything, the database should be getting larger, not smaller (and certainly not 1kb or even 88kb as seen in the attached image). It is very scary that my backups might be corrupt. I'm glad I caught this before actually needing it!

I just reran the backup and this time the file size was 9,259kb - almost double even the average previous backups.

Has anyone seen the same thing as me? Any suggestions?

EDIT: I re-backed up Enpass on Windows, then reinstalled Enpass on Linux. This time, I was successful in entering the password AND key file (it asked for it this time). I suspect the file I tried to restore was corrupt and that is why the password wasn't accepted and no key file was asked for in my original attempt. Also, I found the reason the 2026-03-01 backup was only 1kb was because my Versacrypt volume was full. The volume being full might be the problem starting on 202601 too, where each successive month the file got smaller maybe due to it running out of space????

EDIT 2: I wrote a Python script to check the backup files to see if valid. The files are zip files (though no zip extension). Within the zip there is a root directory and within it a directory name primary (I suspect that depends on what the individual named their vault). In the root there should be a file named "backup.info". This states whether there is a key file required. Within the primary directory are two files named "vault.json" and "vault.enpassdb". I check for the presence of those 3 files to determine whether the backup was valid or not. 5 files were missing one or more of those files.

I can not find any way to hide these and I don't want them every time I start Enpass.

I tried to configure Enpass not to store the "Enpass safe" at the root directory in my cloud.

So I tried to change the URL that Enpass is using. Like so : https://webdav.pcloud.com/Home/myName. But it failed. It says it can't connect and the usual "check credentials".

I tried several URLs (with ending / or not, etc ) with no luck. Then I decided to go back to the original configuration. Only to find it was not working anymore. I had to close the configuration panel completely and then configure WebDAV again with the original settings. It then worked.

Still I'm stuck in the same situation (can't use sub-directory) while I'm connecting flawlessly with a browser to this specific directory (or any other in fact).

There may be a little issue with the config panel and WebDAV. Maybe it doesn't follow the configuration changes upon failed attempts. And maybe something with the WebDAV implementation in Enpass.

Thx

Thank you,
Ken

URL, Username and Password works with a other webdav-client (cyberduck) - but enpass can´t connect to the webdav-server.

Any suggestions for solving the problem are welcome.

I have Windows Hello on but says Master password is required every time you restart - is there a setting i am missing?

I've some certificate files stored, attached to some items, in Enpass. Some weeks ago, I got "Can't save file" error when trying to save some of those certificates to my computer. The issue was troubleshooted by saving those files from a different computer on which I've the vault synced (cloud), on the second computer did not receive any error and could save the files without any problem to its disk.

To solve the problem on both computers, I had to delete all affected entry items in app, first from the one which was failing (deleting the attached files was not enough and when the files were just substituted, were failing again when trying to save them), then sync all items on both computers and, finally, recreate all items, first, on the computer which did not fail and sync the whole vault again, once done those steps I could save the certificates form any of the computers.

Finally, I'm writing this post because is the second time I face this problem. Further I know this problem affects both Enpass app versions Windows Store and Web. It is an anoying issue that could end with very bad consequences for any user who may be does not have more than one computer to do this whole procedure... Also, I checked Enpass logs (configuración > Avanzada > Registros) with no luck, seems Enpass does not log this kind of problems.

I would appreciate if you can check if this is a problem from Enpass or, if its not the case, provide some tips to avoid this problem or how to face it in case of a single computer installation.

Thanks in advance! (pardon my english... I'm not native as you could imagine some lines ago... 😁).

Kind regards.