-
Notifications
You must be signed in to change notification settings - Fork 683
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
Xaml Islands Crash on Start #5766
Comments
I recommended filing this here because both the Terminal and the PowerToys settings are XAML Islands apps. I presumed that both crashing would indicate some sort of issue in Islands itself for this user. |
can you please share a call stack trace? this may be the same as #5435 |
I submitted a windows feedback item which I believe contains dumps https://aka.ms/AAdl7c0 which microsoft people can access? This is the call stack when I open the dump file at
More than happy to send over the dmp files if needed. |
asklar - does the stack trace above help? |
I couldn't glean anything from the dumps in the Feedback Hub bug unfortunately, and I'm out of the office for a couple of weeks :). @zadjii-msft @DHowett can you guys follow up? |
@zadjii-msft and @miniksa given that this repros on 21h1 I don't think this is a dupe of #5435, have you seen this issue in terminal? |
I haven't come across any other reports of this, no. |
@kmelmon as FYI |
To add - I have also tried disabling all non MS startup apps, scheduled tasks, and services with no luck. |
We have a crash with the same crash data for PowerRemame too: On starting the app and sometimes (if start works) on resizing the window: microsoft/PowerToys#14180 |
@marb2000 FYI |
Some more info here microsoft/PowerToys#14356, looks like it can be related to screen resolution and DPI |
Had a play by disabling my second monitor and trying out the resolutions mentioned in the other thread. Sadly, it did not change the behaviour for me. e - to clarify I tried the resolutions and scaling settings mentioned. |
@hoo29 What is your default resolution and dpi? Can you try installing latest PowerToys and check whether PowerRename works for you? Thanks in advance! |
Main monitor is 2560x1440 at 100% scaling. Installed PowerToys 0.49.1 but PowerRename (and the other apps) don't work for me with the same issue. |
@hoo29 Did you try installing latest version of .NET core desktop? Just to rule out that one... |
Downloaded and installed the desktop runtime and runtime from https://dotnet.microsoft.com/download/dotnet/3.1 but no dice. |
Version |
Woah wait if that's the issue, then the root cause all this time has just been "you're missing the vclibs". The Windows 10 Terminal package ships those in our package, while the Windows 11 version doesn't. The Windows 11 version of the package can get away with this, because there were certain fixes to framework packages in Windows 11 that weren't able to be backported to Windows 10[1]. If you're on Windows 10, then yea, install the Windows 10 version of the Terminal. This probably applies to PowerToys too - if PT is using MUX then they too would be assuming that the VCLibs get installed properly as a dependency here. [1]: this is a mild fact. My memory might be hazy here. |
I must admit I install WT manually (extract the .msixbundle file etc)....I only had my eyes on the version numbers. |
Since raising this issue I have installed windows 11 and this is no longer a problem, I will close this issue. I did install WT from Microsoft store as part of the testing so would have assumed that gave me the W10 version with the required deps. |
Describe the bug
Raising based on advice from microsoft/terminal/issues/11025
When I start apps such as Windows Terminal or Microsoft PowerToys settings page, I very briefly see a window and then the app crashes. Event Viewer contains entries such as these:
Steps to reproduce the bug
Open the settings page for Microsoft PowerToys
Open Windows Terminal
Expected behavior
They open
Screenshots
n/a
Version Info
Latest stable builds from GitHub / Microsoft Store
NuGet package version:
n/a
Additional context
Have tried
.NET Core 3.1 Desktop Runtime (v3.1.15) - Windows x64
The text was updated successfully, but these errors were encountered: