starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Crash to desktop when running an invalid Export Certificate Powershell command #3999

New Issue
Closed
opened 2026-01-30 23:35:17 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 23:35:17 +00:00
Owner
Copy Link

Originally created by @Choke101 on GitHub (Sep 24, 2019).

Originally assigned to: @miniksa on GitHub.

Environment

Platform ServicePack Version VersionString

Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0

Windows Terminal
0.4.2382.0

Powershell version
$PSVersionTable.PSVersion Major Minor Build Revision

5 1 18362 145

Any other software?
no

Steps to reproduce

  1. Type a poorly formed Export-Certificate powershell command such as
    Export-Certificate -Type CERT -FilePath "cert:\LocalMachine\my\blah" -Force
  2. Don't supply any details and hit enter when prompted for
    "Supply values for the following Parameters CERT:
  3. Get a great long exception stack trace that you can't read before windows closes as it crashes to desktop ending the WindowsTerminal process.

Expected behavior

Get a stack trace, and the terminal doesn't actually close and crash back to desktop.

Actual behavior

Closes window and Crashes back to desktop after printing out stack trace.

Originally created by @Choke101 on GitHub (Sep 24, 2019). Originally assigned to: @miniksa on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal 0.4.2382.0 Powershell version $PSVersionTable.PSVersion Major Minor Build Revision ----- ----- ----- -------- 5 1 18362 145 Any other software? no # Steps to reproduce 1. Type a poorly formed Export-Certificate powershell command such as Export-Certificate -Type CERT -FilePath "cert:\LocalMachine\my\blah" -Force 2. Don't supply any details and hit enter when prompted for "Supply values for the following Parameters CERT: 3. Get a great long exception stack trace that you can't read before windows closes as it crashes to desktop ending the WindowsTerminal process. # Expected behavior Get a stack trace, and the terminal doesn't actually close and crash back to desktop. # Actual behavior Closes window and Crashes back to desktop after printing out stack trace.
claunia commented 2026-01-30 23:35:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 24, 2019):

/feedback

@zadjii-msft commented on GitHub (Sep 24, 2019): /feedback
claunia commented 2026-01-30 23:35:18 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 24, 2019):

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 commented on GitHub (Sep 24, 2019): Hi there!<br><br>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?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-30 23:35:19 +00:00
Author
Owner
Copy Link

@Choke101 commented on GitHub (Sep 27, 2019):

https://aka.ms/AA65778

@Choke101 commented on GitHub (Sep 27, 2019): https://aka.ms/AA65778
claunia commented 2026-01-30 23:35:19 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 24, 2019):

We can't reproduce this, but we also can't get any helpful information out of your feedback entry. Sorry about that! I'm going to mark this one Needs-Repro.

@DHowett-MSFT commented on GitHub (Oct 24, 2019): We can't reproduce this, but we also can't get any helpful information out of your feedback entry. Sorry about that! I'm going to mark this one Needs-Repro.
claunia commented 2026-01-30 23:35:19 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Nov 11, 2019):

I think this is related to #3380.

@miniksa commented on GitHub (Nov 11, 2019): I think this is related to #3380.
claunia commented 2026-01-30 23:35:19 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 28, 2020):

So, it looks like this was a powershell crash the whole time. Powershell is exiting with code 3221225477 or STATUS_ACCESS_VIOLATION.

@DHowett-MSFT commented on GitHub (Feb 28, 2020): So, it looks like this was a powershell crash the whole time. Powershell is exiting with code 3221225477 or STATUS_ACCESS_VIOLATION.
claunia commented 2026-01-30 23:35:19 +00:00
Author
Owner
Copy Link

@Choke101 commented on GitHub (Feb 28, 2020):

I'm confused by changing the label to Product-Powershell is that stating the bug should only be fixed in powershell and not Terminal? I understand powershell may need to be fixed a bit to handle those but the terminal app should have resilience to safely recover from bad exit codes or violations so that it doesn't close the entire process and destroy the window and other tabs.

@Choke101 commented on GitHub (Feb 28, 2020): I'm confused by changing the label to Product-Powershell is that stating the bug should only be fixed in powershell and not Terminal? I understand powershell may need to be fixed a bit to handle those but the terminal app should have resilience to safely recover from bad exit codes or violations so that it doesn't close the entire process and destroy the window and other tabs.
claunia commented 2026-01-30 23:35:19 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 28, 2020):

You may not have tried this recently, or your terminal settings may be out of date, but this no longer wipes out your terminal. It prints out "process exited with code 322xxx" and just stays open for you to inspect the damage.

@DHowett-MSFT commented on GitHub (Feb 28, 2020): You may not have tried this recently, or your terminal settings may be out of date, but this no longer wipes out your terminal. It prints out "process exited with code 322xxx" and just stays open for you to inspect the damage.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Repro Needs-Tag-Fix Priority-1 Product-Powershell Resolution-External Severity-Crash
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3999
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?