Maui app crached in server 2019 using self contained

[danies8]

Description

Hi,

I used this command to deployed Maui 9 app on server using self contained first time and app crashed during navigation from page to page.

**dotnet publish -f net9.0-windows10.0.19041.0 -c Release -p:WindowsPackageType=None

-p:WindowsAppSDKSelfContained=true /p:PackageCertificateThumbprint="c01ba45666762f3615cf6813aeb4dc4b1919541d"

-p:RuntimeIdentifierOverride=win10-x64 --self-contained**

and on event viewer i got this error.

Source: Application Error
Date: 5/28/2025 2:40:46 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WIN-BKFEO8N4HMU
Description:
Faulting application name: AutomationClient.MAUI.exe, version: 1.0.0.0, time stamp: 0x67fe0000
Faulting module name: coreclr.dll, version: 9.0.525.21509, time stamp: 0x67fe9d00
Exception code: 0xc0000005
Fault offset: 0x00000000002e5904
Faulting process id: 0xddc
Faulting application start time: 0x01dbcfc48e8fb6ab
Faulting application path: C:\Program Files (x86)\Sasa-Software\AutomationManager\Client\AutomationClient.MAUI.exe
Faulting module path: C:\Program Files (x86)\Sasa-Software\AutomationManager\Client\coreclr.dll
Report Id: 562a2a5c-e563-4f6d-b8c2-68c2e2704b30
Faulting package full name:
Faulting package-relative application ID:
Event Xml:



1000
2
100
0x80000000000000

39976
Application
WIN-BKFEO8N4HMU



AutomationClient.MAUI.exe
1.0.0.0
67fe0000
coreclr.dll
9.0.525.21509
67fe9d00
c0000005
00000000002e5904
ddc
01dbcfc48e8fb6ab
C:\Program Files (x86)\Sasa-Software\AutomationManager\Client\AutomationClient.MAUI.exe
C:\Program Files (x86)\Sasa-Software\AutomationManager\Client\coreclr.dll
562a2a5c-e563-4f6d-b8c2-68c2e2704b30

Steps to Reproduce

No response

Link to public reproduction project repository

No response

Version with bug

9.0.40 SR4

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

Windows

Affected platform versions

.....

Did you find any workaround?

Source: Application Error
Date: 5/28/2025 2:40:46 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WIN-BKFEO8N4HMU
Description:
Faulting application name: AutomationClient.MAUI.exe, version: 1.0.0.0, time stamp: 0x67fe0000
Faulting module name: coreclr.dll, version: 9.0.525.21509, time stamp: 0x67fe9d00
Exception code: 0xc0000005
Fault offset: 0x00000000002e5904
Faulting process id: 0xddc
Faulting application start time: 0x01dbcfc48e8fb6ab
Faulting application path: C:\Program Files (x86)\Sasa-Software\AutomationManager\Client\AutomationClient.MAUI.exe
Faulting module path: C:\Program Files (x86)\Sasa-Software\AutomationManager\Client\coreclr.dll
Report Id: 562a2a5c-e563-4f6d-b8c2-68c2e2704b30
Faulting package full name:
Faulting package-relative application ID:
Event Xml:



1000
2
100
0x80000000000000

39976
Application
WIN-BKFEO8N4HMU



AutomationClient.MAUI.exe
1.0.0.0
67fe0000
coreclr.dll
9.0.525.21509
67fe9d00
c0000005
00000000002e5904
ddc
01dbcfc48e8fb6ab
C:\Program Files (x86)\Sasa-Software\AutomationManager\Client\AutomationClient.MAUI.exe
C:\Program Files (x86)\Sasa-Software\AutomationManager\Client\coreclr.dll
562a2a5c-e563-4f6d-b8c2-68c2e2704b30

Relevant log output

[similar-issues-ai]

We've found some similar issues:

• Maui app as exe crashed after 6 hours of running #12593 , similarity score: 81%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[danies8]

Not relevant.

[danies8]

Addition:
Log Name: Application
Source: .NET Runtime
Date: 5/28/2025 3:51:28 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: WIN-BKFEO8N4HMU
Description:
Application: AutomationClient.MAUI.exe
CoreCLR Version: 9.0.525.21509
.NET Version: 9.0.5
Description: The process was terminated due to an unhandled exception.
Stack:
at ABI.Microsoft.UI.Xaml.IApplicationStaticsMethods.Start(WinRT.IObjectReference, Microsoft.UI.Xaml.ApplicationInitializationCallback)
at AutomationClient.MAUI.WinUI.Program.Main(System.String[])

Event Xml:
](http://schemas.microsoft.com/win/2004/08/events/event%22%3E)


1026
2
0
0x80000000000000

39987
Application
WIN-BKFEO8N4HMU



Application: AutomationClient.MAUI.exe
CoreCLR Version: 9.0.525.21509
.NET Version: 9.0.5
Description: The process was terminated due to an unhandled exception.
Stack:
at ABI.Microsoft.UI.Xaml.IApplicationStaticsMethods.Start(WinRT.IObjectReference, Microsoft.UI.Xaml.ApplicationInitializationCallback)
at AutomationClient.MAUI.WinUI.Program.Main(System.String[])

[danies8]

I find the bug.

Create solution with:
1.Create Maui app.
2. Create worker service project.
3. Add class library.
4. Create folder within the root of class library.
5. Add dll not nuget.
6. Add reference from Maui app to class library.
7. Add reference from Worker service to class library.
8. publish the Maui app as exe:
9.dotnet publish -f net9.0-windows10.0.19041.0 -c Release -p:WindowsPackageType=None

-p:WindowsAppSDKSelfContained=true

-p:RuntimeIdentifierOverride=win10-x64 --self-contained
10. run it on window or server 2019 and above
11. if you use the dll on Maui using reference the app crashes.
12. The reason the dls not copy well to publish folder when publishing.

[jsuarezruiz]

Can you try a variant and share the feedback?

Disable Single File Publishing:

dotnet publish -f net9.0-windows10.0.19041.0 -c Release --self-contained -p:PublishSingleFile=false

[danies8]

@jsuarezruiz
I tested on server 2019 and windows 11 using cmd in cli:

dotnet publish -f net9.0-windows10.0.19041.0 -c Release -p:WindowsPackageType=None

-p:WindowsAppSDKSelfContained=true -p:RuntimeIdentifierOverride=win10-x64 --self-contained -p:PublishSingleFile=false
and take the outer folder of pubish and is working.

The publish folder is not working, only the outer folder that contain the publish!!!

[jfversluis]

If I understand correctly: the files in the build output work, but not the version in the actual publish folder. This is not something that we control. This is something in the tooling probably. Please find a relevant issue there or open one if you cannot find one.