Copilot not working on edge

Question

I can't open copilot and I am getting message "copilot.microsoft.com uses an unsupported protocol.

I have tried the following:

1. Installing/updating edge browser
2. clearing cache and cookies
3. Put copilot.microsoft on trusted sites
4. LAN setting are set to automatic detect LAN setting
5. cleared SSL state

How can I solve this problem of copilot not working because of unsupported protocol issue?

Answer 1

You’re encountering the “unsupported protocol” error when trying to access copilot.microsoft.com, which typically points to network-layer or protocol misconfiguration, especially around TLS/SSL.

You’ve already tried many smart steps — here are some targeted, deeper solutions based on the exact error and your efforts so far:

✅

Fix 1: Force TLS 1.2/1.3 Protocol Support in Windows

If TLS 1.2 or 1.3 is disabled on your machine or in your registry, many secure Microsoft services (including Copilot) will refuse to connect.

Steps:

1. Press Windows + R, type inetcpl.cpl, and press Enter.
2. Go to the Advanced tab.
3. Scroll down to Security, ensure the following are checked:
   • ✅ Use TLS 1.2
     • ✅ Use TLS 1.3 (if available)
     1. 1. Click Apply, then OK, and restart your browser.

✅

Fix 2: Reset Winsock + Flush DNS + Clear Proxy Cache

Corrupted Winsock entries or DNS caching can break protocol negotiation.

Run these commands in

Command Prompt (Admin)

:

netsh winsock reset

netsh int ip reset

ipconfig /flushdns

netsh winhttp reset proxy

Then restart your computer.

✅

Fix 3: Check if Antivirus or Firewall is Blocking TLS

Some security software (especially enterprise ones like Symantec, ESET, Sophos) may intercept and break HTTPS (TLS) requests and cause unsupported protocol errors.

Steps:

• Temporarily disable HTTPS scanning in your antivirus.
• Try accessing Copilot again.
• If it works, you’ll need to add copilot.microsoft.com to the exception list of your security software.

✅

Fix 4: Use Edge with a Clean User Profile

Corrupted browser profiles or extensions may interfere with secure connections.

Try:

1. Open Edge.
2. Click on your profile > Browse as Guest or create a New Profile.
3. Go to https://copilot.microsoft.com

If it works in guest mode, the issue is with a corrupt Edge profile or extension.

✅

Fix 5: Group Policy or Network Appliance Issues (Corporate PCs)

If you are on a corporate or school network, it’s possible a Group Policy, firewall, or web filter is forcing legacy protocols or blocking TLS 1.2/1.3.

Ask your IT to:

• Ensure copilot.microsoft.com is not being SSL-intercepted or downgraded.
• Confirm outbound TLS 1.2/1.3 is allowed.
• Verify proxy servers aren’t rewriting HTTPS headers.

🧪 Bonus Check: Confirm TLS Protocols Enabled via Registry

If you’re comfortable with the Registry:

1. Open regedit
2. Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols

Ensure TLS 1.2 and TLS 1.3 are not disabled. You may need to create:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]

"Enabled"=dword:00000001

"DisabledByDefault"=dword:00000000

Then restart the system.

🧪 Test It

You can also test TLS protocol support using this Microsoft page:

➡️ https://www.ssllabs.com/ssltest/viewMyClient.html

It will show what TLS versions your system is using.

Summary of Best Fix Order:

Fix	Description
Fix	Description
✅ Fix TLS settings	via inetcpl.cpl > Advanced tab
✅ Reset Winsock & DNS	netsh, ipconfig, etc.
✅ Antivirus check	Disable HTTPS scanning
✅ Use Edge Guest Mode	To rule out profile/extension
✅ Registry Fix	Ensure TLS 1.2+ enabled
✅ Network policy	Ask IT to verify firewall/proxy configs

Let me know if you’re on a work or school network and I can tailor the advice more, or if you’d like a PowerShell script to apply some of these fixes automatically. You’re encountering the “unsupported protocol” error when trying to access copilot.microsoft.com, which typically points to network-layer or protocol misconfiguration, especially around TLS/SSL.

You’ve already tried many smart steps — here are some targeted, deeper solutions based on the exact error and your efforts so far:

✅ 

Fix 1: Force TLS 1.2/1.3 Protocol Support in Windows

If TLS 1.2 or 1.3 is disabled on your machine or in your registry, many secure Microsoft services (including Copilot) will refuse to connect.

Steps:

1. Press Windows + R, type inetcpl.cpl, and press Enter.
2. Go to the Advanced tab.
3. Scroll down to Security, ensure the following are checked:
   • ✅ Use TLS 1.2
     • ✅ Use TLS 1.3 (if available)
     1. 1. Click Apply, then OK, and restart your browser.

✅ 

Fix 2: Reset Winsock + Flush DNS + Clear Proxy Cache

Corrupted Winsock entries or DNS caching can break protocol negotiation.

Run these commands in 

Command Prompt (Admin)

:

netsh winsock reset

netsh int ip reset

ipconfig /flushdns

netsh winhttp reset proxy

Then restart your computer.

✅ 

Fix 3: Check if Antivirus or Firewall is Blocking TLS

Some security software (especially enterprise ones like Symantec, ESET, Sophos) may intercept and break HTTPS (TLS) requests and cause unsupported protocol errors.

Steps:

• Temporarily disable HTTPS scanning in your antivirus.
• Try accessing Copilot again.
• If it works, you’ll need to add copilot.microsoft.com to the exception list of your security software.

✅ 

Fix 4: Use Edge with a Clean User Profile

Corrupted browser profiles or extensions may interfere with secure connections.

Try:

1. Open Edge.
2. Click on your profile > Browse as Guest or create a New Profile.
3. Go to https://copilot.microsoft.com

If it works in guest mode, the issue is with a corrupt Edge profile or extension.

✅ 

Fix 5: Group Policy or Network Appliance Issues (Corporate PCs)

If you are on a corporate or school network, it’s possible a Group Policy, firewall, or web filter is forcing legacy protocols or blocking TLS 1.2/1.3.

Ask your IT to:

• Ensure copilot.microsoft.com is not being SSL-intercepted or downgraded.
• Confirm outbound TLS 1.2/1.3 is allowed.
• Verify proxy servers aren’t rewriting HTTPS headers.

🧪 Bonus Check: Confirm TLS Protocols Enabled via Registry

If you’re comfortable with the Registry:

1. Open regedit
2. Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols

Ensure TLS 1.2 and TLS 1.3 are not disabled. You may need to create:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]

"Enabled"=dword:00000001

"DisabledByDefault"=dword:00000000

Then restart the system.

🧪 Test It

You can also test TLS protocol support using this Microsoft page:

➡️ https://www.ssllabs.com/ssltest/viewMyClient.html

It will show what TLS versions your system is using.

Summary of Best Fix Order:

Fix	Description
✅ Fix TLS settings	via inetcpl.cpl > Advanced tab
✅ Reset Winsock & DNS	netsh, ipconfig, etc.
✅ Antivirus check	Disable HTTPS scanning
✅ Use Edge Guest Mode	To rule out profile/extension
✅ Registry Fix	Ensure TLS 1.2+ enabled
✅ Network policy	Ask IT to verify firewall/proxy configs