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

Crash on startup #15526

Closed
pizzacrystal opened this issue Jun 8, 2023 · 13 comments
Closed

Crash on startup #15526

pizzacrystal opened this issue Jun 8, 2023 · 13 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. Severity-Crash Crashes are real bad news.

Comments

@pizzacrystal
Copy link

pizzacrystal commented Jun 8, 2023

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

  • double click " C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe"
    or
  • single click the icon that is pinned to taskbar

however, it is normal if it is launched from icon in Start Menu or shortcut under "..\Start Menu\Programs\System Tools".

Expected Behavior

normal startup, either double click directly or single click on taskbar icon.

Actual Behavior

crashed immediately


feedback link: https://aka.ms/AAl3dtt


** More Info **

错误应用程序名称: WindowsTerminal.exe,版本: 1.17.2305.26001,时间戳: 0x647122fe
错误模块名称: KERNELBASE.dll,版本: 10.0.19041.2913,时间戳: 0xa1c3e870
异常代码: 0xc000027b
错误偏移量: 0x000000000012d862
错误进程 ID: 0xe64
错误应用程序启动时间: 0x01d999b746d3a23e
错误应用程序路径: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
错误模块路径: C:\Windows\System32\KERNELBASE.dll
报告 ID: 8f566e1a-cf35-4105-b9f9-7074fec0209e
错误程序包全名:
错误程序包相对应用程序 ID:

故障存储段 1495973896281467734,类型 4
事件名称: APPCRASH
响应: 不可用
Cab ID: 0

问题签名:
P1: WindowsTerminal.exe
P2: 1.17.2305.26001
P3: 647122fe
P4: combase.dll
P5: 10.0.19041.2788
P6: 03e7e147
P7: 802b000a
P8: 000000000001ccfa
P9:
P10:

@pizzacrystal pizzacrystal added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 8, 2023
@lhecker lhecker added Severity-Crash Crashes are real bad news. Product-Terminal The new Windows Terminal. labels Jun 8, 2023
@lhecker lhecker added this to the Terminal v1.19 milestone Jun 8, 2023
@lhecker lhecker added this to To Cherry Pick in 1.17 Servicing Pipeline via automation Jun 8, 2023
@lhecker lhecker added this to To Cherry Pick in 1.18 Servicing Pipeline via automation Jun 8, 2023
@pizzacrystal
Copy link
Author

pizzacrystal commented Jun 8, 2023

update:

  • pretty sure that v1.16.1026 worked normally therefore this issue is introduced in after automatically updating via MS store
  • have updated Win10 to latest (22H2, 19045.2965) but no help
  • have tried to uninstall in system application and re-install via MS store again but no help

@thomas-berg
Copy link

I'm experiencing a similar issue, however only when starting Windows Terminal with 'Run as administrator'. Curiously the UAC displays 'Unknown program' instead of Window Terminal.

Error details:

Faulting application name: WindowsTerminal.exe, version: 1.17.2305.26001, time stamp: 0x647122fe
Faulting module name: KERNELBASE.dll, version: 10.0.19041.964, time stamp: 0x812662a7
Exception code: 0xc000027b
Fault offset: 0x000000000010b39c
Faulting process ID: 0x18dc
Faulting application start time: 0x01d99cf6ec8159a5
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 87ddfae3-6979-41f8-bdbd-457d8fee45ab
Faulting package full name: Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Fault bucket 1862083693364119841, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.17.2305.26001
P4: 647122fe
P5: combase.dll
P6: 10.0.19041.928
P7: c94441ae
P8: 802b000a
P9: 0000000000086256
P10:

@mwpowellhtx
Copy link

Have been experiencing the same thing. As some have suggested, 'that is the point do not have to elevate', that is false and misleading. There are some things you actually do still require elevated in order to use any terminal, not just WT. So whatever the issue is, needs to be fixed ASAP.

@z3nn13
Copy link

z3nn13 commented Jun 14, 2023

I can also confirm. I have the exact same Terminal & Windows version, and this issue started happening recently.
It seems that running either "wt.exe" or "WindowsTerminal.exe" directly from "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe" does not work anymore.

However, as pizzacrystal said, both clicking the Start Menu shortcut and opening via MS Store still functions.
I have attached a screen record showing this issue.

TerminalBug.mp4

@DHowett
Copy link
Member

DHowett commented Jun 14, 2023

You are not intended to launch those files directly out of that directory.

@z3nn13
Copy link

z3nn13 commented Jun 15, 2023

I see, but the problem still persists. Before, I was able to run wt from the search bar or windows run command. Now, it loads for a bit and nothing shows up (as in the video above).

@microsoft microsoft deleted a comment Jun 15, 2023
@microsoft microsoft deleted a comment Jun 15, 2023
@microsoft microsoft deleted a comment Jun 15, 2023
@DHowett
Copy link
Member

DHowett commented Jun 16, 2023

This may not lead anywhere, but can you share the output of running cacls "C:\Program Files\WindowsApps" /s as admin?

@z3nn13
Copy link

z3nn13 commented Jun 17, 2023

This may not lead anywhere, but can you share the output of running cacls "C:\Program Files\WindowsApps" /s as admin?

Sure
C:\Program Files\WindowsApps "D:PAI(A;;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;OICIIO;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;;0x1200a9;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)(A;OICIIO;0x1200a9;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)(A;;FA;;;SY)(A;OICIIO;FA;;;SY)(A;CI;0x1200a9;;;BA)(A;OICI;0x1200a9;;;LS)(A;OICI;0x1200a9;;;NS)(A;OICI;0x1200a9;;;RC)(XA;;0x1200a9;;;BU;(Exists WIN://SYSAPPID))(A;OICI;FA;;;S-1-5-21-757397538-3420403896-3795204366-1001)"

@lhecker
Copy link
Member

lhecker commented Jun 19, 2023

That doesn't quite look correct does it? Compared to mine:

diff --git a/z3nn13.txt b/lhecker.txt
index 8e308da98..502dcdb55 100644
--- a/z3nn13.txt
+++ b/lhecker.txt
@@ -1,13 +1,12 @@
 D:PAI
 (A;;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)
-(A;OICIIO;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)
+(A;OICIIO;GA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)
 (A;;0x1200a9;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)
-(A;OICIIO;0x1200a9;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)
+(A;OICIIO;GXGR;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)
 (A;;FA;;;SY)
-(A;OICIIO;FA;;;SY)
+(A;OICIIO;GA;;;SY)
 (A;CI;0x1200a9;;;BA)
 (A;OICI;0x1200a9;;;LS)
 (A;OICI;0x1200a9;;;NS)
 (A;OICI;0x1200a9;;;RC)
 (XA;;0x1200a9;;;BU;(Exists WIN://SYSAPPID))
-(A;OICI;FA;;;S-1-5-21-757397538-3420403896-3795204366-1001)

@pizzacrystal
Copy link
Author

pizzacrystal commented Jun 20, 2023

my ACLs of "WindowsApps" folder are exactly the same as z3nn13's.

D:PAI
(A;;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)
(A;OICIIO;**FA**;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)
(A;;0x1200a9;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)
(A;OICIIO;**0x1200a9**;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)
(A;;FA;;;SY)
(A;OICIIO;**FA**;;;SY)
(A;CI;0x1200a9;;;BA)
(A;OICI;0x1200a9;;;LS)
(A;OICI;0x1200a9;;;NS)
(A;OICI;0x1200a9;;;RC)
(XA;;0x1200a9;;;BU;(Exists WIN://SYSAPPID))
(A;OICI;FA;;;S-1-5-21-491703059-3840752500-854807576-1001)

it seems that all "GA"(SDDL_GENERIC_ALL) access rights are changed to "FA"(SDDL_FILE_ALL), on the other hand, "GXGR"(SDDL_GENERIC_EXECUTE + SDDL_GENERIC_READ) is replaced by unknown right "0x1200a9", and finally there is an 'extra' line in the end.

Is access right the essential cause of this issue? and why did it occur?

@carlos-zamora
Copy link
Member

There are a couple of remediation steps over in #9452. If you're looking for a solution to this bug, please avoid anything that resets the ACLs or taking ownership of the WindowsApps folder. In the meantime, you might be able to get by with the unpackaged or portable mode install.

/dup #9452

@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot removed this from the Terminal v1.19 milestone Jun 21, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot 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 21, 2023
@zadjii-msft
Copy link
Member

Report ID: 87ddfae3-6979-41f8-bdbd-457d8fee45ab Faulting package full name: Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App

Fault bucket 1862083693364119841, type 5

To link up here:


错误应用程序路径: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
错误模块路径: C:\Windows\System32\KERNELBASE.dll
报告 ID: 8f566e1a-cf35-4105-b9f9-7074fec0209e
错误程序包全名:
错误程序包相对应用程序 ID:

故障存储段 1495973896281467734,类型 4
事件名称: APPCRASH 响应: 不可用 Cab ID: 0

This is:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. Severity-Crash Crashes are real bad news.
Projects
None yet
Development

No branches or pull requests

8 participants