-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Winforms/WPF .NET9.0 app cannot be ran on Windows 10 20H2(OS build 19042.2965) #43115
Comments
https://learn.microsoft.com/en-us/lifecycle/products/windows-10-enterprise-and-education shows support for Windows 10 Enterprise version 20H2 ended on May 9, 2023. https://learn.microsoft.com/en-us/dotnet/core/install/windows#supported-versions says .NET is not supported on end-of-life versions of Windows. |
@Olina-Zhang - are you sure this is specific to Windows 10 20H2(OS build 19042.2965)? Otherwise it looks like a dupe of dotnet/msbuild#10579 |
The screen shot shows a "Faulting application" error in the Application event log. dotnet/msbuild#10579 would not cause that. |
@Tanya-Solyanik Today I verified more Windows versions, It also reproes in Windows 10 21H1, but not Windows 10 21H2 and above. This issue is about created Winforms/WPF apps cannot be ran. |
@merriemcgaw are there any known issues with Windows 10 21H1? |
With Win10 21H1 in general or with WinForms? I think this issue is the one report I've seen for WinForms. |
@merriemcgaw this issue is about Winforms/WPF app failed to use CLI |
Describe the bug
Winforms/WPF .NET9.0 app cannot be ran on Windows 10 20H2(OS build 19042.2965) and Windows 10 21H1, but .NET 8.0 apps work well
To Reproduce
Install the latest .NET 9.0 RC2 SDK build from: https://github.com/dotnet/sdk/blob/main/documentation/package-table.md
Create a Winforms application by CLI
Build and run created Winforms application by CLI
Actual result:
dotnet build
successfully, butdotnet run
failed with nonsense characters output, Winforms runtime doesn't displayThe text was updated successfully, but these errors were encountered: