When I start Windows, Enpass 6.12.0 (2238) opens in my face on the desktop.
Can I make it open discreetly minimized to the system tray like older versions did?

Edited June 28Jun 28 by Dypsis

Hi,

I have the same issue with my Enpass app, updated from the last 6.11 version (non–MS Store), a couple of days ago.

After checking a few things, I realized that the problem was that the autostart entry was still pointing to the "C:\Program Files (x86)\" folder. So I modified the registry key at "\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\" with the correct path and the parameter to start the app minimized:

"C:\Program Files\Enpass\Enpass.exe" -minimize

After making the change, Enpass did start automatically as expected, but it didn’t start minimized.

So that didn’t solve the issue. I also tried configuring it through the GUI, but no luck either.

Hope this helps save some time for anyone who reads this before trying the same workaround I did.

P.S. And to the developers: there’s definitely an issue with minimized autostart that needs to be fixed ASAP. It’s pretty annoying to have the app splash in your face every time the computer starts 😵‍💫.

Regards.

On 5/16/2026 at 8:41 PM, matt73 said:

Hi,

I have the same issue with my Enpass app, updated from the last 6.11 version (non–MS Store), a couple of days ago.

After checking a few things, I realized that the problem was that the autostart entry was still pointing to the "C:\Program Files (x86)\" folder. So I modified the registry key at "\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\" with the correct path and the parameter to start the app minimized:

"C:\Program Files\Enpass\Enpass.exe" -minimize

After making the change, Enpass did start automatically as expected, but it didn’t start minimized.

So that didn’t solve the issue. I also tried configuring it through the GUI, but no luck either.

Hope this helps save some time for anyone who reads this before trying the same workaround I did.

P.S. And to the developers: there’s definitely an issue with minimized autostart that needs to be fixed ASAP. It’s pretty annoying to have the app splash in your face every time the computer starts 😵‍💫.

Regards.

Edited to report a small GUI issue: the password is shown as plain text when the “show password” icon is crossed out (the behavior is inverted).

Our technical team has identified the issue and implemented a fix. The fix will be included in a future release of the Enpass app.

We appreciate your understanding and support.



_SI-4760

11 hours ago, Tarun Singh Rawat said:

Our technical team has identified the issue and implemented a fix. The fix will be included in a future release of the Enpass app.

We appreciate your understanding and support.



_SI-4760

Which bug have you fixed?
The "show password" bug, or the "start minimized" bug?

Do we have an ETA on the fix for minimize at autostart ignore? I haven't witnessed the other "shot pw" bug myself.

Is this bug ever going to be fixed? It can't be that hard.

On 5/26/2026 at 8:13 AM, Tarun Singh Rawat said:

Our technical team has identified the issue and implemented a fix. The fix will be included in a future release of the Enpass app.

We appreciate your understanding and support.



_SI-4760

Wonder what did they identify? Prolly nothing!

Fix implementation ETA Dec. of 2029?

Edited July 8Jul 8 by Akki

I'm starting to think that they don't know what they're doing if they can't fix such a simple problem that didn't exist in previous versions.

Please have it start in the background without showing the window when Windows starts.

We are aware of the issue where Enpass no longer launches minimized to the system tray on Windows startup after recent updates. Our technical team is investigating the behavior, and we'll post an update in this thread as soon as more information becomes available.

After simply uninstalling and reinstalling Enpass, it now starts minimized again. I’m using the Microsoft Store version. I hope this information helps someone!

EDIT: After a few restarts, the error occurred again. So unfortunately, it wasn’t a permanent solution.

Edited July 30Jul 30 by Spaiky