Apr 19, 2020
Chrome won't open in Windows 10
Informational notification.
This question is locked and replying has been disabled.
Community content may not be verified or up-to-date. Learn more.
Jun 3, 2020
Gold Product Expert mudwoman recommended this
Helpful?Upvote Downvote
Jul 9, 2020
To fix this issue I had to remove the User Profile From Chrome. To do this I:
1) Clicked Windows and R keys and pasted this in box: %USERPROFILE%\AppData\Local\Google\Chrome\User Data
2) Copied Default Folder to my desktop
3) Shut computer down and restarted
4) Then navigated to Chrome by typing "Chrome" in search bar bottom left. Right click on Chrome icon in top left and choose "Open file location"
5) This opened to the shortcut version of Chrome so I had to click in the navigation bar to bring me back to the Windows C: directory. From there I chose the folder Program Files x86 > Google > Chrome > Application >
6) In this folder was the real Google Chrome exe file. I right clicked on the Google program. Chose "Run as Administrator" and Google opened for me.
7) Delete Default Folder from Desktop.
8) Save these instructions on your machine, because this will happen again.
Gold Product Expert mudwoman recommended this
Helpful?Upvote Downvote
All Replies (120)
Apr 24, 2020
Apr 19, 2021
Apr 20, 2021
Apr 22, 2021
Apr 23, 2021
Apr 26, 2021
When I click the icon there's about a 40%-ish chance chrome will actually open. I can forcefill the process using command prompt and get spammed with errors saying "There is no running instance of the task".
This is increasingly annoying because it somehow also affects clicking links in certain applications. They will not open at all even though the "loading" icon is next to my cursor.
Apr 26, 2021
This 'process per site' switch fixes it and I have no idea why. Also - what is very strange - with over 50 Windows 10 PCs that I manage this problem only occurs on 2 of them. Weird.
Apr 26, 2021
Apr 28, 2021
Sam Smith, my 10 PCs all have Webroot installed and the problem occurs only on 4. Could you tell me exactly how you found the problem & what it was. The 4 that have the problem are number 3-6 in my naming scheme and I wonder if there was some changes to Webroot's configuration files after I created 1 & 2 then again from 5-10.
After trying several things I ended up changing the Public shortcut's compatibility properties to set "Disable fullscreen optimizations" and "Register this program for restart"
May 13, 2021
May 21, 2021
Jun 5, 2021
Last edited Jun 6, 2021
Jun 10, 2021