[Windows 11 22000.65] Default Terminal does not work with 1.9! #14434

Closed
opened 2026-01-31 04:10:08 +00:00 by claunia · 56 comments
Owner

Originally created by @obrobrio2000 on GitHub (Jul 9, 2021).

MAINTAINER NOTE

There's a version mismatch between Terminal 1.9 and 22000.65. We had to introduce a new "default terminal" code path because the one we had introduced for 22000.51 was broken.

Until we release Terminal 1.10 to Preview, this will not work.


Original Report

Windows Terminal version (or Windows build number)

10.0.22000.65, 1.9.1523.0

Other Software

No response

Steps to reproduce

  1. Update to Windows 11 22000.65
  2. Set Terminal Preview as default terminal app (in Settings > Privacy & security > For developers or in Terminal Preview's settings)
  3. Open non-elevated cmd/powershell/wsl.

Expected Behavior

Terminal Preview should be used as the default terminal, respecting user's choice.

Actual Behavior

After 22000.65 update, Console Host is always used instead of Terminal Preview (ignoring user's choice). Even if I set Terminal Preview as the default terminal instead of conhost, it always opens everything (cmd, powershell, wsl2 etc.) in conhost.
Feedback Hub link: https://aka.ms/AAd5hc6

Originally created by @obrobrio2000 on GitHub (Jul 9, 2021). # MAINTAINER NOTE There's a version mismatch between Terminal 1.9 and 22000.65. We had to introduce a new "default terminal" code path because the one we had introduced for 22000.51 was broken. Until we release Terminal 1.10 to Preview, this will not work. --- ## Original Report ### Windows Terminal version (or Windows build number) 10.0.22000.65, 1.9.1523.0 ### Other Software _No response_ ### Steps to reproduce 1) Update to Windows 11 22000.65 2) Set Terminal Preview as default terminal app (in Settings > Privacy & security > For developers or in Terminal Preview's settings) 3) Open non-elevated cmd/powershell/wsl. ### Expected Behavior Terminal Preview should be used as the default terminal, respecting user's choice. ### Actual Behavior After 22000.65 update, Console Host is always used instead of Terminal Preview (ignoring user's choice). Even if I set Terminal Preview as the default terminal instead of conhost, it always opens everything (cmd, powershell, wsl2 etc.) in conhost. Feedback Hub link: https://aka.ms/AAd5hc6
Author
Owner

@DHowett commented on GitHub (Jul 9, 2021):

Thanks for the report! There's a version mismatch between Terminal 1.9 and 22000.65. We had to introduce a new "default terminal" code path because the one we had introduced for 22000.51 was broken.

Until we release Terminal 1.10 to Preview, this will not work.

Sorry!

@DHowett commented on GitHub (Jul 9, 2021): Thanks for the report! There's a version mismatch between Terminal 1.9 and 22000.65. We had to introduce a new "default terminal" code path because the one we had introduced for 22000.51 was broken. Until we release Terminal 1.10 to Preview, this will not work. Sorry!
Author
Owner

@vaualbus commented on GitHub (Jul 10, 2021):

@DHowett so basically it was done to fix the problem, I reported, that if you set terminal as conhost and you add auto start scripts in the Startup folders, sometime when the system start you got a windows cannot start app?
It's a fix anyway at least now i can use again all of my subst that I set at startup, that was broken in prev build!

@vaualbus commented on GitHub (Jul 10, 2021): @DHowett so basically it was done to fix the problem, I reported, that if you set terminal as conhost and you add auto start scripts in the Startup folders, sometime when the system start you got a windows cannot start app? It's a fix anyway at least now i can use again all of my subst that I set at startup, that was broken in prev build!
Author
Owner

@ghost commented on GitHub (Jul 15, 2021):

This is also the case on Microsoft Windows [Version 10.0.21390.2025]. Set Terminal Preview as default terminal application but Console Host is used when running Command Prompt or Powershell.

@ghost commented on GitHub (Jul 15, 2021): This is also the case on Microsoft Windows [Version 10.0.21390.2025]. Set Terminal Preview as default terminal application but Console Host is used when running Command Prompt or Powershell.
Author
Owner

@obrobrio2000 commented on GitHub (Jul 15, 2021):

[22000.65] I checked for updates on the Store and it updated Terminal Preview to 1.10.1933.0 , the problem is finally solved! Now cmd, ps, wsl etc. open with Terminal Preview if set as default! Thanks to all the devs!

https://user-images.githubusercontent.com/62136803/125801799-034c3a2b-1736-4aca-9c9f-210354f1fe11.mp4

@obrobrio2000 commented on GitHub (Jul 15, 2021): [22000.65] I checked for updates on the Store and it updated Terminal Preview to 1.10.1933.0 , the problem is finally solved! Now cmd, ps, wsl etc. open with Terminal Preview if set as default! Thanks to all the devs! https://user-images.githubusercontent.com/62136803/125801799-034c3a2b-1736-4aca-9c9f-210354f1fe11.mp4
Author
Owner

@ghost commented on GitHub (Jul 16, 2021):

@obrobrio2000, This still does not work on Microsoft Windows [Version 10.0.21390.2025] with Terminal Preview 1.10.1933.0.

@ghost commented on GitHub (Jul 16, 2021): @obrobrio2000, This still does not work on Microsoft Windows [Version 10.0.21390.2025] with Terminal Preview 1.10.1933.0.
Author
Owner

@obrobrio2000 commented on GitHub (Jul 16, 2021):

@obrobrio2000, This still does not work on Microsoft Windows [Version 10.0.21390.2025] with Terminal Preview 1.10.1933.0.

Thanks for letting me know, I reopened the issue.

@obrobrio2000 commented on GitHub (Jul 16, 2021): > @obrobrio2000, This still does not work on Microsoft Windows [Version 10.0.21390.2025] with Terminal Preview 1.10.1933.0. Thanks for letting me know, I reopened the issue.
Author
Owner

@DHowett commented on GitHub (Jul 16, 2021):

That release predates the revised handoff interface, and I believe that it is an insider build that is not currently receiving updates to any of our components. Our recent work is available in Insider builds 22000 and beyond.

@DHowett commented on GitHub (Jul 16, 2021): That release predates the revised handoff interface, and I believe that it is an insider build that is not currently receiving updates to any of our components. Our recent work is available in Insider builds 22000 and beyond.
Author
Owner

@ayamadori commented on GitHub (Jul 18, 2021):

This still does not work on Microsoft Windows [Version 10.0.22000.71] with Terminal Preview 1.10.1933.0...
image

@ayamadori commented on GitHub (Jul 18, 2021): This still does not work on Microsoft Windows [Version 10.0.22000.71] with Terminal Preview 1.10.1933.0... ![image](https://user-images.githubusercontent.com/7036267/126054736-3995f4ff-aec1-4b59-a88b-3d074bfff55c.png)
Author
Owner

@obrobrio2000 commented on GitHub (Jul 18, 2021):

@ayamadori same as you (22000.71 and 1.10.1993.0) but it seems working fine on my end.

https://user-images.githubusercontent.com/62136803/126055371-f74a49a1-a908-4a86-b2b4-e12063f0efe8.mp4

@obrobrio2000 commented on GitHub (Jul 18, 2021): @ayamadori same as you (22000.71 and 1.10.1993.0) but it seems working fine on my end. https://user-images.githubusercontent.com/62136803/126055371-f74a49a1-a908-4a86-b2b4-e12063f0efe8.mp4
Author
Owner

@ghost commented on GitHub (Jul 18, 2021):

@obrobrio2000, @ayamadori, Strange. It still does not work on my machine. Are there any steps required other than changing the setting on the Terminal?

@ghost commented on GitHub (Jul 18, 2021): @obrobrio2000, @ayamadori, Strange. It still does not work on my machine. Are there any steps required other than changing the setting on the Terminal?
Author
Owner

@minpeter commented on GitHub (Jul 26, 2021):

windows 11 PRO build 22000.100
windows terminal build 1.10.1933.0
I also have terminal preferences not working. 😥

@minpeter commented on GitHub (Jul 26, 2021): windows 11 PRO build 22000.100 windows terminal build 1.10.1933.0 I also have terminal preferences not working. 😥
Author
Owner

@minpeter commented on GitHub (Jul 27, 2021):

Rebooting solved it..🤦‍♂️

@minpeter commented on GitHub (Jul 27, 2021): Rebooting solved it..🤦‍♂️
Author
Owner

@ayamadori commented on GitHub (Aug 11, 2021):

This seems to be fixed... (Windows 10.0.22000.120, Terminal Preview 1.10.1933.0)
But I don't know when fixed. 🤔
When Windows was updated to 22000.120, this should be NOT fixed.
Maybe it's when Visual Studio was installed.

@ayamadori commented on GitHub (Aug 11, 2021): This seems to be fixed... (Windows 10.0.22000.120, Terminal Preview 1.10.1933.0) But I don't know when fixed. 🤔 When Windows was updated to 22000.120, this should be NOT fixed. Maybe it's when Visual Studio was installed.
Author
Owner

@The-MAZZTer commented on GitHub (Aug 19, 2021):

Not working with Windows 11 22000.160 with Windows Terminal Preview 1.101.933.0

Only unusual thing about my install is I don't have Windows activated (trying it out in a VM). I don't see any messages in Windows Settings indicating that would stop this feature from working though.

I also had installed PowerShell 7, as well as Windows Terminal Stable and Preview, all through winget (shouldn't matter).

Things I tried:

  1. Changing default host in Windows Terminal Settings.
  2. Verifying default host in Windows Settings (I know Windows has been stingy about letting apps manipulate these types of settings so I'm surprised Windows Terminal can), then switching it back and forth to make sure.
  3. Rebooting.
  4. Running cmd.exe from Run dialog (used console host).
  5. Running Command Prompt from Start Menu (used console host).
  6. Running find.exe/dism.exe from Run dialog (hard to tell but looked like console host window).
  7. Created BAT and CMD files with "pause" command. Ran using "start" from a Windows Terminal Command Prompt. (console host).
  8. Ran "start cmd" from a Windows Terminal Command Prompt (console host).
  9. Ran "start find.exe" from a Windows Terminal Command Prompt (closes immediately, but again seemed to be console host).
@The-MAZZTer commented on GitHub (Aug 19, 2021): Not working with Windows 11 22000.160 with Windows Terminal Preview 1.101.933.0 Only unusual thing about my install is I don't have Windows activated (trying it out in a VM). I don't see any messages in Windows Settings indicating that would stop this feature from working though. I also had installed PowerShell 7, as well as Windows Terminal Stable and Preview, all through winget (shouldn't matter). Things I tried: 1. Changing default host in Windows Terminal Settings. 2. Verifying default host in Windows Settings (I know Windows has been stingy about letting apps manipulate these types of settings so I'm surprised Windows Terminal can), then switching it back and forth to make sure. 3. Rebooting. 4. Running cmd.exe from Run dialog (used console host). 5. Running Command Prompt from Start Menu (used console host). 6. Running find.exe/dism.exe from Run dialog (hard to tell but looked like console host window). 7. Created BAT and CMD files with "pause" command. Ran using "start" from a Windows Terminal Command Prompt. (console host). 8. Ran "start cmd" from a Windows Terminal Command Prompt (console host). 9. Ran "start find.exe" from a Windows Terminal Command Prompt (closes immediately, but again seemed to be console host).
Author
Owner

@n-gao commented on GitHub (Sep 1, 2021):

With Terminal 1.10 I still can't set it as the default terminal, only the preview works
image

@n-gao commented on GitHub (Sep 1, 2021): With Terminal 1.10 I still can't set it as the default terminal, only the preview works ![image](https://user-images.githubusercontent.com/9084670/131631614-60507f2a-7103-4b7e-9b3e-f224fe8873ca.png)
Author
Owner

@swift-lee commented on GitHub (Sep 1, 2021):

With Terminal 1.10 I still can't set it as the default terminal, only the preview works
image

me too

@swift-lee commented on GitHub (Sep 1, 2021): > With Terminal 1.10 I still can't set it as the default terminal, only the preview works > ![image](https://user-images.githubusercontent.com/9084670/131631614-60507f2a-7103-4b7e-9b3e-f224fe8873ca.png) me too
Author
Owner

@zadjii-msft commented on GitHub (Sep 1, 2021):

@n-gao, @swift-lee That's correct. From the blog post for 1.11:

All of the features from our previous release are now in Windows Terminal, except for the default terminal setting, ...

@zadjii-msft commented on GitHub (Sep 1, 2021): @n-gao, @swift-lee That's correct. From the [blog post for 1.11](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-11-release/): > All of the features from our previous release are now in Windows Terminal, **except for the default terminal setting**, ...
Author
Owner

@zadjii-msft commented on GitHub (Sep 1, 2021):

@The-MAZZTer If you're still seeing this, can you share what's in HKEY_CURRENT_USER\Console\%%Startup for you? It should look something like
image

@zadjii-msft commented on GitHub (Sep 1, 2021): @The-MAZZTer If you're still seeing this, can you share what's in `HKEY_CURRENT_USER\Console\%%Startup` for you? It should look something like ![image](https://user-images.githubusercontent.com/18356694/131694162-d15a37f1-b185-4d87-bdf2-3f684d515af3.png)
Author
Owner

@The-MAZZTer commented on GitHub (Sep 2, 2021):

@zadjii-msft I upgraded to Windows 11 22000.176 and Terminal 1.11.2421.0 and tested again, didn't work.

Checked the registry and I am seeing those values there.

I also verified changing the setting in Windows Settings is actually changing those values.

I checked Event Viewer and found this error, not sure if it is related. It does not correspond with my attempts to open a console host by running find.exe from Run.

Faulting application name: OpenConsole.exe, version: 1.11.2108.30001, time stamp: 0x612d15b6
Faulting module name: uiautomationcore.dll, version: 7.2.22000.1, time stamp: 0x96f1b0d3
Exception code: 0xc0000005
Fault offset: 0x0000000000098096
Faulting process id: 0x1478
Faulting application start time: 0x01d7a03048bf79a6
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.11.2421.0_x64__8wekyb3d8bbwe\OpenConsole.exe
Faulting module path: C:\Windows\SYSTEM32\uiautomationcore.dll
Report Id: a30f9f02-483a-4e94-b221-156b0eeac623
Faulting package full name: Microsoft.WindowsTerminalPreview_1.11.2421.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

@The-MAZZTer commented on GitHub (Sep 2, 2021): @zadjii-msft I upgraded to Windows 11 22000.176 and Terminal 1.11.2421.0 and tested again, didn't work. Checked the registry and I am seeing those values there. I also verified changing the setting in Windows Settings is actually changing those values. I checked Event Viewer and found this error, not sure if it is related. It does not correspond with my attempts to open a console host by running find.exe from Run. Faulting application name: OpenConsole.exe, version: 1.11.2108.30001, time stamp: 0x612d15b6 Faulting module name: uiautomationcore.dll, version: 7.2.22000.1, time stamp: 0x96f1b0d3 Exception code: 0xc0000005 Fault offset: 0x0000000000098096 Faulting process id: 0x1478 Faulting application start time: 0x01d7a03048bf79a6 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.11.2421.0_x64__8wekyb3d8bbwe\OpenConsole.exe Faulting module path: C:\Windows\SYSTEM32\uiautomationcore.dll Report Id: a30f9f02-483a-4e94-b221-156b0eeac623 Faulting package full name: Microsoft.WindowsTerminalPreview_1.11.2421.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App
Author
Owner

@zadjii-msft commented on GitHub (Sep 2, 2021):

Faulting module name: uiautomationcore.dll, version: 7.2.22000.1, time stamp: 0x96f1b0d3

HUH. That's a new one. Since the registry does seem to have the right values in it, could you try filing feedback using the feedback hub, and include a trace of trying to run cmd.exe from the run dialog? If something's erroring out, that should catch it.

/feedback

/cc @miniksa

@zadjii-msft commented on GitHub (Sep 2, 2021): > Faulting module name: uiautomationcore.dll, version: 7.2.22000.1, time stamp: 0x96f1b0d3 HUH. That's a new one. Since the registry does seem to have the right values in it, could you try filing feedback using the feedback hub, and include a trace of trying to run `cmd.exe` from the run dialog? If something's erroring out, that should catch it. /feedback /cc @miniksa
Author
Owner

@ghost commented on GitHub (Sep 2, 2021):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Sep 2, 2021): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and 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/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
Author
Owner

@ghost commented on GitHub (Sep 7, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Sep 7, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@Sanluli36li commented on GitHub (Sep 8, 2021):

I cannot set the Terminal as the default console application. Is there a way to fix it?

Windows 11 22000.176 and Terminal 1.10.2383.0

屏幕截图 2021-09-08 185928
屏幕截图 2021-09-08 190028

@Sanluli36li commented on GitHub (Sep 8, 2021): I cannot set the Terminal as the default console application. Is there a way to fix it? Windows 11 22000.176 and Terminal 1.10.2383.0 ![屏幕截图 2021-09-08 185928](https://user-images.githubusercontent.com/5201743/132498019-4dfdf85f-21a9-41fe-bb67-08b7a390822b.png) ![屏幕截图 2021-09-08 190028](https://user-images.githubusercontent.com/5201743/132498025-8aebc21d-c245-4d59-9231-805541ddc65f.png)
Author
Owner

@zadjii-msft commented on GitHub (Sep 8, 2021):

@Sanluli36li You'll need to use the Preview version of the Windows Terminal in order to be able to set it as the default Terminal application. See #11120, https://github.com/microsoft/terminal/issues/10594#issuecomment-910364037

@zadjii-msft commented on GitHub (Sep 8, 2021): @Sanluli36li You'll need to use the Preview version of the Windows Terminal in order to be able to set it as the default Terminal application. See #11120, https://github.com/microsoft/terminal/issues/10594#issuecomment-910364037
Author
Owner

@DHowett commented on GitHub (Sep 8, 2021):

@Sanluli36li your issue probably comes from using the Scoop (or unzipped) version of Terminal. Is that correct?

@DHowett commented on GitHub (Sep 8, 2021): @Sanluli36li your issue probably comes from using the Scoop (or unzipped) version of Terminal. Is that correct?
Author
Owner

@The-MAZZTer commented on GitHub (Sep 9, 2021):

@zadjii-msft I should mention I am seeing this on a VM in Oracle VirtualBox. So not sure if my particular instance is something you'd care to pursue or not. Sorry for not mentioning it sooner.

From a fresh boot I ran cmd.exe from the Run dialog and the error I pasted in earlier does not appear in Event Viewer anywhere in the VM session time frame. So it's caused by some other action, presumably something I did while testing different ways to open consoles and switching the default console host setting back and forth. But it doesn't seem related to actually running a console app with Windows Terminal Preview selected as the default,.

One thing I am noticing is when I have Windows Terminal Preview selected, OpenConsole.exe does run when I launch cmd.exe from Run, but it still shows in a conhost window. OpenConsole.exe for some reason hangs around a minute or two after I close the conhost window (in Windows 10 it exits immediately once a Windows Terminal-hosted console is closed).

If I switch back to conhost as the default host, OpenConsole.exe does not run for cmd.exe from the Run dialog (just like on Windows 10).

When using Windows Terminal Preview OpenConsole reacts the same way it does on Windows 10... it exits immediately once a console closes.

I've filed Feedback with the link to this issue and attached a recording of me attempting to run cmd.exe from Run in case there is something useful in there. Oddly Feedback did not allow me to select "Windows Terminal (Preview)" (no option for it) so I just selected "Windows Terminal".

@The-MAZZTer commented on GitHub (Sep 9, 2021): @zadjii-msft I should mention I am seeing this on a VM in Oracle VirtualBox. So not sure if my particular instance is something you'd care to pursue or not. Sorry for not mentioning it sooner. From a fresh boot I ran cmd.exe from the Run dialog and the error I pasted in earlier does not appear in Event Viewer anywhere in the VM session time frame. So it's caused by some other action, presumably something I did while testing different ways to open consoles and switching the default console host setting back and forth. But it doesn't seem related to actually running a console app with Windows Terminal Preview selected as the default,. One thing I am noticing is when I have Windows Terminal Preview selected, OpenConsole.exe does run when I launch cmd.exe from Run, but it still shows in a conhost window. OpenConsole.exe for some reason hangs around a minute or two after I close the conhost window (in Windows 10 it exits immediately once a Windows Terminal-hosted console is closed). If I switch back to conhost as the default host, OpenConsole.exe does not run for cmd.exe from the Run dialog (just like on Windows 10). When using Windows Terminal Preview OpenConsole reacts the same way it does on Windows 10... it exits immediately once a console closes. I've filed Feedback with the link to this issue and attached a recording of me attempting to run cmd.exe from Run in case there is something useful in there. Oddly Feedback did not allow me to select "Windows Terminal (Preview)" (no option for it) so I just selected "Windows Terminal".
Author
Owner

@zadjii-msft commented on GitHub (Sep 9, 2021):

One thing I am noticing is when I have Windows Terminal Preview selected, OpenConsole.exe does run when I launch cmd.exe from Run, but it still shows in a conhost window. OpenConsole.exe for some reason hangs around a minute or two after I close the conhost window (in Windows 10 it exits immediately once a Windows Terminal-hosted console is closed).

VERY interesting. That seems to suggest that the delegation console part of defterm is working as expected, but the delegation terminal aspect isn't. The reason you're seeing what appears to be a conhost window is because OpenConsole.exe is literally just conhost.exe. It's just the version that's built from this repo, so we can ship an updated version side-by-side with the Terminal.

@miniksa for insights, he's the defterm expert.

@zadjii-msft commented on GitHub (Sep 9, 2021): > One thing I am noticing is when I have Windows Terminal Preview selected, OpenConsole.exe does run when I launch cmd.exe from Run, but it still shows in a conhost window. OpenConsole.exe for some reason hangs around a minute or two after I close the conhost window (in Windows 10 it exits immediately once a Windows Terminal-hosted console is closed). VERY interesting. That seems to suggest that the delegation _console_ part of defterm is working as expected, but the delegation _terminal_ aspect isn't. The reason you're seeing what appears to be a conhost window is because OpenConsole.exe _is literally just conhost.exe_. It's just the version that's built from this repo, so we can ship an updated version side-by-side with the Terminal. @miniksa for insights, he's the defterm expert.
Author
Owner

@miniksa commented on GitHub (Sep 9, 2021):

@The-MAZZTer... what version of VirtualBox? The best thing would be if I could get a reproduction of this issue in my office.

I'm going to search for the feedback but I don't know if I'll be able to find it without the share link. Wish me luck.

@miniksa commented on GitHub (Sep 9, 2021): @The-MAZZTer... what version of VirtualBox? The best thing would be if I could get a reproduction of this issue in my office. I'm going to search for the feedback but I don't know if I'll be able to find it without the share link. Wish me luck.
Author
Owner

@miniksa commented on GitHub (Sep 9, 2021):

Oh my god I found it. Lightspeed txtUifId=32f6166c-7884-4494-b2f0-8a29523bb95d.

Crash Bucket ID = 7b0c1086-7cfa-d0b1-98af-ceeebe5a220c

  • This is a crash on exit of OpenConsole.exe related to UIA destructing...

Still digging.

@miniksa commented on GitHub (Sep 9, 2021): Oh my god I found it. Lightspeed txtUifId=32f6166c-7884-4494-b2f0-8a29523bb95d. Crash Bucket ID = 7b0c1086-7cfa-d0b1-98af-ceeebe5a220c - This is a crash on exit of OpenConsole.exe related to UIA destructing... Still digging.
Author
Owner

@miniksa commented on GitHub (Sep 9, 2021):

OK there's no Terminal crash data associated with this, so I'm not sure why the delegation terminal didn't work unless it was just not found or something. There wasn't an exit code that said why. Short of adding a ton of logging infrastructure to this to try to suss it out... the best thing I could do is get a reproduction of the environment somewhere I can have a debugger on it.

@miniksa commented on GitHub (Sep 9, 2021): OK there's no Terminal crash data associated with this, so I'm not sure why the delegation _terminal_ didn't work unless it was just not found or something. There wasn't an exit code that said *why*. Short of adding a ton of logging infrastructure to this to try to suss it out... the best thing I could do is get a reproduction of the environment somewhere I can have a debugger on it.
Author
Owner

@ghost commented on GitHub (Sep 13, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Sep 13, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@elricli commented on GitHub (Sep 15, 2021):

@n-gao, @swift-lee That's correct. From the blog post for 1.11:

All of the features from our previous release are now in Windows Terminal, except for the default terminal setting, ...

Is there a plan to set the default terminal in the Stable version?

@elricli commented on GitHub (Sep 15, 2021): > @n-gao, @swift-lee That's correct. From the [blog post for 1.11](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-11-release/): > > > All of the features from our previous release are now in Windows Terminal, **except for the default terminal setting**, ... Is there a plan to set the default terminal in the Stable version?
Author
Owner

@DHowett commented on GitHub (Sep 15, 2021):

Is there a plan to set the default terminal in the Stable version?

Yes, when the feature is stable.

@DHowett commented on GitHub (Sep 15, 2021): > Is there a plan to set the default terminal in the Stable version? Yes, when the feature is stable.
Author
Owner

@jerryc127 commented on GitHub (Sep 19, 2021):

The default Terminal only for windows 11 ?

In windows 10, i have not this option in 1.11.2421.0

image

@jerryc127 commented on GitHub (Sep 19, 2021): The default Terminal only for windows 11 ? In windows 10, i have not this option in 1.11.2421.0 ![image](https://user-images.githubusercontent.com/16351105/133921619-02ab1dc9-1f6d-4315-96e6-5d5050c876e1.png)
Author
Owner

@minpeter commented on GitHub (Sep 19, 2021):

The default Terminal only for windows 11 ?

In windows 10, i have not this option in 1.11.2421.0

image

Is the 'windows terminal preview' correct?

@minpeter commented on GitHub (Sep 19, 2021): > The default Terminal only for windows 11 ? > > In windows 10, i have not this option in 1.11.2421.0 > > ![image](https://user-images.githubusercontent.com/16351105/133921619-02ab1dc9-1f6d-4315-96e6-5d5050c876e1.png) > > Is the 'windows terminal preview' correct?
Author
Owner

@jerryc127 commented on GitHub (Sep 19, 2021):

The default Terminal only for windows 11 ?
In windows 10, i have not this option in 1.11.2421.0
image

Is the 'windows terminal preview' correct?

yes
image

@jerryc127 commented on GitHub (Sep 19, 2021): > > The default Terminal only for windows 11 ? > > In windows 10, i have not this option in 1.11.2421.0 > > ![image](https://user-images.githubusercontent.com/16351105/133921619-02ab1dc9-1f6d-4315-96e6-5d5050c876e1.png) > > Is the 'windows terminal preview' correct? yes ![image](https://user-images.githubusercontent.com/16351105/133921937-4cb459e7-056a-4494-a017-7baf18a430dd.png)
Author
Owner

@zadjii-msft commented on GitHub (Sep 20, 2021):

The default Terminal only for windows 11 ?

In windows 10, i have not this option in 1.11.2421.0

That's correct, this feature is only available in Windows 11, when you're using the Preview version of the Terminal.

@zadjii-msft commented on GitHub (Sep 20, 2021): > The default Terminal only for windows 11 ? > > In windows 10, i have not this option in 1.11.2421.0 That's correct, this feature is only available in Windows 11, when you're using the Preview version of the Terminal.
Author
Owner

@The-MAZZTer commented on GitHub (Sep 20, 2021):

I have reinstalled Windows 11 in a VM from (mostly) scratch to create a reproduction case.

One thing I really should have mentioned is this involves third-party tools; I THINK they just use MS tools internally (DISM, etc) but I'm not sure. It's entirely possible these tools are responsible for this problem (but I don't see how; I would expect something more catastrophic if the tool produced something broken).

  1. I am using VirtualBox Version 6.1.26 r145957 (Qt5.6.2) under Windows 10 21H1. I have Hyper-V Hypervisor disabled as I find VirtualBox runs better in this configuration.
  2. I downloaded a script from uupdump.net to build a Windows 11 ISO. https://uupdump.net/download.php?id=7fbfaec5-bd63-4532-b022-22eb9247a57e&pack=en-us&edition=professional
  3. I ran the script and allowed it to build the ISO.
  4. I booted my existing Windows 11 VM into the ISO
  5. I used the Repair options from Windows Setup to run regedit and add bypass registry values to ignore TPM/SecureBoot requirements. I added the registry values listed here: https://appuals.com/bypass-windows-11-installation-requirements/
  6. I ran setup.exe from cmd to start Windows Setup. I skipped the key entry. I selected a Custom install, and I formatted and installed over the Windows partition from my previous Windows 11 VM, replacing it.
  7. I booted into Windows 11 and completed the OoB experience wizard with a local account.
  8. I opened Microsoft Store and installed Windows Terminal Preview.
  9. I launched Windows Terminal Preview and opened Settings, and configured it to use Windows Terminal Preview for the default console host.
  10. I hit Win+R and ran cmd.exe
  11. Command Prompt opened in a console host window instead of the expected Windows Terminal Preview.
  12. I verified Windows Settings also showed Windows Terminal Preview was set as the default console host (it was).

Hopefully this will be helpful for reproduction.

@The-MAZZTer commented on GitHub (Sep 20, 2021): I have reinstalled Windows 11 in a VM from (mostly) scratch to create a reproduction case. One thing I really should have mentioned is this involves third-party tools; I THINK they just use MS tools internally (DISM, etc) but I'm not sure. It's entirely possible these tools are responsible for this problem (but I don't see how; I would expect something more catastrophic if the tool produced something broken). 1. I am using VirtualBox Version 6.1.26 r145957 (Qt5.6.2) under Windows 10 21H1. I have Hyper-V Hypervisor disabled as I find VirtualBox runs better in this configuration. 2. I downloaded a script from uupdump.net to build a Windows 11 ISO. https://uupdump.net/download.php?id=7fbfaec5-bd63-4532-b022-22eb9247a57e&pack=en-us&edition=professional 3. I ran the script and allowed it to build the ISO. 4. I booted my existing Windows 11 VM into the ISO 5. I used the Repair options from Windows Setup to run regedit and add bypass registry values to ignore TPM/SecureBoot requirements. I added the registry values listed here: https://appuals.com/bypass-windows-11-installation-requirements/ 6. I ran setup.exe from cmd to start Windows Setup. I skipped the key entry. I selected a Custom install, and I formatted and installed over the Windows partition from my previous Windows 11 VM, replacing it. 7. I booted into Windows 11 and completed the OoB experience wizard with a local account. 8. I opened Microsoft Store and installed Windows Terminal Preview. 9. I launched Windows Terminal Preview and opened Settings, and configured it to use Windows Terminal Preview for the default console host. 10. I hit Win+R and ran cmd.exe 11. Command Prompt opened in a console host window instead of the expected Windows Terminal Preview. 12. I verified Windows Settings also showed Windows Terminal Preview was set as the default console host (it was). Hopefully this will be helpful for reproduction.
Author
Owner

@miniksa commented on GitHub (Sep 20, 2021):

FWIW, I tried to install and use VirtualBox 6.1.26 on my Windows 11 host machine and it couldn't start any VMs. I wonder if that's a known issue for VirtualBox and I need a Windows 10 host machine?

@miniksa commented on GitHub (Sep 20, 2021): FWIW, I tried to install and use VirtualBox 6.1.26 on my Windows 11 host machine and it couldn't start any VMs. I wonder if that's a known issue for VirtualBox and I need a Windows 10 host machine?
Author
Owner

@CDAGaming commented on GitHub (Oct 4, 2021):

Any updates on this?

Given the release of Windows 11 is under 24 hours away at time of writing, I'd love to know whether this was nearing stability...

(On the fence about using the preview version of the terminal, since the only thing I'm after is the default console setting)

@CDAGaming commented on GitHub (Oct 4, 2021): Any updates on this? Given the release of Windows 11 is under 24 hours away at time of writing, I'd love to know whether this was nearing stability... (On the fence about using the preview version of the terminal, since the only thing I'm after is the default console setting)
Author
Owner

@zadjii-msft commented on GitHub (Oct 4, 2021):

@CDAGaming This isn't the thread for that discussion, though I'm not sure there is another one. This one's tracking a very specific bug in the defterm implementation that we're still trying to track down, but there's only the one user with the repro.

I'm gonna file another issue to track that discussion in the immediate future.

@zadjii-msft commented on GitHub (Oct 4, 2021): @CDAGaming This isn't the thread for that discussion, though I'm not sure there is another one. This one's tracking a very specific bug in the defterm implementation that we're still trying to track down, but there's only the one user with the repro. I'm gonna file another issue to track that discussion in the immediate future.
Author
Owner

@zadjii-msft commented on GitHub (Oct 4, 2021):

If you want to discuss that topic more, let's move over to #11415.

We still haven't found anything that looks like a root cause for this one, nor do we have any live repros unfortunately.

@zadjii-msft commented on GitHub (Oct 4, 2021): If you want to discuss that topic more, let's move over to #11415. We still haven't found anything that looks like a root cause for this one, nor do we have any live repros unfortunately.
Author
Owner

@shaunthorne commented on GitHub (Oct 7, 2021):

This seems to be fixed... (Windows 10.0.22000.120, Terminal Preview 1.10.1933.0) But I don't know when fixed. 🤔 When Windows was updated to 22000.120, this should be NOT fixed. Maybe it's when Visual Studio was installed.

Windows 11 Build 2200.194. Windows Terminal Preview 1.11.2731.0

Windows Terminal started to work as expected immediately after installing Visual Studio 2019 with .NET components
Is it kind of magic?
image

@shaunthorne commented on GitHub (Oct 7, 2021): > This seems to be fixed... (Windows 10.0.22000.120, Terminal Preview 1.10.1933.0) But I don't know when fixed. 🤔 When Windows was updated to 22000.120, this should be NOT fixed. Maybe it's when Visual Studio was installed. Windows 11 Build 2200.194. Windows Terminal Preview 1.11.2731.0 Windows Terminal started to work as expected immediately after installing Visual Studio 2019 with .NET components Is it kind of magic? ![image](https://user-images.githubusercontent.com/52523716/136463059-a5af1956-f693-4e00-9ffb-97850822b641.png)
Author
Owner

@zadjii-msft commented on GitHub (Oct 13, 2021):

@The-MAZZTer These questions might seem silly, but I'm just trying to correlate with an internal report of a similar bug. Are you by any chance running on an ARM CPU?

Even more wildly: Is the copy of Windows you're running in VirtualBox activated?

We've got a crazy theory that the second bit might somehow be causing this to fail (but we've still got NO idea why that might be)

@zadjii-msft commented on GitHub (Oct 13, 2021): @The-MAZZTer These questions might seem silly, but I'm just trying to correlate with an internal report of a similar bug. Are you by any chance running on an ARM CPU? Even more wildly: Is the copy of Windows you're running in VirtualBox activated? We've got a crazy theory that the second bit might somehow be causing this to fail (but we've still got NO idea why that might be)
Author
Owner

@NotTheDr01ds commented on GitHub (Oct 18, 2021):

@zadjii-msft While we're waiting on The-MAZZTer's reply, I will chime in that I can also reproduce this with:

  • An activated Windows 11 (22000.258)
  • Installed on KVM/QEMU on a Linux (openSUSE Tumbleweed) installation with nested virtualization enabled
  • Completed initial install with no network, so local account (sounds similar to The-MAZZTer's process)
  • Did not activate during install
  • After reboot, installed virtio drivers
  • Connected to network
  • Activated Windows
  • Converted to Microsoft Account
  • Installed WSL with Ubuntu, Debian, and Alpine
  • Installed Windows Terminal Preview (currently 1.11.2731.0)
  • Set it to default through the Windows "For Developers" settings
  • Ran cmd.exe
  • Opened in Windows Console Host
  • Rebooted
  • Ran cmd.exe
  • Opened in Windows Console Host
@NotTheDr01ds commented on GitHub (Oct 18, 2021): @zadjii-msft While we're waiting on The-MAZZTer's reply, I will chime in that I can also reproduce this with: * An activated Windows 11 (22000.258) * Installed on KVM/QEMU on a Linux (openSUSE Tumbleweed) installation with nested virtualization enabled * Completed initial install with no network, so local account (sounds similar to The-MAZZTer's process) * Did not activate during install * After reboot, installed virtio drivers * Connected to network * Activated Windows * Converted to Microsoft Account * Installed WSL with Ubuntu, Debian, and Alpine * Installed Windows Terminal Preview (currently 1.11.2731.0) * Set it to default through the Windows "For Developers" settings * Ran `cmd.exe` * Opened in Windows Console Host * Rebooted * Ran `cmd.exe` * Opened in Windows Console Host
Author
Owner

@zadjii-msft commented on GitHub (Oct 18, 2021):

@NotTheDr01ds Are you by any chance running on an ARM CPU?

@zadjii-msft commented on GitHub (Oct 18, 2021): @NotTheDr01ds Are you by any chance running on an ARM CPU?
Author
Owner

@NotTheDr01ds commented on GitHub (Oct 18, 2021):

@zadjii-msft I knew I would miss some critical information in there :-). No. The host CPU is an i5-9500T. The kvm setup is per this guide, so the guest is "Skylake, IBRS, No TSX".

@NotTheDr01ds commented on GitHub (Oct 18, 2021): @zadjii-msft I knew I would miss some critical information in there :-). No. The host CPU is an i5-9500T. The kvm setup is per [this guide](https://www.reddit.com/r/VFIO/comments/inrlxc/comment/g70visv/?utm_source=share&utm_medium=web2x&context=3), so the guest is "Skylake, IBRS, No TSX".
Author
Owner

@zadjii-msft commented on GitHub (Oct 26, 2021):

@NotTheDr01ds @The-MAZZTer We think we have a fix for this over in #11610. Could you do the steps in this comment: https://github.com/microsoft/terminal/issues/11529#issuecomment-948649578 and send me the trace? I should be able to tell from the trace if this you were hitting the same cause.

Even if it's not, we should probably move the discussion to a new thread, just so we can follow up and track the bug separately.

@zadjii-msft commented on GitHub (Oct 26, 2021): @NotTheDr01ds @The-MAZZTer We think we have a fix for this over in #11610. Could you do the steps in this comment: https://github.com/microsoft/terminal/issues/11529#issuecomment-948649578 and send me the trace? I should be able to tell from the trace if this you were hitting the same cause. Even if it's not, we should probably move the discussion to a new thread, just so we can follow up and track the bug separately.
Author
Owner

@The-MAZZTer commented on GitHub (Oct 27, 2021):

@zadjii-msft Alright, I haven't updated my VM to Windows 11 RTM so it is still on 22458.1000, and I generated the trace using it. Let me know if you want a trace running on Windows 11 RTM or whatever.

Trace sent to your e-mail as directed.

@The-MAZZTer commented on GitHub (Oct 27, 2021): @zadjii-msft Alright, I haven't updated my VM to Windows 11 RTM so it is still on 22458.1000, and I generated the trace using it. Let me know if you want a trace running on Windows 11 RTM or whatever. Trace sent to your e-mail as directed.
Author
Owner

@zadjii-msft commented on GitHub (Oct 27, 2021):

Yep, that's the same thing. Manually installing the visual c++ redistributable will probably fix this for you. We'll probably roll out a hotfix with #11610 in it soon enough.

Thanks everyone for the persistence on this one!

@zadjii-msft commented on GitHub (Oct 27, 2021): Yep, that's the same thing. Manually installing the visual c++ redistributable will probably fix this for you. We'll probably roll out a hotfix with #11610 in it soon enough. Thanks everyone for the persistence on this one!
Author
Owner

@szilvaa-adsk commented on GitHub (Oct 29, 2021):

I'm seeing this issue when I run cmd.exe as ADMINISTRATOR. It works fine when I run it as "regular user".

Steps to repro:

  1. Open File Explorer
  2. Right click on %windir%\system32\cmd.exe and choose "Run as Administrator".

Actual results:
Cmd.exe runs with Conhost.

Expected result:
Cmd.exe runs with Windows Terminal. In fact, this happens if I simply click on cmd.exe (without choosing "Run As Administrator")

Windows version: 10.0.22000.282
Terminal version: 1.11.2921.0
I also have VS 2019 16.11.5 and VS 2022 Preview4 installed in case that matters.

@szilvaa-adsk commented on GitHub (Oct 29, 2021): I'm seeing this issue when I run cmd.exe as **ADMINISTRATOR**. It works fine when I run it as "regular user". Steps to repro: 1. Open File Explorer 2. Right click on %windir%\system32\cmd.exe and choose "Run as Administrator". Actual results: Cmd.exe runs with Conhost. Expected result: Cmd.exe runs with Windows Terminal. In fact, this happens if I simply click on cmd.exe (without choosing "Run As Administrator") Windows version: 10.0.22000.282 Terminal version: 1.11.2921.0 I also have VS 2019 16.11.5 and VS 2022 Preview4 installed in case that matters.
Author
Owner

@zadjii-msft commented on GitHub (Oct 29, 2021):

@szilvaa-adsk Please read the FAQ.

Launching elevated commandline applications won't open in the Terminal. Unfortunately, this is by design right now. Due to a limitation in the app platform it is impossible for Terminal to be "discovered" as the handler when the application that needs a terminal is running elevated. We're working on this, but this is something that needs OS-side work to resolve.

@zadjii-msft commented on GitHub (Oct 29, 2021): @szilvaa-adsk Please [read the FAQ](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#launching-the-windows-terminal-as-the-default-terminal-doesnt-work---it-opens-the-vintage-console-window-instead). > Launching elevated commandline applications won't open in the Terminal. Unfortunately, this is by design right now. Due to a limitation in the app platform it is impossible for Terminal to be "discovered" as the handler when the application that needs a terminal is running elevated. We're working on this, but this is something that needs OS-side work to resolve.
Author
Owner

@ghost commented on GitHub (Nov 3, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Nov 3, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@The-MAZZTer commented on GitHub (Nov 3, 2021):

@zadjii-msft Missed your other questions, I'm running on a x64 host (is there even an ARM VirtualBox?) and I didn't activate Windows 11 since I don't have a license, apart from a couple Windows 10 ones (just wanted to take a sneak peek before I update my Windows 10 PC).

@The-MAZZTer commented on GitHub (Nov 3, 2021): @zadjii-msft Missed your other questions, I'm running on a x64 host (is there even an ARM VirtualBox?) and I didn't activate Windows 11 since I don't have a license, apart from a couple Windows 10 ones (just wanted to take a sneak peek before I update my Windows 10 PC).
Author
Owner

@zadjii-msft commented on GitHub (Nov 3, 2021):

@The-MAZZTer Oh sorry, we moved on past those theories. We believe this was due to an accidental dependency on the CRT. Manually installing the C Runtime should fix this (until we roll out a hotfix build of the Terminal that doesn't have this dependency anymore)

@zadjii-msft commented on GitHub (Nov 3, 2021): @The-MAZZTer Oh sorry, we moved on past those theories. We believe this was due to an accidental dependency on the CRT. Manually installing the [C Runtime](https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-160) should fix this (until we roll out a hotfix build of the Terminal that doesn't have this dependency anymore)
Author
Owner

@ghost commented on GitHub (Nov 7, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Nov 7, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14434