Failed to install Cursor update

When getting the latest update (I guess from 0.45.x to 0.46.x) the installer is failing everytime, using Windows 11.

I retryed it several time, without any success.
When I finally abort the update, I get the following error message:

Here are the last lines of the named log file:

Feb 26 06:24:22.785 INFO Collected all directories and file handles
Feb 26 06:24:22.820 INFO All file handles marked for deletion
Feb 26 06:24:23.095 INFO All files deleted
Feb 26 06:24:23.095 INFO Delete directory recursively: "C:\\Users\\foo\\AppData\\Local\\Programs\\cursor\\locales" (attempt 1)
Feb 26 06:24:23.095 INFO Delete directory recursively: "C:\\Users\\foo\\AppData\\Local\\Programs\\cursor\\resources" (attempt 1)
Feb 26 06:24:23.489 INFO Rename: "chrome_100_percent.pak" (attempt 1)
Feb 26 06:24:23.490 INFO Rename: "chrome_200_percent.pak" (attempt 1)
Feb 26 06:24:23.490 INFO Rename: "Cursor.exe" (attempt 1)
Feb 26 06:24:23.490 INFO Rename: "Cursor.VisualElementsManifest.xml" (attempt 1)
Feb 26 06:24:23.490 INFO Rename: "d3dcompiler_47.dll" (attempt 1)
Feb 26 06:24:23.491 INFO Rename: "ffmpeg.dll" (attempt 1)
Feb 26 06:24:23.491 INFO Rename: "icudtl.dat" (attempt 1)
Feb 26 06:24:23.491 INFO Rename: "libEGL.dll" (attempt 1)
Feb 26 06:24:23.492 INFO Rename: "libGLESv2.dll" (attempt 1)
Feb 26 06:24:23.492 INFO Rename: "LICENSES.chromium.html" (attempt 1)
Feb 26 06:24:23.492 INFO Rename: "locales" (attempt 1)
Feb 26 06:24:23.493 INFO Rename: "resources" (attempt 1)
Feb 26 06:24:23.497 INFO Rename: "resources.pak" (attempt 1)
Feb 26 06:24:23.497 INFO Rename: "snapshot_blob.bin" (attempt 1)
Feb 26 06:24:23.498 INFO Rename: "tools" (attempt 1)
Feb 26 06:24:23.549 INFO Rename: "tools" (attempt 2)
Feb 26 06:24:23.750 INFO Rename: "tools" (attempt 3)
Feb 26 06:24:24.203 INFO Rename: "tools" (attempt 4)
Feb 26 06:24:25.006 INFO Rename: "tools" (attempt 5)
Feb 26 06:24:26.257 INFO Rename: "tools" (attempt 6)
Feb 26 06:24:28.059 INFO Rename: "tools" (attempt 7)
Feb 26 06:24:30.510 INFO Rename: "tools" (attempt 8)
Feb 26 06:24:33.711 INFO Rename: "tools" (attempt 9)
Feb 26 06:24:37.762 INFO Rename: "tools" (attempt 10)
Feb 26 06:24:42.764 INFO Rename: "tools" (attempt 11)
Feb 26 06:24:49.003 INFO Rename: "tools" (attempt 1)
Feb 26 06:24:49.056 INFO Rename: "tools" (attempt 2)
Feb 26 06:24:49.258 INFO Rename: "tools" (attempt 3)
Feb 26 06:24:49.709 INFO Rename: "tools" (attempt 4)
Feb 26 06:24:50.511 INFO Rename: "tools" (attempt 5)
Feb 26 06:24:51.762 INFO Rename: "tools" (attempt 6)
Feb 26 06:24:53.564 INFO Rename: "tools" (attempt 7)
Feb 26 06:24:56.015 INFO Rename: "tools" (attempt 8)
Feb 26 06:24:59.217 INFO Rename: "tools" (attempt 9)
Feb 26 06:25:03.268 INFO Rename: "tools" (attempt 10)
Feb 26 06:25:08.269 INFO Rename: "tools" (attempt 11)
Feb 26 06:25:52.333 INFO Rename: "tools" (attempt 1)
Feb 26 06:25:52.384 INFO Rename: "tools" (attempt 2)
Feb 26 06:25:52.585 INFO Rename: "tools" (attempt 3)
Feb 26 06:25:53.038 INFO Rename: "tools" (attempt 4)
Feb 26 06:25:53.839 INFO Rename: "tools" (attempt 5)
Feb 26 06:25:55.091 INFO Rename: "tools" (attempt 6)
Feb 26 06:25:56.892 INFO Rename: "tools" (attempt 7)
Feb 26 06:25:59.343 INFO Rename: "tools" (attempt 8)
Feb 26 06:26:02.544 INFO Rename: "tools" (attempt 9)
Feb 26 06:26:06.596 INFO Rename: "tools" (attempt 10)
Feb 26 06:26:11.597 INFO Rename: "tools" (attempt 11)
Feb 26 06:26:22.285 ERRO Zugriff verweigert (os error 5)

In Windows programms I do have two “Cursor” apps listed now:

But as soon as this failed update happens, I can not launch the Cursor app anymore!
I do have to install it again. And everytime I close it (later), the next update process will be started, leading to a broken installation as reported. :frowning_face:

I’ve already checked my anti virus for some quarantained cursor files, but there is nothing.

I also can see, that there are some other guys struggling - see the comments of this thread: [SOLVED] Failed Cursor Second update for the day. Unable to Reinstall

Please urgently provide a fix!

Thanks for some help and hopefully a fix!

Ok, I think there is already another big thred for this topic:

Didn’t see it when creating the bug entry here, sorry


Installing the 0.46 update directly solved it for me, thanks to @Jorn

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