CoreMessagingXP.dll crash

[marioraffin]

Describe the bug

I am maintaining a .NET application with a WinUI3 UI which sometime crashes. In the event viewer I see that the crash is caused by CoreMessagingXP.dll but I have no idea about the real cause of the problem since I see the application crashing without any exception an I see the event shown below in the event viewer. At the moment I have no idea about how I could fix this or where to start searching for a solution. The OS is Windows 10 Enterprise (ver 1809). WindowsAppSDK 1.2.230118.102

Steps to reproduce the bug

It happens randomly. I have not found a procedure to reproduce the bug.

Expected behavior

No response

Screenshots

No response

NuGet package version

None

Windows version

Windows 10 (1809): Build 17763

Additional context

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2024-04-16T22:29:53.7299382Z" />
  <EventRecordID>69252</EventRecordID>
  <Channel>Application</Channel>
  <Computer>HAWKAGLE4PRO0265</Computer>
  <Security />
  </System>
- <EventData>
  <Data>HAWKManager.exe</Data>
  <Data>2.0.0.0</Data>
  <Data>65ab0000</Data>
  <Data>CoreMessagingXP.dll</Data>
  <Data>10.0.22622.1036</Data>
  <Data>d9ffb8dc</Data>
  <Data>c000027b</Data>
  <Data>000000000009418c</Data>
  <Data>21e4</Data>
  <Data>01da904d905aaf91</Data>
  <Data>C:\Program Files\PLL\HAWK Manager X\HAWKManager.exe</Data>
  <Data>C:\Program Files\PLL\HAWK Manager X\CoreMessagingXP.dll</Data>
  <Data>c063be60-6ef1-456e-a02e-ee33adaf34be</Data>
  <Data />
  <Data />
  </EventData>
  </Event>

[github-actions[bot]]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one. Thank you!

Open similar issues:

• Faulting Module : Microsoft.UI.Xaml.DLL - Win32 WinUI 3 App not loading (#7163), similarity score: 0.71

Closed similar issues:

• Access violation in CoreMessaging!Windows::System::DispatcherQueue::CompleteShutdown (#9075), similarity score: 0.79
• Bug: Random app crash mentions AnimatedIcon, which I'm not directly using anywhere (#6625), similarity score: 0.72
• Long running UWP App Crash | Exception 0xc0000005 in Windows.UI.Xaml.dll (#2106), similarity score: 0.71
• Long running UWP App crashes | Exception c0000374 (#9128), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[kirwan-safesurfer]

Just wanted to corroborate that I have seen this issue on Windows App SDK 1.5.7 when running (debugging) my packaged .NET 8 WinUI 3 app for the second time after cloning my project onto a workstation. This crash happened after approximately one second of the app window spawning (with no XAML elements showing). I couldn't reproduce it after the crash.

Event Viewer log:

Faulting application name: safesurfer.exe, version: 1.2.0.0, time stamp: 0x66e80000
Faulting module name: CoreMessagingXP.dll, version: 10.0.26105.1010, time stamp: 0x3cb81cec
Exception code: 0xe0464645
Fault offset: 0x000000000000a387
Faulting process id: 0x21E0
Faulting application start time: 0x1DB322D535375FB
Faulting application path: C:\Users\[User]\Source\Repos\SafeSurfer-Windows\src\SafeSurferWindows\bin\x64\Debug\net8.0-windows10.0.26100.0\win-x64\AppX\safesurfer.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.5_5001.275.500.0_x64__8wekyb3d8bbwe\CoreMessagingXP.dll
Report Id: 7dbcc311-2f5b-4354-a4e2-c1a6b767917f
Faulting package full name: SafeSurferLimited.SafeSurfer_1.2.0.0_x64__g9f2k15qvwspg
Faulting package-relative application ID: App

[DavidLiu642874264]

Hi , I have got the same crash in my app.

Event Log:

  AppName Hualong.TestWorldPro.exe 
  AppVersion 1.0.0.0 
  AppTimeStamp 67110000 
  ModuleName CoreMessagingXP.dll 
  ModuleVersion 10.0.26105.1011 
  ModuleTimeStamp 32fecfa4 
  ExceptionCode c000027b 
  FaultingOffset 00000000000945b2 
  ProcessId 0xb30 
  ProcessCreationTime 0x1db7ea0c7bb9572 
  AppPath C:\Program Files\WindowsApps\ShanghaiHualongTestInstru.TestWorldPro_1.0.17.0_x64__jznc3r06yv2t8\Hualong.TestWorldPro.exe 
  ModulePath C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.5_5001.311.2039.0_x64__8wekyb3d8bbwe\CoreMessagingXP.dll 
  IntegratorReportId 818bf348-7948-41c0-8e9e-f757d45c8e2d 
  PackageFullName ShanghaiHualongTestInstru.TestWorldPro_1.0.17.0_x64__jznc3r06yv2t8 
  PackageRelativeAppId App 

[andreisbarnea]

Similar problem on Windows 10 LTSC Build 19041

Faulting module name: CoreMessagingXP.dll, version: 10.0.27106.2602, time stamp: 0x38db939a Exception code: 0xc000027b Fault offset: 0x00000000000945b2

[alexlogvin]

Some of my customers are also having this type of issue.

On Windows 11:

Fehlerhafter Anwendungsname: APPNAME.exe, Version: APPVERSION, Zeitstempel: 0x67890000 Fehlerhafter Modulname: CoreMessagingXP.dll, Version: 10.0.26105.1013, Zeitstempel: 0x7dcce710 Ausnahmecode: 0xc000027b Fehleroffset: 0x00000000000945b2 Fehlerhafte Prozess-ID: 0xD6C Fehlerhafte Anwendungsstartzeit: 0x1DBA94D46347D15 Fehlerhafter Anwendungspfad: C:\Program Files\WindowsApps\COMPANY.APPID_APPVERSION_x64__etf61x1d7g4ea\APPNAME.exe Fehlerhafter Modulpfad: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.5_5001.373.1736.0_x64__8wekyb3d8bbwe\CoreMessagingXP.dll Berichts-ID: cb30146e-d9ac-4fdb-a44f-c235fe217aa4 Vollständiger Name des fehlerhaften Pakets: COMPANY.APPID_APPVERSION_x64__etf61x1d7g4ea Fehlerhafte paketbezogene Anwendungs-ID: App

On Windows 10:

Name der fehlerhaften Anwendung: APPNAME.exe, Version: APPVERSION, Zeitstempel: 0x67890000 Name des fehlerhaften Moduls: CoreMessagingXP.dll, Version: 10.0.26105.1013, Zeitstempel: 0x7dcce710 Ausnahmecode: 0xc000027b Fehleroffset: 0x00000000000945b2 ID des fehlerhaften Prozesses: 0xb64 Startzeit der fehlerhaften Anwendung: 0x01dba9437535c4c6 Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\COMPANY.APPID_APPVERSION_x64__etf61x1d7g4ea\APPNAME.exe Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.5_5001.373.1736.0_x64__8wekyb3d8bbwe\CoreMessagingXP.dll Berichtskennung: 544c7963-3f7a-4752-b96e-c0c594d2526f Vollständiger Name des fehlerhaften Pakets: COMPANY.APPID_APPVERSION_x64__etf61x1d7g4ea Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

Is there any solution or workaround?

Installing different versions of Windows App SDK doesn't help.

[Colin-AFCO]

I'd really love to know more about this, as I've just started writing a WinUI3 application that experiences seemingly random crashes with this exception. I've felt crazy trying to track this down. Is there a way I can better capture these exceptions or other unhandled exceptions? I started blaming the SDK, but I just hate resorting to blaming my tools. I feel a little less crazy seeing others running into this same issue.

[VishyBala007]

Hi All any update on this issue i am also facing the same??

[alexlogvin]

For me, the installation of these packages solved the issue, not sure which one is actually needed (seems like the last one):

• Microsoft.DotNet.DesktopRuntime.9
• Microsoft.EdgeWebView2Runtime
• Microsoft.VCRedist.2015+.x64

Run winget install packageNameHere to install the package

[emaschino]

Same issue with Windows 11 Widgets (WidgetBoard.exe):

Faulting application name: WidgetBoard.exe, version: 525.12501.10.0, time stamp: 0x68276e7b Faulting module name: CoreMessagingXP.dll, version: 10.0.27106.2611, time stamp : 0x65f1999a Exception code: 0xc0000602 Fault offset: 0x000000000000b8fd Faulting process id: 0x0x30A0 Faulting application start time: 0x0x1DBDE9F95A0B4D9 Faulting application path: C:\Program Files\WindowsApps\MicrosoftWindows.Client.WebExperience_525.12501.20.0_x64__cw5n1h2txyewy\WidgetBoard.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.6_6000.519.329.0_x64__8wekyb3d8bbwe\CoreMessagingXP.dll Report Id: 1a781d40-aaaa-4ebc-ba57-d4a9c35ce576 Faulting package full name: MicrosoftWindows.Client.WebExperience_525.12501.20.0_x64__cw5n1h2txyewy Faulting package-relative application ID: Global.WidgetBoard

[emaschino]

Same issue with Windows 11 Widgets (WidgetBoard.exe):

Faulting application name: WidgetBoard.exe, version: 525.12501.10.0, time stamp: 0x68276e7b Faulting module name: CoreMessagingXP.dll, version: 10.0.27106.2611, time stamp : 0x65f1999a Exception code: 0xc0000602 Fault offset: 0x000000000000b8fd Faulting process id: 0x0x30A0 Faulting application start time: 0x0x1DBDE9F95A0B4D9 Faulting application path: C:\Program Files\WindowsApps\MicrosoftWindows.Client.WebExperience_525.12501.20.0_x64__cw5n1h2txyewy\WidgetBoard.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.6_6000.519.329.0_x64__8wekyb3d8bbwe\CoreMessagingXP.dll Report Id: 1a781d40-aaaa-4ebc-ba57-d4a9c35ce576 Faulting package full name: MicrosoftWindows.Client.WebExperience_525.12501.20.0_x64__cw5n1h2txyewy Faulting package-relative application ID: Global.WidgetBoard

Seems that Windows 11 Update 23H2 (KB5060999) fixed the problem for me.

[DanielGlick]

Same issue with Windows 11 Widgets (WidgetBoard.exe): Faulting application name: WidgetBoard.exe, version: 525.12501.10.0, time stamp: 0x68276e7b Faulting module name: CoreMessagingXP.dll, version: 10.0.27106.2611, time stamp : 0x65f1999a Exception code: 0xc0000602 Fault offset: 0x000000000000b8fd Faulting process id: 0x0x30A0 Faulting application start time: 0x0x1DBDE9F95A0B4D9 Faulting application path: C:\Program Files\WindowsApps\MicrosoftWindows.Client.WebExperience_525.12501.20.0_x64__cw5n1h2txyewy\WidgetBoard.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.6_6000.519.329.0_x64__8wekyb3d8bbwe\CoreMessagingXP.dll Report Id: 1a781d40-aaaa-4ebc-ba57-d4a9c35ce576 Faulting package full name: MicrosoftWindows.Client.WebExperience_525.12501.20.0_x64__cw5n1h2txyewy Faulting package-relative application ID: Global.WidgetBoard

Seems that Windows 11 Update 23H2 (KB5060999) fixed the problem for me.

@emaschino I have that version and it is not working. Did you install the update on the machine that you are building the application from? Or did installing it on the machine you are running the application from fix the problem?

[emaschino]

@DanielGlick The PC where I was experiencing the issue was updated. But I didn't develop the faulting app: WidgetBoard.exe is Windows 11's integrated Widgets ;-)

[swax]

I figured out how to fix this crash in my case (.Net 9, WinUI 3, App SDK 1.7). It turned out I wasn't copying assets to the publish folder. Without the assets the app would crash on startup in CoreMessagingXP.dll. There was no indication at all the crash was related to trying to load resources it couldn't find.

If you're interested in reproducing the crash, you can download my release from here (https://github.com/swax/WallTrek), delete the assets folder, and the app should crash on startup.

[davesmits]

I changed some loading logic to Parallel.ForEachAsync and this error started to show up; Doesn't happen in debug / release. just after publish.. any advice how to troubleshoot?

[applefanbois]

It's just part and parcel of using a Microsoft deprecated CPM based operating system in 2025. The solution is easy, get a Chromebook and use Linux app.

[tipa]

I've had the same issue reported by a customer using Windows 10 when trying to access features in my app that use SkiaSharp. According to him, installing Microsoft.VCRedist.2015+.x64 as suggested above resolved the issue.