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

Example URL:
http://www.facebook.com, www.strava.com, www.pinkbike.com, any website with the Remember Me option

Steps to reproduce the problem:
1. Log into a website, choosing the "Remember Me" or "Keep Me Logged In" option
2. Close Chrome
3. Return to website, find that you are no longer logged in. This only seems to happen with NEW cookies. Existing log ins with the Remember Me flag set still work.

What is the expected behavior?
When selecting Remember Me, returning to the website should show that you're still logged in.

What went wrong?
No idea. This just stopped working this past week. It may be that the problem has existed but, I recently cleared my browsing history. Since then, Remember Me no longer works. However, I have tried just logging out of websites on a completely different computer, using Chrome, and the Remember Me function doesn't work on that computer any longer either. I've done clean installs of Chrome, after uninstalling and removing every trace of it from my system, rebooting and reinstalling. Running Windows 10 Pro 64 Bit, V 1709, & V 1703 as well on another computer. Same behavior. Chrome is remembering my User Names and Passwords, and autofilling forms. It's just the Cookie problem with the Remember Me functionality. Deleting just the Cookie file in the Chrome directory doesn't fix the problem. Creating a new User account in Windows and doing a clean install of Chrome doesn't fix the problem. Logging into my Google account or not logging in has no effect on the behavior.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes Don't know. Don't keep track of which version of Chrome is on my system. It generally just works...

Does this work in other browsers? Yes

Chrome version: 64.0.3282.119  Channel: stable
OS Version: 10.0
Flash Version: 

This seems like a genuine bug to me since it's reproducible. Most hits when searching for this problem date to 2009-10 time-frame. None of the suggested fixes help.