UE5.vcxproj Warnings when Opening Cloned Project Inside VS2022

I get the following warnings when opening a cloned/converted (I think 4.26) project:

Project\Intermediate\ProjectFiles\UE5.vcxproj : warning  : The build tools for Visual Studio 2022 (v143) cannot be found. Install Visual Studio 2022 (v143) to build using the Visual Studio 2022 (v143) build tools.

Project\Intermediate\ProjectFiles\UE5.vcxproj : warning  : Platform 'Win64' referenced in the project file 'UE5' cannot be found.

I found a few topics related to this, like this one, but since UE5.vcxproj is autogenerated (I tried deleting intermediate) I don’t think this is the root cause. Also, this happens only for the cloned project, and it does not appear when opening a newly created project in UE5 (Both projects point to the same folder, and I only have one engine version currently installed anyway).

I tried deleting VS2019, and reinstall VS2022, verify UE5 and this did not help either.

I can compile, and run fine so far.

2 Likes

Did you ever figure it out? I am having same issue except my project is a Lyra based project. And I didn’t have the issue when I first created the project. It just started showing me the warning a few days ago. Seen this post and figured I’d save myself from reinstalling VS2022.

Personally I have tried deleting the Intermediate folder and regenerating project files. That did not get rid of the warning. I gave up after that cause I dont know of anything else to do, and my project builds fine other than that warning.

Also, when I first created the project, it was fine. I just noticed it happening a few days ago. I been moving a blueprint actor component to be a C++ Actor component. I had changed a bunch of things so I dont remember exactly what it was, just before noticing it. Heck Windows was updated recently and could have been that update that caused it. Dont really want to roll back windows tho.

I’ve just encountered – for the first time – this same issue. Mine is on a renamed project, not a cloned one, but I suspect the root cause will turn out to be the name change.

What I’ve tried so far are these steps (where $PROJ is my top-level project directory):

  1. From $PROJ deleted Binaries, Intermediate, .vs, .vsconfig, and $PROJ.sln.
  2. Used “grep” (Linux text search utility) to find all occurrences of the old project name, then edited the files to change them to the new name.
  3. Right-clicked on $PROJ.uproject and regenerated the Visual Studio files.
  4. Opened $PROJ.sln in Visual Studio 2022.

After these steps, the VS error is still present.

My usual development tools are JetBrains Rider and the various Linux tools. I’m very new to VIsual Studio and not normally a Windows programmer. I’m not sure where to go next on solving this, so as a workaround I’m going to create a new project instead of trying to use this renamed one.

3 Likes

Hey guys. I had the same issue.

What worked for me was deleting the .vs folder, .vsconfig, Intermediate, Binaries, DerivedDataCache. I then used Switch Unreal Engine Version and chose the same version (I’m guessing this is the same as Generate Visual Studio Files)

This allowed the compile. I suspect the issue came from .vs folder or .vsconfig

6 Likes

can confirm this was the solution for me

in my case i just changed the projects directory and got this issue