Malwarebytes has released a patch for a known issue breaking Google Chrome on customer systems after installing Windows 11 Cumulative Update 22H2 KB5027231 released last week.

On Wednesday, the company confirmed user reports that the Google Chrome user interface would no longer appear after rolling out this month’s Patch Tuesday cumulative updates.

The conflict with Google Chrome is cause by Malwarebytes anti-exploit module prevents web browser from loading or crashing after installing KB5027231 update.

Customers affected by this known issue have been advised to disable Chrome’s entry from the list of protected apps in their Malwarebytes product as a temporary workaround.

Malwarebytes has now resolved the conflict with the Chrome web browser on up-to-date Windows 11 systems.

“This patch enables Chrome as a protected app for all Windows 11 devices, but does not apply our anti-exploit code to all Chrome processes,” the company says.

“Update to Component Version: 1.0.2047 and Malwarebytes Version: 4.5.31.270 to receive this fix. This update is automatic over time. To update manually, open Malwarebytes, click Settings > About > Check for updates.”

Malwarebytes says the update will automatically be applied to new installations and advises customers who have used the workaround to re-enable Exploit Protection for Chrome after installing the patch.

To re-enable Chrome as a protected application in your Malwarebytes product, you must:

1. Open Malwarebytes.
2. At the top right, click the Settings wheel.
3. Click it Security tongue.
4. Below Exploit ProtectionClick on Manage protected apps.
5. Enable Google Chrome (and plugins).
6. Click on Do.

As BleepingComputer reported last week, the same Windows 11 update would also break Google Chrome on systems protected by Cisco and WatchGuard EDR and antivirus solutions.

Based on user reports and as WatchGuard staff confirmedWeb browser would not open if Cisco Secure Endpoint and WatchGuard Exploit Prevention Engines were enabled after installing KB5027231.

“We’re rolling out Secure Endpoint 8.1.7 to our few thousand devices, and we started getting a mountain of reports this morning that Google Chrome wouldn’t appear on the screen after trying to open it,” said declared a Windows administrator. said.

“With some trial and error, I found that removing the Secure Endpoint service or uninstalling Secure Endpoint will cause Chrome to open again.”

Although a fix has yet to be released by Cisco and WatchGuard, affected customers are advised to disable exploit protection or set Chrome as the default web browser in Settings > Select Default Browser to re-enable it. web browser on affected Windows 11 systems.

Spokespersons for Microsoft and Cisco have yet to respond to requests for further details regarding this issue.