Where does the bug appear (feature/product)?
Cursor CLI
Describe the Bug
The standalone Cursor Agent installed using the official Windows installer cannot start on Windows 11 Pro when Smart App Control is enabled.
The command:
irm 'https://cursor.com/install?win32=true' | iex
completes successfully, but every Agent command immediately fails.
Example:
agent --version
Output:
Error: Failed to load native binding for win32/x64
(expected: ./merkle-tree-napi.win32-x64-msvc.node)
Original error:
Error: node-loader:
Error: An Application Control policy has blocked this file.
C:\Users\<username>\AppData\Local\cursor-agent\versions\2026.07.01-41b2de7\merkle-tree-napi.win32-x64-msvc.node
The file exists on disk.
Running:
Get-AuthenticodeSignature "...\merkle-tree-napi.win32-x64-msvc.node"
returns:
Status: NotSigned
SignatureType: None
Environment
-
Windows 11 Pro
-
Smart App Control: ON
-
Node.js 22.23.1
-
Installed using:
irm 'https://cursor.com/install?win32=true' | iex
Actual behavior
Windows blocks the unsigned native module (merkle-tree-napi.win32-x64-msvc.node) before the agent starts.
Steps to Reproduce
-
Use Windows 11 Pro with Smart App Control enabled.
-
Install Cursor Agent using the official installer.
-
Run:
agent --version
Expected Behavior
Cursor Agent starts normally.
Operating System
Windows 10/11
Version Information
2026.07.01-41b2de7
Additional Information
This appears to be caused by the native module being unsigned, which causes Windows Smart App Control / Application Control to block it.
Does this stop you from using Cursor
Yes - Cursor is unusable