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

Terminal versions after 1.14.2282.0 won't start #18683

New Issue
Closed
opened 2026-01-31 06:21:14 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:21:14 +00:00
Owner
Copy Link

Originally created by @KyleKorndoerfer on GitHub (Oct 13, 2022).

Windows Terminal version

1.14.2282.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

I can only run WT at version 1.14.2282.0. If I install any newer version it fails to start (no window appears, no process is listed in Task Manager, etc.). Even when attempting to start from the command prompt/PowerShell with wt.exe, nothing is reported back to the console. This would be fine except it appears that Windows Terminal is getting updated in the background somehow so each time I restart my Azure DevTestLabs VM I need to uninstall, reinstall, & overwrite settings.

Microsoft Store is blocked on my VM so I have to manually install WT from the GitHub releases and would not assume that it would be auto-updated.

Expected Behavior

launch as normal and not be updated automatically

Actual Behavior

Any version above 1.14.2282.0 fails to start and results in an Application Error in the Windows Application Event Log as follows:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" /> 
    <EventID Qualifiers="0">1000</EventID> 
    <Version>0</Version> 
    <Level>2</Level> 
    <Task>100</Task> 
    <Opcode>0</Opcode> 
    <Keywords>0x80000000000000</Keywords> 
    <TimeCreated SystemTime="2022-10-13T14:40:52.2829793Z" /> 
    <EventRecordID>10596</EventRecordID> 
    <Correlation /> 
    <Execution ProcessID="13228" ThreadID="0" /> 
    <Channel>Application</Channel> 
    <Computer>(redacted)</Computer> 
    <Security /> 
  </System>
  <EventData>
    <Data>WindowsTerminal.exe</Data> 
    <Data>1.15.2209.28003</Data> 
    <Data>6334cd9b</Data> 
    <Data>Windows.UI.Xaml.dll</Data> 
    <Data>10.0.22000.978</Data> 
    <Data>82655b66</Data> 
    <Data>c000027b</Data> 
    <Data>00000000004a3e02</Data> 
    <Data>31f8</Data> 
    <Data>01d8df11cae1f6ed</Data> 
    <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.2713.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> 
    <Data>C:\Windows\System32\Windows.UI.Xaml.dll</Data> 
    <Data>17440c44-24fe-4338-add1-cb36a6c31dee</Data> 
    <Data>Microsoft.WindowsTerminal_1.15.2713.0_x64__8wekyb3d8bbwe</Data> 
    <Data>App</Data> 
  </EventData>
</Event>
Originally created by @KyleKorndoerfer on GitHub (Oct 13, 2022). ### Windows Terminal version 1.14.2282.0 ### Windows build number 10.0.22000.0 ### Other Software _No response_ ### Steps to reproduce I can only run WT at version 1.14.2282.0. If I install any newer version it fails to start (no window appears, no process is listed in Task Manager, etc.). Even when attempting to start from the command prompt/PowerShell with wt.exe, nothing is reported back to the console. This would be fine except it appears that Windows Terminal is getting updated in the background somehow so each time I restart my Azure DevTestLabs VM I need to uninstall, reinstall, & overwrite settings. Microsoft Store is blocked on my VM so I have to manually install WT from the GitHub releases and would not assume that it would be auto-updated. ### Expected Behavior launch as normal and not be updated automatically ### Actual Behavior Any version above 1.14.2282.0 fails to start and results in an Application Error in the Windows Application Event Log as follows: ```xml <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2022-10-13T14:40:52.2829793Z" /> <EventRecordID>10596</EventRecordID> <Correlation /> <Execution ProcessID="13228" ThreadID="0" /> <Channel>Application</Channel> <Computer>(redacted)</Computer> <Security /> </System> <EventData> <Data>WindowsTerminal.exe</Data> <Data>1.15.2209.28003</Data> <Data>6334cd9b</Data> <Data>Windows.UI.Xaml.dll</Data> <Data>10.0.22000.978</Data> <Data>82655b66</Data> <Data>c000027b</Data> <Data>00000000004a3e02</Data> <Data>31f8</Data> <Data>01d8df11cae1f6ed</Data> <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.2713.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> <Data>C:\Windows\System32\Windows.UI.Xaml.dll</Data> <Data>17440c44-24fe-4338-add1-cb36a6c31dee</Data> <Data>Microsoft.WindowsTerminal_1.15.2713.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event> ```
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:21:15 +00:00
claunia commented 2026-01-31 06:21:15 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 13, 2022):

Oof! Is there a chance that you're running "Windows N" (the no-media SKU) on that host?

@DHowett commented on GitHub (Oct 13, 2022): Oof! Is there a chance that you're running "Windows N" (the no-media SKU) on that host?
claunia commented 2026-01-31 06:21:16 +00:00
Author
Owner
Copy Link

@KyleKorndoerfer commented on GitHub (Oct 13, 2022):

Yes, System > About is reporting Windows 11 Enterprise N (21H2)

@KyleKorndoerfer commented on GitHub (Oct 13, 2022): Yes, **System > About** is reporting Windows 11 Enterprise N (21H2)
claunia commented 2026-01-31 06:21:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 13, 2022):

Argh! Thank you for reporting it and confirming.

This is a /duplicate of #14104, for which a fix is being released shortly.

If you need to get unblocked today, installing the media feature pack will help. I'm sorry about the issue.

@DHowett commented on GitHub (Oct 13, 2022): Argh! Thank you for reporting it and confirming. This is a /duplicate of #14104, for which a fix is being released shortly. If you need to get unblocked _today_, installing the media feature pack will help. I'm sorry about the issue.
claunia commented 2026-01-31 06:21:17 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 13, 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 (Oct 13, 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#18683
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?