Auto Update check Notification and Licensing

Hello,

We want to inform you that Group Policy Object (GPO) support is on our roadmap for the next major release. In the initial phase, we plan to introduce policies for:​

• Locking options (e.g., lock on idle)
• Disabling automatic updates
• Disabling access to the update menu
• Preventing the addition of new Spaces

For more details, please refer to our discussion here.
If you have any additional policy requirements or suggestions, feel free to share them with us.​

Best regards,

Hi @Sébastien Aubin

As we can see there is new Major release available(2026.2). Is a feature to disable update/notification added in this release?
If its included please let us know how to implement it like registry value or installation parameters.

Thank you.

Hi @meta

We support Group Policy Object (GPO) in the latest version. You can view the documentation here: https://docs.devolutions.net/password-manager/kb/application-knowledge-base/application-policies/?tab=windows

Best regards,
Marc-Olivier Lalonde

Hi @Marc-Olivier Lalonde

Thanks for the update.
I have a few more queries regarding the pre-configuration options for Devolutions Password Manager: Devolutions Password Manager pre-configuration | Devolutions Password Manager | Devolutions Documentation.

1. Can DEPLOY_CONFIG and the MSI properties be used together during the same installation?
2. If both are specified, is there any order of precedence between them?
3. During an upgrade, if we deploy an updated DEPLOY_CONFIG or modify the MSI properties, will the existing customizations be updated?

Hi @meta,

Can DEPLOY_CONFIG and the MSI properties be used together?
Yes. They aren't merged, though — each writes configuration independently, so avoid defining the same setting through both to prevent conflicts. Use DEPLOY_CONFIG for a full pre-built config, or the MSI properties for a few specific settings, but not the same setting in both.

Is there an order of precedence?
No formal precedence. Configuration is applied on a user's first launch, and once their config exists it won't be re-applied from the system-wide source — so coordinating your settings across the two is what avoids surprises.

On upgrade, does redeploying DEPLOY_CONFIG / changed properties update existing customizations?
No, by design. Pre-configuration applies only on a user's first launch and only when they have no existing config. Existing users keep their settings; a redeployed DEPLOY_CONFIG affects only brand-new users.

Best regards,
Marc-Olivier Lalonde