[NETSDKE2E][ARM64].net9preview4sdk can't be used on ARM64OS.

[v-ainigao]

Build:
9.0.100-preview.4.24253.11

Repro steps:
1.Install .net9 preview4 SDK on arm64.
2.run dotnet --info on CLI.

Expected Result:
dotnet --info can be displayed normally and the project can be created without any problems.

Actual Result:
dotnet --info is not fully loaded and the project can't build and run.

[v-ainigao]

This memory dump file has been placed in this path. \mlangfs1\public\v-aini\arm64dump.zip

[v-ainigao]

Installing some workloads can be successful.
dotnet workload install maui --skip-manifest-update

dotnet workload install wasm-tools

But the dotnet workload list will also get stuck.

[v-ainigao]

This issue also repro's on arm64OS with .net9preview5SDK(9.0.100-preview.5.24256.12) installed.

The project can be created successfully, but it does not jump to the next line.

However, it took a long time and the build is still in progress

@richaverma1 Hi richa, can you help me take a look?

[LoopedBard3]

Hello, my team is also seeing this hang after ".Net workloads installed:" is printed when running dotnet --info on our windows arm64 machines. The latest failure we have seen has been with .NET SDK version: 9.0.100-preview.5.24257.6 with the last working version being 9.0.100-preview.4.24215.2. We are seeing this hang specifically on Windows ARM64 devices, or Linux ARM64 devices are still running as expected.

[LoopedBard3]

@ViktorHofer, do you happen to know the correct person/group to cc for this? I suspect it to be under the area src/CLI, but am having trouble figuring out which group to choose based on the CODEOWNERS file. Thanks!

[mangod9]

we are trying to investigate. @LoopedBard3, are you able to get things work after setting DOTNET_LegacyExceptionHandling=1 ?

[LoopedBard3]

Yes, that seems to fix the issue.

[mangod9]

ok good to know, believe there has been a fix recently for it: #101971

[Forgind]

@mangod9,
Should this be moved over the runtime repo then?