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

[error 2147958031 (0x80073d0f) when launching `%SystemRoot%\System32\cmd.exe'] #16780

New Issue
Closed
opened 2026-01-31 05:22:39 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 05:22:39 +00:00
Owner
Copy Link

Originally created by @Darkster1 on GitHub (Feb 15, 2022).

Windows Terminal version

1.13.10336.0

Windows build number

22543.1000

Other Software

No response

Steps to reproduce

Use the terminal for a few days, at lest leave it running for quite some time.
At some random point open a new tab/pane using control+shift+2 or alt+shift -.

This error appears:
[error 2147958031 (0x80073d0f) when launching %SystemRoot%\System32\cmd.exe'] for cmd. Or powershell: [error 2147958031 (0x80073d0f) when launching %SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe']

At the moment of that error when you try control+shift+n for a new instance, the question raises "Do youy want to close all tabs" NOO I DON"T click cancel and.... of cource, the thing goes down entirely anyways! :(

(and there I say goodby to all my running scrips again...)
Sadly, the windows event viewer shows NOTHING about it, it just looks like the terminal knows it needs a restart and opening a new instance will solve it but it takes the running instance with it.

Expected Behavior

Opening a new tab/pane launches the associated program.

Actual Behavior

No new tabs/panes can be opened.
A new instance can be opened but it takes down the running instance.
Scripts terminals apps whatever running in the bad instance work(ed) fine though, it's just impossible to open new panes.

I haven't seen this in any other earlier build.

Originally created by @Darkster1 on GitHub (Feb 15, 2022). ### Windows Terminal version 1.13.10336.0 ### Windows build number 22543.1000 ### Other Software _No response_ ### Steps to reproduce Use the terminal for a few days, at lest leave it running for quite some time. At some random point open a new tab/pane using control+shift+2 or alt+shift -. This error appears: [error 2147958031 (0x80073d0f) when launching `%SystemRoot%\System32\cmd.exe'] for cmd. Or powershell: [error 2147958031 (0x80073d0f) when launching `%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe'] At the moment of that error when you try control+shift+n for a new instance, the question raises "Do youy want to close all tabs" NOO I DON"T click cancel and.... of cource, the thing goes down entirely anyways! :( (and there I say goodby to all my running scrips again...) Sadly, the windows event viewer shows NOTHING about it, it just looks like the terminal knows it needs a restart and opening a new instance will solve it but it takes the running instance with it. ### Expected Behavior Opening a new tab/pane launches the associated program. ### Actual Behavior No new tabs/panes can be opened. A new instance *can* be opened but it takes down the running instance. Scripts terminals apps whatever running in the bad instance work(ed) fine though, it's just impossible to open new panes. I haven't seen this in any other earlier build.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:22:39 +00:00
claunia commented 2026-01-31 05:22:40 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 15, 2022):

0x80073d0f is ERROR_NEEDS_REGISTRATION. That's a super weird error code, so I'd bet that you just so happened to open a tab right in the split moment where the Store decided to complete the update to the latest version of the Terminal (whether you asked it to update or not).

That also explains the dialog warning for the "Do you want to close all tabs". There's no reason that would have opened in response to just trying to open a new tab. But it does happen when the Store closes the terminal window (again, so it can install updates).

This has been a persistent thorn in our side: /dup #6726. Sorry you got caught right in the middle of one 😕 If this repros frequently, then my guess is totally off base and we can reopen this. (do note though we did push another update as a hotfix last week, so you'll probably need another update before long)

@zadjii-msft commented on GitHub (Feb 15, 2022): `0x80073d0f` is `ERROR_NEEDS_REGISTRATION`. That's a super weird error code, so I'd bet that you just so happened to open a tab right in the split moment where the Store decided to complete the update to the latest version of the Terminal (whether you asked it to update or not). That also explains the dialog warning for the "Do you want to close all tabs". There's no reason that would have opened in response to just trying to open a new tab. But it _does_ happen when the Store closes the terminal window (again, so it can install updates). This has been a persistent thorn in our side: /dup #6726. Sorry you got caught right in the middle of one 😕 If this repros frequently, then my guess is totally off base and we can reopen this. (do note though we did push another update as a hotfix last week, so you'll probably need another update before long)
claunia commented 2026-01-31 05:22:41 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 15, 2022):

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 commented on GitHub (Feb 15, 2022): 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!
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 Resolution-Duplicate
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#16780
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?