Few things mess up a digital workflow faster than your favorite browser just refusing to open or crashing out of nowhere, especially after a big Windows update like KB5037591. For some reason, this update seems to trigger issues specifically with Chrome — it either closes instantly, shows a blank window, or just crashes before it even fully loads. Weird, right? Maybe other browsers like Edge stay okay, but Chrome’s stability gets messed up. Because of course, Windows has to make it more complicated than necessary. Anyway, this guide’s got some practical (and sometimes unpolished) tips to figure out what’s going on and hopefully get Chrome back on track without too much head-scratching. These methods are a mix of system tweaks, config adjustments, and a few tricks learned from biting the bullet on similar issues before.
How to Fix Chrome Crashing After Windows 11 KB5037591 Update
Test with a New User Profile — Is it Systemwide or Profile-Specific?
This is a classic, yet often overlooked. Bad user data or a corrupted profile can make all apps act weird. Creating a fresh Windows account temporarily can tell if the issue is tied to your current user settings or system-wide.
Why it helps: If Chrome works fine in a new profile, you know the problem’s probably localized, saving hours of troubleshooting. If not, it’s systemic, and you need to look elsewhere.
When it applies: Often after a Windows update, when Chrome suddenly crashes or shows blank screens on your main profile, but not in a fresh one.
What to expect: Chrome should launch normally in the new profile if the problem is user-data related. If it’s still crashing, the conflict might be deeper, like system-level security or conflicts.
Action plan:
- Open an elevated terminal: Right-click the Start menu or press Windows key + X, then select Terminal (Admin) or Command Prompt (Admin).
- Create a new admin account: Run this command:
net user newuser newpassword /addthen this to add it to admins:net localgroup administrators newuser /addReplacenewuserandnewpasswordwith something secure. - Log in to the new profile: Restart, then pick the newuser login. Sign in and launch Chrome.
- Test Chrome: Download Chrome fresh from [Google’s official site](https://www.google.com/chrome/).If it works here, problem is with your old profile’s data or config files. If it crashes again, the root cause is probably system-wide or update-related.
Run Chrome with a Special Launch Flag — Is It Security or Sandbox Conflict?
Another thing that’s kinda weird, but disabling some security features temporarily can tell you if they’re blocking Chrome. Sometimes, Windows updates tighten security in a way that conflicts with Chrome’s sandbox or other functions.
Why it helps: By launching Chrome with -no-sandbox, you bypass some restrictions, possibly sidestepping whatever’s causing the crash.
When it applies: Chrome crashes immediately after launch, especially after a recent update that could’ve changed security policies.
What to expect: If Chrome launches and stays open, then the sandbox might be the kicker. But remember, this is only a debugging trick — don’t keep -no-sandbox enabled long-term because it’s a security risk.
Action plan:
- Find your Chrome shortcut on desktop or in the Start menu.
- Right-click, choose Properties.
- In the Target field, add
-no-sandboxafter the existing path, making sure to leave a space. It should look like:"C:\Program Files\Google\Chrome\Application\chrome.exe" -no-sandbox - Click Apply and OK. Launch Chrome directly from this shortcut.
- If it opens—great! Test browsing or extensions to see if stability is improved. But don’t forget to remove this flag after you’re done troubleshooting to keep your browser safe.
Adjust Exploit Protection Settings — Sometimes Windows’s Security Gets a Little Overzealous
Windows Security has some built-in exploit protection settings, aimed at blocking malware, but they can interfere with apps like Chrome, especially after updates. Tweaking them can clarify if security configs are causing the crashes.
Why it helps: Overly aggressive security flags can make Chrome’s behavior look suspicious, leading to conflicts or crashes. Relaxing those settings temporarily can confirm if security is the culprit.
When it applies: Chrome closes or crashes after update, and other steps haven’t helped.
What to expect: If Chrome runs smoothly with adjusted settings, then it’s likely a security conflict. At this point, revert settings back afterward.
Action plan:
- Open Windows Security from the Start menu.
- Go to App & browser control > Exploit protection settings.
- Switch to the Program settings tab and click Add program to customize.
- Select Add by program name and type
chrome.exe. Click Add. - Find Hardware-enforced stack protection in the list, click Edit, then choose Override system settings. Set it to On and change to Audit only. This logs conflicts without blocking Chrome.
- Optional: Disable Real-time protection temporarily in Windows Defender or your third-party antivirus. Remember to turn it back on afterward.
Reinstall Chrome Completely — Sometimes a Clean Start Is Needed
If the above tricks aren’t enough, maybe your Chrome installation or user data got corrupted or was only partially removed before. Doing a thorough uninstall and fresh install can wipe out those lingering issues.
Why it helps: Files or configs left over from previous installations can cause crashes, even after uninstalling. Cleaning out everything before a reinstall can fix persistent problems.
When it applies: Chrome crashes repeatedly, or you get blank screens even after trying other fixes.
What to expect: A clean reinstallation typically resets everything to a default, stable state, fixing corruption or bad files.
Action plan:
- Press Windows key + I to open Settings, then go to Apps > Installed apps.
- Find “Google Chrome, ” click Uninstall. Follow the prompts, and when asked, check the box to delete browsing data to remove all profiles and cached info.
- Reboot your machine to clear any remaining temp files.
- Download the latest installer from [Google Chrome](https://www.google.com/chrome/).Run the setup and let it create a fresh, clean profile.
Speed Things Up: Disable Hardware Acceleration & Extensions
Once Chrome finally launches, internal settings like hardware acceleration or bad extensions can cause quick crashes or instability.
Why it helps: Turning off hardware acceleration shifts rendering to CPU instead of GPU, which can sidestep driver conflicts. Disabling extensions can identify if a plugin’s causing the issues.
When it applies: Chrome runs briefly before crashing, or you notice instability with certain features enabled.
What to expect: Chrome becomes more stable, and re-enabling extensions one-by-one helps isolate problem ones.
Action plan:
- Open Chrome, go to the three-dot menu > Settings > System.
- Turn off Use graphics acceleration when available. Restart Chrome to see if this stabilizes things.
- Navigate to More tools > Extensions. Disable all extensions, then restart. Enable them one-by-one later to find the culprit if crashes return.
Check for Windows Updates — Sometimes Fixes Come From Redmond
Microsoft keeps rolling out patches that fix bugs and improve compatibility, especially after big updates. Keeping Windows fully updated might resolve the problem without all the fuss.
Why it helps: After KB5037591, Windows might be missing follow-up patches that iron out bugs, including compatibility patches for Chrome.
When it applies: You’ve tried everything else, and Chrome still crashes.
What to expect: After updating, Chrome may work better or even flawlessly. Restart after installing updates to ensure everything applies correctly.
Action plan:
- Press Windows key + I, go to Windows Update.
- Click Check for updates. Install all pending updates, especially cumulative updates and the. NET Framework patches.
- Reboot and test Chrome again.
Scan for Malware & Review Antivirus Settings
Silly as it sounds, malware or overly cautious antivirus settings can cause weird crashes, too. Do a full scan with Windows Defender or your preferred scanner, and make sure Chrome isn’t accidentally blocked or quarantined.
Why it helps: Some malicious or even legit files can interfere with browser processes, or your AV might be blocking Chrome’s execution without obvious notice.
When it applies: All else has failed, and you doubt the core system or Chrome itself. Also good to do after suspicious activity or if you suspect malware.
What to expect: Fixing potential conflicts, and you might discover malware lurking in the background.
Wrap-up
Dealing with Chrome crashing after a Windows 11 update can be a pain, but methodically working through profile repair, security tweaks, reinstallation, and wait-it-out updates usually does the trick. Sometimes, it’s just a matter of clearing out corrupted data or tweaking the security settings a bit. Of course, patience is key—just like any troubleshooting, it’s process of elimination. Good thing is, most of these fixes are quick to try, and often enough, they’ll get Chrome back to its smooth, reliable self.
Summary
- Try a new Windows user profile to see if the issue is localized
- Launch Chrome with
-no-sandboxtemporarily to test sandbox conflicts - Adjust Exploit Protection settings for Chrome in Windows Security
- Perform a complete reinstall of Chrome, wiping all old data
- Disable hardware acceleration and extensions inside Chrome for stability
- Keep Windows up to date, especially following major updates
- Scan for malware and review antivirus/exploit protection rules