Turn Off Windows Authentication for Chrome

This guide shows you how to stop Chrome from automatically using your Windows login credentials (username and password) to sign in to websites that support Integrated Windows Authentication (IWA), such as corporate intranet portals or SharePoint sites. This is useful when you want to use a different account, avoid automatic sign-ins, or troubleshoot authentication loops. You’ll need to be signed in to Windows with an administrator account to change Chrome’s policy settings.

What You’ll Need

• Windows 10 or Windows 11
• An administrator account on the PC
• Chrome installed (any recent version)

Step-by-Step

1. Close Chrome completely. Make sure no Chrome windows or background processes are running. You can check the system tray for the Chrome icon and right-click it to exit, or use Task Manager to end all Chrome processes.
2. Open the Windows Registry Editor. Press Win + R, type regedit, and press Enter. Click “Yes” if prompted by User Account Control.
3. Navigate to the Chrome policy key. In the Registry Editor, go to the following path:
   HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
   If the Google or Chrome folders don’t exist, you’ll need to create them: right-click on SOFTWARE, select New > Key, name it Google, then right-click on Google, create a new key named Chrome.
4. Create a new DWORD value. Right-click on the Chrome key (or in the empty space on the right pane), select New > DWORD (32-bit) Value, and name it AuthNegotiateDelegateWhitelist.
5. Set the value to a single dash. Double-click the newly created AuthNegotiateDelegateWhitelist value. In the “Value data” field, enter a single hyphen character: -. This tells Chrome to not delegate credentials to any server. Click OK.
6. Create a second DWORD value. Repeat step 4, but name this one AuthServerWhitelist.
7. Set the second value to a single dash. Double-click AuthServerWhitelist and set its value data to -. This tells Chrome to not use Windows authentication for any server. Click OK.
8. Close the Registry Editor. Save your changes by simply closing the window.
9. Restart Chrome. Open Chrome again. The changes should take effect immediately. If not, restart your computer.

Common Mistakes

• Using the wrong registry path. The policy must be under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome. Placing it under HKEY_CURRENT_USER or directly under Google without the Chrome subkey will not work.
• Setting the value to empty instead of a dash. An empty string or a zero value may not be recognized. The single hyphen - is the standard way to disable the whitelist entirely.
• Forgetting to close Chrome before editing the registry. Chrome reads these policies at startup. If Chrome is already running, the changes won’t apply until you fully restart it.
• Confusing the two whitelist values. AuthServerWhitelist controls which servers can use Windows authentication. AuthNegotiateDelegateWhitelist controls which servers your credentials can be delegated to. Both need to be set to - to fully disable the feature.

Tips

• Use a separate Chrome profile for sites that need Windows authentication. This way you can keep your main profile with authentication disabled and a work profile where it’s enabled.
• Test with a specific site. If you only want to disable Windows authentication for one or two sites, you can set the whitelist to a list of sites you want to keep enabled, rather than disabling all. For example, example.com,sharepoint.company.com. But to turn it off entirely, use the dash.
• Check Chrome’s policy page. Type chrome://policy in the address bar to verify that the two values are being applied. If they show up there, Chrome is reading them correctly.
• Remember this is a machine-wide setting. The registry key under HKEY_LOCAL_MACHINE affects all users on the computer. If you only want to change it for your user account, you would need to use a different method (like a command-line flag), but the registry approach is the most reliable.

Troubleshooting

• Chrome still prompts for Windows credentials. First, verify the registry values are exactly as described. Then, check chrome://policy to see if the policies are listed. If they are not, the registry path may be wrong or Chrome wasn’t restarted. If they are listed, but the behavior persists, try clearing Chrome’s cache and cookies for the affected site.
• You see “Your connection is not private” errors. This can happen if the site uses a certificate that isn’t trusted. The registry change doesn’t affect certificates, so this is unrelated. Check the site’s certificate and your system date/time.
• Other browsers still use Windows authentication. This guide only affects Chrome. Edge, Firefox, and Internet Explorer have their own settings. You’ll need to adjust those separately if needed.
• The registry key disappears after a reboot. This can happen if your organization enforces a Group Policy that overwrites it. In that case, you’ll need to contact your IT administrator.
• You can’t create the registry key due to permissions. Make sure you’re logged in as an administrator. If you are, right-click on the Chrome key, select Permissions, and give your account full control.

Frequently Asked Questions

Will this affect my Google account sign-in in Chrome?

No. This only affects Integrated Windows Authentication, which is used for enterprise sites that authenticate against Windows Active Directory. Your Google account sign-in is separate and unaffected.

Can I re-enable Windows authentication later?

Yes. Simply go back to the registry, delete the two DWORD values (or set them to a list of allowed servers), and restart Chrome. The changes are fully reversible.

Does this work on Chrome for Mac or Linux?

No. The registry method is Windows-specific. On Mac and Linux you would need to use command-line flags or configuration files, which are more complex.

Why would I want to turn this off?

Common reasons include: you want to sign in with a different account than your Windows login, the automatic authentication is causing errors (like an infinite redirect loop), or you’re on a shared computer and don’t want your credentials sent to every site.

Is it safe to edit the Windows registry?

Editing the registry can be risky if you change the wrong keys. However, this specific change only affects Chrome’s authentication behavior and is easily reversible. Always back up the registry before making changes, and follow the steps exactly.

What if I don’t see the Google or Chrome folders in the registry?

That’s normal if no Chrome policies have been set before. You’ll need to create them manually by right-clicking and selecting New > Key as described in step 3.

Related

• Fix AOC USB Monitor Not Working on Windows 10
• Windows 10 Settings to Customize First
• Venmo Payments: How to Pay & Protect Your Purchase