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
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?
Run where.exe node
Run node --version
Run echo $env:NODE_OPTIONS
Run these two lines, which start the same helper Canvas uses with your Node:
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.
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:
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:
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.
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.