-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terminal does not run on N SKU after latest Windows Feature Update 22H2 #14104
Comments
It works just fine for me after the update. |
Same problem, it was working fine but now fails.
It fails the same with Windows Terminal and Windows Terminal Preview |
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. |
Same here. Reparing, resetting and reinstalling does not solve the problem. |
@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 |
Hi there! |
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? |
@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 I'm not sure it's related... The reports are mostly about 1.15/1.16 and those don't use the MIDI code. |
Installing the Media Feature Pack, reboot and install of Windows Terminal fixed my issue. Thank you! |
It worked for me aswell. |
@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. |
FYI, #13751 also has a 0xc000027b exception listing Windows.UI.Xaml.dll as the faulting module. |
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). |
Same thing here. I have an N SKU (11 Pro N) with 22H2. Getting this error:
|
@hmartinez82 As mentioned above, you may be able to resolve the issue by installing the Media Feature Pack. |
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. |
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.
The text was updated successfully, but these errors were encountered: