Errors being reported when native code debugging is enabled.

Describe the bug

If I enable native code debugging I get errors in my output window

onecore\internal\sdk\inc\wil/resource.h(955)\dwmcorei.dll!00007FF8466C268A: (caller: 00007FF8466C99E5) ReturnNt(1) tid(55e4) C0000022 onecoreuap\windows\frameworkudk\warppal.cpp(783)\Microsoft.Internal.WarpPal.dll!00007FF954FFEE4C: (caller: 00007FF914FEE62F) ReturnHr(1) tid(9b0) 80004002 No such interface supported
onecoreuap\windows\frameworkudk\warppal.cpp(783)\Microsoft.Internal.WarpPal.dll!00007FF954FFEE4C: (caller: 00007FF914FEE62F) ReturnHr(2) tid(9b0) 80004002 No such interface supported
onecoreuap\windows\frameworkudk\warppal.cpp(783)\Microsoft.Internal.WarpPal.dll!00007FF954FFEE4C: (caller: 00007FF914FEE62F) ReturnHr(3) tid(55e4) 80004002 No such interface supported
onecoreuap\windows\frameworkudk\warppal.cpp(783)\Microsoft.Internal.WarpPal.dll!00007FF954FFEE4C: (caller: 00007FF95601AAEE) ReturnHr(4) tid(55e4) 80004002 No such interface supported
Microsoft.UI.Xaml.dll!00007FF915839A62: 80070057 - E_INVALIDARG
Microsoft.UI.Xaml.dll!00007FF915839A62: 80070057 - E_INVALIDARG
Microsoft.UI.Xaml.dll!00007FF915839A62: 80070057 - E_INVALIDARG

Please, can you either sort out the errors or suppress the messages. If these are internal errors, then you need an internal logging system, or flag them so that they can be filtered in the Output window. These are not useful to me, I do not know what to do about them and they are confusing when I'm trying to determine what the errors are in my application.

I rewrote a test app today, using up some hours, because I thought these errors were from the code I had written. I thought I was doing something wrong. Particularly because these errors mention 'warp' and I was setting up a direct-x device. I couldn't understand what I was doing wrong, and how my code was falling back to a warp device.

Steps to reproduce the bug

1. Create project Blank WinUI app.
2. Enable native code debugging.
3. Run the app.

Expected behavior

I expect the output window to be clear of internal errors.

Start by reproducing the issue with a Blank WinUI app and native code debugging enabled, then inspect the Output window messages involving Microsoft.UI.Xaml.dll, Microsoft.Internal.WarpPal.dll, and dwmcorei.dll. Determine whether these internal messages originate in WinUI or its native dependencies. Done means the misleading internal errors are suppressed or clearly filterable without hiding application errors.