Cursor Pro not activating – Network diagnostics stuck on DNS/HTTP/SSL

Support Help
1

Hello Cursor Support Team, i try to email the team but nobody is responding ,

I have an active Cursor Pro subscription on my account, but the Windows Cursor app is not activating Pro.

Here is the issue in detail:

  • Cursor Pro is paid and active on my account

  • Windows app still does not show Free or Pro in Settings

  • When I use the Agent, it stays on “Planning next moves” for a very long time and never responds

  • In Diagnostics → Network, the following stay on Loading:

    • DNS

    • HTTP

    • SSL

  • Other items like Marketplace, Agent, Chat, Ping, and API show as connected (dot)

What I have already tried:

  • Clean uninstall and fresh reinstall of Cursor (User x64)

  • Cleared AppData (Roaming and Local Cursor folders)

  • Restarted Windows multiple times

  • Disabled Windows Defender temporarily

  • Tried mobile hotspot and different networks

  • Confirmed system date/time and timezone

  • Reset WinHTTP proxy

  • Verified that https://api.cursor.sh opens securely in my browser

  • Windows version: Windows 10 22H2

Despite all this, the problem persists only inside the Cursor app.

Could you please:

  1. Check my account status on your side

  2. Advise if there is a known issue or workaround for SSL/HTTP/DNS stuck on “Loading” in the Windows app

  3. Let me know if there are logs or additional diagnostics I should provide

Thank you for your support.

Best regards,

1 Like
Another lag-victim / CPU 90-100%
2

Hey, thanks for the report.

In the past, we’ve been able to fix this kind of issue, where DNS/HTTP/SSL gets stuck loading, by installing the Microsoft Visual C++ Redistributable. Could you please check if it’s installed on your machine, and if not, install the latest version from here: Latest supported Visual C++ Redistributable downloads | Microsoft Learn

Also, please try this:

  • Disable HTTP/2: Cursor Settings > type “HTTP/2” in the search bar > enable “Disable HTTP/2”
  • Add Google DNS: add 8.8.8.8 to your network DNS settings

Could you also share:

  • Your Cursor version (Help > About Cursor > Copy)
  • The email linked to your account, so we can check your subscription

Let me know if installing VC++ fixes the issue.

3

Hello Dean Rie,

Thank you for your reply.

I would like to share some additional details and confirm the steps I have already tried from what you told me:

  • I have the latest Microsoft Visual C++ Redistributable installed on my computer

  • I changed my DNS to 8.8.8.8

  • I attempted to switch HTTP/2 to HTTP/1.1 and back, but there is no option to disable HTTP/2 in Cursor settings (searching for it returns no results)

Cursor version details:

  • Cursor Version: 2.2.44 (system setup)

  • VSCode Version: 1.105.1

  • Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0

  • Date: 2025-12-24T21:41:47.598Z

  • Electron: 37.7.0

  • Chromium: 138.0.7204.251

  • Node.js: 22.20.0

  • V8: 13.8.258.32-electron.0

System information:

  • OS: Windows 10 (Windows_NT x64 10.0.19045 / 22H2)

Account issue:

  • My Cursor app still shows Free Plan, even though I have already paid for Cursor Pro

  • My account email is: [email protected]

Additionally, when I use the Agent in the Cursor app, it stays on “Planning next moves” for a long time and never responds, and in Diagnostics → Network, DNS, HTTP, and SSL remain stuck on “Loading”.

Please let me know if you need any logs, screenshots, or further diagnostics from my side. I appreciate your help in resolving this issue.

Best regards,
Alazer Milaw

4

Thanks for the detailed info. I see the issue. The HTTP/2 setting isn’t in Cursor Settings, it’s in VS Code Settings:

  • Press CTRL+,. This opens VS Code Settings, not Cursor Settings.
  • In the search bar, type “HTTP/2”
  • Turn on “Disable HTTP/2”

After that, restart Cursor and run Network Diagnostics again.

Let me know if disabling HTTP/2 helped.

1 Like
5

I’ve had the same problem described in the topic.

  1. Installing the latest Microsoft Visual C++ Redistributable didn’t seem to help — the problem wasn’t fixed even after a reboot.
  2. Disabling HTTP/2 in VS Code settings instantly fixed it.

Thank you!

1 Like