I cannot create a project in D:/

Development Programming & Scripting C++
,
1

here is the report

Running D:/UE_5.8/Engine/Build/BatchFiles/Build.bat -projectfiles -project=“D:/Unreal Projects/ironandblood/ironandblood.uproject” -game -rocket -progress
Using bundled DotNet SDK version: 10.0 win-x64
Running UnrealBuildTool: dotnet “..\..\Engine\Binaries\DotNET\UnrealBuildTool\UnrealBuildTool.dll” -projectfiles -project=“D:/Unreal Projects/ironandblood/ironandblood.uproject” -game -rocket -progress
Log file: C:\Users\??巵ĵ???\AppData\Local\UnrealBuildTool\Log_GPF.txt

Some Platforms were skipped due to invalid SDK setup: Win64.
See the log file for detailed information

Generating VisualStudio project files:
Discovering modules, targets and source code for project…
Writing automation project files took 0.07s
Unexpected ProjectFileFormat ‘Default’

Result: Failed (OtherCompilationError)
Total execution time: 7.50 seconds

what should I do to solve it

2

The log is two separate failures, and the D: drive is not what failed.

  1. Win64 was skipped. “Some Platforms were skipped due to invalid SDK setup: Win64” means UBT cannot see a Windows C++ toolchain, so it will not emit a usable VS project. Install Visual Studio 2022 with the “Game development with C++” workload (MSVC v143, the Windows 10/11 SDK). Then generate again.

  2. Unexpected ProjectFileFormat ‘Default’ is UBT rejecting the format string Default. That value is stored in %APPDATA%\Unreal Engine\UnrealBuildTool\BuildConfiguration.xml, under ProjectFileGenerator / Format. Set Format to VisualStudio2022, or delete that xml so UBT falls back. Then run:

GenerateProjectFiles.bat -project=“D:\Unreal Projects\ironandblood\ironandblood.uproject” -game -2022

A space in “Unreal Projects” is fine when the path is quoted. Build.bat -projectfiles hits the same generator, so the format error stays until the xml is fixed. The quotes in the command have to be straight quotes. The ones in the post look curly, and curly quotes make the project path invalid.

  1. The log path is C:\Users<garbled>\AppData\Local\UnrealBuildTool\Log_GPF.txt. A Windows username with non-ASCII characters breaks a lot of UBT and SDK detection, and the mojibake in that path is the symptom. If Win64 is still “invalid” after VS 2022 is installed, that username is the next suspect. An ASCII-only Windows account, with the engine and the project kept on D:, avoids it.

After the xml change, generate once from a normal cmd window. The new Log_GPF.txt in that same AppData folder should no longer contain the Default line or the Win64 skip line.