Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: openclaw doctor reports "Could not determine the installed Chrome version" despite Chrome 148 installed at expected path [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Running openclaw doctor shows the following warning in the Browser section: | - Chrome MCP existing-session is configured for profile(s): user. | | - Chrome path: C:\Program Files\Google\Chrome\Application\chrome.exe | | - Could not determine the installed Chrome version. Chrome MCP requires Google | | Chrome 144+ on this host. | However, Chrome IS installed at the expected path and the version is well above the minimum requirement (Chrome 148.0.7778.179). The installed binary contains the correct ProductVersion in its metadata. This appears to be a false positive — the doctor check is failing to read the version from the installed binary.

Root Cause

Likely root cause: the version detection code in doctor reads from the Windows registry or uses a different API than the actual browser connection code, and fails when registry entries are incomplete/redirected

Fix Action

Fixed

Code Example

Chrome Version: 148.0.7778.179
Browser Location: C:\Program Files\Google\Chrome\Application\chrome.exe
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Running openclaw doctor shows the following warning in the Browser section: | - Chrome MCP existing-session is configured for profile(s): user. | | - Chrome path: C:\Program Files\Google\Chrome\Application\chrome.exe | | - Could not determine the installed Chrome version. Chrome MCP requires Google | | Chrome 144+ on this host. | However, Chrome IS installed at the expected path and the version is well above the minimum requirement (Chrome 148.0.7778.179). The installed binary contains the correct ProductVersion in its metadata. This appears to be a false positive — the doctor check is failing to read the version from the installed binary.

Steps to reproduce

Steps to reproduce the behavior: Install Chrome 148.x at C:\Program Files\Google\Chrome\Application\chrome.exe (standard location) Run openclaw doctor See the "Could not determine the installed Chrome version" warning However, the browser tool actually works correctly — it connects and runs fine. So the doctor check is the only thing broken.

Expected behavior

openclaw doctor should correctly detect Chrome 144+ and show no warning.

Actual behavior

The Chrome binary has the correct ProductVersion in its file metadata (Get-Item ... | VersionInfo.ProductVersion returns 148.0.7778.179)

The actual browser tool works fine — this is purely a doctor check issue

Likely root cause: the version detection code in doctor reads from the Windows registry or uses a different API than the actual browser connection code, and fails when registry entries are incomplete/redirected

OpenClaw version

2026.5.26 (10ad3aa)

Operating system

Windows 11

Install method

No response

Model

qianfan/deepseek-v4-flash

Provider / routing chain

openclaw qianfan/deepseek-v4-flash

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Chrome Version: 148.0.7778.179
Browser Location: C:\Program Files\Google\Chrome\Application\chrome.exe

Impact and severity

No response

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

openclaw doctor should correctly detect Chrome 144+ and show no warning.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: openclaw doctor reports "Could not determine the installed Chrome version" despite Chrome 148 installed at expected path [1 pull requests]