It’s Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
Forum Discussion
Solved
EXE Deprecation
As I'm sure the rest of us did, I received the e-mail notice that
- The EXE installer is being deprecated from 11th November 2025
- 1Password will force a re-install to the MSI on all users on 11th November 2025
Deprecating the installer, fine.
But re-installing the application on all devices outside of the scope of our own software controls and only giving 30-day notice is not fine.
The reasons for forcing the EXE re-installations are inaccurate, as we have been using the EXE installer with a "Protected Install" (ie. installed in C:\Program Files\1Password\) for months.
We already disable 1Password updates by using the same registry keys the MSI installer creates for "MANAGED_INSTALL" and "MANAGED_UPDATE" (both set to "1"). Is this enough to prevent 1Password from trying to migrate to the new installation method on the 11th November 2025?
Having to change installation architecture, maybe installation location, and a new version is going to require CAB approval from two different departments, be pushed to pilot groups, re-approved following testing, and then scheduled for the wider business. Only 30-days notice for this type of major change feels like a lack of consideration for customers.
So two things to take away for the 1Password team here:
- Detail methods on how to prevent this change from being automatically pushed as part of the update e-mail and change articles as it isn't clear that just disabled updates is enough
- Give 60 days+ notice on these types of major changes
1Password is the most important software we have in our business. We trust 1Password literally with the keys to every system. It is heavily scrutinised and has to go through several rounds of approval for updates.
Hello hpssa. Thanks for reaching out with your feedback regarding the EXE notification.
Regarding the amount of notice given, we understand the need to give enough time for our customers to prepare for these sorts of events. The most recent email was the latest of a series of three emails that we sent citing the upcoming deprecation of the EXE installer. The first email was sent in mid-June giving notice that the MSIX installer was coming and that the EXE would be deprecated in October. The second email was sent in early August giving notice that the MSIX installer has released and that the EXE would be deprecated on October 28. The third email was sent last week with an updated deprecation date due to the delays on our end to get the MSIX published on the Microsoft Store. These notices were sent to all active 1Password admins on Business accounts with Windows users.
Is this enough to prevent 1Password from trying to migrate to the new installation method on the 11th November 2025?
If your deployment solution blocks in-app updates, it should prevent 1Password from migrating to the new installation method. Having said that, there will not be new versions of the EXE to manually deploy so it'll be stuck on the last version available prior to November 11.
3 Replies
My apologies for my outburst. You are correct, e-mails were sent prior to then and I totally glossed over them. I am a bad person. I will go hide in a corner and wallow in my shame.
- 1P_justin
1Password Team
Absolutely no need to apologize hpssa! It happens and that's why we send out multiple notices—better seeing it late than never!
FWIW, your feedback is still valuable to help us improve future messaging. The first two notifications were centered around the MSIX which could be ignored if you didn't necessarily care about the MSIX release. Will make sure to account for this in future notifications!
- 1P_justin
Hello hpssa. Thanks for reaching out with your feedback regarding the EXE notification.
Regarding the amount of notice given, we understand the need to give enough time for our customers to prepare for these sorts of events. The most recent email was the latest of a series of three emails that we sent citing the upcoming deprecation of the EXE installer. The first email was sent in mid-June giving notice that the MSIX installer was coming and that the EXE would be deprecated in October. The second email was sent in early August giving notice that the MSIX installer has released and that the EXE would be deprecated on October 28. The third email was sent last week with an updated deprecation date due to the delays on our end to get the MSIX published on the Microsoft Store. These notices were sent to all active 1Password admins on Business accounts with Windows users.
Is this enough to prevent 1Password from trying to migrate to the new installation method on the 11th November 2025?
If your deployment solution blocks in-app updates, it should prevent 1Password from migrating to the new installation method. Having said that, there will not be new versions of the EXE to manually deploy so it'll be stuck on the last version available prior to November 11.
