Terminal does not run on N SKU after latest Windows Feature Update 22H2

[Ceffas84]

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.

[RiteshChepuri]

It works just fine for me after the update.

[drakonien]

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

[RiteshChepuri]

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

[drakonien]

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.

[Ceffas84]

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

[zadjii-msft]

@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

[ghost]

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!

[zadjii-msft]

x-links:

• Windows Terminal is unable to start in windows 11 #14110
• Crash On Startup #14124

[drakonien]

@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?

[zadjii]

@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 😨

[lhecker]

@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.

[relcodedev]

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.

[Ceffas84]

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.

[j4james]

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]

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

[DHowett]

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).

[hmartinez82]

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

[j4james]

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

[happybaby8882]

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?

[DHowett]

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.