-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Crash at startup when running as admin (combase.dll) #15745
Comments
NOTE: Looking at the event viewer i also see tons of errors/warnings related to DistributedCOM |
Note to team: There's a number of crashes on watson and I've requested more data. |
What's |
It's another name for Windows Error Reporting. |
Hey @retr0cube. Can you confirm your OS version number please? Is it still 10.0.19041.172? |
Hmmmmmmm blame looks like it's pointing towards: terminal/src/cascadia/TerminalSettingsModel/FileUtils.cpp Lines 35 to 65 in d70794a
Like, terminal/src/cascadia/WinRTUtils/inc/WtExeUtils.h Lines 7 to 21 in d70794a
|
@carlos-zamora yep, it's still the same |
If you're wondering why we asked... That's an alarmingly low build and revision number! Terminal depends on some things that have been fixed in Windows Update, but that version number predates the first publicly available Windows 10 20H1 update. Is this machine an insider program "drop-out"? It sounds like that version was not released to the public. |
No, this is 2004 an I'm not in an insider program. I plan to update it to 22h2 Soon™ Side story: Well I had 22h2 but I had a boot sector corruption and was unable to boot and because I didn't have a USB I gave my laptop for someone else to reinstall Windows for me but they installed 2004 Edit: I'm not sure if that's the NT version or the Windows version. I copied it from Powershell (the part where it says "Microsoft Windows 10 (10.0.....)") |
Hmm. Do you get the same version number if you run |
I don't have access to my laptop right now because I'm going to sleep, will inform you tomorrow! |
Hmm, in these stacks, we're all
That's mildly curious, that the |
@zadjii-msft After updating Windows 10 to 22H2, The problem no longer occurs. The event viewer (watson) no longer complains about DCOM and combase.dll It looks like Terminal relies on some functionality that is broken in older versions of Windows 10, that's because I noticed that the UAC prompt in 2004 referred to Terminal as "Unknown Program", but that changed to "Terminal" in 22H2. |
Ah, that's actually a well known bug (at least on our team) in the way the app platform, elevation, and centennial apps interact. They did fix that for Windows 11, but alas, couldn't backport that to certain older Win10 versions. It honestly could have been any number of things. Maybe things that were fixed in the OS that we never knew about! Glad it's at least fixed, and thanks for following up! |
Leaving notes to self:
|
Hi, I have the almost same issue on 21H2(19044.1288) and I could not upgrade the system because the system update is restricted by my company's policy. |
Windows Terminal version
1.17.11461.0_x64
Windows build number
10.0.19041.172
Other Software
No response
Steps to reproduce
Expected Behavior
App run in admin mode.
Actual Behavior
Crashes at startup, logs from Event viewer and Report.wer:
The text was updated successfully, but these errors were encountered: