diff --git a/releases-manifest.json b/releases-manifest.json
index a8c0c00..c38fbda 100644
--- a/releases-manifest.json
+++ b/releases-manifest.json
@@ -22,14 +22,14 @@
     {
       "id": "ariadne-resolver",
       "product": "Ariadne Resolver (Windows)",
-      "version": "0.1.9",
-      "date": "2026-09-28",
+      "version": "0.1.10",
+      "date": "2026-09-29",
       "platform": "win-x64",
       "signed": false,
       "signingAuthority": null,
-      "changes": "Bare BNS names in the address bar now work in Chrome and Edge. The daemon exposes a local search shim at http://127.0.0.1/search?q=%s -- point your browser's default search engine at it. Typing `ariadne.x` (no scheme), which Chromium would otherwise treat as a search query because `.x` isn't in ICANN's known-TLD list, is 301'd to https://ariadne.x/; anything with whitespace, or a TLD the local CA isn't constrained to, is 302'd to your fallback (DuckDuckGo by default; set `searchFallback` in ariadne.config.json to any `https://engine.tld/?q=` URL to change it). Paths are preserved -- `ariadne.x/foo` goes to `https://ariadne.x/foo`. Works offline: no network hop through navigate.st, everything decided locally against the CA's permitted-TLD set. Includes 0.1.8 (pinned-origin proxy for `ip`+`tls` names) and 0.1.7 (runtime-switchable collision policy). Upgrades in place.",
+      "changes": "Works on networks that block electrum WSS. Before 0.1.10 the daemon's initial index build was `await buildIndex()` over electrum WSS (port 50004); on corporate networks or restrictive ISPs that filter WSS, the await never returned, `dns.bind()` never ran, and every browser on the machine sat waiting -- symptom: task is Running, port 53 is bound, but every query hangs. 0.1.10 warm-starts the index from HTTPS snapshots in parallel (`dl.silentmode.st/bns-name-index.json` on the operator VPS + `s3.silentmode.st:8600/bns/name-list.json` on Sia, first-wins with an 8 s deadline), falls back to an on-disk cache at `C:\\ProgramData\\Ariadne\\bns-name-snapshot.json` from the last successful fetch, then lets electrum WSS keep it current in the background -- WSS updates win when they arrive because they're strictly newer, so no freshness regression when the network is fine. dns.bind runs the moment warm-start completes. Same snapshot format Android's Ariadne consumes, one artifact for the whole ecosystem. Configurable via `snapshotUrls` in ariadne.config.json. Includes 0.1.9 (local search shim), 0.1.8 (pinned-origin proxy), 0.1.7 (runtime-switchable policy). Upgrades in place.",
       "files": {
-        "AriadneResolver-Setup-0.1.9.exe": "3b973e0ae584113ad776c756b16b895fd0dfb217a02bfae6376c5abb48f9a77c"
+        "AriadneResolver-Setup-0.1.10.exe": "29710c4011dfe058a252f94af221c02593e728e89cc7427e3e01eaa530f8e526"
       }
     },
     {
diff --git a/releases/index.html b/releases/index.html
index 5e56add..067c35b 100644
--- a/releases/index.html
+++ b/releases/index.html
@@ -72,12 +72,12 @@
   </div>
 
   <div class="rel">
-    <h2>Ariadne Resolver — Windows <span style="color:var(--acid)">0.1.9</span></h2>
-    <div class="meta">Windows 64-bit · unsigned · bundled Node runtime · 2026-09-28 · <b>0.1.9 — bare BNS names in the address bar</b> — Typing <code style="display:inline">ariadne.x</code> (no scheme) into Chrome or Edge would previously send you to a search engine, because <code style="display:inline">.x</code> isn't on ICANN's known-TLD list and Chromium's omnibox falls back to search on unknown TLDs. 0.1.9 adds a local search shim at <code style="display:inline">http://127.0.0.1/search?q=%s</code>. Point your browser's default search engine at it: BNS-shaped queries (<code style="display:inline">&lt;label&gt;.&lt;permitted-tld&gt;</code>) get 301'd to <code style="display:inline">https://…/</code>; anything with whitespace, or a TLD outside the CA's constrained set, gets 302'd to your fallback (DuckDuckGo by default; change with <code style="display:inline">searchFallback</code> in <code style="display:inline">ariadne.config.json</code>). Paths preserved. Zero network hop through navigate.st — everything decided locally. Includes 0.1.8 (pinned-origin proxy for <code style="display:inline">ip</code>+<code style="display:inline">tls</code> names). Upgrades in place.</div>
+    <h2>Ariadne Resolver — Windows <span style="color:var(--acid)">0.1.10</span></h2>
+    <div class="meta">Windows 64-bit · unsigned · bundled Node runtime · 2026-09-29 · <b>0.1.10 — snapshot warm-start (works on networks that block electrum WSS)</b> — Before 0.1.10 the daemon's initial index build ran over electrum WSS (port 50004); on corporate networks or restrictive ISPs that filter WSS, the await never returned, <code style="display:inline">dns.bind</code> never ran, and every browser on the machine hung — task showed Running, port 53 was bound, but every query timed out. 0.1.10 warm-starts the index from HTTPS snapshots in parallel — <code style="display:inline">dl.silentmode.st/bns-name-index.json</code> on the operator VPS + <code style="display:inline">s3.silentmode.st:8600/bns/name-list.json</code> on Sia, first-wins with an 8-second deadline — falls back to a local cache at <code style="display:inline">C:\ProgramData\Ariadne\bns-name-snapshot.json</code> from the last successful fetch, then lets electrum WSS keep the index current in the background (WSS updates win because they're strictly newer). Same snapshot format Android's Ariadne consumes. Configurable via <code style="display:inline">snapshotUrls</code> in <code style="display:inline">ariadne.config.json</code>. Includes 0.1.9 (local search shim). Upgrades in place.</div>
 
     <div class="file">
-      <div class="n"><a href="https://dl.silentmode.st/AriadneResolver-Setup-0.1.9.exe">AriadneResolver-Setup-0.1.9.exe</a> — ~24 MB</div>
-      <code>3b973e0ae584113ad776c756b16b895fd0dfb217a02bfae6376c5abb48f9a77c</code>
+      <div class="n"><a href="https://dl.silentmode.st/AriadneResolver-Setup-0.1.10.exe">AriadneResolver-Setup-0.1.10.exe</a> — ~24 MB</div>
+      <code>29710c4011dfe058a252f94af221c02593e728e89cc7427e3e01eaa530f8e526</code>
     </div>
   </div>