How to uninstall 1Password on Windows
Sign in to 1Password on the web or another device and open a recently added or edited item before uninstalling the Windows app. This checks that your vault is available elsewhere with its latest changes. This guide covers 1Password installed machine-wide from the AgileBits.1Password winget package.
Keep what you need to sign in
Keep your account password, Secret Key and access to your two-factor authentication method. An Emergency Kit helps you sign in; it is not a vault backup and does not prove that recent items have synced. What an Emergency Kit contains
If you cannot sign in elsewhere or recent items are missing, resolve that first and keep the local data.
Quit 1Password first
Right-click the 1Password tray icon and quit it, then check Task Manager (Ctrl+Shift+Esc) for any 1Password.exe still listed before you uninstall. 1Password starts itself at sign-in through a machine-wide startup entry.
Browser extensions are handled per browser: 1Password's Chrome, Edge and Firefox extensions were installed from each browser's own store, so keep an extension if you still want autofill, or remove it through that browser's extension manager.
Remove the app with its own uninstaller
Go to Settings › Apps › Installed apps, find 1Password, and choose Uninstall, or run:
winget uninstall --id AgileBits.1Password
Where the data lives
Do not treat any of these as a cache; an app-matching name does not mean the folder holds no vault data.
| Location | What it holds | What to do |
|---|---|---|
%LOCALAPPDATA%\1Password |
Local vault data, including logs | Keep it until access elsewhere is proven |
%APPDATA%\1Password |
App settings and caches | Same as above |
| Native messaging host entries for Chrome, Edge and Firefox | Let a browser extension talk to the app | Removed by the uninstaller; the browser extension itself stays until you remove it separately |
Check the result
Run these read-only commands after the uninstall finishes:
Get-Process 1Password -ErrorAction SilentlyContinue
winget list --id AgileBits.1Password
Test-Path "$env:ProgramFiles\1Password"
Test-Path "$env:LOCALAPPDATA\1Password"
- No output from
Get-Processonly means this query observed no matching process; a suppressed error leaves the running state unknown. - A completed
winget listquery with no match means the package record is gone; a matching row means the uninstall did not finish. - The first
Test-PathreturningFalsemeans the program folder is gone;Truemeans files remain there. Test-Path "$env:LOCALAPPDATA\1Password"returningTruemeans local vault data is still there, which is what you want until access elsewhere is confirmed.
Open the vault again on the device or website you kept, and check your items. Removing the app neither cancels your subscription nor deletes your account.
If you cannot sign in elsewhere
If the web vault or another device lacks recently changed items, investigate sync first. Use your Emergency Kit and two-step verification method to confirm you can actually sign in; possessing the Secret Key alone is not a recovery test. Keep this machine's app and data until access elsewhere is proven. Reinstalling is not a way to test an incomplete backup.
If you installed it with winget
winget uninstall runs the same MSI uninstaller (msiexec /x ... /passive) Settings › Apps uses and removes the same program files, its startup entry and the browser native messaging host registrations; it does not touch %LOCALAPPDATA%\1Password or %APPDATA%\1Password on its own.
What Mole lists
For 1Password installed machine-wide from winget:
- The program folder is selected by default.
%LOCALAPPDATA%\1Passwordand%APPDATA%\1Passwordare listed but not selected, since they hold local vault data; theCacheandCode Cachefolders inside%APPDATA%\1Passwordare listed on their own and selected by default.- The native messaging host entries for Chrome, Edge and Firefox are selected by default.
- The Start Menu shortcut is selected by default.
What this test covered
Tested with 1Password 8.12.36 installed through winget, machine-wide scope. No vault was signed in during the test, so sync, vault access and browser extensions were not exercised end to end.
