MenuFlyout leaves unclickable region after main app has been minimized and restored via task bar

[437569]

Describe the bug

If a user opens a context menu in WinUI3 app, leaves the menu open and clicking on the app button in task bar to minimize and restore the app, the context menu will disappear but the region will be unclickable.
It happens on Win 11 machine but not on our Win 10 environment.

Steps to reproduce the bug

1. Create a simple WinUI3 app using template studio and add a context menu using MenuFlyout

            <NavigationView.ContextFlyout>
                <MenuFlyout>
                    <MenuFlyoutItem Text="Option 1" />
                    <MenuFlyoutItem Text="Option 2" />
                    <MenuFlyoutItem Text="Option 3" />
                </MenuFlyout>
            </NavigationView.ContextFlyout>

2. Build the app and run it on a Windows 11 machine (our test environment is 22H2, OS Build 22621.1702)
3. Run the app
4. Right click to open the context menu (see attached image part 1) leave it there without clicking on any menu item
5. Click on taskbar icon to minimize and restore the app (see attached image part 2)
6. Go back to the app, notice that the region behind where the context menu was becomes unclickable (see attached image part 3 and the animated gif)

The above cannot be reproduced on Windows 10 version 2009 machine.

Expected behavior

After a context menu disappears it leaves no unclickable region.

Screenshots

No response

NuGet package version

None

Windows version

Windows 11 (22H2): Build 22621

Additional context

No response