If Chrome on Windows keeps asking you to sign in again (or you get signed out every time you close the browser), the cause is usually cookies being cleared, a time mismatch, or a corrupted Chrome profile.
This guide walks through the quickest checks first, then the deeper fixes.
1. Check if Chrome is clearing cookies on exit
Most “constant sign-out” problems come down to cookies being deleted. If cookies don’t persist, your login session can’t persist either.
- Open Chrome settings and search for cookies.
- Make sure Clear cookies and site data when you close all windows is turned off.
- Under site data settings, confirm you’re not blocking third-party cookies in a way that breaks your specific sign-in flow (some accounts rely on them).
After changing this, fully close Chrome (all windows) and reopen it.
2. Remove “google.com” from any “Always clear on exit” site list
Even if global cookie clearing is off, Chrome can still be told to wipe specific sites on close.
- In Chrome settings, look for sections like Sites that can always use cookies and Sites that are always cleared when you close Chrome.
- If you see entries such as google.com, accounts.google.com, or your workplace login domain in a “clear on exit” list, remove them.
- If your sign-in is through a company identity provider, check that domain too (for example: okta, azuread, auth0 domains).
This is a common “it only breaks on my PC” setting because it can be added accidentally by cleanup tools or old privacy tweaks.
3. Fix Windows date/time (it can break sessions and tokens)
If your Windows clock is off, secure sign-in tokens can be considered expired or not valid yet—leading to repeated logouts.
- Open Windows Settings → Time & language.
- Turn on Set time automatically and Set time zone automatically (or pick the correct time zone manually).
- Use Sync now if available.
Then restart Chrome and try signing in again.
4. Pause extensions that touch privacy, cookies, or security
Some extensions can clear cookies, block sign-in scripts, or strip headers—especially ad blockers, privacy tools, and “security” add-ons.
- Temporarily disable extensions one by one (or disable all, then re-enable gradually).
- Prioritize testing anything related to: ad blocking, tracking protection, cookie control, antivirus web shields, password managers, or “cleaner” tools.
- Retry sign-in after disabling, and close/reopen Chrome to see if the session sticks.
If the problem disappears, you’ve found the culprit—keep it disabled or adjust its settings to allow your account domains.
5. Create a fresh Chrome profile (corrupt profile = unstable sign-in)
When Chrome’s local profile files get corrupted, you can see weird behavior like instant sign-outs, sync failing, or endless “sign in” prompts.
- In Chrome, add a new profile (you can do this from the profile menu near the top of Chrome).
- Sign in in the new profile and test whether it stays signed in after a full Chrome restart.
- If it works, move your essentials: bookmarks (export/import), password manager vault, and extension list.
If you’re using Chrome Sync, a fresh profile often stabilizes everything quickly.
6. Reset Chrome settings (last resort, but often decisive)
If you’ve tried the above and Chrome still won’t hold a session, resetting settings can remove a hidden configuration causing cookie/session loss.
- Open Chrome settings and search for Reset settings.
- Use Restore settings to their original defaults.
- After the reset, sign in again and test by closing and reopening Chrome.
This won’t delete your bookmarks, but it will disable extensions and reset things like startup pages and site settings.
Final thoughts
When Chrome on Windows won’t stay signed in, the fix is usually cookie persistence (global or per-site) or a Windows time mismatch.
If a new Chrome profile solves it, don’t overthink it—profile corruption is surprisingly common, and starting fresh is often the cleanest win.