Can't create any c++ projects

Hello, I can’t create any c++ projects I uninstalled 4.26 but i still get the error it is the same with 4.25 …

Here is the error message :

The project could not be compiled. Would you like to open it in Visual Studio?

Running C:/Program Files/Epic Games/UE_4.26/Engine/Binaries/DotNET/UnrealBuildTool.exe Development Win64 -Project="D:/Documents/UnrealProjects/ProjectS/ProjectS.uproject" -TargetType=Editor -Progress -NoEngineChanges -NoHotReloadFromIDE
Creating makefile for ProjectSEditor (no existing makefile)
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> NetCore.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> NetCore -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> SlateCore.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> SlateCore -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> SlateCore.Build.cs -> InputCore.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> SlateCore -> InputCore -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> Slate.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> Slate -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> Slate.Build.cs -> ImageWrapper.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> Slate -> ImageWrapper -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> Messaging.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> Messaging -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> MessagingCommon.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> MessagingCommon -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on ProjectS.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> RenderCore.Build.cs -> ProjectS.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> RenderCore -> ProjectS.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> EngineMessages.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> EngineMessages -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> PacketHandler.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> PacketHandler -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> PropertyAccess.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> PropertyAccess -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on ProjectS.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> ProjectS.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> ProjectS.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> PortalRpc.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> PortalRpc -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Circular dependency on CoreUObject.Build.cs detected.
       	Full Route: Target -> Launch.Build.cs -> SessionServices.Build.cs -> Core.Build.cs -> SourceCodeAccess.Build.cs -> Settings.Build.cs -> CoreUObject.Build.cs -> ProjectS.Build.cs -> Engine.Build.cs -> PerfCounters.Build.cs -> CoreUObject.Build.cs
       	Cycled Route: is SourceCodeAccess -> Settings -> CoreUObject -> ProjectS -> Engine -> PerfCounters -> CoreUObject.
       Break this loop by moving dependencies into a separate module or using Private/PublicIncludePathModuleNames to reference declarations
ERROR: Module 'Launch' (Engine) should not reference module 'ProjectS' (Project). Hierarchy is Project -> Engine Programs -> Engine Plugins -> Engine.

I hope someone can help me

I had the same issue. While reading your logs I noticed that you named your project “ProjectS”. I gave my project the same name, had the same issue. Named it to something other than “ProjectS” and the error went away. Just name it something else.

Really ?! The name of the project f up everything… That’s an interesting lesson thanks

Hello,

We’ve made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.

Thanks