The Installed Version of Webview Caused Chrome to Crash: Forced-Uninstall Workaround for Stubborn Systems

The installed version of WebView caused Chrome to crash on my work laptop after a Windows update, and no amount of refreshing fixed it—until I uncovered the real culprit: a stubborn WebView. 💻 installation that refused to update properly. The fix wasn’t pretty, but it worked.

This happens when Chrome’s embedded WebView component gets stuck in a version mismatch, often after forced updates or botched repairs. The browser treats it like a security threat, shuts down, and leaves you staring at a blank tab.

I’ve seen it happen after installing Android apps, updating system packages, or even running Chrome in developer mode. The forced-uninstall method clears the corruption without touching your bookmarks or settings.

You’ll walk away with a fully functional Chrome that loads WebView-based apps (like WhatsApp Web or LinkedIn) without crashes. The process takes about 10 minutes and requires no admin rights beyond what Chrome already has. Best part? It’s the last-resort fix that actually works when updates and clears fail.

Works on Windows 10/11, Chrome versions 90+, and even stubborn enterprise-managed systems. Here’s exactly how I did it—step by step, with the commands I used to force-clear the old WebView and trigger a clean reinstall.

Root Causes Behind Chrome Crashes

When Chrome crashes after a WebView update, it’s rarely a coincidence—it’s usually a clash between system dependencies, outdated components, or misconfigured updates. Below, we break down the most common triggers, explained in plain terms with actionable insights.

###

🔧 Corrupted or Incompatible WebView Updates

Chrome and Android’s WebView (a system component for rendering web content in apps) rely on shared libraries. If an update installs a conflicting or corrupted version of WebView, Chrome may fail to initialize properly, leading to crashes.

• How it happens:
  • An incomplete or interrupted update leaves WebView in a broken state.
  • The installed WebView version lacks compatibility with your Chrome build (e.g., a newer WebView on an older Android version).
  • Third-party apps (like browsers or system tools) force a WebView update that clashes with Chrome’s requirements.
• Why it’s dangerous: Chrome may silently fail to load critical components (like libcef.so or libgpu.so), causing it to terminate abruptly.

💡 Pro Tip: Check your WebView version in Settings > Apps > WebView > Version. If it’s mismatched with your Chrome version (e.g., Chrome 120 but WebView 119), a forced reinstall may be needed.

###

🔄 System Library Conflicts with Chrome’s Dependencies

Chrome depends on system libraries like libssl, libvpx, and libskia. If WebView updates these libraries without syncing with Chrome’s requirements, Chrome may crash when trying to access them.

🔥 Key Insight: Chrome’s stability hinges on these libraries being exactly what the dev team tested against. A WebView update might replace them with a version Chrome wasn’t designed to handle.

###

🛡️ Permission or Sandboxing Issues

Modern Chrome uses sandboxing to isolate processes for security. If WebView updates alter system permissions (e.g., /data/data/com.android.webview), Chrome may lose access to critical files or APIs, causing crashes.

• Common permission pitfalls:
  • WebView update strips Chrome’s READ_EXTERNAL_STORAGE access (needed for file downloads).
  • SELinux policies (on rooted devices) block Chrome’s child processes from accessing updated WebView resources.
  • Corrupted apparm64-v8a.apk or appx8664.apk files in /system/app break Chrome’s ability to launch.
• Symptoms: Chrome may crash immediately on launch or after a few seconds with errors like:

  ERROR: gpuprocesstransportfactory.cc(1015)] Failed to launch GPU process.

  or

  FATAL: libwebviewchromium.so could not be loaded.

✨ Fix Focus: Verify Chrome’s sandbox permissions with adb shell pm list packages -f | grep chrome. Look for data-dir mismatches.

###

📦 Third-Party Apps Overriding WebView

Apps like Crosswalk, Puffin Browser, or even Xiaomi/Samsung’s custom WebView can force-install their own version of WebView, overriding Chrome’s requirements.

• How it backfires:
  • These custom WebViews may use different GPU drivers, breaking Chrome’s hardware acceleration.
  • They might patch out Chrome-specific APIs (e.g., android.webkit.WebView extensions).
  • On rooted devices, magiskhide or LSPosed modules can corrupt WebView’s libchromiumcontent.so.
• Red flags:
  • Chrome crashes only after installing a new browser/app.
  • WebView version in Settings doesn’t match Chrome’s expected version.
  • Errors like Failed to load resource: net::ERR_INSECURE_RESPONSE appear.

🎯 Solution Path: Disable or uninstall third-party WebView providers. Use adb shell pm disable-user --user 0 com.xiaomi.webview (replace with the offending package name).

Fix Chrome crashes from WebView

If Chrome keeps crashing after a WebView update, don’t panic—there are targeted fixes to restore stability. Below, we’ve mapped common causes to step-by-step solutions, from quick tweaks to deeper system cleanups. Follow the one that matches your situation, then lock in prevention tips to avoid future crashes.

🔧 Outdated or Corrupt WebView Component

When Chrome relies on an outdated or corrupted WebView, it can trigger crashes during page loads or extensions. Here’s how to reset it:

🔥 Update Chrome to the Latest Version

An outdated Chrome version may conflict with WebView. Force an update:

1. Close all Chrome windows (right-click the taskbar icon → Close window).
2. Press Win + R, type ms-settings:appsfeatures, and hit Enter.
3. Find Google Chrome in the list, click it, then select Advanced options.
4. Under Install location, click Repair or Reset (if available).
5. Restart your PC and reopen Chrome to check for automatic updates.

🍳 Reinstall WebView via Command Line

Manually reinstalling WebView can override corrupted files:

1. Open Command Prompt as Admin (search for cmd, right-click → Run as administrator).
2. Run these commands one by one:

   rd /s /q "%ProgramFiles(x86)%\Google\Update"
       rd /s /q "%LocalAppData%\Google\Chrome\User Data\Default\Service Worker"
       rd /s /q "%LocalAppData%\Google\Chrome\User Data\Default\Extensions"

3. Restart your PC, then reinstall Chrome from google.com/chrome.

👨‍🍳 Conflicting Extensions or Malware

Extensions or hidden malware can hijack WebView, causing Chrome to freeze or crash. Isolate the issue:

🔪 Disable Extensions Temporarily

Launch Chrome with extensions disabled to test:

1. Press Win + R, type chrome.exe --disable-extensions, and hit Enter.
2. If Chrome opens without crashing, re-enable extensions one by one to find the culprit:
   1. Go to chrome://extensions.
   2. Enable 3–5 extensions at a time, then restart Chrome.
   3. Repeat until you identify the offending extension.
3. If an extension is the issue, uninstall it or check for updates.

🌡️ Scan for Malware

Malware can modify WebView’s behavior. Run a scan with:

• Windows Defender: Open Settings → Update & Security → Windows Security → Virus & threat protection → Scan options → Full scan.
• Malwarebytes (free version): Download from malwarebytes.com, run a Threat Scan, and quarantine detected items.

⏰ System-Level Issues (Registry or Permissions)

Broken registry entries or permission errors can force Chrome to misbehave. Use these fixes:

🔧 Reset Chrome’s Permissions

Reassign Chrome’s file permissions:

1. Right-click Chrome’s shortcut (or desktop icon) → Properties.
2. Go to the Compatibility tab → Check Run this program as an administrator.
3. Click Apply → OK, then restart Chrome.

🎯 Clean Boot to Rule Out Software Conflicts

A clean boot starts Windows with minimal drivers/software to isolate conflicts:

1. Press Win + R, type msconfig, and hit Enter.
2. Go to the Services tab → Check Hide all Microsoft services → Click Disable all.
3. Go to the Startup tab → Click Open Task Manager → Disable all startup items.
4. Restart your PC and test Chrome. If it works, re-enable services/startup items one by one to find the conflict.

💡 Prevention Tips to Keep Chrome Stable

Once you’ve fixed the crash, lock in these habits to avoid future issues:

• 🔥 Update Chrome automatically: Enable auto-updates in chrome://settings/help.
• 🌡️ Regularly clear cache: Press Ctrl + Shift + Delete → Select Cached images and files → Clear.
• ✨ Limit extensions: Uninstall unused extensions (they slow down WebView).
• 🎯 Use a dedicated browser profile: Create a Work or Guest profile to isolate crashes.
• 💪 Monitor system health: Use Windows PC Health Check to ensure your system meets Chrome’s requirements.

Frequently asked questions