VS Code: "Unable to resolve configuration with compilerPath" and #include error

Development Programming & Scripting
1

After updating to 4.27.1 I have been having trouble with VS Code.
Firstly, all the #include are giving error. I have tried all the fixes but nothing seems to work.
Secondly, the output tab on the bottom is saying “Unable to resolve configuration with compilerPath “C:\Program”. Using “cl.exe” instead.” multiple times.

352768-untitled.png

352769-2.png
352769-2.png974×404 50.5 KB

Everything is working fine in the engine, so it appears to be a problem with vscode. This is only happening in this version of the engine. Is it a bug or something?

Here is what the properties file looks like, in case it is related.

352771-3.png
352771-3.png1212×459 24.6 KB

Im not sure this is a serious problem, just need help understanding what is going on as it is really annoying for the whole page to be marked red with errors.

Thanks a lot!

2

Hi! Got the same issue here, seems that the spaces from the command paths from compileCommands_Default.json are causing the compilerPath problem

1 Like
3

any solution?

4

See this post : UE 4.27 how to fix issues in visual studio code: "red squiggles" and "Unable to resolve configuration with compilerPath C:\Program"

5

Adding VS Code extension named <> by rhighs solved the issue for me. Once added that extension we need to manually check the (UEIntellisense Fixes: Enable Fixes) and (UEIntellisense Fixes: Enable Optional Fixes) and restart the Code to solve the errors.
Link :

2 Likes
6

i got the solution right here :

GameDev.tv – 24 Mar 21

#include errors detected in VS Studio Code

Could you try down grading to the latest stable release? 1.2.2? You can do that via this menu

its a very simple problem and you can fix it by simply down grading version of the C/C++ extension to 1.2.2

3 Likes
7

I know it’s been a couple years since you posted this, but, if you’re still in the dev community, I just wanted to say THANK YOU so much! I have been having such a problem with these errors (even downloaded an older version of Unreal to try to fix it) but nothing worked. This plugin saved me. Thank you, again, for posting about it!