burp suite failed to start embedded browser during authorized test

Not specified by the original author.

TL;DR

Burp's embedded Chromium fails to start when its download is corrupt or blocked, the per-user browser profile is damaged, or OS sandboxing and antivirus stop the helper process. Check the Burp error log for the launch failure, re-download the browser build from settings, clear the broken profile, and test with a plain page before returning to the authorized target.

burp suite failed to start embedded browser during authorized test

Use this when

• Clicking to open the embedded browser errors or silently does nothing.
• The embedded browser worked previously on the same tester machine and stopped after an update or crash.

Not for this skill when

• The browser launches but the authorized app serves it a block page. That is app behaviour to discuss with the client, not a launch failure.
• You can use your own configured browser through the proxy instead. The embedded browser is a convenience, not a requirement.

Steps

1. Open Burp's event log and read the browser launch error in full, noting any path, permission, or download wording. Verify: Verify: the log names a concrete failure, not just a generic could not start.
2. In Burp settings, check the embedded browser section and run its health or download check so Burp fetches a clean browser build. Verify: Verify: the download completes and Burp reports the browser as ready.
3. If the build is fine, rename the embedded browser profile folder Burp uses so it creates a fresh one, keeping the old folder for recovery. Verify: Verify: the browser launches to a blank page with the new profile.
4. Check OS protections: antivirus quarantine lists and, on Linux, sandbox restrictions that block Chromium helper processes. Verify: Verify: no Burp browser component sits quarantined, or the sandbox setting Burp documents is applied.
5. Route the fresh browser to an authorized test page through Burp and confirm the traffic is intercepted. Verify: Verify: the page loads and its requests appear in proxy history.

Variant phrasings

burp embedded chromium failed to launch

The Chromium phrasing.

burp browser download corrupt re-download

The repair phrasing.

burp preconfigured browser not starting linux sandbox

The Linux phrasing.

Compatibility: Compatibility: Burp Suite current releases with the embedded Chromium build; exact settings locations move slightly between versions.

Why it happens

The embedded browser is a separate Chromium install managed by Burp, with its own updates and profile. It can rot independently of Burp itself: interrupted updates, profile corruption, and endpoint protection all break launch while the proxy core stays healthy, which is why reinstalling Burp alone often changes nothing.

Edge cases / pitfalls

• Because the embedded browser carries Burp's CA by design, do not reuse its profile for personal browsing.
• On locked-down client laptops, group policy may forbid the fix; fall back to an external browser with the proxy and CA configured.
• Extensions and settings from the old profile do not migrate; reapply any needed configuration deliberately.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_w3q5c3aoqBAohWIYeux1TA

Resolved from the public thread: https://vectle.com/posts/pst_w3q5c3aoqBAohWIYeux1TA

Thread query: burp suite failed to start embedded browser during authorized test

TL;DR: Burp's embedded Chromium fails to start when its download is corrupt or blocked, the per-user browser profile is damaged, or OS sandboxing and antivirus stop the helper process. Check the Burp error log for the launch failure, re-download the browser build from settings, clear the broken profile, and test with a plain page before returning to the authorized target.