Exclusive Content:

Google Wallet can now display flight tickets on smartwatches.

The Google Wallet app for Wear OS now allows...

Elon Musk conquers the toughest obstacle in Diablo 4 by playing alone.

Elon Musk, a billionaire known for his love of...

iPhone possesses a hidden feature designed to assist with laundry.

Technological progress in mobile devices is remarkable, with smartphones...

Update KB5034129 on Windows Server 2022 causes Chrome, Edge, and Firefox to crash.

The KB5034129 Windows Server 2022 update is leading to browser crashes such as Chrome, Edge, and Firefox due to file corruption issues, causing significant problems for Windows Server 2022 PC administrators. Opening the browser results in just a blank window, as reported.

Update KB5034129 causing crashes in Chrome, Edge, and Firefox browsers

Após a instalação da atualização KB5034129 do Windows Server 2022, navegadores Chrome, Edge e Firefox travam. Fonte: Oficina da Net
Imagem: karvanth/FreePik

The KB5034129 update for Windows Server 2022, released on January 9, 2024, addressed various issues such as bugs impacting InTune, hybrid devices, Microsoft Excel, and Wi-Fi adapters. This update was crucial for many companies seeking to resolve these issues promptly.

After installing the most recent Windows Server 2022 update (KB5034129), some users experienced issues where browsers like Google Chrome, Microsoft Edge, and Mozilla Firefox would only display blank pages. One administrator noted that Edge was utilizing about 50% of CPU processing power with 12 Microsoft browser-related processes, which also led to disk space being filled up.

When attempting to launch Chrome, a blank screen appears and an error related to GPU loading occurs. Despite attempts to troubleshoot using VMWare Tools or reinstalling Chrome, the issue persisted until the update was uninstalled.

Captura de tela mostrando o bug da tela branca no navegador Google Chrome após a atualização KB5034129 do Windows Server 2022. Fonte: WindowsLatest
Imagem: MaxWdhs/FreePik

Possible solutions to address the issue

Mayank Parmar, of WindowsLatest, fixes the issue by deleting the registry key “chrome.exe” at the location “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options.”

An alternative method to resolve the bug involves using PowerShell to execute a command that deletes the file.

One way to fix the issue is by changing the file name “chrome.exe” to something different, such as “chrome_test”. This will allow Chrome to function properly once more.

LINK:  Google's search results are deteriorating.

Newsletter

iPhone possesses a hidden feature designed to assist with laundry.

Technological progress in mobile devices is remarkable, with smartphones now capable of performing tasks that were unimaginable a decade ago. Some functions and features...

Ben Affleck and Matt Damon team up for a Netflix original movie called Animals: Get all the details

Ben Affleck and Matt Damon, a prominent creative pair in Hollywood for the last 25 years, have worked together on various projects. Their latest...

Toyota is the top-selling car manufacturer globally, with 11 million vehicles sold, followed by Volkswagen in second place.

The automotive market is constantly evolving, with a growing interest in electric vehicles. Despite the popularity of brands like Tesla and BYD, Toyota remains...

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Frame Quantum
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.