That sounds quite frustrating. Does anything happen at all when you try to start the browser? How are you launching the browser? The next time it happens, could you confirm (via Task Manager, Process Manager, or Process Hacker) that no chrome.exe processes are running prior to launching? Do you see any chrome.exe processes start and then stop when you try to launch Chrome?

Could you look for and attach both %TEMP%\chrome_installer.log and C:\Windows\Temp\chrome_installer.log?

wfh: do you have any additional questions that might prove fruitful?

yes that's weird. perhaps something up with multiple users and terminal services, perhaps still running Chromes for other users...

Would be good to get answers to #2. Perhaps even trying to see the exit code from Chrome.exe by CD to the Chrome application directory and running it directly from CMD.exe:

start /wait chrome.exe
echo %errorlevel%

So it does start from the a command prompt using your suggestion start
/wait chrome.exe
What does this mean?

You're saying that "start /wait chrome.exe" works? How do you normally launch Chrome when it fails to work (e.g., from a desktop shortcut, a taskbar shortcut, the Windows Start Menu, etc)?

Yes, I am saying that "Start /wait chrome.exe" works but the standard Google Chrome lnk file does not.

The lnk target is the standard format.
"C:\Program Files x86)\Google\Chrome\Application\chrome.exe"

Yes, I have several LNK shortcuts all with the standard target of:
"C:\Program Files x86)\Google\Chrome\Application\chrome.exe"

The LNK shortcuts will not work but the "Start /wait chrome.exe" from command line does. 

Anyone willing to help me on this issue?

is there really a missing ( in the shortcut?

C:\Program Files x86)\Google\Chrome\Application\chrome.exe

should be

C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

or is this a typo?

Unfortunately, Just a typo. Would of been nice if that was the problem.

can you check if you have any compatibility options set on your chrome?

can you go to chrome://crash to generate a synthetic crash report, then paste the crash id (the "Server ID:") you get from chrome://crashes into this bug?

Thank you for providing more feedback. Adding requester "grt@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

OP: is this still an issue for you? If so, could you use Process Monitor (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx) to capture a trace and send it in to us for analysis?

Archiving this due to lack of activity. Feel free to followup if you have any new info to help us diagnose the problem. Thanks