-
Notifications
You must be signed in to change notification settings - Fork 674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WinUI 3.0 in Desktop crash on startup #2773
Comments
Probably related: #2677 |
Call Stack combase.dll!RoFailFastWithErrorContextInternal2(HRESULT hrError, unsigned long cStowedExceptions, _STOWED_EXCEPTION_INFORMATION_V2 * * aStowedExceptionPointers) Line 1455 |
Given that you state "run the .exe that is produced" I assume you are attempting to make and unpackaged app. That is not supported for the WinUI Preview. Does F5 or running the appx work? here is the documentation on winui3 desktop. @MikeHillberg and @stevenbrix FYI. |
I think @StephenLPeters guess is correct, this looks similar to other callstacks we've seen when people try to run the application unpackaged. We don't have support for this quite yet, we're expecting it to arrive sometime in September. |
Ah, you are correct. Launching via F5 works. Keen on the unpackaged solution. Will stay tuned! |
Hello - I am seeing the same problem. This exception (0xC000027B) has only showed up on one Win10 system (build 1809) we tested. The problem is impacting our ability to ship our application. I have not heard of this problem on other Win 10 and Win 11 systems we've tested. We are building with WindowsAppSDK 1.1. A WinUI3 unpackaged desktop app, configured as self-contained. BTW - the only way I know of to start an via F5 is from Visual Studio - is there some other meaning that I'm missing? Anyway, hopefully there will be a fix soon. Thanks very much. |
Hello - I am also seeing this same crash when trying to run an unpackaged WinUI 3 desktop app on Windows Server 2019. The app runs just fine on Win10 and Win11. Here is as much of a stacktrace as I could get (exception: 0xC000027B):
I'm running with Microsoft.WindowsAppSDK 1.1.2. To make things even more challenging, I was able to build a toy app: GettingStarted, with a couple of pages and that does not have this crash. The real application is pretty large and it could take a long time (if ever) to strip out implementation until I don't get the crash, so any pointers on what to look for would be most appreciated. Thank you. Robert Cohn |
The unmodified "Blank App, Packaged (WinUI in Desktop)" visual studio project template crashes on startup with error:
Unhandled exception at 0x00007FFE94FF6589 (Microsoft.Internal.XamlUdk.dll) in App16.exe: 0xC000027B: An application-internal exception has occurred (parameters: 0x000002F2E3AD6350, 0x0000000000000001).
I am on 1803, OS Build 17134.1550.
Steps to reproduce the behavior:
Note the crash that occurs in:
template WINRT_IMPL_AUTO(void) consume_Microsoft_UI_Xaml_IApplicationStatics::Start(Microsoft::UI::Xaml::ApplicationInitializationCallback const& callback) const
{
check_hresult(WINRT_IMPL_SHIM(Microsoft::UI::Xaml::IApplicationStatics)->Start(*(void**)(&callback)));
}
Unhandled exception at 0x00007FFE94FF6589 (Microsoft.Internal.XamlUdk.dll) in App16.exe: 0xC000027B: An application-internal exception has occurred (parameters: 0x000002F2E3AD6350, 0x0000000000000001).
Expected behavior
No Crashes.
Screenshots
N/A
Version Info
NuGet package version:
[Microsoft.WinUI 3.0.0-preview1.200515.3]
Additional context
The text was updated successfully, but these errors were encountered: