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 does not run on N SKU after latest Windows Feature Update 22H2 #18571

New Issue
Closed
opened 2026-01-31 06:17:59 +00:00 by claunia · 20 comments
claunia commented 2026-01-31 06:17:59 +00:00
Owner
Copy Link

Originally created by @Ceffas84 on GitHub (Sep 30, 2022).

Windows version
Windows 11 Education N, 22H2

Windows build number
22621.521

Windows Feature Experience Pack
1000.22634.1000.0

Windows Terminal version
1.15.2713.0

Steps to reproduce
Update Windows to Version 22H2
Install Windows Terminal using the Windows Store;
Open Windows Terminal;

Expected Behavior
Windows Terminal should open a window.

Actual Behavior
Windows Terminal does not open a window.

What I have done, so far:
Re-installed the Windows Terminal

Remarks:
It was working fine before de Windows update, so I assume, the problem it's related to modifications made by the update.

Originally created by @Ceffas84 on GitHub (Sep 30, 2022). Windows version Windows 11 Education N, 22H2 Windows build number 22621.521 Windows Feature Experience Pack 1000.22634.1000.0 Windows Terminal version 1.15.2713.0 Steps to reproduce Update Windows to Version 22H2 Install Windows Terminal using the Windows Store; Open Windows Terminal; Expected Behavior Windows Terminal should open a window. Actual Behavior Windows Terminal does not open a window. What I have done, so far: Re-installed the Windows Terminal Remarks: It was working fine before de Windows update, so I assume, the problem it's related to modifications made by the update.
claunia commented 2026-01-31 06:18:02 +00:00
Author
Owner
Copy Link

@RiteshChepuri commented on GitHub (Sep 30, 2022):

It works just fine for me after the update.

@RiteshChepuri commented on GitHub (Sep 30, 2022): It works just fine for me after the update.
claunia commented 2026-01-31 06:18:03 +00:00
Author
Owner
Copy Link

@drakonien commented on GitHub (Oct 2, 2022):

Same problem, it was working fine but now fails.
Here is a trace from the Event Viewer:

Nombre de la aplicación con errores: WindowsTerminal.exe, versión: 1.16.2209.21001, marca de tiempo: 0x632b96ad Nombre del módulo con errores: Windows.UI.Xaml.dll, versión: 10.0.22621.608, marca de tiempo: 0xbb1317fb Código de excepción: 0xc000027b Desplazamiento de errores: 0x00000000005b2e90 Identificador del proceso con errores: 0x0x1F24 Hora de inicio de la aplicación con errores: 0x0x1D8D6917089F60B Ruta de acceso de la aplicación con errores: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.16.2641.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Ruta de acceso del módulo con errores: C:\Windows\System32\Windows.UI.Xaml.dll Identificador del informe: 8e211333-e387-4009-829e-bea2dafd29bf Nombre completo del paquete con errores: Microsoft.WindowsTerminalPreview_1.16.2641.0_x64__8wekyb3d8bbwe Identificador de aplicación relativa del paquete con errores: App

It fails the same with Windows Terminal and Windows Terminal Preview

@drakonien commented on GitHub (Oct 2, 2022): Same problem, it was working fine but now fails. Here is a trace from the Event Viewer: `Nombre de la aplicación con errores: WindowsTerminal.exe, versión: 1.16.2209.21001, marca de tiempo: 0x632b96ad Nombre del módulo con errores: Windows.UI.Xaml.dll, versión: 10.0.22621.608, marca de tiempo: 0xbb1317fb Código de excepción: 0xc000027b Desplazamiento de errores: 0x00000000005b2e90 Identificador del proceso con errores: 0x0x1F24 Hora de inicio de la aplicación con errores: 0x0x1D8D6917089F60B Ruta de acceso de la aplicación con errores: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.16.2641.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Ruta de acceso del módulo con errores: C:\Windows\System32\Windows.UI.Xaml.dll Identificador del informe: 8e211333-e387-4009-829e-bea2dafd29bf Nombre completo del paquete con errores: Microsoft.WindowsTerminalPreview_1.16.2641.0_x64__8wekyb3d8bbwe Identificador de aplicación relativa del paquete con errores: App` It fails the same with Windows Terminal and Windows Terminal Preview
claunia commented 2026-01-31 06:18:04 +00:00
Author
Owner
Copy Link

@RiteshChepuri commented on GitHub (Oct 3, 2022):

I think this problem occurs in terminal preview. Try resetting or reinstalling the app.

@RiteshChepuri commented on GitHub (Oct 3, 2022): I think this problem occurs in terminal preview. Try resetting or reinstalling the app.
claunia commented 2026-01-31 06:18:04 +00:00
Author
Owner
Copy Link

@drakonien commented on GitHub (Oct 3, 2022):

I think this problem occurs in terminal preview. Try resetting or reinstalling the app.

For me it fails in the "Preview" version and also in the "Standard". I tried reparing, resetting and reinstalling both versions to no avail, same problem.

@drakonien commented on GitHub (Oct 3, 2022): > I think this problem occurs in terminal preview. Try resetting or reinstalling the app. For me it fails in the "Preview" version and also in the "Standard". I tried reparing, resetting and reinstalling both versions to no avail, same problem.
claunia commented 2026-01-31 06:18:04 +00:00
Author
Owner
Copy Link

@Ceffas84 commented on GitHub (Oct 3, 2022):

Same here. Reparing, resetting and reinstalling does not solve the problem.

@Ceffas84 commented on GitHub (Oct 3, 2022): Same here. Reparing, resetting and reinstalling does not solve the problem.
claunia commented 2026-01-31 06:18:05 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 3, 2022):

@drakonien Can you submit feedback via the feedback hub? Make sure to start a recording then try to launch the Terminal. That should get us a stack trace for whatever the root cause is here.

As an aside, are you running the N SKU of Windows by any chance?

Thanks!

/feedback

@zadjii-msft commented on GitHub (Oct 3, 2022): @drakonien Can you submit feedback via the feedback hub? Make sure to start a recording then try to launch the Terminal. That should get us a stack trace for whatever the root cause is here. As an aside, are you running the N SKU of Windows by any chance? Thanks! /feedback
claunia commented 2026-01-31 06:18:05 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 3, 2022):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@ghost commented on GitHub (Oct 3, 2022): Hi there!<br><br>Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, 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/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png)<br><br>![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png)<br><br>![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 06:18:05 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 3, 2022):

x-links:

@zadjii-msft commented on GitHub (Oct 3, 2022): x-links: * #14110 * #14124
claunia commented 2026-01-31 06:18:06 +00:00
Author
Owner
Copy Link

@drakonien commented on GitHub (Oct 3, 2022):

@drakonien Can you submit feedback via the feedback hub? Make sure to start a recording then try to launch the Terminal. That should get us a stack trace for whatever the root cause is here.

As an aside, are you running the N SKU of Windows by any chance?

Thanks!

/feedback

In fact I am running a Windows N, but I have just installed the Media Feature Pack, and installed again the Windows Terminal from the Store, and now is working!!

@Ceffas84 are you using a Windows N too? Do you have installed the Media Feature Pack?

@drakonien commented on GitHub (Oct 3, 2022): > @drakonien Can you submit feedback via the feedback hub? Make sure to start a recording then try to launch the Terminal. That should get us a stack trace for whatever the root cause is here. > > As an aside, are you running the N SKU of Windows by any chance? > > Thanks! > > /feedback In fact I am running a Windows N, but I have just installed the Media Feature Pack, and installed again the Windows Terminal from the Store, and now is working!! @Ceffas84 are you using a Windows N too? Do you have installed the Media Feature Pack?
claunia commented 2026-01-31 06:18:06 +00:00
Author
Owner
Copy Link

@zadjii commented on GitHub (Oct 3, 2022):

@carlos-zamora @lhecker someone should check which version of the MIDI code is in the inbox build. We're getting a lot of these, and idk if we can even service that 😨

@zadjii commented on GitHub (Oct 3, 2022): @carlos-zamora @lhecker someone should check which version of the MIDI code is in the inbox build. We're getting a lot of these, and idk if we can even service that 😨
claunia commented 2026-01-31 06:18:06 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 3, 2022):

@zadjii I'm not sure it's related... The reports are mostly about 1.15/1.16 and those don't use the MIDI code. 0xc000027b is STATUS_STOWED_EXCEPTION, which means we could wait and see what the debug logs (if anyone posts them here) or ETW traces show as the original exception.

@lhecker commented on GitHub (Oct 3, 2022): @zadjii I'm not sure it's related... The reports are mostly about 1.15/1.16 and those don't use the MIDI code. `0xc000027b` is `STATUS_STOWED_EXCEPTION`, which means we could wait and see what the debug logs (if anyone posts them here) or ETW traces show as the original exception.
claunia commented 2026-01-31 06:18:06 +00:00
Author
Owner
Copy Link

@relcodedev commented on GitHub (Oct 3, 2022):

Installing the Media Feature Pack, reboot and install of Windows Terminal fixed my issue. Thank you!
FYI: Media Feature Pack failed to install until I uninstalled Windows Terminal first. I don't know if it was the cause of failure.

@relcodedev commented on GitHub (Oct 3, 2022): Installing the Media Feature Pack, reboot and install of Windows Terminal fixed my issue. Thank you! FYI: Media Feature Pack failed to install until I uninstalled Windows Terminal first. I don't know if it was the cause of failure.
claunia commented 2026-01-31 06:18:07 +00:00
Author
Owner
Copy Link

@Ceffas84 commented on GitHub (Oct 3, 2022):

Installing the Media Feature Pack, reboot and install of Windows Terminal fixed my issue. Thank you! FYI: Media Feature Pack failed to install until I uninstalled Windows Terminal first. I don't know if it was the cause of failure.

It worked for me aswell.

@Ceffas84 commented on GitHub (Oct 3, 2022): > Installing the Media Feature Pack, reboot and install of Windows Terminal fixed my issue. Thank you! FYI: Media Feature Pack failed to install until I uninstalled Windows Terminal first. I don't know if it was the cause of failure. It worked for me aswell.
claunia commented 2026-01-31 06:18:07 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Oct 4, 2022):

someone should check which version of the MIDI code is in the inbox build

@zadjii I think the original MIDI code was always behind a velocity flag (PR #13258), so that shouldn't have been available outside dev/preview builds. This might be an issue with the DirectSound implementation though. @DHowett mentioned that there were versions of Windows that didn't have DirectSound included, and recently updated the code to load the dsound.dll on demand (see PR #14005). I suspect that fix hasn't been released though.

If this is my fault - which seems quite likely - I sincerely apologise to everyone affected.

@j4james commented on GitHub (Oct 4, 2022): > someone should check which version of the MIDI code is in the inbox build @zadjii I think the original MIDI code was always behind a velocity flag (PR #13258), so that shouldn't have been available outside dev/preview builds. This might be an issue with the DirectSound implementation though. @DHowett mentioned that there were versions of Windows that didn't have DirectSound included, and recently updated the code to load the dsound.dll on demand (see PR #14005). I suspect that fix hasn't been released though. If this is my fault - which seems quite likely - I sincerely apologise to everyone affected.
claunia commented 2026-01-31 06:18:07 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Oct 4, 2022):

FYI, #13751 also has a 0xc000027b exception listing Windows.UI.Xaml.dll as the faulting module.

@j4james commented on GitHub (Oct 4, 2022): FYI, #13751 also has a 0xc000027b exception listing Windows.UI.Xaml.dll as the faulting module.
claunia commented 2026-01-31 06:18:08 +00:00
Author
Owner
Copy Link

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

I'm quite horrified (also, worried?) that my local testing in the N sku did not uncover this issue. We set up Windows N VMs for this express purpose 😄

Fortunately, we can fix this in time for Nickel+1 (since that's where we live-check-in new versions), and the issue doesn't exist in Nickel (it's stuck on 1.12).

@DHowett commented on GitHub (Oct 4, 2022): I'm quite horrified (also, worried?) that my local testing in the N sku _did not uncover this issue._ We set up Windows N VMs for this express purpose :smile: Fortunately, we can fix this in time for Nickel+1 (since that's where we live-check-in new versions), and the issue doesn't exist in Nickel (it's stuck on 1.12).
claunia commented 2026-01-31 06:18:08 +00:00
Author
Owner
Copy Link

@hmartinez82 commented on GitHub (Oct 12, 2022):

Same thing here. I have an N SKU (11 Pro N) with 22H2. Getting this error:

Faulting application name: WindowsTerminal.exe, version: 1.15.2209.28003, time stamp: 0x6334cd9b
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22621.521, time stamp: 0xb075f736
Exception code: 0xc000027b
Fault offset: 0x000000000057e44e
Faulting process id: 0x0x237C
Faulting application start time: 0x0x1D8DE7991C2D830
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.2713.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: e6319153-ca44-4b7c-a2b0-d7d0950f1c88
Faulting package full name: Microsoft.WindowsTerminal_1.15.2713.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: APP
@hmartinez82 commented on GitHub (Oct 12, 2022): Same thing here. I have an N SKU (11 Pro N) with 22H2. Getting this error: ``` Faulting application name: WindowsTerminal.exe, version: 1.15.2209.28003, time stamp: 0x6334cd9b Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22621.521, time stamp: 0xb075f736 Exception code: 0xc000027b Fault offset: 0x000000000057e44e Faulting process id: 0x0x237C Faulting application start time: 0x0x1D8DE7991C2D830 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.2713.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: e6319153-ca44-4b7c-a2b0-d7d0950f1c88 Faulting package full name: Microsoft.WindowsTerminal_1.15.2713.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: APP ```
claunia commented 2026-01-31 06:18:09 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Oct 12, 2022):

@hmartinez82 As mentioned above, you may be able to resolve the issue by installing the Media Feature Pack.

@j4james commented on GitHub (Oct 12, 2022): @hmartinez82 As mentioned above, you may be able to resolve the issue by installing the [Media Feature Pack](https://support.microsoft.com/en-us/topic/media-feature-pack-list-for-windows-n-editions-c1c6fffa-d052-8338-7a79-a4bb980a700a).
claunia commented 2026-01-31 06:18:09 +00:00
Author
Owner
Copy Link

@happybaby8882 commented on GitHub (Oct 17, 2022):

Installing the Media Feature Pack, reboot and install of Windows Terminal fixed my issue. Thank you! FYI: Media Feature Pack failed to install until I uninstalled Windows Terminal first. I don't know if it was the cause of failure.

Mine maybe have the same issue. but I could't install media feature pack through Opional feature. It reports an error 0x80070490. Could you help me with that?
2022-10-17_085252

@happybaby8882 commented on GitHub (Oct 17, 2022): > Installing the Media Feature Pack, reboot and install of Windows Terminal fixed my issue. Thank you! FYI: Media Feature Pack failed to install until I uninstalled Windows Terminal first. I don't know if it was the cause of failure. Mine maybe have the same issue. but I could't install media feature pack through Opional feature. It reports an error 0x80070490. Could you help me with that? ![2022-10-17_085252](https://user-images.githubusercontent.com/70244073/196069381-18b2f944-affb-4e15-a9ed-94851f0e5813.png)
claunia commented 2026-01-31 06:18:09 +00:00
Author
Owner
Copy Link

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

FWIW this should be fixed with Terminal 1.15.2874 and 1.15.2875, which are rolling out via the store as of Friday evening.

@DHowett commented on GitHub (Oct 17, 2022): FWIW this should be fixed with Terminal 1.15.2874 and 1.15.2875, which are rolling out via the store as of Friday evening.
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 Area-VT Needs-Tag-Fix Priority-0 Product-Terminal Severity-Blocking 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#18571
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?