Unable to reproduce this issue, was able to successfully launch in Win 10.

62.0.3192.0 (Official Build) dev (64-bit) (cohort: Dev)

Can you try renaming user data directory and launch again, may be its corrupted.

I removed this folder :

C:\Users\<username>\AppData\Local\Google\Chrome Dev

and when trying to launch Chrome Dev, which does not launch, some crash log files are dropped into that folder. Attached.

Deleted: Crashpad.zip 2.0 KB

Crashpad.zip 2.0 KB Download

Thanks for that. The "reports" directory is empty, so no crashes were recorded.

Could you check Task Manager to see if there are any lingering chrome.exe processes?

Also, would you try this from a command prompt:

"%ProgramFiles(x86)%\Google\Chrome Dev\Application\chrome.exe" --enable-logging

and copy/paste any output it generates? Thanks.

There are no chrome.exe processes running - I've rebooted my system just in case.

Trying to launch with that command results in the same. Nothing happens, and no output is generated.

I had uninstalled the Dev version and tried the Beta, and that works fine. Dev is still a no go.

Thanks.

Thank you for providing more feedback. Adding requester "grt@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

For tracking purpose adding an RBS.

I am unable to launch chrome dev on windows 10 OS 64 bit.

Tried to install from following link: https://www.google.com/chrome/browser/desktop/index.html?extra=devchannel&platform=win64

Great. Looks like we have a repro in-house. I'm looking for someone who can pass by to see this in action. Thanks.

Regarding labels, I don't think this is related to side-by-side dev, but I can't be certain without seeing it in action. If it is, then this doesn't need to block stable releases, as the issue won't be present there.

Could those of you impacted try installing canary (https://www.google.com/chrome/browser/canary.html?platform=win64) to see if that exhibits the same behavior?

I will stop by at  pchalla@ desktop later this afternoon and will take a look what's going on.

After doing a manual bisect over Chrome Remote Desktop, this looks like a regression introduced in 62.0.3190.0. I'm fairly sure it's not a problem with side-by-side installs, but rather with Chrome as a whole. chrome.dll is failing to load, which leads me to believe that we've introduced a new import that isn't everpresent. I'll investigate more tomorrow.

Huh. 3189 -> 3190 is a clang -> msvc switch. Coincidence? I'm looking at chrome.dll's imports in those two builds now.

Yes, coincidence. Some media foundation imports lost their delayload setting. This is already fixed on trunk in r496117 (62.0.3193.N). We just got unlucky that dev was cut while the regression was in. The next dev build will fix it.

Users who happen to not have the media foundation DLLs on their system will be unable to launch dev channel until the next dev push. I'm not sure how big this population is.

+dalecurtis@,do you have any idea how likely it is that machines are missing the media foundation DLLs? Pls see comment #12 for more details.

Pretty likely since Microsoft released an entire OS (Windows N) for Europe without them :)