Cursor cannot enter the page normally

Support Bug Reports
,
1

I have just installed cursor by the dmg from the official site，version 2.26.2. However, after clicking “Continue” as instructed, I cannot proceed. The page is stuck and won’t load。Reinstalling and clearing the cache didn’t work either.

MacBook pro pre 2015， os version：14.8.5 ，update from 12.7.6 。

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

See above

Steps to Reproduce

Expected Behavior

Proceed to the cursor

Screenshots / Screen Recordings

See above

Operating System

MacOS

Version InformationProvide IDE version OR CLI version depending on your selection above

Version: 2.6.21
VSCode Version: 1.105.1
Commit: fea2f546c979a0a4ad1deab23552a43568807590
Date: 2026-03-21T22:09:10.098Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin x64 23.6.0

Additional Information

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

4

Hey, I saw your video. The onboarding page freezes after you click Continue.

A pre-2015 MacBook Pro running macOS 14.8.5 Sonoma is pretty unusual since Sonoma officially supports only 2018+ Macs. Are you using OpenCore Legacy Patcher or something similar to install macOS Sonoma?

This is probably a GPU rendering issue on older hardware. Try launching Cursor from Terminal with GPU acceleration disabled:

/Applications/Cursor.app/Contents/MacOS/Cursor --disable-gpu

If that works, you can also try:

/Applications/Cursor.app/Contents/MacOS/Cursor --disable-gpu-compositing

Let me know:

  • Did --disable-gpu fix the onboarding page?
  • What exact MacBook Pro model and year is this?
  • Are you using any macOS patcher?
5

  • --disable-gpu \–disable-gpu-compositing doesn’t work。

  • What exact MacBook Pro model and year is this?
    MacBook Pro 13" Early 2015（MacBookPro12,1）

  • Are you using any macOS patcher?
    update macOS 14.8.5 using OpenCore Legacy Patcher

6

Got it. OpenCore Legacy Patcher with Intel Iris 6100 is likely the root cause. That GPU does not have native support in macOS Sonoma, and OCLP patches can conflict with Chromium rendering.

Let’s try forcing software rendering with SwiftShader. Run this in Terminal:

/Applications/Cursor.app/Contents/MacOS/Cursor --disable-gpu --disable-gpu-compositing --disable-gpu-sandbox --use-gl=swiftshader

If that does not work, try this variant:

/Applications/Cursor.app/Contents/MacOS/Cursor --disable-gpu --use-angle=swiftshader --disable-gpu-rasterization

Another option is to bypass onboarding by editing the storage file. Close Cursor completely, then run:

# Find and view the storage file
cat ~/Library/Application\ Support/Cursor/User/globalStorage/storage.json

Look for onboarding related keys. If the file exists, you can try adding or setting onboarding completion flags manually.

One important note: MacBook Pro Early 2015 is not officially supported by macOS Sonoma, and running it through OCLP means GPU acceleration is patched or emulated. This can cause rendering issues in Electron apps like Cursor. If none of the steps above work, it might be a hardware and OS compatibility limit.

Can you also check if the latest VS Code works on this machine without issues?

7

  1. 命令行参数不起作用。

  2. “~/Library/Application\ Support/Cursor/User/globalStorage/storage.json”里面没有onboarding关键字。

  3. the latest VS CodeIt also reported the error “Extension host terminated unexpectedly 3 times within the last 5 minutes.” The editor opens normally. Some plugins do not work properly, as shown on the left side of the image below, but the built-in chat feature works, as shown on the right side of the image below.

    image
    image2632×1522 140 KB

It seems these frameworks still rely on the hardware and aren’t compatible with the system version. Is there a solution?

8

The fact that VS Code also crashes with “Extension Host terminated unexpectedly” confirms the issue isn’t on Cursor’s side. It’s a compatibility problem between Electron/Chromium and the Intel Iris 6100 GPU when using OCLP.

MacBook Pro Early 2015 isn’t officially supported on macOS Sonoma. When OCLP patches the GPU drivers, Chromium-based apps like Cursor and VS Code can become unstable, which is exactly what you’re seeing.

A couple more things to try:

  1. Environment variable to fully disable the GPU:
ELECTRON_DISABLE_GPU=1 /Applications/Cursor.app/Contents/MacOS/Cursor
  1. If you can, roll macOS back to 12.7.6 Monterey. That version officially supports your MacBook Pro, and Cursor should work normally.

If neither option helps, unfortunately this is a hardware plus unsupported macOS limitation. Cursor, like VS Code, relies on Chromium for rendering, and Chromium doesn’t work well with OCLP patched GPU drivers.

Let me know if ELECTRON_DISABLE_GPU=1 helped.

9

  1. The environment variable ELECTRON_DISABLE_GPU=1 does not work on macOS Sonoma, and VS Code still gets stuck on the loading page when opened.

    image
    image2072×1518 75.5 KB

  2. After my testing, VS Code 1.104 (Electron: 37.3.1) works fine, but version 1.105 reports the error “Extension Host terminated unexpectedly”. This should be related to the Electron upgrade.

  3. I haven’t backed up my system, so I can’t revert to 12.7.6 Monterey for the time being. I’ll try reinstalling 12.7.6 Monterey later when I have time. I hope MacBook users with this version of the system can help test it.

10

Great catch with VS Code 1.104 vs 1.105. That confirms the issue is the Electron update from 37.x to a newer version. Cursor is currently using Electron 39.8.1, which is also incompatible with OCLP-patched Intel Iris 6100 drivers.

Sadly, this limitation is on the Electron and Chromium side, not Cursor, so we can’t fix it. There are basically two real options:

  1. Roll back to macOS 12.7.6 Monterey like you planned. Cursor should work normally.
  2. If you can find an older Cursor build on Electron 37.x or lower, it might work, but we can’t guarantee stability on older versions.

I’ll keep the thread open in case there are updates after you roll back to Monterey. Let me know how it goes.