Application crashes on Startup if installed as MSIX package

[Kristallranke]

Description

Application crashes on Startup if installed as MSIX package. But it works if installed by Visual Studio. The Stacktrace looks like this:

KernelBase.dll!RaiseFailFastException�()
combase.dll!RoFailFastWithErrorContextInternal2(HRESULT hrError, unsigned long cStowedExceptions, _STOWED_EXCEPTION_INFORMATION_V2 * * aStowedExceptionPointers) Line 1455
Microsoft.ui.xaml.dll!DirectUI::FrameworkApplication::StartDesktop()
Microsoft.ui.xaml.dll!DirectUI::FrameworkApplicationFactory::Start()
00007ffe4b8b4ecd()
000001fe00000002()
coreclr.dll!GenericPInvokeCalliGenILStub�()

Steps to Reproduce

1. Create template project ".Net MAUI-App"
2. Edit the Package.appxmanifest using the Editor
   • Fill the required fields (e.g. default language)
   • Set the Certificate
3. Build using dotnet publish -f net6.0-windows10.0.19041.0 -c Release
4. Install the package (app starts automatically)

Version with bug

Release Candidate 3 (current)

Last version that worked well

Unknown/Other

Affected platforms

Windows 10
Version 21H1 (Build 19043.1706)

Windows 11
Version 21H1 (Build 22000.194)

Affected platform versions

Windows SDK 10.0.19041.0

Did you find any workaround?

No response

Relevant log output

From the Windows event log:
Faulting application name: MauiApp1.exe, version: 1.0.0.0, time stamp: 0x62571213
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1645, time stamp: 0x630193b4
Exception code: 0xc000027b
Fault offset: 0x000000000010b362
Faulting process ID: 0x40c
Faulting application start time: 0x01d870320c92e1af
Faulting application path: C:\Program Files\WindowsApps\testPackage_1.0.0.0_x64__a4npxv28xhv58\MauiApp1.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: c9bc1429-d199-4693-af73-14c4475c0595
Faulting package full name: testPackage_1.0.0.0_x64__a4npxv28xhv58
Faulting package-relative application ID: App

[MagicAndre1981]

I can't repro it on my Win11 VM.

• configure Windows to create a full dump (DumpType = 2)
• download/Install Windbg (part of Windows 11 SDK)
• download the pde.dll from Andrew Richards and extract the zip
• open the dump with Windbg, setup debug symbols, load the pde dll (.load path\to\pde.dll)
• run !PDE.dpx -dse to shows all Stowed Exceptions (those 0xC000027B exceptions):
• now show exception details with !PDE.dse ADDRESS you see in output of the -dse command

Here is an example of the commands, that I posted some years ago for 8.1 apps, but it still works the same way today:

[Kristallranke]

Turns out, the modified project template and our actual project crash for different reasons, but in the same method.
Our application:

rsi : 0x000001cbe90f60a0 : !dse combase!STOWED_EXCEPTION_INFORMATION_V1:

Edit:
Removed the other issue, since my test project didn't work unpackaged as well due too the selected default language
I'm trying to find a new way to reproduce the issue.

[MagicAndre1981]

ok, this looks like an WinUI issue. Here I can't really help, wait for reply of the team.

[jfversluis]

I see you mention "Release Candidate 3 (current)" as the version. If that's the case, did you update your templates? Most notably, in your csproj do you have a reference to the Win2D package? If you do, that should either have at least version 1.0.3.1 or you don't even have to specify it anymore, it will be brought in automatically.

Let me know if that's the case or not.

[ghost]

Hi @Kristallranke. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.