How to Fix the Windows 11 “Browser May Not Be Secure” Login Warning in Chrome and Microsoft Edge

Fix it by updating Chrome or Microsoft Edge first, then test the login in a clean browser profile with extensions off. The Windows 11 “Browser may not be secure” warning most often appears when a sign-in page detects an outdated browser, blocked cookies, disabled JavaScript, a damaged profile, VPN filtering, or an extension that changes how the browser behaves. Google says sign-in can fail when a browser or app does not meet its security checks [source: Google].

TLDR: Update Chrome or Edge, restart Windows 11, then try the login in Incognito or InPrivate mode. If it works there, one of your extensions, cookies, or profile settings is likely the problem. For example, in a 25-person office, if 18 users can sign in from InPrivate but not from their normal browser window, the browser profile is the first place to check. Do not enter your password on a strange copy of the login page just to “get past” the warning.

What the warning usually means

This warning does not always mean your PC is infected. It means the login service does not trust something about the browser session. That “something” can be boring and annoying: an old browser build, blocked third-party cookies, a broken cache, strict privacy tools, or a work policy pushed by your company.

Honestly, it feels like a small browser setting can cost you 20 minutes for no good reason. But the safest fix is to work through the basics first. Do not disable every security feature at once. Do not install random “browser repair” tools.

1. Update Chrome or Edge

Start here. Old browser versions are a common cause of login warnings, especially with Google, Microsoft, banking, school, and work accounts.

  • In Chrome: open Menu > Help > About Google Chrome.
  • In Edge: open Menu > Help and feedback > About Microsoft Edge.
  • Let the browser update.
  • Close every browser window.
  • Restart Windows 11.

Edge updates from its About page and usually finishes after a restart of the browser [source: Microsoft].

2. Try Incognito or InPrivate mode

This is the fastest test. It takes under a minute and tells you a lot.

  • Chrome: press Ctrl + Shift + N.
  • Edge: press Ctrl + Shift + N.
  • Go to the correct login page manually.
  • Try signing in again.

If the warning disappears, the issue is probably in your normal browser profile. The usual suspects are extensions, cookies, cached files, or custom privacy settings.

3. Turn off extensions that touch privacy, ads, or scripts

Extensions can break login pages. Ad blockers, script blockers, coupon extensions, password tools, antivirus extensions, and “privacy hardening” add-ons can all change requests in ways that trigger a warning.

  • Open the browser extension page.
  • Disable all extensions for a quick test.
  • Restart the browser.
  • Try the login again.
  • If it works, turn extensions back on one by one.

Expect to waste time on this part if you have 10 or more extensions. Still, it is safer than guessing. Pay close attention to anything that blocks JavaScript, cookies, tracking, redirects, or login pop-ups.

4. Clear cookies and cache for the affected site

A bad cookie can keep sending the login page in circles. Clear site data for the affected service instead of wiping your whole browser if you want to keep other sessions intact.

  • Open browser settings.
  • Search for cookies or site data.
  • Find the affected domain, such as google.com, microsoft.com, or your company login domain.
  • Delete its stored data.
  • Close and reopen the browser.

If that fails, clear cached images and files for the last 24 hours. Avoid clearing saved passwords unless you know you have them backed up.

5. Check cookies, JavaScript, time, and VPN settings

Login systems need basic browser features. If they are blocked, the page may treat the session as unsafe.

  • Enable JavaScript for the site.
  • Allow cookies, at least for the login domain.
  • Allow pop-ups and redirects for trusted login pages.
  • Sync Windows time: go to Settings > Time and language > Date and time.
  • Turn off VPN or proxy for a test.

Wrong time settings can break secure sessions. VPNs can also cause problems if the login service sees your sign-in jump between regions. If your VPN exit point changes from London to New York in seconds, some services will flag it.

6. Create a new browser profile

If private mode works but your normal profile keeps failing, create a fresh profile. This avoids damaged settings without forcing a full browser reset.

  • Click the profile icon in Chrome or Edge.
  • Select Add or Set up new profile.
  • Skip sync at first.
  • Try the login from that clean profile.

If the new profile works, your old profile is the issue. You can move bookmarks later, then reinstall only the extensions you trust.

7. Check work, school, antivirus, and security policies

On managed Windows 11 PCs, your IT department may control browser settings. A proxy, SSL inspection tool, endpoint agent, or blocked cookie rule can trigger the warning. Do not fight company policy by installing a portable browser. Ask IT to check browser policies, certificates, proxy rules, and identity provider settings.

On personal PCs, temporarily pause only the browser-related part of your antivirus tool if it has one, such as “web shield” or “HTTPS scanning.” Turn it back on after testing. Never leave core protection off.

When to stop and treat it as suspicious

Stop if the login page URL looks wrong, the certificate warning appears, or the site asks for your password after redirecting through an unknown domain. Close the tab. Type the real address yourself. Change your password from a trusted device if you already entered it.

The safest fix is simple: update the browser, test private mode, remove the extension or profile setting causing the issue, and keep Windows 11 time and security settings clean. If the warning appears only on a work account, let IT handle it. That saves time and avoids making the PC less secure.