[dotnet-sdk-7.0.100-alpha.1.21568.2] WinForms Samples app launch failed with error System.ComponentModel.Win32Exception (1400): Error creating window handle

[Junjun-zhao]

Description

When testing WinForms Samples app against runtime dotnet-sdk-7.0.100-alpha.1.21568.2, it failed to launch with error System.ComponentModel.Win32Exception

Reproduction Steps

App Source, App checking at: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1458251 Repro Steps for the Problematic App: Copy Apps\Winforms Samples from server to local machine. Launch MatchingGame.exe from Winforms Samples\matching-game

Minimal Repro steps: 1.Create a .NET 5.0 WinForm project. 2.Install MetroFramework nuget package from nuget.org. 3.Update the Form1.cs to inherit from MetroForm:

public partial class Form1 : MetroForm
    {
        public Form1()
        {
            InitializeComponent();
        }
    }

4.Build the project to generate WinFormApp1.exe 5.Launch the exe on a machine that only dotnet-sdk-7.0.100-alpha.1.21568.2 installed

Expected behavior

App launch successful.

Actual behavior

Launch failed with error

Regression?

Verify Scenarios: 1). Windows10 RS5 x64+dotnet-sdk-7.0.100-alpha.1.21568.2:Fail 2). Windows10 RS5 x64+dotnet-sdk-6.0.200-preview.21603.2: Pass

Known Workarounds

No response

Configuration

Application Name: WinForms Samples OS: Windows 10 RS5 CPU: X64 .NET Build Number: dotnet-sdk-7.0.100-alpha.1.21568.2

Other information

1) Launch failed with MatchingGame.exe: If we launch the dll with dotnet command from command prompt window, we will get below error message:

Unhandled exception. System.ComponentModel.Win32Exception (1400): Error creating window handle.
   at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
   at System.Windows.Forms.Control.CreateHandle()
   at System.Windows.Forms.Form.CreateHandle()
   at System.Windows.Forms.Control.get_Handle()
   at System.Windows.Forms.Control.SetVisibleCore(Boolean value)
   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
   at MetroFramework.Forms.MetroForm.SetVisibleCore(Boolean value)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(msoloop reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(msoloop reason, ApplicationContext context)
   at MatchingGame.Program.Main() in C:\.NETCoreUpgradeApps\AppSources\samples\windowsforms\matching-game\net5-windows\cs\MatchingGame\Program.cs:line 13

And we found this issue is caused by MetroFramework nuget package used in the project. But this package only one version. NuGet Gallery | MetroFramework 1.2.0.3

2)Launch failed with error with minimal demo WinFormsApp1.exe:

Application: WinFormsApp1.exe
CoreCLR Version: 7.0.21.56701
.NET Version: 7.0.0-alpha.1.21567.1
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception (1400): Error creating window handle.
   at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
   at System.Windows.Forms.Control.CreateHandle()
   at System.Windows.Forms.Form.CreateHandle()
   at System.Windows.Forms.Control.get_Handle()
   at System.Windows.Forms.Control.SetVisibleCore(Boolean value)
   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
   at MetroFramework.Forms.MetroForm.SetVisibleCore(Boolean value)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(msoloop reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(msoloop reason, ApplicationContext context)
   at WinFormsApp1.Program.Main() in E:\App Source\WinFormsApp1\WinFormsApp1\Program.cs:line 20

When using Windbg to launch the minimal demo WinFormsApp1.exe, we will get these:

(4f10.ba4): CLR exception - code e0434352 (first chance)
(4f10.ba4): CLR exception - code e0434352 (!!! second chance !!!)
CLR exception type: System.ComponentModel.Win32Exception
    "Error creating window handle."
*** WARNING: Unable to verify checksum for C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.0-alpha.1.21567.1\coreclr.dll
*** WARNING: Unable to verify checksum for C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\7.0.0-alpha.1.21566.3\System.Windows.Forms.dll
KERNELBASE!RaiseException+0x69:
00007fff`91c24f69 0f1f440000      nop     dword ptr [rax+rax]
0:000> k
*** WARNING: Unable to verify checksum for C:\Appcompat\applications\net5.0-windows\WinFormsApp1.dll
*** WARNING: Unable to verify checksum for C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.0-alpha.1.21567.1\hostpolicy.dll
*** WARNING: Unable to verify checksum for C:\Program Files\dotnet\host\fxr\7.0.0-alpha.1.21567.1\hostfxr.dll
*** WARNING: Unable to verify checksum for apphost.exe
 # Child-SP          RetAddr               Call Site
00 000000c8`5a37dfe0 00007fff`34ceeeb5     KERNELBASE!RaiseException+0x69
01 000000c8`5a37e0c0 00007fff`34dde3df     coreclr+0x4eeb5
02 000000c8`5a37e1b0 00007fff`0cb26c39     coreclr!coreclr_initialize+0x653ff
03 000000c8`5a37e310 00007fff`0c9c2637     System_Windows_Forms!
04 000000c8`5a37e3f0 00007fff`0cac7c1b     System_Windows_Forms!
05 000000c8`5a37e4b0 00007fff`0c9bd030     System_Windows_Forms!
06 000000c8`5a37e520 00007fff`0c9cf6c6     System_Windows_Forms!
07 000000c8`5a37e560 00007fff`0cac5d23     System_Windows_Forms!
08 000000c8`5a37e650 00007ffe`d5264456     System_Windows_Forms!
09 000000c8`5a37e6b0 00007fff`0cc78f99     MetroFramework!
0a 000000c8`5a37e6f0 00007fff`0cc78e58     System_Windows_Forms!
0b 000000c8`5a37e790 00007ffe`d524a093     System_Windows_Forms!
0c 000000c8`5a37e7f0 00007fff`34e04cf3     WinFormsApp1!
0d 000000c8`5a37e830 00007fff`34cb07b8     coreclr!MetaDataGetDispenser+0x12053
0e 000000c8`5a37e870 00007fff`34d7c97b     coreclr+0x107b8
0f 000000c8`5a37e9b0 00007fff`34d7c7fa     coreclr!coreclr_initialize+0x399b
10 000000c8`5a37eae0 00007fff`34d7c4ad     coreclr!coreclr_initialize+0x381a
11 000000c8`5a37eb90 00007fff`34d7bf76     coreclr!coreclr_initialize+0x34cd
12 000000c8`5a37ef20 00007fff`34d78c92     coreclr!coreclr_initialize+0x2f96
13 000000c8`5a37f090 00007fff`4fb5926b     coreclr!coreclr_execute_assembly+0xe2
14 000000c8`5a37f130 00007fff`4fb5959c     hostpolicy+0x1926b
15 000000c8`5a37f2d0 00007fff`4fb59f37     hostpolicy+0x1959c
16 000000c8`5a37f310 00007fff`4fbbb539     hostpolicy!corehost_main+0x107
17 000000c8`5a37f4c0 00007fff`4fbbe506     hostfxr!hostfxr_close+0xfb9
18 000000c8`5a37f5c0 00007fff`4fbc0821     hostfxr!hostfxr_close+0x3f86
19 000000c8`5a37f6c0 00007fff`4fbbeb62     hostfxr!hostfxr_close+0x62a1
1a 000000c8`5a37f770 00007fff`4fbb82ab     hostfxr!hostfxr_close+0x45e2
1b 000000c8`5a37f8b0 00007ff6`0acadc1c     hostfxr!hostfxr_main_startupinfo+0xab
1c 000000c8`5a37f9b0 00007ff6`0acadf81     apphost+0xdc1c
1d 000000c8`5a37fba0 00007ff6`0acaf4f8     apphost+0xdf81
1e 000000c8`5a37fd10 00007fff`92447034     apphost+0xf4f8
1f 000000c8`5a37fd50 00007fff`93f62651     KERNEL32!BaseThreadInitThunk+0x14
20 00000000`00000000 00000000`00000000     0x0

@dotnet-actwx-bot @dotnet/compat

[ghost]

Tagging subscribers to this area: @dotnet/area-system-componentmodel See info in area-owners.md if you want to be subscribed.

Issue Details

---

### Description When testing WinForms Samples app against runtime dotnet-sdk-7.0.100-alpha.1.21568.2, it failed to launch with error System.ComponentModel.Win32Exception ### Reproduction Steps **App Source, App checking at**: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1458251 **Repro Steps for the Problematic App**: Copy Apps\Winforms Samples from server to local machine. Launch MatchingGame.exe from Winforms Samples\matching-game **Minimal Repro steps:** 1.Create a .NET 5.0 WinForm project. 2.Install MetroFramework nuget package from nuget.org. 3.Update the Form1.cs to inherit from MetroForm: ``` public partial class Form1 : MetroForm { public Form1() { InitializeComponent(); } } ``` 4.Build the project to generate WinFormApp1.exe 5.Launch the exe on a machine that only dotnet-sdk-7.0.100-alpha.1.21568.2 installed ### Expected behavior App launch successful. ### Actual behavior Launch failed with error ### Regression? **Verify Scenarios**: 1). Windows10 RS5 x64+dotnet-sdk-7.0.100-alpha.1.21568.2:Fail 2). Windows10 RS5 x64+dotnet-sdk-6.0.200-preview.21603.2: Pass ### Known Workarounds _No response_ ### Configuration **Application Name**: WinForms Samples **OS**: Windows 10 RS5 **CPU**: X64 **.NET Build Number**: dotnet-sdk-7.0.100-alpha.1.21568.2 ### Other information 1) Launch failed with MatchingGame.exe: If we launch the dll with dotnet command from command prompt window, we will get below error message: ``` Unhandled exception. System.ComponentModel.Win32Exception (1400): Error creating window handle. at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp) at System.Windows.Forms.Control.CreateHandle() at System.Windows.Forms.Form.CreateHandle() at System.Windows.Forms.Control.get_Handle() at System.Windows.Forms.Control.SetVisibleCore(Boolean value) at System.Windows.Forms.Form.SetVisibleCore(Boolean value) at MetroFramework.Forms.MetroForm.SetVisibleCore(Boolean value) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(msoloop reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(msoloop reason, ApplicationContext context) at MatchingGame.Program.Main() in C:\.NETCoreUpgradeApps\AppSources\samples\windowsforms\matching-game\net5-windows\cs\MatchingGame\Program.cs:line 13 ``` And we found this issue is caused by MetroFramework nuget package used in the project. But this package only one version. NuGet Gallery | MetroFramework 1.2.0.3 2)Launch failed with error with minimal demo WinFormsApp1.exe: ``` Application: WinFormsApp1.exe CoreCLR Version: 7.0.21.56701 .NET Version: 7.0.0-alpha.1.21567.1 Description: The process was terminated due to an unhandled exception. Exception Info: System.ComponentModel.Win32Exception (1400): Error creating window handle. at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp) at System.Windows.Forms.Control.CreateHandle() at System.Windows.Forms.Form.CreateHandle() at System.Windows.Forms.Control.get_Handle() at System.Windows.Forms.Control.SetVisibleCore(Boolean value) at System.Windows.Forms.Form.SetVisibleCore(Boolean value) at MetroFramework.Forms.MetroForm.SetVisibleCore(Boolean value) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(msoloop reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(msoloop reason, ApplicationContext context) at WinFormsApp1.Program.Main() in E:\App Source\WinFormsApp1\WinFormsApp1\Program.cs:line 20 ``` When using Windbg to launch the minimal demo WinFormsApp1.exe, we will get these: ``` (4f10.ba4): CLR exception - code e0434352 (first chance) (4f10.ba4): CLR exception - code e0434352 (!!! second chance !!!) CLR exception type: System.ComponentModel.Win32Exception "Error creating window handle." *** WARNING: Unable to verify checksum for C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.0-alpha.1.21567.1\coreclr.dll *** WARNING: Unable to verify checksum for C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\7.0.0-alpha.1.21566.3\System.Windows.Forms.dll KERNELBASE!RaiseException+0x69: 00007fff`91c24f69 0f1f440000 nop dword ptr [rax+rax] 0:000> k *** WARNING: Unable to verify checksum for C:\Appcompat\applications\net5.0-windows\WinFormsApp1.dll *** WARNING: Unable to verify checksum for C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.0-alpha.1.21567.1\hostpolicy.dll *** WARNING: Unable to verify checksum for C:\Program Files\dotnet\host\fxr\7.0.0-alpha.1.21567.1\hostfxr.dll *** WARNING: Unable to verify checksum for apphost.exe # Child-SP RetAddr Call Site 00 000000c8`5a37dfe0 00007fff`34ceeeb5 KERNELBASE!RaiseException+0x69 01 000000c8`5a37e0c0 00007fff`34dde3df coreclr+0x4eeb5 02 000000c8`5a37e1b0 00007fff`0cb26c39 coreclr!coreclr_initialize+0x653ff 03 000000c8`5a37e310 00007fff`0c9c2637 System_Windows_Forms! 04 000000c8`5a37e3f0 00007fff`0cac7c1b System_Windows_Forms! 05 000000c8`5a37e4b0 00007fff`0c9bd030 System_Windows_Forms! 06 000000c8`5a37e520 00007fff`0c9cf6c6 System_Windows_Forms! 07 000000c8`5a37e560 00007fff`0cac5d23 System_Windows_Forms! 08 000000c8`5a37e650 00007ffe`d5264456 System_Windows_Forms! 09 000000c8`5a37e6b0 00007fff`0cc78f99 MetroFramework! 0a 000000c8`5a37e6f0 00007fff`0cc78e58 System_Windows_Forms! 0b 000000c8`5a37e790 00007ffe`d524a093 System_Windows_Forms! 0c 000000c8`5a37e7f0 00007fff`34e04cf3 WinFormsApp1! 0d 000000c8`5a37e830 00007fff`34cb07b8 coreclr!MetaDataGetDispenser+0x12053 0e 000000c8`5a37e870 00007fff`34d7c97b coreclr+0x107b8 0f 000000c8`5a37e9b0 00007fff`34d7c7fa coreclr!coreclr_initialize+0x399b 10 000000c8`5a37eae0 00007fff`34d7c4ad coreclr!coreclr_initialize+0x381a 11 000000c8`5a37eb90 00007fff`34d7bf76 coreclr!coreclr_initialize+0x34cd 12 000000c8`5a37ef20 00007fff`34d78c92 coreclr!coreclr_initialize+0x2f96 13 000000c8`5a37f090 00007fff`4fb5926b coreclr!coreclr_execute_assembly+0xe2 14 000000c8`5a37f130 00007fff`4fb5959c hostpolicy+0x1926b 15 000000c8`5a37f2d0 00007fff`4fb59f37 hostpolicy+0x1959c 16 000000c8`5a37f310 00007fff`4fbbb539 hostpolicy!corehost_main+0x107 17 000000c8`5a37f4c0 00007fff`4fbbe506 hostfxr!hostfxr_close+0xfb9 18 000000c8`5a37f5c0 00007fff`4fbc0821 hostfxr!hostfxr_close+0x3f86 19 000000c8`5a37f6c0 00007fff`4fbbeb62 hostfxr!hostfxr_close+0x62a1 1a 000000c8`5a37f770 00007fff`4fbb82ab hostfxr!hostfxr_close+0x45e2 1b 000000c8`5a37f8b0 00007ff6`0acadc1c hostfxr!hostfxr_main_startupinfo+0xab 1c 000000c8`5a37f9b0 00007ff6`0acadf81 apphost+0xdc1c 1d 000000c8`5a37fba0 00007ff6`0acaf4f8 apphost+0xdf81 1e 000000c8`5a37fd10 00007fff`92447034 apphost+0xf4f8 1f 000000c8`5a37fd50 00007fff`93f62651 KERNEL32!BaseThreadInitThunk+0x14 20 00000000`00000000 00000000`00000000 0x0 ``` @dotnet-actwx-bot @dotnet/compat

Author:	Junjun-zhao
Assignees:	ericstj
Labels:	`area-System.ComponentModel`
Milestone:	-

[dreddy-work]

@Junjun-zhao , if the app is targeting net5.0, how is it running on only net7.0? are you sure app is targeting net 7.0 and machine only has net 7.0 but not net5.0?

@Olina-Zhang , can you try if you guys can repro this?

[Junjun-zhao]

@dreddy-work Thanks for helping look into this issue. I'm from AppCompat team and doing third-party apps runtime combability validation with .NET 7 now. This issue was found when run the app against .NET 7.0 runtime.

You can Set the DOTNET_ROLL_FORWARD_ON_NO_CANDIDATE_FX environment variable to 2 to let the .NET 5.0 app run against .NET 7.0

[dreddy-work]

Reference, following is code snippet that throwing.

IntPtr modHandle = Kernel32.GetModuleHandleW(null);

                            // Older versions of Windows AV rather than returning E_OUTOFMEMORY.
                            // Catch this and then we re-throw an out of memory error.
                            try
                            {
                                // CreateWindowEx throws if WindowText is greater than the max
                                // length of a 16 bit int (32767).
                                // If it exceeds the max, we should take the substring....
                                if (cp.Caption is not null && cp.Caption.Length > short.MaxValue)
                                {
                                    cp.Caption = cp.Caption.Substring(0, short.MaxValue);
                                }

                                createResult = User32.CreateWindowExW(
                                    (User32.WS_EX)cp.ExStyle,
                                    windowClass._windowClassName,
                                    cp.Caption,
                                    (User32.WS)cp.Style,
                                    cp.X,
                                    cp.Y,
                                    cp.Width,
                                    cp.Height,
                                    cp.Parent,
                                    IntPtr.Zero,
                                    modHandle,
                                    cp.Param);

                                lastWin32Error = Marshal.GetLastWin32Error();
                  .
                  .
                  if (createResult == IntPtr.Zero)
                    {
                        throw new Win32Exception(lastWin32Error, SR.ErrorCreatingHandle);
                    }
``

[dreddy-work]

@Junjun-zhao, What is the scenario here? What is set DOTNET_ROLL_FORWARD_ON_NO_CANDIDATE_FX=2 doing here? can you retarget the app to .NET7.0 and run it? can you double click and run it? or its same issue with command line as well as double click? Can you please attach sample here or grant permission to us to access share in the linked Azdo item?

[PriyaPurkayastha]

Provided information to Devendar via Teams - DOTNET_ROLL_FORWARD_ON_NO_CANDIDATE_FX setting is to make app use the latest major runtime installed on the machine instead of using the .NET version that the app was built with. More details available in Roll Forward section of https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-2-1 Have also shared permissions to source and app binaries.

[ghost]

@dreddy-work The same stack info and ComponentModel.Win32Exception exception occurred when I was writing a program before. I'm not sure if it's similar to this current post. I might be able to provide some useful information.

When I upgrade my program from .net 4.8 to .net 5.0 :

.net 4.8 code:

namespace WinFormsApp1
{
    internal static class Program
    {
        [STAThread]
        static void Main()
        {
            Application.EnableVisualStyles();
            Application.SetCompatibleTextRenderingDefault(false);

            Application.Run(new Form1());
        }
    }
}

.net 5.0 code:

namespace WinFormsApp1
{
    internal static class Program
    {
        [STAThread]
        static void Main()
        {
            Application.EnableVisualStyles();
            Application.SetCompatibleTextRenderingDefault(false);
            Application.SetHighDpiMode(HighDpiMode.SystemAware);

            Application.Run(new Form1());
        }
    }
}

You can compare the difference between these two pieces of code. These are all from templates that come with Visual Studio.

If this statement is missing:

Application.SetHighDpiMode(HighDpiMode.SystemAware);

Since Visual Studio just upgrades the .net version number, it doesn't automatically add this statement for you.

Then in method Form.ShowDialog(), there is a certain probability that ComponentModel.Win32Exception will be prompted. It's not 100% wrong. It doesn't go wrong every time. But at indeterminate times, sometimes it goes wrong and sometimes it doesn't.

Currently I am using .net 6.0 With Win10 to run these codes. After the above adjustment, there is basically no Exception.

[Junjun-zhao]

@dreddy-work

can you retarget the app to .NET7.0 and run it?

When retargeting the app to .NET7.0 and run it from Visual Studio, We get the same exception, see screenshot from Visual Studio:

can you double click and run it? or its same issue with command line as well as double click?

If we double click to run the exe directly, the app doesn't launch and we can see the same error message from Event Viewer.

In addition, we have tested with dotnet-sdk-7.0.100-alpha.1.22057.7, issue still exists.

[ghost]

@Junjun-zhao

You can see my previous content in this post.

Add this statement to your code:

Application.SetHighDpiMode(HighDpiMode.SystemAware);

It might solve the problem. This could be a bug due to DPI.

Full Sample Code:

namespace WinFormsApp1
{
    internal static class Program
    {
        [STAThread]
        static void Main()
        {
            Application.EnableVisualStyles();
            Application.SetCompatibleTextRenderingDefault(false);
            Application.SetHighDpiMode(HighDpiMode.SystemAware);

            Application.Run(new Form1());
        }
    }
}

[Junjun-zhao]

@roland5572 Thanks for your comments for this issue. We have tried after adding Application.SetHighDpiMode(HighDpiMode.SystemAware);, this issue still repro with same error.

[Olina-Zhang]

@Olina-Zhang , can you try if you guys can repro this?

As issue's steps, it can repro on a machine with just .net 7.0 installed and that environment variables set. And it also repro when retargeting app from .net 5.0 to .net 7.0 in VS. Here is the .net 5.0 testing app with MetroFramework nuget package: WinFormsApp9.zip

More Info: If skip to install MetroFramework nuget package, it cannot repro.

[Tanya-Solyanik]

@roland5572 - if you could collect a crash dump. or call stack for exception related to the lack of Application.SetHighDpiMode(HighDpiMode.SystemAware);, could you please open a dedicated issue?

[ghost]

@Tanya-Solyanik Missing this statement can make the program unstable, but it won't fire 100% of the time. I'll try this bug again in the next few days. I'm not sure if the current .NET version has fixed this. If it still happens, I will create a new post.

[Olina-Zhang]

And also verified this issue using that testing app with MetroFramework nuget package on a just .Net 6.0 SDK: 6.0.200-preview.22055.15, it cannot repro.

[merriemcgaw]

@Olina-Zhang when you run the app skipping the MetroFramework what do you get? Does the matching game correctly load and execute? This Framework was last touched in 2013. Though I don't know what changed in 7.0 that would have impacted this at all.

[Olina-Zhang]

@merriemcgaw If skip to install MetroFramework nuget package, this issue cannot repro, our form is launched successfully after executed sample app exe.

[merriemcgaw]

At some point I'd love to see what is in that MetroFramework package and debug to see what has changed with .NET 7. @dreddy-work is this something we could get on your backlog (pretty low down of course 😉 )?

[Junjun-zhao]

@Tanya-Solyanik Do you have any update for this bug? We still repro this with build dotnet-sdk-7.0.100-preview.3.22179.4

[merriemcgaw]

@Olina-Zhang do you think your team would be able to try to repro this to see if it's still a problem?

[Olina-Zhang]

@merriemcgaw It also reproduces the application with MetroFramework nuget package in the latest .Net 8 SDK build: 8.0.100-preview.2.23121.12.

[merriemcgaw]

Thank you for the seriously fast turnaround here! 💥

[Tanya-Solyanik]

Duplicate of https://github.com/dotnet/winforms/issues/8803

[Junjun-zhao]

Verified and issue is fixed on dotnet-sdk-8.0.100-preview.3.23178.7.