Amandeep Kumar

Could you please raise a request with us at support@enpass.io along with your device details, and the exact error message? Our team will look into this closely and assist you further.

Yes, we have received your request and have forwarded it to our product team for further investigation. Our team will review this in detail and share a fix or workaround with you soon.

@My1 Thank you for sharing the details. Regarding the screenshot - please go to Enpass Settings → Advanced → Enable Screenshots and check the box. This will allow you to capture screenshots within the app. For the biometric issue, we request you to please share more details with us (such as a short video if possible) by contacting us directly at support@enpass.io. This will help our technical team investigate the behavior further. (Note:- Please hide sensitive information while recroding your screen)

Thanks for checking this and sharing the detailed steps with us. We’ve noted your observations and will be sharing this with our product team for further investigation. We appreciate your patience and will keep you updated on any progress.

Thank you for sharing the detailed information about your setup and the troubleshooting steps you’ve already taken. I will pass this along to our technical team for further investigation. If we need any additional details from you, we’ll reach out. We truly appreciate your patience as we work to resolve this issue! #SI-4490

Thank you for sharing the detailed steps to reproduce the issue. I will pass this along to our technical team for further investigation. If we need any additional details from you, we will reach out. We truly appreciate your patience as we work to resolve this! #SI-4489

This issue was caused by a temporary glitch on Microsoft’s end, and it has now been resolved.

@fermati Could you please confirm if you have closed all Enpass icons from the dock and then restarted your device? After restarting, test again to see if multiple dock icons still appear.

We totally get that this isn’t ideal, and feedback like yours really helps us understand how important proper Wayland and broader Linux support is. I’ve passed this along to our product team so it’s on their roadmap. We are actively pushing for this improvement and will get back to you as soon as it is prioritized.

Due to a minor glitch, MP4 attachments were initially rejected by our ticketing system. We sincerely apologize for the delay this may have caused. Please be assured that we have now received your email and will respond to you as soon as possible via email.

@MrElectrifyer Thank you for confirming. Since the PortableOperatingSystem registry item isn’t present in your case, it seems the cause is different. I’ve shared your details with our Technical Team and asked them to investigate further. I’ll keep you updated here with any findings, and if we need additional information, I’ll reach out directly on this thread. We really appreciate your support and patience while we look into this. #SI-4482

To help us investigate further, could you please provide a few more details about the issue: Enpass extension version on Edge A short video of the behavior (if possible) You can send these details to us at support@enpass.io so our team can look into this more closely. NOTE- Please hide or blur the sensitive info while recording video.

I’ve shared your detailed findings with our product team so they can review the client-side sync module behavior further. We’ll update this thread once we have more insights. Thanks again for your patience and for helping us investigate this further.

It’s great to hear everything is working fine again. Your notes about restarting the Wi-Fi Sync Server and the VPN behavior will surely help other users who might face a similar situation. We’ll also review this on our end to see if we can improve detection and connectivity in such cases. Really appreciate you taking the time to document your experience!

Thanks for your interest and valuable feedback. We’re already working on adding RSS support for our blog, and you can expect this feature to be available in the future.

Thank you for taking the time to share your experience in detail. We’re glad to hear you were able to resolve the issue. We’ll review this behavior on our side to understand why it occurs and see how we can improve Enpass to handle such cases better in the future.

We understand the inconvenience and want to assure you that our team is aware of the Safari issue and working on a fix. Your data remains fully encrypted and secure, only certain Safari functionality is affected. The Safari autofill extension is part of the macOS app bundle and will be released by the end of the month. Until then, you can disable the inline autofill popup in Safari Extension Settings ▶︎ “Show Inline Autofill Popup Menu” ▶︎ Off. Thanks for your patience, we’ll update this thread once the fix is out.

Thank you for sharing your update. You’re correct, the security issues you mentioned have already been addressed in v6.11.6.2, so you can continue using the extension with confidence. Regarding the issue with certain websites, our team is still working on improving compatibility, and we’ll release a fix in an upcoming update. We’ll make sure to keep this thread updated once it’s available. We appreciate your patience and understanding.

Hi @fermati, Thank you for sharing these detailed observations and screenshots. This information is very helpful. We’ve forwarded your report to our product team for further investigation. We’ll update you here as soon as we have more insights to share. #SI-4476

We truly apologize for the inconvenience. The issue turned out to be more complex than expected, but our team is on it. We’re committed to getting this resolved and will keep you posted through this thread. Thanks so much for your patience.

Thanks for confirming that Enpass 6.11.13 is working well on macOS 26 Tahoe beta 7! About the dock icon duplication, we weren’t aware of this behavior in the current build, so your report is very helpful. Could you please share a few details (steps to reproduce, any patterns you’ve noticed) so our team can investigate?

That’s right, this isn’t a bug in the traditional sense. What’s happening is expected: our signing key is nearing the end of its validity window under the updated policy requirements (specifically, stricter hashing rules around SHA-1). We’re fully aware that this needs updating. Rest assured, our technical team is already working on rotating the signing key. Once that’s ready, it will be rolled out in an upcoming update. Thanks for your patience and for helping us improve the Linux install experience

Thanks for checking in! Yes, we’re aware of the issue with Samsung Internet and it’s already on our priority list. Our team is actively working on broader browser support, and Samsung Internet is part of that roadmap. While I don’t have an exact ETA to share just yet, please rest assured it’s in progress and will be addressed in an upcoming release.

That’s correct. If your vault is synced with OneDrive, an expired token could trigger the re-authentication prompt. It’s usually nothing to worry about, just a routine security step from Microsoft when the token expires or refreshes.

Thanks for sharing the detailed info and version specifics, this will surely help our technical team investigate further. We appreciate you confirming the behavior across Firefox vs. Chromium/Vivaldi and the extension versions. If you notice any new errors or if updating the Firefox extension becomes possible, please let us know.