{"version":"2.1.211","anchor":"windows-browser-resolution-for-claude-in-chrome-via-app-path","canonical_anchor":"windows-browser-resolution-for-claude-in-chrome-via-app-path","heading":"Windows Browser Resolution for Claude in Chrome via App Paths","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.211\/e\/windows-browser-resolution-for-claude-in-chrome-via-app-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.211","markdown":"### Windows Browser Resolution for Claude in Chrome via App Paths\n\n**What**\n\nOn Windows, Claude in Chrome now uses the Windows Registry `App Paths` mechanism (via `reg.exe`) to locate installed browser executables for Edge and Vivaldi, rather than only falling back to `rundll32`.\n\n**Details**\n\n- Queries both `HKCU` and `HKLM` registry hives under `SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\App Paths` for `msedge.exe` and `vivaldi.exe`.\n- Falls back to `rundll32 url,OpenURL` if registry resolution fails or the exe cannot be verified.\n- Expands `%VARIABLE%` environment-variable tokens in registry values.\n- Rejects results that point to a directory rather than an executable.\n- Uses a timeout to avoid blocking on slow or stale registry entries.\n\n**Evidence**\n\nWindows App Paths registry key (search for `\"SOFTWARE\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\App Paths\"`)"}