Microsoft websites broken/poor performance

Hi Ray Charbonneau,

Thank you for reaching out to Microsoft Q&A forum and sharing the details of the issue. I understand how frustrating it can be when pages take longer to load, and I truly appreciate your patience while we work through this together.

The delay you’re seeing, caused by the wcp-consent.js script timing out, is often related to network routing or DNS resolution rather than your browser settings.

Below are some steps you can try to improve performance:

Step 1: Switch to a Public DNS Provider

This can help bypass slow or blocked routes.

• Open Settings > Network & Internet > Advanced Network Settings.
• Right-click your active network > More adapter Options > Edit.
• Select Internet Protocol Version 4 (TCP/IPv4) > Properties.
• Choose Use the following DNS server addresses and enter:
  • Preferred DNS: 8.8.8.8 (Google)
  • Alternate DNS: 1.1.1.1 (Cloudflare)
• Click OK, then restart your browser.

Step 2: Test Using a VPN

A VPN can route traffic through a different region, avoiding local ISP issues.

• Connect to a trusted VPN service.
• Reload the Microsoft site and check if the delay disappears.

If the site loads normally, the issue is likely regional routing.

Step 3: Temporarily Disable IPv6

Some networks misroute IPv6 traffic, causing timeouts.

• Open Settings > Network & Internet > Advanced Network Settings.
• Right-click your active network > More adapter Options > Edit.
• Uncheck Internet Protocol Version 6 (TCP/IPv6).
• Click OK, then restart your browser.

Step 4: Check Connectivity to Microsoft CDN

Verify if your system can reach the CDN hosting the script.

• Open Command Prompt and run:

    nslookup wcpstatic.microsoft.com
    ping wcpstatic.microsoft.com
  

If these commands fail or show high latency, it indicates a network issue.

In case the issue persists after these steps, please let me know. I'm here to help.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

tracert runs into Microsoft network space, then fails:

C:\Users\rchar>tracert wcpstatic.microsoft.com

Tracing route to part-0012.t-0009.t-msedge.net [13.107.213.40]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1

2 9 ms 9 ms 9 ms lo0-100.BSTNMA-VFTTP-305.verizon-gni.net [100.0.196.1]

3 14 ms 7 ms 7 ms B3305.BSTNMA-LCR-22.verizon-gni.net [100.41.221.208]

4 * * * Request timed out.

5 7 ms 9 ms 9 ms customer.alter.net [204.148.176.2]

6 * * 10 ms 51.10.27.51

7 * * * Request timed out.

8 * * * Request timed out.

9 * 9 ms 9 ms 51.10.4.48

10 * * * Request timed out.

11 18 ms 25 ms 11 ms ae24-0.ear04.nyc30.ntwk.msn.net [104.44.33.206]

12 12 ms 8 ms 9 ms 51.10.17.41

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

While your instructions are incorrect, disabling IPv6 seems to help. So thanks.