Skip to content
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

suddenly refuses to start #10294

Closed
black-snow opened this issue May 31, 2021 · 22 comments
Closed

suddenly refuses to start #10294

black-snow opened this issue May 31, 2021 · 22 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@black-snow
Copy link

black-snow commented May 31, 2021

Windows Terminal version (or Windows build number)

1.8.1444.0

Other Software

No response

Steps to reproduce

Idk. Worked fine for ages. Now after a week-end and a reboot due to a windows update and apparently also a Windows Terminal update done automatically (installed via store) it refuses to start.

Expected Behavior

Windows Terminal starts up.

Actual Behavior

Application is active in task bar for about 2 seconds then just crashes without showing even a window.

Name der fehlerhaften Anwendung: WindowsTerminal.exe, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2e94
Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.19041.789, Zeitstempel: 0x2bd748bf
Ausnahmecode: 0xc0000409
Fehleroffset: 0x000000000007286e
ID des fehlerhaften Prozesses: 0x2aa4
Startzeit der fehlerhaften Anwendung: 0x01d755f363c37cd6
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\ucrtbase.dll
Berichtskennung: e744ecdd-b0f3-43d0-af28-00fa2abbbea6
Vollständiger Name des fehlerhaften Pakets: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

grafik

/edit: dupe of #8358
/edit: dupe of #10211 (apparently)

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels May 31, 2021
@black-snow
Copy link
Author

P.S.: wsl from power shell works fine

@swahilli
Copy link

I have the same issue. It was working fine on Friday, then, following a silent upgrade, it's not doing anything.

@Rafagd
Copy link

Rafagd commented May 31, 2021

+1

It was working on Thursday, opened it on Friday for a job interview and it instantly crashed on me.
It has not worked since.

ps.: wsl, cmd and powershell are working fine, the problem seems to be the terminal application itself.

@swahilli
Copy link

I uninstalled and reinstalled from the app store and it's now working, but I obviously lost all my settings

@gfraiteur
Copy link

Same here. Broken after silent update.

@timanstey
Copy link

Opening the App Settings for Windows Terminal Preview (Start -> Windows Terminal Preview -> on the jump list expand it and choose App Settings; or Settings -> Apps -> Windows Terminal Preview -> Advanced Options) then choosing the Repair option appears to fix this. Repair doesn't erase any settings (or didn't for me anyway).

@zarunet
Copy link

zarunet commented May 31, 2021

Can confirm. Here's a short clip of what happens in the taskbar :

2021-05-31_11-55-44.mp4

Same crash report as @black-snow afterwards.

Unfortunately, @timanstey's suggestion did nothing for me :/

@Rafagd
Copy link

Rafagd commented May 31, 2021

Opening the App Settings for Windows Terminal Preview (Start -> Windows Terminal Preview -> on the jump list expand it and choose App Settings; or Settings -> Apps -> Windows Terminal Preview -> Advanced Options) then choosing the Repair option appears to fix this. Repair doesn't erase any settings (or didn't for me anyway).

I tried uninstalling and reinstalling, and I just have tried both the Repair and the Reset options. No luck.

@hagronnestad
Copy link

Opening the App Settings for Windows Terminal Preview (Start -> Windows Terminal Preview -> on the jump list expand it and choose App Settings; or Settings -> Apps -> Windows Terminal Preview -> Advanced Options) then choosing the Repair option appears to fix this. Repair doesn't erase any settings (or didn't for me anyway).

This worked perfectly for me as well.

@TheThing
Copy link

TheThing commented May 31, 2021

Opening the App Settings for Windows Terminal Preview (Start -> Windows Terminal Preview -> on the jump list expand it and choose App Settings; or Settings -> Apps -> Windows Terminal Preview -> Advanced Options) then choosing the Repair option appears to fix this. Repair doesn't erase any settings (or didn't for me anyway).

I tried uninstalling and reinstalling, and I just have tried both the Repair and the Reset options. No luck.

This occured on both my machines. Uninstalling and installing fixed the problem for me though.

@zadjii-msft
Copy link
Member

Huh. The ucrtbase.dll is definitely new. We've got a bunch of other crashes, but none coming from the CRT iirc. Best way to get to the bottom of this would be a feedback hub trace: /feedback

@ghost
Copy link

ghost commented May 31, 2021

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost ghost added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 31, 2021
@Rafagd
Copy link

Rafagd commented May 31, 2021

Like this? https://aka.ms/AAcroqk

@black-snow
Copy link
Author

black-snow commented May 31, 2021

Now after lunch break it works again ... I have just installed the feedback hub and wanted to record when WT suddenly just worked again ...

/edit: anyone else having it (double-) mysteriously working again?

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels May 31, 2021
@zarunet
Copy link

zarunet commented May 31, 2021

Still broken for me :/ I sent a feedback from the hub ; did not get a link to share here, tho.

@whereisaaron
Copy link

whereisaaron commented May 31, 2021

Windows Update struck yesterday and since it installed Windows Terminal will no longer start. Well it appears to run for 2-5 seconds then exits again. Using 1.8.1444.0 from the Windows Store (I know, I know, foolish, but only thing close to a package manager for Windows 😄). Same ucrtbase.dll related crash others are reporting.

Faulting application name: WindowsTerminal.exe, version: 1.8.2105.24004, time stamp: 0x60ac2e94
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process ID: 0x6cd4
Faulting application start time: 0x01d75614900bd9f6
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 78473d8b-303a-4caf-b8c9-b77587623e04
Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Using @timanstey's 'Repair' option (#10294 (comment)) has seemed to fix it though!

@smiler
Copy link

smiler commented May 31, 2021

This is also being discussed in #8358. Doing the repair dance seems as mentioned above seems fix the issue (I've had this on two systems so far).

@Eric2203
Copy link

Eric2203 commented May 31, 2021

Hi, I'm having the exact same error. Repairing does NOT help in my case. Uninstall/reinstall does not either. It was working a few days ago. I've not rebooted since then.

From the Event viewer:

Faulting application name: WindowsTerminal.exe, version: 1.8.2105.24004, time stamp: 0x60ac2e94 Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process id: 0x6e2c Faulting application start time: 0x01d7566cb1e7e12d Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: b996e0eb-a6bc-40dd-a27e-f4e9a8463d49 Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App

And:

`Fault bucket 1320776192965560009, type 5
Event Name: MoBEX
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.8.2105.24004
P4: 60ac2e94
P5: ucrtbase.dll
P6: 10.0.19041.789
P7: 2bd748bf
P8: 000000000007286e
P9: c0000409
P10: 0000000000000007

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE811.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREAF0.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB30.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB3D.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB9C.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Window_bb1488c3939d65a4e3fed65bb628a3e554bf88_19389ec9_075e3dda-3c75-4edf-9061-4048fca64605

Analysis symbol:
Rechecking for solution: 0
Report Id: b996e0eb-a6bc-40dd-a27e-f4e9a8463d49
Report Status: 268435456
Hashed bucket: 4ba5cd02f28599e4625456f3218146c9
Cab Guid: 0`

@matthewstuartedwards
Copy link

Also having the issue starting up, and repair did not work for me.

@bsmely-w

This comment has been minimized.

@zadjii-msft
Copy link
Member

Nevermind, I'm crazy. The ucrtbase.dll crash is /dup #10211

@ghost
Copy link

ghost commented Jun 1, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jun 1, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 1, 2021
@ghost ghost removed Needs-Tag-Fix Doesn't match tag requirements Needs-Attention The core contributors need to come back around and look at this ASAP. labels Jun 1, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests