maui: MAUI apps crash on launch on Windows after Visual Studio update - code 2147942405 (0x80070005)

What worked for me: Build your app in any mode. It will crash on startup as expected.

Now go to the windows start menu, right click the app you just build: More => Run as Admin.

The app will start and so will every other MAUI app from now on even when started within Visual Studio.

A workround seems to be to set

<WindowsAppSdkDeploymentManagerInitialize>false</WindowsAppSdkDeploymentManagerInitialize>

in my csproj. This is because the wasdk is adding some extra dependency by accident. So this disables that.

I cannot understand how this is passed. So, now no one can build Windows apps until 2023? The fix is to what: rollback VS version?

My solution was to manually install the Microsoft.WindowsAppRuntime.1.2 redist

@jpreece6 did you install the runtime from here? https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/downloads#windows-app-sdk-12

Could be one of these microsoft/WindowsAppSDK#3228

Can confirm, running the app once as admin works.

MAUI 7.0.58 does not yet include this fix, however the upcoming 7.0.59 release will include it.

We’ve made a couple of changes to mitigate the Windows OS bug:

1. We are setting <PropertyGroup><WindowsAppSdkDeploymentManagerInitialize>false</WindowsAppSdkDeploymentManagerInitialize></PropertyGroup> to disable the automatic code generation of the Deployment Manager by the Windows App SDK.
2. We are calling the Deployment Manager Initialize code ourselves and handling the result differently than the generated invocation from the Windows App SDK.

Ultimately the Windows OS level bug was causing the Deployment Manager’s Initialize call to return a failed result (due to an Access Denied error, which is why running the app as Admin would fix this). The generated code from the Windows App SDK would abrubtly invoke Environment.Exit on a failed result and did not log any useful information when this happened. Previous versions of WindowsAppSDK (1.1.x) had a different order of evaluating MSBuild properties and did not automatically include the generated code to call this initialize method which is why we didn’t see the bug in MAUI before this.

Since we are calling this Deployment Manager Initialize method ourselves now within MAUI instead, we are choosing to not exit immediately on a failed result, since in many cases the app will still work as expected. This call is mostly important for apps using windows specific notification API’s and a few others, which many MAUI apps will not be using as it installs the additional framework references that ship with the windows app runtime but can’t be installed in all distribution scenarios. It’s correct to have this call in a MAUI app regardless of if you think you need it, the bug isn’t in the fact that the deployment manager is being called, but rather in that on Windows 10 there was a bug where that call required elevation.

The reason this change works around the Windows 10 OS bug is that we are choosing to not fail if the deployment manager cannot complete because it’s possible the app will still execute normally, which is the same behaviour MAUI apps had in previous releases.

To summarize, there are a few ways this issue can be mitigated:

1. Update to the latest Windows 10 OS January 19 update
2. Manually install the runtime with the Windows App SDK Runtime Installer
3. Set the project property in your MAUI app project: <PropertyGroup><WindowsAppSdkDeploymentManagerInitialize>false</WindowsAppSdkDeploymentManagerInitialize></PropertyGroup>
4. Update to MAUI 7.0.59 when it is released in the coming weeks

I ran Visual Studio as admin, then installed the redistributable from here, and my Windows 10 installation {with .NET 7 target) is now working. @jpreece6 https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/downloads#windows-app-sdk-12

Downloading https://aka.ms/windowsappsdk/1.2/1.2.221209.1/Microsoft.WindowsAppRuntime.Redist.1.2.zip and running its WindowsAppRuntimeInstall.exe (as admin) has solved the issue for me.

@mattleibow positive.

Here is what I did:

1. Installed VS2022 Community today (version info below);
2. Created a brand new MAUI app;
3. Tried running the app by pressing F5;
4. Got an error, was asked to turn on Developer Mode on Windows;
5. Turned on Developer Mode on Windows;
6. Back to VS, pressed F5 again to run;
7. The debugger runs, tries to start the app; and
8. Fails. The UI is never shown. The builder logs the error below.

The program '[9276] SimpleMauiApp.exe' has exited with code 2147942405 (0x80070005).

Seems to be an issue with an unregistered class in InteropServices… Or something along those lines.

When I try to run the generated .exe as admin, the Event Viewer logs an error with source on .NET Runtime:

Application: SimpleMauiApp.exe
CoreCLR Version: 7.0.122.56804
.NET Version: 7.0.1
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeInitializationException: The type initializer for '<Module>' threw an exception.
 ---> System.TypeInitializationException: The type initializer for 'WinRT.ActivationFactory'1' threw an exception.
 ---> System.Runtime.InteropServices.COMException (0x80040154): Class not registered (0x80040154 (REGDB_E_CLASSNOTREG))
   at WinRT.BaseActivationFactory..ctor(String typeNamespace, String typeFullName)
   at WinRT.ActivationFactory'1..ctor()
   at WinRT.ActivationFactory'1..cctor()
   --- End of inner exception stack trace ---
   at WinRT.ActivationFactory'1.ActivateInstance[I]()
   at Microsoft.Windows.ApplicationModel.WindowsAppRuntime.DeploymentInitializeOptions..ctor()
   at Microsoft.Windows.ApplicationModel.WindowsAppRuntime.DeploymentManagerCS.AutoInitialize.get_Options() in C:\Users\luizp\.nuget\packages\microsoft.windowsappsdk\1.2.221109.1\include\DeploymentManagerAutoInitializer.cs:line 44
   at Microsoft.Windows.ApplicationModel.WindowsAppRuntime.DeploymentManagerCS.AutoInitialize.AccessWindowsAppSDK() in C:\Users\luizp\.nuget\packages\microsoft.windowsappsdk\1.2.221109.1\include\DeploymentManagerAutoInitializer.cs:line 30
   at .cctor()
   --- End of inner exception stack trace ---

It also logs another error with source “Application Error”:

Faulting application name: SimpleMauiApp.exe, version: 1.0.0.0, time stamp: 0x6377b62e
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2251, time stamp: 0x0d929ca0
Exception code: 0xe0434352
Fault offset: 0x0012e062
Faulting process id: 0x4640
Faulting application start time: 0x01d9102f6683654d
Faulting application path: D:\Path\To\SimpleMauiApp\SimpleMauiApp\bin\Release\net7.0-windows10.0.19041.0\win10-x86\SimpleMauiApp.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: a40cdbbd-98f8-4c08-8ef0-c5849c156506
Faulting package full name: 
Faulting package-relative application ID: 

And an Event Viewer Information entry:

Fault bucket 1917344860151851230, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: SimpleMauiApp.exe
P2: 1.0.0.0
P3: 6377b62e
P4: KERNELBASE.dll
P5: 10.0.19041.2251
P6: 0d929ca0
P7: e0434352
P8: 0012e062
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26E5.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2754.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2764.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER276A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER277B.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_SimpleMauiApp.ex_e4bcef75ea05e55a5ed54d2bba619b01981a84c_107c69d7_95c1858b-9e39-4dd8-b43b-fa92bc4fee7a

Analysis symbol: 
Rechecking for solution: 0
Report Id: a40cdbbd-98f8-4c08-8ef0-c5849c156506
Report Status: 268435456
Hashed bucket: 96fc34bc2ed296267a9bc6fde545a8de
Cab Guid: 0 

Below my VS instance info:

Microsoft Visual Studio Community 2022 Version 17.4.3 VisualStudio.17.Release/17.4.3+33205.214 Microsoft .NET Framework Version 4.8.04084 Installed Version: Community

I had this issue too, and running the app once as an admin didn’t fix it. In fact, I was unable to even run the app as admin.

I just installed Visual Studio Community 2022 today, running the latest version.

Edition: Windows 10 Home Version: 22H2 OS build: 19045.2251 Experience: Windows Feature Experience Pack 120.2212.4180.0 Processor: Intel® Core™ i7-8750H CPU @ 2.20GHz 2.21 GHz

I can confirm this problem for MAUI Blazor Hybrid as well. Doesn’t matter for me if its in Release or Debug mode.

Update: I recreated the app targeting.NET 6, and it works just fine. Can even run via VS.

@jpreece6 did you install the runtime from here? https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/downloads#windows-app-sdk-12

Yep, runtime version 1.2.1.2.221116.1

Current workaround is to run the app once as admin. Or manually installing the Microsoft.WindowsAppRuntime 1.2 redist.

Fix is coming automatically on Win 10 in Feb 2023:

This is a known issue in the Windows 10 OS and not an issue with the WinAppSDK. The fix in Windows 10 OS is anticipated to be serviced on 3rd Tuesday of Jan 2023 as an OnDemand update patch and on 2nd Tuesday of Feb 2023 in an Auto update security patch.

Windows 10 Pro 22H2 Build 19045.2364

Downloading https://aka.ms/windowsappsdk/1.2/1.2.221209.1/Microsoft.WindowsAppRuntime.Redist.1.2.zip and running its WindowsAppRuntimeInstall.exe (as admin) has solved the issue for me.

Fix the problem on Windows for me. WHy am i needing this ?

They are fixing it (see above). But if you want it to work in the meantime, you need to install the above as a workaround or right-click and run as admin, which is working for some people.

Rollback VS version did not work for me, instead it led to a broken MAUI installation.

Same Problem here too !

In debug mode, they start for me, but in release mode, I also get an error

VS 2022 17.4.5 also includes the MAUI 7.0 SR3 7.0.59:

• Updates .NET MAUI to 7.0.59 (SR3), see https://aka.ms/dotnet-maui-releases for release notes.

Ask @Redth what else is needed to get this fixed.

Sorry, maybe I’m a bit slow on the uptake, but I don’t see how updating my Visual Studio is gonna help me fix the problems with our Azure build, where (according to build logs) MAUI 7.0.59 is already being used. In fact we have to manually ship release binaries from a developer’s Visual Studio which apparently work better or at least start, compared to what dotnet publish outputs for Windows.

I suggest we leave it at that for now. We’ll see how the next release of MAUI behaves in our Azure Pipeline and if that still produces unstartable binaries on Windows, I’ll open another issue. Sorry for stirring this up.

And it would be really great to get meaningful error messages. It seems that when the mix fails it fails silently.

On Tue, 14 Feb 2023, 3:44 pm Helmut Schmidt, @.***> wrote:

We still cannot get an installable Release build from our Azure Pipeline to start normally on a Windows 10 machine, following all the workarounds from this issue:

• Install latest Windows App SDK Runtime on target machine
• Include <WindowsAppSdkDeploymentManagerInitialize>false</WindowsAppSdkDeploymentManagerInitialize> in csproj file
• Run app as Administrator

dotnet workload install … installs .Net SDK 7.0.102 on the build machine and we see the output Installing workload manifest microsoft.net.sdk.maui version 7.0.59… in the build logs, meaning this is the version that should produce a flawless release build, if I read this issue correctly, right?

Nevertheless: Whenever we try to install & start the generated msix file, the app will not be started at all. Not even a window pops up and there is no error recorded in the Windows event viewer either.

We have to manually build for Release mode on a developer’s machine in Visual Studio for now, but we really would like to produce our Release builds in a more streamlined fashion. Does anyone have an idea if there is an obscure/special switch for the dotnet workloads install or dotnet publish commands that needs to be flipped for this to work?

— Reply to this email directly, view it on GitHub https://github.com/dotnet/maui/issues/12080#issuecomment-1429859523, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABCSC7OTXWS3WOIL5733QOLWXOK5JANCNFSM6AAAAAAS6BBRYM . You are receiving this because you commented.Message ID: @.***>

Of all suggested workarounds, these worked for me:

1. <WindowsAppSdkDeploymentManagerInitialize>false</WindowsAppSdkDeploymentManagerInitialize> in csproj
2. Manually installing latest WIndows App SDK runtime

And these did not work:

1. Running app as admin
2. Installi Windows Update KB5019275

I am using VS Community 17.4.3 with MAUI 7.0.52. Also as suggested for the future to update to MAUI 7.0.59 is it possible to just update MAUI version or we have to wait until a VS update is available with updated version of MAUI?

When will this fix be available? Does MAUI 7.0.58 (SR2) include it?

@mattleibow Could the MAUI team add milestone to issues which are fixed? We don’t know when to expect this change. For example this issue as well: “merged”/“fixed” but it is not available for developers using MAUI. https://github.com/dotnet/maui/issues/10858#issuecomment-1380591739

Same here. Really appreciate it @mattleibow!

<WindowsAppSdkDeploymentManagerInitialize>false</WindowsAppSdkDeploymentManagerInitialize> worked for me @mattleibow . Thank you

I tried rolling back to 17.4.2 and that did not fix it. Apps which worked fine under 17.4.2 (before the upgrade to 17.4.3) still do not work. 👎

I ran Visual Studio as admin, then installed the redistributable from here, and my Windows 10 installation {with .NET 7 target) is now working. @jpreece6 https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/downloads#windows-app-sdk-12

Thanks now its ok

Thank you so much, that worked!

From: mike3sullivan @.> Sent: Thursday, December 15, 2022 9:09 PM To: dotnet/maui @.> Cc: Joe Tinguely @.>; Comment @.> Subject: Re: [dotnet/maui] MAUI apps crash on launch on Windows after Visual Studio update - code 2147942405 (0x80070005) (Issue #12080)

I ran Visual Studio as admin, then installed the redistributable from here, and my Windows 10 installation is now working. @jpreece6https://github.com/jpreece6 https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/downloads#windows-app-sdk-12

— Reply to this email directly, view it on GitHubhttps://github.com/dotnet/maui/issues/12080#issuecomment-1353710571, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC5LHS2HCOIJMOZD3UORP7DWNOCI5ANCNFSM6AAAAAAS6BBRYM. You are receiving this because you commented.Message ID: @.***>

Same Problem here too!

Any one have solution for this BIG HEADAGE? I’ve the same trouble like this. And I’ve check that the new version can starting app OK if you are using .NET6 and It’s fails if .NET7.

Running the app as admin first solved the problem for me (Windows 10, 21H2).

I have very similar OS version as luiz. MAUI apps had been working for me until I upgraded to Visual Studio v17.4.3. A vanilla MAUI app from project template does not run and debug output window has this

The program ‘[21360] MauiApp1.exe’ has exited with code 2147942405 (0x80070005).

Running VS as admin does not resolve the issue. Is there a way to continue MAUI development without undoing this VS upgrade?

Correction run MAUI app as admin worked. I missed that you have to choose the app that got deployed and run that (instead of thru VS).

Yes, that worked for me too. I was overlooking this solution because I am still in the process of developing the MAUI app in Visual Studio. Thanks!

ok, so this looks like a Windows 10 Bug in combination with WinApp SDK 1.2.x which will be fixed in 2023

The fix in Windows 10 OS is anticipated to be serviced on 3rd Tuesday of Jan 2023 as an OnDemand update patch and on 2nd Tuesday of Feb 2023 in an Auto update security patch.

I have the same problem. The app deployment worked normally in VS 17.4.2.

Windows 10 22H2 Build 19045.2364