# Remote Control worker crashes on Windows — better\_sqlite3 NODE\_MODULE\_VERSION 127 vs 137

**URL:** <https://forum.cursor.com/t/remote-control-worker-crashes-on-windows-better-sqlite3-node-module-version-127-vs-137/171693>\
**Category:** Bug Reports\
**Tags:** cli, windows, remote-control\
**Created:** [September 15, 2026, 2:42am UTC](https://forum.cursor.com/t/remote-control-worker-crashes-on-windows-better-sqlite3-node-module-version-127-vs-137/171693 "2026-09-15T02:42:28Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [October 16, 2026, 7:31pm UTC](https://forum.cursor.com/t/remote-control-worker-crashes-on-windows-better-sqlite3-node-module-version-127-vs-137/171693/12 "2026-10-16T19:31:09Z")

</div>

Hey @JD_Sandhu,

The Windows worker crash loading better\_sqlite3 (the NODE\_MODULE\_VERSION 127 vs 137 error) is fixed in the latest Cursor CLI, version 2026.10.16 or newer.

To pick it up, run `agent update`, or rerun the PowerShell install command, then restart Cursor so the Remote Control worker comes up on the new build. `agent worker start` should get past the exec-daemon step, and tasks started from the mobile app should move past “Setting up environment.” The worker also needs Git for Windows installed, so check that if it still doesn’t show up.

If it still gets stuck after updating, paste the output of `agent worker start` here and I’ll take a look.

---

_[View the full topic](https://forum.cursor.com/t/remote-control-worker-crashes-on-windows-better-sqlite3-node-module-version-127-vs-137/171693)._
