UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.75 Safari/537.36

Steps to reproduce the problem:
*Requires a Google account secured with 2SV and a U2F key.
1. Install a fresh copy of Chrome.
2. Click "No thanks" on the initial sign in page.
3. Try to sign in using the profile manager, and opt to use a verification method other than the U2F key.

What is the expected behavior?
The Google account should be signed into Chrome.

What went wrong?
The Google account is not signed into Chrome.

Did this work before? Yes Worked in 49.

Chrome version: 50.0.2661.75  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

I work with a lot of remote desktops, so I often sign into Chrome via RDP. Obviously, I can't use my U2F key, so I opt to enter an Authenticator app code instead. In 49, this worked fine, even after I had skipped the initial profile setup process.

Now when I do the same thing (click "No thanks", and sign in later), Chrome will sign in to my account on the web, but it will not sign me in to my account in Chrome. The only way around this appears to be to delete the default "You" profile and start over with Chrome. Creating a new profile might also work.