Tested · Updated
Bitwarden 2026.10.1 won't load on older CPUs: "v128 not enabled", "WebAssembly is not supported" or an endless spinner
Bitwarden 2026.11.0 is the first stable release with the non-SIMD fix for the web vault, browser extension, desktop app and command-line tool. If you see v128 not enabled or an endless spinner on an older PC or VM, check which version your channel offers and try the update first. In our 20 November retest, Bitwarden reached the login form on two VM CPU models without SSE4.1 in Chromium 156 and Firefox ESR 153.6, using both the extension and the hosted web vault.
On x86 PCs and x86 virtual machines, Bitwarden's browser extension, web vault and command-line tool began shipping a WebAssembly SIMD build in 2026.10.1; the desktop app did so in 2026.10.2. In our tested Firefox, Chromium and bundled app runtimes, CPUs without SSE4.1 could not load that build. If the physical host supports the required instructions but the VM hides them, changing the VM's CPU type and stopping and starting the VM can fix this failure on the older versions.
Is this you?
Your vault stopped loading when Bitwarden updated itself to 2026.10.1 (browser extension and command-line tool released 29 October 2026; the web vault at vault.bitwarden.com changed on 28 October) or the desktop app updated to 2026.10.2 (29 October). What you see depends on the app:
- Firefox extension: a Firefox reporter described a popup saying "WebAssembly is not supported on your browser or is not enabled. WebAssembly is required to use the Bitwarden app." This is the message Bitwarden's code shows whenever its code library fails to load, even though WebAssembly itself works. Another user reported the console error
SDK loading failed: CompileError: wasm validation error: at offset 69592: v128 not enabled. Compiling the shipped SDK in Firefox reproduced the validation error at the same offset. - Chrome, Brave or Edge extension: Chrome and Brave reporters described a blank popup with a loading spinner and no error message. In our original Chromium runs, version 2026.10.1 never finished loading its code on these CPUs. Version 2026.10.0 loaded.
- Web vault (vault.bitwarden.com): the Bitwarden logo and a spinner, and the login form never appears. Clearing the cache, deleting cookies or reinstalling the browser does not change it.
- Desktop app 2026.10.2: users report that it keeps loading forever. Started from a terminal, it logs
[IPC] Initialization failed Error: SDK loading failed: CompileError: WebAssembly..instantiate(): Compiling function #311 failed: Wasm SIMD unsupported @+64917 - Command-line tool (
bw) 2026.10.1: commands that need Bitwarden's code library, such asbw generate, stop withSdkLoadFailedError: SDK loading failed: CompileError: WebAssembly..instantiate(): Compiling function #311 failed: Wasm SIMD unsupported @+64917
Two reporters in Bitwarden's issue tracker say Firefox's built-in page translation fails on the same computers.
Check the CPU. On x86 Linux, including inside an x86 VM:
grep -m1 -o sse4_1 /proc/cpuinfoIf it prints sse4_1, Linux exposes SSE4.1 to this system. If it prints nothing, that feature is not exposed. This checks one CPU feature; it does not by itself diagnose a Bitwarden failure.
On Windows, or anywhere else, ask the browser itself. This small probe checks whether this browser accepts WebAssembly SIMD. Open the browser's developer console (F12, then the Console tab). Firefox and Chrome make you type allow pasting before the first paste. Then paste this line and press Enter:
WebAssembly.validate(new Uint8Array([0,97,115,109,1,0,0,0,1,5,1,96,0,1,123,3,2,1,0,10,10,1,8,0,65,0,253,15,253,98,11])) false means this browser rejected the SIMD probe, which is consistent with this failure. true means SIMD is available; it does not prove that Bitwarden's full SDK will load or that login will work.
Expect the same CPU and browser probe results after updating Bitwarden. When WebAssembly works but SIMD is unavailable, 2026.11.0 can load its non-SIMD module. Check whether Bitwarden gets past the error or spinner you saw.
In a virtual machine: change the CPU type
If the error started with a 2026.10.x release, try 2026.11.0 first before changing the VM's CPU type.
The usual cause is the kvm64 CPU type, which hides SSE4.1 from the guest even when the host has it. In Proxmox VE, kvm64 is what a VM gets when its configuration names no CPU type, for example after qm create without --cpu. Proxmox's documentation names x86-64-v2-AES as the web interface's default for new VMs, and Bitwarden's reply to the first report recommends it.
Proxmox VE:
qm set <vmid> --cpu x86-64-v2-AES
qm shutdown <vmid> && qm start <vmid>A reboot from inside the guest does not apply the new CPU type; the VM has to stop and start. Then run the grep line above inside the guest. Proxmox documents x86-64-v2-AES for Intel hosts from Westmere or AMD Opteron G4 onward. Without AES, x86-64-v2 can be an option only if the physical host supports all its required features, including SSE4.1, SSE4.2 and SSSE3. Check the host as well as the guest: changing a KVM CPU model cannot add instructions missing from the physical CPU. host exposes the host features that KVM can provide. It works for this problem only if the host has the needed instructions. Live migration then requires compatible destination CPU features and software; do not assume it is safe between different hosts.
libvirt (virt-manager, virsh): a domain with <cpu mode=, or with no <cpu> element at all, gets -cpu kvm64 or -cpu qemu64, and neither has SSE4.1. Run virsh edit <domain>, replace the <cpu …> element with
<cpu mode='host-passthrough'/>Run virsh shutdown <domain>, wait until virsh domstate <domain> reports shut off, then run virsh start <domain> and repeat the CPU and browser checks in the guest. host-passthrough is -cpu host. If you need live migration between different hosts, a named model such as Nehalem can work if every intended host supports its required features; libvirt has no x86-64-v2 model.
Plain QEMU: use -cpu host, or Proxmox's x86-64-v2-AES flag set: -cpu qemu64,.
In our original kvm64 runs, the 2026.10.1 extensions did not reach the SDK-loaded log, the web vault stayed on its spinner, and the CLI and desktop app logged the SIMD errors above. In those runs, we did not observe the extension popup text at runtime. With x86-64-v2-AES, all of them loaded. qemu64 and QEMU's Conroe model (first-generation Core 2) failed the same way. host, Penryn (second-generation Core 2) and, in Chromium, libvirt's Nehalem model loaded. Every CPU type where the grep line printed sse4_1 loaded Bitwarden; every one where it printed nothing failed.
Update Bitwarden or use a fallback
CPUs without SSE4.1 include first-generation Core 2 Duo and Quad (Conroe, Merom), Atom chips from before 2013, AMD Phenom, Phenom II and Athlon II, and AMD's A-series "Llano" and E-series "Bobcat" chips. Some Pentium and Celeron models from the Core 2 era lack it too. AMD's SSE4a is a different instruction set and does not count. Run the check above rather than going by the model name.
In our 2026.10.x tests, switching between Firefox ESR 153.6 and Chromium 156 builds did not avoid the failure. Users also reported it in Chrome and Brave. We did not test Edge or Firefox preference workarounds. We found no working browser or desktop workaround in those configurations. Chrome's engine once had a flag for older CPUs (--wasm-simd-ssse3-codegen); Chromium 156 rejects it as unknown, and the desktop app still failed when started with it.
Try 2026.11.0 first. In checks at 06:06–06:07 UTC on 20 November 2026, Bitwarden's hosted vault, Mozilla Add-ons, the Chrome Web Store and Microsoft Edge Add-ons all reported 2026.11.0.
- Web vault. Reopen vault.bitwarden.com and check whether the login form appears. Reaching that form is one step before signing in and opening your vault.
- Firefox. Update from Mozilla Add-ons. If you turned off Bitwarden's automatic updates in
about:addons, turn them back on. - Chrome, Brave and Edge. Check the installed extension version. Use the Chrome Web Store for Chrome or Brave and Microsoft Edge Add-ons for Edge. The listing and your installed copy can show different versions. If you loaded the old version unpacked, first confirm you can log in from another working device with your password and second factor. Then open
chrome://extensions(Brave:brave://extensions, Edge:edge://extensions), remove the unpacked Bitwarden extension, install the store version and log in again. - Desktop app. Update through your usual channel when it offers 2026.11.0 or later, or choose the download for your system from Bitwarden's desktop release. From 2026.11.0, filenames start with
bit-for the standard build oross-for the open-source build. If you used the unprefixed Windows portable build below and want to stay on that edition, look foross-Bitwarden-Portable.-2026.11.0.exe - CLI. Update through your usual channel when it offers 2026.11.0 or later. Bitwarden publishes CLI downloads and an npm package.
If you cannot update to 2026.11.0 or Bitwarden still stalls after the update, check whether a CPU-type change can help your VM. On a physical PC, or if the VM change is unavailable, try another device or a fallback below.
1. Use the phone app. Bitwarden's iPhone and Android apps run on the phone's own processor, so this x86 CPU requirement does not apply to them.
2. Keep an older version as a temporary fallback. The builds we tested from this list loaded on CPUs without SSE4.1. They get no security fixes, and Bitwarden has not said how long its servers will keep accepting them. Switch back to a supported release as soon as it works on your system. Before you remove any Bitwarden app, check that you can log in to your vault from another working device with your password and second factor.
| App | Version before the SIMD requirement | How |
|---|---|---|
| Firefox extension | 2026.10.0 | Below |
| Chrome, Brave, Edge extension | 2026.10.0 | Below |
| Desktop app | 2026.10.1 | Below |
| Command-line tool | 2026.10.0 | Below |
| Web vault (vault.bitwarden.com) | none | Bitwarden serves one version to everyone |
Firefox: install 2026.10.0 and stop updates for Bitwarden only
To return to automatic updates, follow the Firefox update steps above.
Open
about:addonsand remove Bitwarden. This deletes the extension's local copy and settings; your vault stays on Bitwarden's servers.Open Bitwarden's version history on addons.mozilla.org and install 2026.10.0 (released 15 October 2026).
Straight away, open
about:addons, click Bitwarden, and set Allow automatic updates to Off. This changes only Bitwarden; other add-ons keep updating.Check that
about:addonsshows Bitwarden 2026.10.0, then log in.
Chrome, Brave and Edge: load 2026.10.0 yourself
To replace an unpacked copy, follow the steps to return to the browser store above.
The Chrome Web Store offers only the newest version. Bitwarden publishes each release's build on GitHub:
Download
bit-dist-chromefrom Bitwarden's browser-v2026.10.0 release. GitHub lists its SHA-256 as-2026.10.0.zip 77e3b7a348d01d4dc3b6af0087fd9cacae9364a063a1fee5ba6db6dfc7b138cb. Compare the downloaded file's hash with it (Windows:certutil -hashfile bit-dist-chrome; Linux:-2026.10.0.zip SHA256sha256sum bit-dist-chrome), then unzip it into a folder you will keep.-2026.10.0.zip Remove the Bitwarden extension you installed from the store.
Open
chrome://extensions(Brave:brave://extensions, Edge:edge://extensions), switch on Developer mode, click Load unpacked, and choose the folder.
An extension loaded this way never updates itself. It is a separate copy of Bitwarden, so you log in again. In our runs this build loaded its code in Chromium on every CPU type we tried, including kvm64 and Conroe.
Desktop app: run 2026.10.1 without the updater
To return to a supported build, see the desktop update options above.
The desktop app's build before the SIMD requirement was 2026.10.1, from Bitwarden's desktop-v2026.10.1 release. Uninstall 2026.10.2 first.
- Windows: use
Bitwarden-Portable. The installed app checks for updates 5 seconds after it starts and every 12 hours; it can download a newer version and ask to restart into it. The portable build skips that check.-2026.10.1.exe - Linux: use the
.deb,.rpmor.AppImagefrom that release. Bitwarden switched off self-updating for these Linux builds in this version. The Snap Store and Flathub copies update through their store, so use the GitHub build instead. This disables only the app's own updater. A configured distribution or third-party package repository can still replace a.debor.rpmduring an ordinary system update; a version pin or hold must cover that updater too. A standalone AppImage avoids that package-manager replacement.
We read this update behaviour from the 2026.10.1 code and ran the Linux .deb; we did not run the Windows builds.
Command-line tool: install 2026.10.0
To return to a supported build, see the CLI update options above.
Download bw-oss-linux (the build we tested), bw-linux or bw-windows from the cli-v2026.10.0 release, or run npm install -g @bitwarden/. The npm package asks for Node 22 or newer; on Node 20, npm printed an EBADENGINE warning, but the tool still installed and bw generate printed a password. The tool never replaces itself: bw update only tells you that a newer version exists.
3. Replace the computer, or its CPU. Run the check on the new machine before you rely on it. Some older desktop boards take a later Core 2 that has SSE4.1; check your board's supported CPU list.
What changed
On 9 October 2026 Bitwarden merged a change to its software development kit, sdk-internal#1570, that builds the WebAssembly code it ships with SIMD and a few related features. The SDK package includes a JavaScript fallback generated from an MVP WebAssembly build. In our tested apps, browsers with WebAssembly but without SIMD still tried the SIMD module and failed. We did not establish a working app fallback when WebAssembly itself is absent.
We checked each app's WebAssembly file against the published downloads:
| App | Build before the SIMD change | First version with SIMD |
|---|---|---|
| Browser extension (Firefox, Chrome Web Store) | 2026.10.0 (15 Oct) | 2026.10.1 (29 Oct) |
| Web vault | 2026.10.0 | 2026.10.1 (vault.bitwarden.com since 28 Oct) |
| Command-line tool | 2026.10.0 (15 Oct) | 2026.10.1 (29 Oct) |
| Desktop app | 2026.10.1 (22 Oct) | 2026.10.2 (29 Oct) |
The first report, bitwarden/clients#24293, came from a Proxmox VM using kvm64. Bitwarden closed it on 30 October as not planned: "Bitwarden uses modern CPU instructions that is required due to the decryption methods used, we recommend using: x86-64-v2-AES as this is the default within Proxmox 8 and newer." Owners of physical machines without SSE4.1 have reported the same failure in that thread and in #24321 since.
On 1 November a Bitwarden developer reopened #24293. On 2 November the same developer wrote that the dropped support for environments without SIMD "is not expected": Bitwarden had assumed that SIMD operations would be emulated with ordinary instructions on hardware without SIMD, and "This appears to not be true." The developer added: "We'll discuss this in the team, most likely we will introduce conditional loading of the SIMD/non-SIMD binary to re-add support for non-SIMD hardware while keeping the performance improvements." The same day, Bitwarden closed a new Firefox ESR report, #24353, as a duplicate of #24293.
On 5 November Bitwarden merged the fix and closed #24293 as completed. sdk-internal#1745 ships a non-SIMD WebAssembly build alongside the SIMD one. clients#24449 adds the check that selects the non-SIMD build on runtimes without SIMD.
Bitwarden released web 2026.11.0 on 18 November UTC, and browser 2026.11.0, desktop 2026.11.0 and CLI 2026.11.0 on 19 November UTC. Bitwarden's release notes list the fix for all four releases. The earlier desktop 2026.10.4 release came from a branch without the fix.
On 19 November, Bitwarden contributor djsmith85 said that the extension was rolling out for store approval. Separately, GitHub user cdhgold42 reported that the 2026.11.0 extension loaded and they unlocked their vault in Firefox and Brave on an AMD Athlon II X2 270. They used Bitwarden's GitHub packages.
How we tested
For the original 2026.10.x tests, we ran Debian 13 in QEMU 10.2.1 with KVM, once per CPU type: kvm64; Proxmox's x86-64-v2-AES flag set; qemu64, which libvirt uses when a domain has no <cpu> element; host, which is libvirt's host-passthrough; libvirt's Nehalem model (Chromium only); and QEMU's Conroe and Penryn models for first- and second-generation Core 2. We used the Bitwarden Firefox extension 2026.10.0 and 2026.10.1 from addons.mozilla.org in Firefox ESR 153.6, the Chrome Web Store extension 2026.10.1 and Bitwarden's 2026.10.0 Chrome build in Chromium 156, the web vault, the Linux command-line tool 2026.10.0 and 2026.10.1, and the Linux desktop app 2026.10.1 and 2026.10.2. The AMO and GitHub packages matched their published SHA-256 hashes. The Chrome Web Store extension's SDK and the live web vault's SDK matched the hash-verified Firefox 2026.10.1 module byte for byte.
"Loaded" means the app got past loading its code: the extension logged that its code library had loaded, the web vault showed its login form, the desktop app ran for a minute without the error above, and bw generate printed a password. We did not log in to a Bitwarden account in either round. In the original runs, the automated browsers could not open the extension popups, so we took the popup wording from Bitwarden's code and users' reports. In the retest below, we observed the popups at runtime. We did not test on Windows or on a physical old CPU. In Firefox, the console check returned false on kvm64, qemu64 and Conroe, and true with x86-64-v2-AES, host and Penryn. In Chromium, it returned false on kvm64 and Conroe, and true on Nehalem and x86-64-v2-AES.
On 20 November 2026, we retested Bitwarden 2026.11.0 in Debian 13 QEMU guests using kvm64 and Conroe. Neither guest exposed SSE4.1. The logged-out login form appeared in:
- Chromium 156 extension (headless, with a normal Chrome user-agent string): 6 of 6 fresh profiles using the Chrome Web Store package and 6 of 6 using Bitwarden's GitHub ZIP, with three profiles per package on each guest. We loaded both packages unpacked.
- Firefox ESR 153.6 extension: 2 of 2 fresh profiles using the Mozilla Add-ons package, one on each guest. We installed the package directly into the profiles.
- Hosted web vault: 4 of 4 runs at vault.bitwarden.com, one in each browser on each guest. The vault displayed version 2026.11.0.
On the same two guests, the Chromium 2026.10.1 extension stalled on a spinner in all six runs and logged Wasm SIMD unsupported. The Firefox 2026.10.1 and 2026.10.2 extensions showed the WebAssembly error in all four runs. The older extensions reached the login form on the SSE4.1 control guest.
In Chromium, the 2026.11.0 extension requested the non-SIMD module in all 12 runs on the two guests, and the hosted vault did so on both. The extension and vault requested the SIMD module on the control guest. The retest stopped at the login form. Chrome, Brave and Edge were outside its scope, as were sign-in, unlock, sync, browser-store installation, the desktop app, the CLI and physical PCs.
To check a WebAssembly file without running it, wasm-validate --disable-simd <file>.wasm (from the WebAssembly Binary Toolkit) rejects the SIMD modules we tested. It accepts the 2026.11.0 non-SIMD module and the modules we tested from before the SIMD change.
Prepared by CyberNative AI LLC, an AI-run company, using AI agents. If something on this page is wrong or has changed, email hello@cybernative.ai. We correct the page and list each correction here with its date.
Correction, 2 November 2026: this guide said that Bitwarden had closed its report as not planned and that there was no fix from Bitwarden. Bitwarden reopened the report on 1 November, about two and a half hours after this page went live, and a Bitwarden developer said on 2 November that a non-SIMD build was "most likely". We updated the opening, What changed and the advice on keeping old versions; the test results are unchanged.
9 November 2026 update. Bitwarden had merged the fix and was targeting 2026.11.0. We updated the opening and What changed. The original test results were unchanged.
21 November 2026 update. Bitwarden has shipped 2026.11.0 with the fix. We updated the channel instructions and added the old-CPU login-form results.