Problem with slow performance in Windows

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I was having some slowdown issues, so I decided to remove my project folder from the Windows Defender list;

After that, I ran Cursor as administrator;

Then I closed it and exited administrator mode;

Removing the project folder from the Windows Defender list already helped a lot;

Possible bug: the cursor no longer sends notifications, or the problem is with Windows, I’m not sure, but I thought it was good to share.

(Cursor is wonderful, so I came to share something I found useful.)

Steps to Reproduce

Its in the description.

Operating System

Windows 10/11

Version Information

Version: 2.6.22 (user setup)
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.18363

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for sharing this tip. Excluding project folders from Windows Defender is a solid way to improve performance on Windows. Real-time scanning can slow things down, especially with large projects that have lots of files.

About notifications after running as administrator, this is probably a Windows behavior, not a Cursor bug. When you run an app as administrator and then switch back, Windows can sometimes reset notification permissions. Please check Windows Settings > System > Notifications and make sure Cursor is allowed to send notifications.

If it still happens, feel free to open a separate topic with more details and we can take a look.

1 Like

Hi Dean;

Thank you for the feedback, it was really accurate.

For some reason, after I set the Windows Defender project folder to be deleted, the folder was marked as “read only”;

I realized that marking only node_modules is better;

For some reason, the “read only” marking by Windows doesn’t directly affect all files, nor did it affect anything noticeable to me;

But when I sent the project to Android Studio, using “npx cap sync android” (something normal for me), Android Studio started displaying several errors in the build;

I had to use icacls /reset /inheritance:e /T /C to be able to delete the build folder from the Android directory of my project, because Windows started demanding administrator permission even though I was the owner, something quite typical of it. Basically, the command reset the permissions, reactivated inheritance, and applied it recursively, finally allowing me to delete the folder without restrictions.

After that, everything went back to normal.

1 Like