Now checked version of Chrome with the problem: 62.0.3202.94.
Update: Installed Canary (64.0.3273.3) and that works! :-)

donwiid1@ - Could you please let us know if the issue can be closed as per comment#1.

Thanks...!!

To be clear:

Canary (build 64.0.3273.3) works.
Chrome (build 62.0.3202.94) does *NOT* work.

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

@Reporter: Could you try un-installing current chrome build from control panel , download latest stable from https://www.chromium.org/getting-involved/dev-channel and install it. Launch chrome from command prompt and let us know if you see any error in command prompt. This would help in further triaging of the issue.

Thanks!

I'm experiencing the same issue. The chrome window is black with only a white bar at the top. The application seems to think it has loaded correctly as when I move my cursor around on the screen it registers the tab name and the url of hyperlinks (which I cannot see). I tried loading Canary and it does not work for me. (It broke yesterday when I did the latest Windows10 updates.)

Steve

I am unable to uninstall. When I try to do this, I get past UAC. Then a Chrome window pops up on the taskbar, but I cannot maximise it. The thumbnail is all black - presumably this is a chrome browser window trying to find out why I am uninstalling, and waits for a confirmation. And since I cannot see (the black) window, I cannot wave my mouse around to try and click on a link that is hidden. See attached screenshot.

Deleted: chrome uninstall.jpg 19.2 KB

	chrome uninstall.jpg 19.2 KB View Download

Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I found that the problem was a display driver. Apparently, the updated windows broke the display driver. Once that was updated, it worked just fine. The clue was that Chrome obviously had loaded correctly because the mouse pointer would still register active urls in the window even though I could not see them.

I ran the creators update recently 1709 and that broke chrome
Version 63.0.3239.132 (Official Build) (64-bit)
basically a white screen all over with a recurring error in the event log

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user XXXXXXXXX\XXXXXXX SID (S-1-5-21-1958334163-2673800866-3711758769-1001) from address LocalHost (Using LRPC) running in the application
container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

tried updating the graphics drivers but nope
also did the whole permissions thing for Runbroker via the registry / DCOM which is what you get if you google the error but nope
I found only the following ways to fix it

  * Set the compatibility mode to windows 8 in exe properties
  * disable hardware acceleration in the settings
  * use --disable-gpu on the command line

once the hardware acceleration is disabled, then you can turn off the compatibility mode to windows 8
however disabling the hardware acceleration pretty much stops any webgl from being reasonably fast
running under windows 8 compatibility mode at least gives me some webgl performance

I've not tried the dev build of chrome (64)

Issue is not reproducible from TE end. Could someone from dev team please have a look at this issue.

cc'ing @sunnyps from similar issue 785648 for further inputs on this.

Thanks!

For me this was due to an old display driver which was working fine until the upgrade of the OS to "creator". When I updated the display driver, Chrome worked fine, but Chrome seemed to be the only application which suddenly broke with the OS update.

Seems like there are only sporadic reports of this with some suspicion cast on the graphics drivers.

I'm closing this for now. Feel free to reopen if this becomes a widespread issue.