Unable to deploy WinUI App after updating to 8.0.10, 8.0.14, 8.0.20, or installing VS 17.10

[GXSA-Qi]

Information

It looks like this is a bug in the Windows OS that went out beginning of March related to deploying the WinAppSDK runtime that's packaged with the WinAppSDK nuget. There is a planned OS update in the near future that will resolve this issue.

Workaround

2 available workarounds

1. Manually install the runtime that corresponds to the version you are using https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/downloads

   • MAUI 8.0.20+ is 1.5.2
   • MAUI 8.0.10-8.0.14 is 1.4.2

2. Set the project property in your MAUI app project. Ideally workaround 1 works for you. Disabling the DeploymentManager will cause some features of WinUI to no longer work.

   <PropertyGroup>
       <WindowsAppSdkDeploymentManagerInitialize>false</WindowsAppSdkDeploymentManagerInitialize>
   </PropertyGroup>

Description

The program fails to compile after version 8.0.20 of the Microsoft.Maui.Controls and Microsoft.Maui.Controls.Compatibility packages.

Steps to Reproduce

1.Use visual studio 2022 to create a new MAUI project file.
2.Compile and run it on Windows platform, and the program starts normally.

(The Nuget package version used is shown in the figure)

4.Upgrade the nuget package version to 8.0.20.

5.Compile the program again and find that the program cannot run normally.

The exception information is as follows:
引发的异常:“System.Runtime.InteropServices.COMException”(位于 WinRT.Runtime.dll 中) WinRT 信息: 找不到元素。

Link to public reproduction project repository

No response

Version with bug

8.0.20 SR4

Is this a regression from previous behavior?

No, this is something new

Last version that worked well

8.0.14 SR3.1

Affected platforms

Windows

Affected platform versions

Windows 11,version 22631.3296

Did you find any workaround?

No response

Relevant log output

No response

[PureWeen]

@GXSA-Qi if you Close VS, delete your bin/obj folder, and then reopen the project does it work?

[GXSA-Qi]

@GXSA-Qi if you Close VS, delete your bin/obj folder, and then reopen the project does it work?

Nope, Even deleting the bin and obj folders does not solve the problem.
Here is a video demonstrating these operations:

2024-04-10.152555.mp4

[MartinRothschink]

I have the exact same issue on multiple projects. 8.014 is fine, 8.0.20 crashes.

Contrary to the issue title, the compile works fine, the app crashes on start.

Event log shows this error for a release build:

CoreCLR Version: 8.0.424.16909
.NET Version: 8.0.4
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeInitializationException: The type initializer for '<Module>' threw an exception.
 ---> System.Runtime.InteropServices.COMException (0x80070490): Element nicht gefunden.

Element nicht gefunden.

   at WinRT.ExceptionHelpers.<ThrowExceptionForHR>g__Throw|39_0(Int32 hr)
   at WinRT.ExceptionHelpers.ThrowExceptionForHR(Int32 hr)
   at ABI.Microsoft.Windows.ApplicationModel.WindowsAppRuntime.IDeploymentManagerStatics2Methods.Initialize(IObjectReference _obj, DeploymentInitializeOptions deploymentInitializeOptions)
   at Microsoft.Windows.ApplicationModel.WindowsAppRuntime.DeploymentManager.Initialize(DeploymentInitializeOptions deploymentInitializeOptions)
   at Microsoft.Windows.ApplicationModel.WindowsAppRuntime.DeploymentManagerCS.AutoInitialize.AccessWindowsAppSDK()
   at .cctor()
   --- End of inner exception stack trace ---

[Yannikk1996]

Same issue here. The app crashes on start with 8.0.20.

[GXSA-Qi]

I have the exact same issue on multiple projects. 8.014 is fine, 8.0.20 crashes.

Contrary to the issue title, the compile works fine, the app crashes on start.

Event log shows this error for a release build:

CoreCLR Version: 8.0.424.16909 .NET Version: 8.0.4 Description: The process was terminated due to an unhandled exception. Exception Info: System.TypeInitializationException: The type initializer for '' threw an exception. ---> System.Runtime.InteropServices.COMException (0x80070490): Element nicht gefunden.

Element nicht gefunden.

at WinRT.ExceptionHelpers.g__Throw|39_0(Int32 hr) at WinRT.ExceptionHelpers.ThrowExceptionForHR(Int32 hr) at ABI.Microsoft.Windows.ApplicationModel.WindowsAppRuntime.IDeploymentManagerStatics2Methods.Initialize(IObjectReference _obj, DeploymentInitializeOptions deploymentInitializeOptions) at Microsoft.Windows.ApplicationModel.WindowsAppRuntime.DeploymentManager.Initialize(DeploymentInitializeOptions deploymentInitializeOptions) at Microsoft.Windows.ApplicationModel.WindowsAppRuntime.DeploymentManagerCS.AutoInitialize.AccessWindowsAppSDK() at .cctor() --- End of inner exception stack trace ---

Maybe there is something wrong with what I have described, (the translator cannot accurately express my meaning) you are right 😂, the compilation is not a problem, the problem is the program running.

[mattleibow]

There may be an issue in Windows App SDK 1.5, so you can do either of these 2 things for now:

Help us debug the issue

1. get the output of get-appxpackage micro*win*app*run* -allusers from running powershell in admin mode. This will help us determine the root cause.

More info here: microsoft/WindowsAppSDK#4268 (comment)

2. try installing he latest WASDK that just went out today:
   https://www.nuget.org/packages/Microsoft.WindowsAppSDK/1.5.240404000

Possible workarounds

1. Manually install the runtime with the Windows App SDK Runtime Installer x64
2. Set the project property in your MAUI app project:

   <PropertyGroup>
       <WindowsAppSdkDeploymentManagerInitialize>false</WindowsAppSdkDeploymentManagerInitialize>
   </PropertyGroup>

[PureWeen]

related
microsoft/WindowsAppSDK#4268
marticliment/UniGetUI#1939

[bmacombe]

There may be an issue in Windows App SDK 1.5, so you can do either of these 2 things for now:

1. Manually install the runtime with the Windows App SDK Runtime Installer x64
2. Set the project property in your MAUI app project:

   <PropertyGroup>
       <WindowsAppSdkDeploymentManagerInitialize>false</WindowsAppSdkDeploymentManagerInitialize>
   </PropertyGroup>
   

I tried option 2 on a reproduction I was setting up when I thought this was an issue in SyncFusion 25.1.39, I could deploy and debug WinUI after adding that to project

[PureWeen]

There may be an issue in Windows App SDK 1.5, so you can do either of these 2 things for now:

1. Manually install the runtime with the Windows App SDK Runtime Installer x64
2. Set the project property in your MAUI app project:

   <PropertyGroup>
       <WindowsAppSdkDeploymentManagerInitialize>false</WindowsAppSdkDeploymentManagerInitialize>
   </PropertyGroup>
   

I tried option 2 on a reproduction I was setting up when I thought this was an issue in SyncFusion 25.1.39, I could deploy and debug WinUI after adding that to project

Can you run this command on powershell in admin mode?

Get-AppxPackage -allusers WinAppRuntime