Platform Win64 is not valid for UE 5.6

[jonpas]

Using ue4-docker:master (for BuildUBT.sh fix, but also included in patches, also tried with ue4-docker:v0.0.116) and some patches for UE 5.6 (see top 3 commits on https://github.com/IDI-Systems/UnrealEngine/commits/5.6.0-release-docker-fix/).

$ ue4-docker build custom:5.6.0 -repo https://github.com/IDI-Systems/UnrealEngine.git -branch=5.6.0-release-docker-fix -isolation=process --target=full --visual-studio 2022 --exclude debug --exclude templates --monitor
...
Unknown argument 'VS2022' for 'C:\UnrealEngine\Engine\Build\InstalledEngineBuild.xml'
...
Platform Win64 is not a valid platform to build. Check that the SDK is installed properly and that you have the necessary platform support files (DataDrivenPlatformInfo.ini, SDK.json, etc).
...
Result: Failed (OtherCompilationError)

[ChilledCosmonaut]

I currently have the same issue for 5.5.4.
An error gets thrown at Build Stage 2: ****** [2/12] Compile UnrealEditor Win64.

The error is:

Platform Win64 is not a valid platform to build. Check that the SDK is installed properly and that you have the necessary platform support files (DataDrivenPlatformInfo.ini, SDK.json, etc).
Took 0.99s to run dotnet.exe, ExitCode=6

[emilianomaccaferri]

I have the same issue building 5.6
edit: I found out about this, I'll try it out tomorrow.

[emilianomaccaferri]

I have the same issue building 5.6 edit: I found out about this, I'll try it out tomorrow.

I added that vsconfig file to the Windows Dockerfile like this:

...
COPY visual-studio-2022.vsconfig C:\
...

and then I used it via the $vs_args variable:

$vs_args = @(
    "--quiet",
    "--wait",
    "--norestart",
    "--nocache",
    "--installPath", "C:\BuildTools",
    "--channelUri", "https://aka.ms/vs/$visual_studio_build/release/channel",
    "--installChannelUri", "https://aka.ms/vs/$visual_studio_build/release/channel",
    "--channelId", "VisualStudio.$visual_studio_build.Release",
    "--productId", "Microsoft.VisualStudio.Product.BuildTools",
    "--locale", "en-US",
    "--add", "Microsoft.VisualStudio.Workload.VCTools",
    "--add", "Microsoft.VisualStudio.Workload.MSBuildTools",
    "--add", "Microsoft.VisualStudio.Component.VC.14.38.17.8.x86.x64",
    "--add", "Microsoft.VisualStudio.Component.Windows10SDK.$windows_sdk_version",
    "--add", "Microsoft.VisualStudio.Component.NuGet",
    "--add", "Microsoft.Net.Component.4.5.TargetingPack",
    "--add", "Microsoft.Net.Component.4.6.2.TargetingPack",
    "--add", "Microsoft.Net.ComponentGroup.DevelopmentPrerequisites",
    "--add", "Microsoft.NetCore.Component.SDK",
    "--add", "Microsoft.NetCore.Component.Runtime.3.1",
    "--config", "C:\visual-studio-2022.vsconfig"
)

and the error went away and I was able to build the engine (until I encountered a compilation error, unrelated to this repo I think, since we're using a custom UE5.6 build).
I don't know if this fully fixes the issue since I only got to the point from where the engine starts building, but it looks promising.

[IEVin]

MS has renamed Windows10SDK to Windows11SDK.
Use:

"--add", "Microsoft.VisualStudio.Component.Windows11SDK.22621"

instead of

"--add", "Microsoft.VisualStudio.Component.Windows10SDK.$windows_sdk_version"

But this way may cause problems with older engine versions and requires checking the supported SDK versions for them.

[slonopotamus]

https://learn.microsoft.com/en-us/answers/questions/2280142/msb8026-the-windows-sdk-version-10-0-20348-0-was-n

Nice... They just dropped 10.0.20348 Windows SDK.