Canvas couldn't compile service has stopped working cursor

Any Canvas does not work. I’ve tried reinstalling a User/System versions of Cursor and updated it to the latest version available but it still doesn’t work. I have verified nothing is being blocked by our IT. Logs attached

20261005T130352.zip (105.7 KB)

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)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something 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!

Hey @cartwheel_IT, thanks for the report and the logs!

The logs show that Canvas can’t start the small Node.js helper it uses to compile canvases. Canvas runs that helper with the node it finds on your PATH, and on this machine the helper exits right after it starts. Could you run these in a PowerShell window and paste the output?

  1. Run where.exe node
  2. Run node --version
  3. Run echo $env:NODE_OPTIONS
  4. Run these two lines, which start the same helper Canvas uses with your Node:
$esb = (Get-ChildItem "C:\Program Files\cursor\resources\app" -Recurse -File -Filter esbuild -ErrorAction SilentlyContinue | Where-Object { $_.FullName -like "*esbuild-wasm\bin\esbuild" } | Select-Object -First 1).FullName
node $esb --version

A healthy setup prints 0.25.9. If you see an error instead, please paste it as-is.

In the meantime, one thing to try: update the Node.js that where.exe node lists first to the current LTS (or remove it from PATH if you don’t need it). When no Node is on PATH, Cursor uses its own bundled Node for Canvas. Then fully quit Cursor (including the tray icon) and reopen it. It’s also worth checking Windows Security > Protection history for any blocks on node.exe around the time you opened a canvas.

I am getting this error as well. Here is the output from running those commands.

PS S:> where.exe node
C:\Program Files\nodejs\node.exe
PS S:> node --version
v26.11.1
PS S:> echo $env:NODE_OPTIONS
PS S:> $esb = (Get-ChildItem "C:\Program Files\cursor\resources\app" -Recurse -File -Filter esbuild -ErrorAction SilentlyContinue | Where-Object { $_.FullName -like "*esbuild-wasm\bin\esbuild" } | Select-Object -First 1).FullName
PS S:> node $esb --version
Error: error:1C8000BA:Provider routines::entropy source strength too weak
at randomFillSync (node:internal/crypto/random:179:3)
at getRandomValues (node:internal/crypto/random:367:3)
at Crypto.getRandomValues (node:internal/crypto/webcrypto:2025:10)
at runtime.getRandomData (C:\Program Files\cursor\resources\app\extensions\node_modules\esbuild-wasm\wasm_exec.js:295:14)
at wasm://wasm/02e99f5e:wasm-function[520]:0x7ef76
at wasm://wasm/02e99f5e:wasm-function[741]:0xb0b34
at wasm://wasm/02e99f5e:wasm-function[609]:0x8d0ea
at wasm://wasm/02e99f5e:wasm-function[1203]:0x10e570
at wasm://wasm/02e99f5e:wasm-function[1265]:0x1111b4
at globalThis.Go.run (C:\Program Files\cursor\resources\app\extensions\node_modules\esbuild-wasm\wasm_exec.js:534:23) {
opensslErrorStack: [
'error:1200006C:random number generator::error instantiating drbg',
'error:1C8000BD:Provider routines::error retrieving entropy'
],
library: 'Provider routines',
reason: 'entropy source strength too weak',
code: 'ERR_OSSL_ENTROPY_SOURCE_STRENGTH_TOO_WEAK'
}
PS S:>

I resolved this issue by removing OPENSSL_CONF environment variable on my profile. I dont recall why I had a custom OPENSSL_CONF file.

After reboot, the error is back. I have confirmed I do not have any openssl configuration file defined.

Cursor version
Version 3.25.6 (system setup)

openssl --version
OpenSSL 4.0.3 29 Sep 2026 (Library: OpenSSL 4.0.3 29 Sep 2026)

node --version
v26.11.1

node -e “const c=require(‘node:crypto’); console.log({node:process.version,openssl:process.versions.openssl,fips:c.getFips(),args:process.execArgv,env:Object.fromEntries(Object.entries(process.env).filter(([k])=>/OPENSSL|NODE_OPTIONS|FIPS/i.test(k)))}); c.randomBytes(16); console.log(‘random OK’)”
{
node: ‘v26.11.1’,
openssl: ‘3.5.9’,
fips: 0,
args: [
‘-e’,
“const c=require(‘node:crypto’); console.log({node:process.version,openssl:process.versions.openssl,fips:c.getFips(),args:process.execArgv,env:Object.fromEntries(Object.entries(process.env).filter(([k])=>/OPENSSL|NODE_OPTIONS|FIPS/i.test(k)))}); c.randomBytes(16); console.log(‘random OK’)”
],
env: {}
}
random OK

Hey Kevin,

Thank you for the update. I think we got it to work when we deleted Node.js from the PATH. I’m pasting still the findings on the commands:

PS C:\Windows\system32> where.exe node
C:\Program Files\nodejs\node.exe
PS C:\Windows\system32> node --version
v26.12.0
PS C:\Windows\system32> echo $env:NODE_OPTIONS
PS C:\Windows\system32> $esb = (Get-ChildItem “C:\Program Files\cursor\resources\app” -Recurse -File -Filter esbuild -ErrorAction SilentlyContinue | Where-Object { $_.FullName -like “*esbuild-wasm\bin\esbuild” } | Select-Object -First 1).FullName
PS C:\Windows\system32> node $esb --version
Error: error:1C8000BA:Provider routines::entropy source strength too weak
at randomFillSync (node:internal/crypto/random:179:3)
at getRandomValues (node:internal/crypto/random:367:3)
at Crypto.getRandomValues (node:internal/crypto/webcrypto:2018:10)
at runtime.getRandomData (C:\Program Files\cursor\resources\app\extensions\node_modules\esbuild-wasm\wasm_exec.js:295:14)
at wasm://wasm/02e99f5e:wasm-function[520]:0x7ef76
at wasm://wasm/02e99f5e:wasm-function[741]:0xb0b34
at wasm://wasm/02e99f5e:wasm-function[609]:0x8d0ea
at wasm://wasm/02e99f5e:wasm-function[1203]:0x10e570
at wasm://wasm/02e99f5e:wasm-function[1265]:0x1111b4
at globalThis.Go.run (C:\Program Files\cursor\resources\app\extensions\node_modules\esbuild-wasm\wasm_exec.js:534:23) {
opensslErrorStack: [
‘error:1200006C:random number generator::error instantiating drbg’,
‘error:1C8000BD:Provider routines::error retrieving entropy’
],
library: ‘Provider routines’,
reason: ‘entropy source strength too weak’,
code: ‘ERR_OSSL_ENTROPY_SOURCE_STRENGTH_TOO_WEAK’
}
PS C:\Windows\system32>

Same failure on Windows, with one extra detail about per-user installs.

Node v26.10.0 was the first `node` on PATH (nvm-windows). `NODE_OPTIONS` was unset, and there was no `OPENSSL_CONF`.

```text

where.exe node

C:\Users\Sam\AppData\Local\Author Software\nvm\.nodejs\node.exe

node --version

v26.10.0

```

The diagnostic in the staff reply looks under `C:\Program Files\cursor`. This machine is the per-user install, so that search found nothing. The helper that actually fails is:

`C:\Users\Sam\AppData\Local\Programs\cursor\resources\app\extensions\node_modules\esbuild-wasm\bin\esbuild`

Running that file with Node 26 exits immediately:

```text

Error: error:1C8000BA:Provider routines::entropy source strength too weak

code: ERR_OSSL_ENTROPY_SOURCE_STRENGTH_TOO_WEAK

```

Cursor’s bundled Node at `…\resources\app\resources\helpers\node.exe` is v24.22.1. The same helper prints `0.25.9` under that binary.

Fix that kept Node on PATH: `nvm use 24.20.0` (LTS, already installed). That Node also prints `0.25.9`. Then fully quit Cursor, including the tray icon, and reopen it. Node 26 is still installed; `nvm use 26.10.0` brings the canvas error back.

Removing Node from PATH would also work, because Canvas then uses the bundled Node. Switching the PATH Node from 26 to 24 LTS was enough.

Hey @Phil_Bolduc, the cause is Node.js 26 on Windows, not your OpenSSL setup. Canvas compiles with the Node on your PATH, and Node 26 fails as soon as that helper asks it for random bytes, so every canvas shows “The service was stopped”. Cursor’s own bundled Node 24 runs the same helper fine.

To get Canvas working now:

  1. Make Node 24 the node on your PATH. With the nodejs.org installer, install Node 24 in place of 26. With nvm-windows, run nvm install 24 and then nvm use 24.
  2. Fully quit Cursor, including the tray icon, and reopen it.

If you don’t need Node on your PATH at all, removing it works too, since Canvas then falls back to Cursor’s bundled Node.

One correction to the earlier reply: Node 26 became the LTS release on Oct 28, so “update to the current LTS” now lands on the affected version. Stay on Node 24 for now.

This is a known issue the team is aware of. They’re working on having Canvas switch to its bundled Node automatically when the one on your PATH can’t run the helper, so you won’t need to change anything once that ships.