Configured debug type 'cppvsdbg' is installed by not supported in this environment

[FocuzJS]

1) If you can, please include a screenshot of your problem 2) Please include the name of your operating system 3) If you can, steps to reproduce are super helpful

Operating System: Windows 10

• Create a CPP project using the run & debug feature of VSCode via the tasks.json/launch.json files
• Try to run & debug a project with 'cppvsdbg' as the type

The above works fine in my VSCode but it would be really nice if I could also use this feature in Cursor and to my knowledge I don't believe the issue to be on my side.

[jamesnolanverran]

Yes I have the same problem.

[vector76]

I am having the same problem.

I am on Windows 11

[ken-noland]

On Windows 10 here and getting the same issue. I heard somewhere that this may be due to Microsoft limiting some stuff behind their official VSCode builds. Not sure if that is the case here, but I thought I should at least comment. Please let me know if I am wrong.

[pidn666]

Me too

I am having the same problem.

I am on Windows 11

Now on August 8, 2024, the latest version of cursor hasn't solved this problem. Do you guys have any other solutions?

[aiyolo]

me too

[tedmiddleton]

I'm getting this too. That's too bad because this is a show-stopper for me.

[tedmiddleton]

This is the version of Cursor I'm using:

This is the version of VSCode (which works) that I'm using:

[tedmiddleton]

This is kind of too bad. I love what I've seen the last week with Cursor.

But if Cursor breaks on something like an extension setting like this, it means Cursor is probably implemented in a fairly fragile kind of way and can probably be expected to break a lot on non-standard environments and non-standard workflows.

Visual studio c++ on Windows is already pretty non-standard in the whole software development milieu, and msvc within VS Code is even more non-standard. I'm wondering if this development path, using Cursor.ai, will ever really work. This is a completely show-stopping bug that has been around for literally a year now and it doesn't seem to be any closer to being fixed.

Working with a new dev tool is an investment. You have to spend time and mental energy setting up a comfortable and productive environment, and if Cursor is just going to break every once in a while, I'm not sure it's really worth getting to know - not only for C++ but for python and typescript and my other dev environments. The one saving grace here is if Cursor was working and it broke again, I could probably just uninstall it and revert to using VC code + copilot.

Anyhoo, we'd really appreciate a fix, here.

[TannerHollis]

same issure here:

Version: 0.39.6 VSCode Version: 1.91.1 Commit: a4f99b7dfb14460cb0bcebd9f6ac7ca158217920 Date: 2024-08-19T00:03:08.275Z Electron: 29.4.0 ElectronBuildId: undefined Chromium: 122.0.6261.156 Node.js: 20.9.0 V8: 12.2.281.27-electron.0 OS: Windows_NT x64 10.0.19045

[JonathanRosado]

That's too bad. Bought the subscription yesterday and already faced with a showstopper.

[pidn666]

I'd like to ask what the official stance is on this issue. I don't know if this will be addressed officially in the future, or a way to bypass it will be provided.

[SEI-John]

I was thinking of moving to cursor for my C++ apps, and hit with this showstopper too

[blizzzrdda]

I figured out the solution. Now I can run UE5 with cursor.

The problem is caused by cppvsdbg, as well as vsdbg, which is exclusively licensed by Microsoft product.

To solve this, you need to set up your debugger. I use GCC with MinGW.

[wuzhi22]

How exactly should I set up the debugger, I have installed g++,gcc, etc debug

[wuzhi22]

Should I select launch VsCodeCursorEditor(Development)(workspace) for debugging

[tedmiddleton]

I figured out the solution. Now I can run UE5 with cursor.

The problem is caused by cppvsdbg, as well as vsdbg, which is exclusively licensed by Microsoft product.

To solve this, you need to set up your debugger. I use GCC with MinGW.

That's very frustrating, and for many users just switching to gcc isn't really an option.

But I guess we have our answer.

[hushengkai]

sad,I am hesitating whether to switch from GitHub+vs to this, I use UE5 .

[hushengkai]

I figured out the solution. Now I can run UE5 with cursor.

The problem is caused by cppvsdbg, as well as vsdbg, which is exclusively licensed by Microsoft product.

To solve this, you need to set up your debugger. I use GCC with MinGW.

Thank you for your method, but I think MSVC is the best way to debug UE5, and it seems that it doesn't complete much of the program I wrote myself. I wonder if this is the case when you developed with UE5

[RetroSteve0]

It really is a shame. I ran into the same issue too. Unfortunately, this is out of Cursor's control. These build tools are proprietary and Microsoft doesn't allow them to be used outside of the official builds of VS Code. Fortunately, I personally was able to just install GCC and was able to compile my program and run successfully. If you can, use GCC. If you can't, you're just going to have to use Cursor to write code, then use Visual Studio or the official VS Code client to build and debug.

[benrbowers]

https://github.com/microsoft/vscode-cpptools/issues/4707#issuecomment-562670907

Yeah I think this is a deeper issue. May just have to use vanilla vscode if you want to use cppvsdbg for c++ projects for now

[yog-ARK]

Facing the same problem. The extension has been installed. Environment variables are set.

[RetroSteve0]

Facing the same problem. The extension has been installed. Environment variables are set.

Open the Command Pallet (Ctrl+Shift+P), and set the C++ compiler to use GCC. That should do the trick far as C/C++ goes.