How to identify an obsolete embedded browser

A sign-in page, help center, or dashboard works in your regular browser but breaks inside an app. The app may use an embedded browser, a small browser window built into the app, and its engine may be older than the browser you use every day.

You can check the engine and version from inside that app, then compare the result with the same check in a current standalone browser. This helps you find out whether the embedded browser is likely the problem, without assuming every unfamiliar version is obsolete.

Check the embedded browser

1. Open the Browser Info tool inside the app where the problem happens. If the app lets you enter a web address, open toolab.io/tools/browser-info there. Make sure the page stays inside the app rather than opening your regular browser.
2. Note the browser version and engine that Browser Info reports. It also checks supported features, which can help when the page depends on newer browser capabilities.
3. Return to the page that is failing and note what does not work, such as a blank panel, a login button that does nothing, or a message that the browser is unsupported.
4. Open Browser Info in your usual, updated browser on the same device. Compare the engine, version, and supported features with the result from inside the app.

If the app will not open an address you enter, look for a help, support, or sign-in page within it that uses the same embedded window. You can also ask the app maker which browser component the app uses. A check in your regular browser alone does not identify the browser inside the app.

What the result means

The embedded view reports Internet Explorer or Trident

Trident is the engine used by Internet Explorer. It is obsolete for modern websites, and many sites no longer support it. If an app still relies on Trident, update the app or use its option to open the page in a current browser. Updating Microsoft Edge alone will not necessarily replace an old browser component built into an app.

The engine is much older than the standalone browser

This is a useful warning, not proof by itself. An app can use a separately updated component, or bundle its own browser engine. Check the app maker's release notes or support information to see whether that engine version is still supported. If the failing page works in the current browser but not in the app, the app's embedded browser or its settings are likely involved.

The engine versions are close, but the page still fails

The issue may be a restriction in the app's embedded view, rather than an obsolete engine. Some apps block pop-ups, third-party sign-ins, downloads, or features that a website expects. The app may also use a different account session or network connection. Try the same task in the standalone browser to confirm whether the problem is limited to the app.

Browser Info cannot identify the app or gives an unexpected result

Some apps change or limit the information their embedded browser reports. Browser Info can show what the page's browser context exposes, but it cannot always name the host app or prove which component it uses. Check the app's version and release notes, or ask its developer what engine it uses and how that component is updated.

How to fix it

1. Close and reopen the app. This can clear a stuck embedded window or finish an update that has already been installed. Recheck the problem page before changing system settings.
2. Update the app itself. Use the app's built-in updater or the store you installed it from. Embedded browsers are often updated with the app, so updating your regular browser may not change what the app uses.
3. Check the WebView2 runtime on Windows. Many Windows apps use Microsoft's WebView2, based on the Edge browser engine. In Windows 11, open Settings › Apps › Installed apps and look for Microsoft Edge WebView2 Runtime. It may update automatically or through the app maker's installer. If it is missing or an update fails, use the app maker's instructions or contact its support team instead of downloading runtime files from an unknown source.
4. Install available macOS updates. Many Mac apps use Apple's WebKit engine through WKWebView, which is updated with macOS. Open System Settings › General › Software Update and install an available update. Some apps use a different, bundled engine, so update the app too.
5. Open the page in your regular browser. If the app offers an option to open a link externally, use it as a workaround. This is also a useful check: if the page works there, report the embedded-browser result and the app version to the app maker.
6. Ask your administrator before changing a work device. A company may manage the app or browser runtime centrally. Share the app name, app version, reported engine and version, and the page that fails. Do not remove a shared runtime or replace system files on a managed computer.

Why a version number can be misleading

There is no single version number that makes every embedded browser obsolete. Chromium-based components, WebKit, and app-specific browser shells use different version schemes. A number that looks low beside a current Chrome version may belong to a different engine, while a familiar browser name does not guarantee that the underlying engine is current.

Some embedded browsers also report a customized browser identity. Treat the engine, reported version, supported features, and the app maker's support information as evidence together. If the app maker no longer updates the embedded component and the page fails only inside that app, using a standalone browser may be the safest practical option.