Mike Crider

As stated in [here](https://github.com/microsoft/microsoft-ui-xaml/blob/main/docs/contribution_handling.md#winui-2), the general policy for WinUI2 bugs is to close them so we can focus on WinUI3. WinUI2 changes add significant extra work, particularly in areas like...

This is currently by design. It is a little hidden down in the Remarks section of [the documentation](https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.application.requestedtheme?view=winrt-19041): > The theme can only be set when the app is started,...

I believe this restriction exists simply because way back in Windows 8 when the RequestedTheme support was implemented there weren't available resources to also support dynamic changes. Adding that support...

Working on getting the docs updated to indicate that this was never in a stable release. Marking as a feature request to get this to stable.

It sounds like this install issue has been resolved. Closing.

Thanks for providing the stowed exception stacks, @jhert0! This shows a reentrancy crash triggered by CTextBoxBase::Destroy calling ShutdownTextServices which makes some COM calls: > 7ffe58f2a77e WinUIEdit!ShutdownTextServices+0x8e > 7ffe5e36f91c Microsoft_ui_xaml!CTextBoxBase::Destroy+0x254 This...

@jhert0 The other stowed exceptions there have different HRESULTs and appear unrelated, so it these must have been handled and can be ignored. XAML stows many error codes it sees...

The internal copy of the issue was resolved as duplicate of another internal issue. Reactivating for continued tracking against the other, still-active internal issue.

The fix has been checked in for the next 1.6 servicing release in January.

From the error, maybe your project isn't consistent on whether 19041 or 22000 is the target?