Inno_updater.exe unable to start correctly - #th

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Installing Cursor on a newly minted Windows 11 Pro machine and the last Cursor stable build (the one available 6 days ago), inno_updater.exe is unable to start correctly.

All reports on the error resulting from starting an update (0xC000007B error-code - which means STATUS_INVALID_IMAGE_FORMAT) correctly indicate that a 32-bit process is trying to load a 64-bit exe/dll - or the other way around.

This problem has been reported before on this forum. The suggested fixes don’t work or work by chance because one of them installs the required dll with the correct bit-ness.

Looking at the tools folder of the Cursor installation I found two files that do not match each other in bit-ness:

  • inno_updater.exe is a 64-bit exe
  • vsruntime140.dll is a 32-bit dll

Please ensure that the Cursor installation provides a vsruntime140.dll matching the bit-ness of the inno_updater.exe!

The simplest fix for this problem (as long as the cursor builds haven’t been fixed) is to get your hands on the vcruntime140.dll with the bit-ness that matches your inno_updater.exe by downloading and installing the appropriate Visual C redistributable:

UNFORTUNATELY you’ll have to rename/delete every time after an update until the builds are fixed because the update will re-add the ‘missing’ dll.

Steps to Reproduce

I got into this trouble with a newly minted Windows 11 Pro machine and the last Cursor stable build available 6 days ago,

Expected Behavior

Update without a glitch

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.35 (system setup)
VSCode Version: 1.99.3
Commit: b753cece5c67c47cb5637199a5a5de2b7100c180
Date: 2025-09-19T17:39:38.846Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.