[ARM64]The Form1.cs[Design] page cannot load successfully after installed the latest .NET 9.0 Preview4 or Preview5

[Forgind]

---

Issue moved from dotnet/sdk#40786

• Please respond to @Zheng-Li01.

---

From @Zheng-Li01 on Thursday, May 9, 2024 8:01:14 AM

SDK Versions:
Bad SDK: dotnet-sdk-9.0.100-preview.5.24258.8-win-arm64 & dotnet-sdk-9.0.100-preview.4.24258.4-win-arm64
Good SDK: dotnet-sdk-9.0.100-preview.3.24204.13-win-arm64

Visual Studio Versions:
17.11.0 Preview 1.0 [34908.277.d17.11] & 17.11.0 Preview 2.0 [34908.267.main]

Describe the bug

The Form1.cs[Design] page cannot load successfully after installed the latest .NET 9.0 Preview4 & Preview5 on the ARM64 machine

To Reproduce

1. Install the latest .NET 9.0 Preview4 or Preview5 Windows arm 64 from https://github.com/dotnet/installer
2. Create a .NET WinForms project targeting to .NET 9.0
3. Observe the Form1.cs[Design] page

Expected Result:
The Form1.cs[Design] page can load successfully after installed the latest .NET 9.0 Preview4 & Preview5 on the ARM64 machine,

Actual Result:
Preview5Results
The Form1.cs[Design] page cannot load successfully after installed the latest .NET 9.0 Preview4 & Preview5 on the ARM64 machine, and the Visual Studio will not be responding after clicked anywhere.


Preview4Results

More info:

1. The issue cannot reproduce Windows x64 platform with same sdk version.
2. The issue cannot reproduce after installed latest .NET 9.0 Preview3 from https://dotnet.microsoft.com/en-us/download/dotnet on the ARM64 machine
3. The issue also can reproduce on the .NET 9.0 Preview4.24257.5(arm64) which bring in PR https://devdiv.visualstudio.com/DevDiv/_git/VS/pullrequest/525045,

[Forgind]

---

Issue moved from dotnet/sdk#40786

• Please respond to @dotnet-issue-labeler[bot].

---

From @dotnet-issue-labeler[bot] on Thursday, May 9, 2024 8:01:20 AM

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[Tanya-Solyanik]

duplicate of dotnet/runtime#102056

[Zheng-Li01]

dotnet/runtime#102056 (comment) this workaround working well.