{"id":4838,"date":"2020-10-13T01:37:12","date_gmt":"2020-10-13T01:37:12","guid":{"rendered":"https:\/\/pariswells.com\/blog\/?p=4838"},"modified":"2020-10-13T01:37:12","modified_gmt":"2020-10-13T01:37:12","slug":"chrome-exe-not-opening-windows-10-2004","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/random\/chrome-exe-not-opening-windows-10-2004","title":{"rendered":"Chrome.exe not opening – Windows 10 2004"},"content":{"rendered":"

 <\/p>

Windows 10 – Update 2004 – Issues with Chrome whereby you go and launch the application in windows and the browser does not open.\u00a0 What does happen though is you can see the process running in task mgr.\u00a0 This happens for previously deployed workstations and new machines which are run up.\u00a0 You can click several times on the chrome icon before it will open a window which is reflected by the number of chrome processes running.<\/p>

There are several articles out there which all talk about removing chrome, reg entries and the profile itself.\u00a0 None of those make a difference the symptoms still persist.\u00a0 I have almost narrowed it down to say that it has been caused by the cumulative updates applied to Win10 Build 2004.<\/p>

\u00a0<\/p>

One interesting thing I found which is off the back of an article is if you rename the exe to chrome1 it works flawlessly every time.\u00a0 Change it back to Chrome and the same symptoms persist<\/p>

Fix 1)<\/p>

Remove 09 Cumulative update (KB4571756) this also fixes the problem.<\/p>

After finding that I was able to come up with the following\u00a0https:\/\/support.google.com\/chrome\/thread\/70587649?hl=en<\/a><\/p>

Fix 2)<\/p>