Bitwarden ships three Windows builds, all from the same signing certificate. Pick whichever matches how you manage software on your machine.
The standard installer for Windows 10 and 11. Signed by Bitwarden, Inc. — SmartScreen recognises the certificate and allows the install without warnings.
| Build | Best for | Auto-update |
|---|---|---|
| Installer Download |
Personal use, full features | In-app updater, on launch |
| Microsoft Store Open Store |
Managed Windows, work laptops, sandbox | Through Windows Update |
| Portable Download |
USB stick, no-install scenarios, restricted PCs | Manual re-download |
This is what most people want. The installer drops Bitwarden into %LocalAppData%\Programs\Bitwarden\, registers a Start menu shortcut, and configures the in-app updater. After install, opening Bitwarden lets you sign in or create an account.
This shouldn't happen — Bitwarden's signing certificate is well established. But if you see a blue screen saying "Windows protected your PC":
The Store build is a Universal Windows Platform package. Functionally identical to the standard installer — same vault sync, same UI, same encryption — but installed via Microsoft's distribution channel and updated through Windows Update.
When to choose Store version:
When to skip:
A self-contained executable that runs without installing anything. Stash it on a USB stick or Dropbox folder, double-click, the app launches and stores its data in a folder next to the executable rather than under %LocalAppData%.
Use cases: shared workstations where you can't install software; a tech-support kit on a USB drive; testing Bitwarden without touching the registry; running Bitwarden on a write-protected machine.
Caveats: no file association, no Start menu shortcut, no auto-update — you re-download manually when a new version is out. Ideal as a backup-of-last-resort, not as your daily driver.
Download portable build →The desktop app is a vault viewer; the browser extension is what does autofill. If you want Bitwarden to fill passwords on websites — which is 80% of why people install a password manager — the extension is the actual feature you want.
Install both: desktop app from above, plus the browser extension for whichever browser you actually use:
On Windows 11, Bitwarden integrates with several OS features cleanly:
Windows 10 (1809 and later) is fully supported until Bitwarden drops it — currently no announcement. Windows Hello works on supported devices (Surface, ThinkPad fingerprint readers, IR cameras for face). Snap Layouts is Windows 11 only; on 10, Bitwarden's window behaves like any standard app.
If you're on Windows 10 22H2 (the final version before 11), everything works identically to 11 except the OS-level UI integrations.
Windows 11 ships with a basic password manager tied to your Microsoft account — primarily through Edge\'s autofill and Authenticator app TOTP storage. Comparison:
| Bitwarden | Microsoft / Windows built-in | |
|---|---|---|
| Cross-browser | Yes (Chrome, Firefox, Edge, Safari) | Edge mainly |
| Cross-OS | Yes (Win, Mac, Linux, iOS, Android) | Windows + iOS/Android Authenticator |
| Open source | Yes | No |
| Self-host | Yes | No |
| Master password | Yes (zero-knowledge) | Microsoft account only |
| Sharing | Organisations, family plans | Limited |
| Cost | Free / $10 Premium | Free with MS account |
If you live entirely in the Microsoft ecosystem (Edge browser, Windows-only, no mobile), the built-in suffices. For everyone else — multiple browsers, multiple OSes, family sharing — Bitwarden is the better choice.
For IT admins deploying Bitwarden across Windows fleets:
Bitwarden-Installer-X.X.X.exe /S (NSIS standard)./D=C:\Path appended (no quotes, no equals after /D).For biometric unlock to work between desktop app and browser extension, the browser-integration handshake uses native messaging on Windows. Sometimes blocked by aggressive antivirus — if biometric unlock fails, whitelist the Bitwarden folder in Defender / your AV software.
Bitwarden\'s installer is signed by "Bitwarden Inc." with a well-established Authenticode certificate. SmartScreen will recognise it and allow install without warnings. If you see a SmartScreen warning, you\'re downloading from a wrong source — verify the publisher line says Bitwarden Inc. before proceeding.
If your enterprise uses WDAC for app whitelisting, Bitwarden\'s signing certificate ("Bitwarden Inc.", Microsoft Authenticode) typically maps to a publisher rule. Verify against your WDAC policy before deployment.
If you use WSL for development, the Bitwarden CLI inside WSL works the same as on native Linux — install via npm install -g @bitwarden/cli or the Linux native binary. The WSL CLI session is separate from your Windows desktop app session; sign in once per environment.
The .exe installer comes from GitHub Releases under github.com/bitwarden/clients/releases — specifically the asset named Bitwarden-Installer-X.X.X.exe on the latest desktop-vYYYY.X.X tag. Our redirect resolves that automatically. The Microsoft Store version is at apps.microsoft.com/detail/9pjsdv0vpk04.
It doesn't, by default — Bitwarden installs to %LocalAppData% for the current user, which doesn't require elevation. If you choose "all users" install scope or run the installer as Administrator, then yes, it'll prompt for UAC. The current-user default is fine for most cases.
No. Bitwarden 2024.4 dropped Windows 7 support. The Electron runtime version Bitwarden bundles requires Windows 10 1809 or later. If you're still on Windows 7, the only practical option is the web vault in a modern browser.
Yes — the installer accepts /S for silent install (NSIS standard). Useful for fleet deployment via Group Policy, Intune, or PowerShell DSC. Example: Bitwarden-Installer-2026.4.0.exe /S. Specify install dir with /D=C:\Path.
The desktop app is the GUI vault viewer. The CLI is a separate command-line tool (bw) for scripting — exporting vault data to JSON, fetching specific items in bash scripts, integrating with CI pipelines. They share no code; install whichever (or both) based on need.
Yes — recent Bitwarden releases include an ARM64 .exe alongside the x64 build. Surface Pro X, ARM-based ThinkPads, and Snapdragon-X laptops should pick the Bitwarden-Installer-X.X.X-arm64.exe asset on GitHub Releases (or the Microsoft Store version, which auto-detects architecture).
Settings → Apps → Bitwarden → Uninstall. The vault data folder under %AppData%\Bitwarden\ is left in place by default — delete it manually if you want a complete wipe. The vault contents on Bitwarden's servers are independent of the local install; your account remains accessible from other devices.
Yes, but with caveats: the browser-integration handshake (which lets the extension talk to the desktop app for biometric unlock) won't work across sandbox boundaries. You'll need to either run both extension and app inside the same sandbox, or accept that the desktop app runs standalone. The Microsoft Store UWP version already runs in a sandbox by default.