Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
Expected behaviour of the (newish) MANAGED_UPDATE=1 MSI deployment parameter
The article https://support.1password.com/deploy-1password/?windows#msi-deployment-options states: and the https://releases.1password.com/windows/stable/ page states in the release notes for ve...
1Password for Windows (1PfW) 8.11.0 installed with 8.11.2 available.
After overcoming an install string regression issue and sorting out rogue .msi files in the %LocalAppData%\1Password\ directory, I think the MANAGED_UPDATE=1 parameter is now working as intended.
The behaviour now - from the 1PfW main dialog, the "Check for Updates..." menu item is still enabled and launches the 1PfW "Settings" dialog "About" pane, but available updates are no longer listed or generating update notification banners.I should also reference the related community discussion Disable 1Password Updates | 1Password Community, in case you're interested in the MANAGED_UPDATE related registry settings.
Just deployed 8.10.82 to clients. Let's see how it handles the next 1Password for Windows update. I did notice on the first launch (post install) of 8.10.82, that the application was still flagging the update to 8.10.82. What's with that?
Yes, the %localappdata%\1Password folder would have been preserved between the installations. No .msi in the folder at the moment but I'll monitor that folder when we deploy the next version of 1Password for Windows. Thanks.
