&#34;Default Terminal&#34; mysteriously doesn&#39;t work at all - boots up the vintage console instead #15569

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

@zadjii-msft

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

claunia commented

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

What OS build are you using?
can you share what's in HKEY_CURRENT_USER\Console\%%Startup?
What architecture is your machine? (AMD64? x86? ARM?)

#11524 might be related, https://github.com/microsoft/terminal/issues/10594#issuecomment-945232104 may ne as well

@zadjii-msft commented on GitHub (Oct 18, 2021): * What OS build are you using? * can you share what's in `HKEY_CURRENT_USER\Console\%%Startup`? * What architecture is your machine? (AMD64? x86? ARM?) #11524 might be related, https://github.com/microsoft/terminal/issues/10594#issuecomment-945232104 may ne as well

claunia commented

@ghost commented on GitHub (Oct 19, 2021):

OS Bulid - 22000.258

x64

@ghost commented on GitHub (Oct 19, 2021): OS Bulid - 22000.258 ![image](https://user-images.githubusercontent.com/84385465/137900401-a143bf00-73f6-4cae-88c5-c8802ae0a4f5.png) x64

claunia commented

@ghost commented on GitHub (Oct 19, 2021):

@zadjii-msft

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

claunia commented

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

That all seems on the up-and-up.... I think at the moment we're at a but of an impasse as far as trying to debug this one. However, we'll hopefully be shipping 1.12 later this week. When that lands, I'm gonna try following up with you to see if you can follow some other repro steps with 1.12. That should include a bunch more diagnostics which should help to figure out what's going on here.

Couple other questions off the dome while thinking about this:

Are you trying to run cmd.exe elevated / as an admin? (this includes anything that might autoelevate cmd.exe, like this checkbox:
Does your machine have UAC disabled?

@zadjii-msft commented on GitHub (Oct 19, 2021): That all seems on the up-and-up.... I think at the moment we're at a but of an impasse as far as trying to debug this one. However, we'll hopefully be shipping 1.12 later this week. When that lands, I'm gonna try following up with you to see if you can follow some other repro steps with 1.12. That should include a bunch more diagnostics which should help to figure out what's going on here. Couple other questions off the dome while thinking about this: * Are you trying to run `cmd.exe` elevated / as an admin? (this includes anything that might autoelevate cmd.exe, like this checkbox: ![image](https://user-images.githubusercontent.com/18356694/137946864-c2dadb97-6e7b-4eb2-b1b8-56943bade324.png) * Does your machine have UAC disabled?

claunia commented

@ghost commented on GitHub (Oct 19, 2021):

Are you trying to run cmd.exe elevated / as an admin? (this includes anything that might autoelevate cmd.exe, like this - No
Does your machine have UAC disabled? - It is enabled

@ghost commented on GitHub (Oct 19, 2021): Are you trying to run cmd.exe elevated / as an admin? (this includes anything that might autoelevate cmd.exe, like this - No Does your machine have UAC disabled? - It is enabled

claunia commented

@ghost commented on GitHub (Oct 21, 2021):

@zadjii-msft it is fixed or not?

@ghost commented on GitHub (Oct 21, 2021): @zadjii-msft it is fixed or not?

claunia commented

@happybear88 commented on GitHub (Oct 21, 2021):

Same here with v1.11.2921.0 on two pretty much clean install VMs (Home, Pro) with 22000.258
Repro with powershell 5.1 and cmd when launched from Start, win+r. Neither is elevated in any way.
FWIW, the same issue is repro with the Terminal Preview.

@happybear88 commented on GitHub (Oct 21, 2021): Same here with v1.11.2921.0 on two pretty much clean install VMs (Home, Pro) with 22000.258 Repro with powershell 5.1 and cmd when launched from Start, win+r. Neither is elevated in any way. FWIW, the same issue is repro with the Terminal Preview. ![terminal](https://user-images.githubusercontent.com/18210408/138227279-342a2e5d-9b39-4397-8378-2f28b8794d6f.gif)

claunia commented

@ghost commented on GitHub (Oct 21, 2021):

Same here with v1.11.2921.0 on two pretty much clean install VMs (Home, Pro) with 22000.258 Repro with powershell 5.1 and cmd when launched from Start, win+r. Neither is elevated in any way. FWIW, the same issue is repro with the Terminal Preview.

It is in Stable version of Windows Terminal no preview. Good to know

@ghost commented on GitHub (Oct 21, 2021): > Same here with v1.11.2921.0 on two pretty much clean install VMs (Home, Pro) with 22000.258 Repro with powershell 5.1 and cmd when launched from Start, win+r. Neither is elevated in any way. FWIW, the same issue is repro with the Terminal Preview. ![terminal](https://user-images.githubusercontent.com/18210408/138227279-342a2e5d-9b39-4397-8378-2f28b8794d6f.gif) It is in Stable version of Windows Terminal no preview. Good to know

claunia commented

@ghost commented on GitHub (Oct 21, 2021):

Same here with v1.11.2921.0 on two pretty much clean install VMs (Home, Pro) with 22000.258 Repro with powershell 5.1 and cmd when launched from Start, win+r. Neither is elevated in any way. FWIW, the same issue is repro with the Terminal Preview.

It is in Stable version of Windows Terminal no preview. Good to know

It is not working with Start Menu also

@ghost commented on GitHub (Oct 21, 2021): > > Same here with v1.11.2921.0 on two pretty much clean install VMs (Home, Pro) with 22000.258 Repro with powershell 5.1 and cmd when launched from Start, win+r. Neither is elevated in any way. FWIW, the same issue is repro with the Terminal Preview. ![terminal](https://user-images.githubusercontent.com/18210408/138227279-342a2e5d-9b39-4397-8378-2f28b8794d6f.gif) > > It is in Stable version of Windows Terminal no preview. Good to know It is not working with Start Menu also

claunia commented

@ghost commented on GitHub (Oct 21, 2021):

@zadjii-msft ?????

@ghost commented on GitHub (Oct 21, 2021): @zadjii-msft ?????

claunia commented

@happybear88 commented on GitHub (Oct 21, 2021):

Please stop spamming the thread. I guess posting here was a mistake. Unsubscribed. If dev needs my input, reach out otherwise.

@happybear88 commented on GitHub (Oct 21, 2021): Please stop spamming the thread. I guess posting here was a mistake. Unsubscribed. If dev needs my input, reach out otherwise.

claunia commented

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

Hokay, so while we don't think this was fixed in 1.12, there should be some additional logging that might be useful. To get these logs, I'm gonna need you to follow a couple steps:

Download the Terminal.wprp file from our repo somewhere on your PC. For example, let's put the file at C:\path\to\Terminal.wprp
Setup Windows Terminal Preview as the default terminal application. You can do this in the Console Property sheet, the Settings app, the Terminal Settings UI, anywhere, doesn't matter. It just needs to be set to Windows Terminal Preview, so we get the diagnostics from 1.12.
(Preferably, close all other Terminal & console windows. That'll make the logging less noisy).
From an elevated commandline, run:

wpr -start C:\path\to\Terminal.wprp!Defterm.Verbose

Try launching powershell.exe or cmd.exe. Could be from the Start Menu, the Run Dialog, anywhere. Doesn't matter. (It'll pop up in the vintage console window, but that's fine. We want to find out why that happened.)
Go back to the elevated commandline window and run:

wpr -stop defterm-trace.etl

Take the defterm-trace.etl file, and send it to me (my email is on my GH profile).

HOPEFULLY, the logging we added in #11537 should help clue us in as to why this is failing.

@zadjii-msft commented on GitHub (Oct 21, 2021): Hokay, so while we don't think this was fixed in 1.12, there should be some additional logging that might be useful. To get these logs, I'm gonna need you to follow a couple steps: 1. Download the [`Terminal.wprp` file from our repo](https://github.com/microsoft/terminal/blob/main/src/Terminal.wprp) somewhere on your PC. For example, let's put the file at `C:\path\to\Terminal.wprp` 2. Setup Windows Terminal Preview as the default terminal application. You can do this in the Console Property sheet, the Settings app, the Terminal Settings UI, anywhere, doesn't matter. It just needs to be set to Windows Terminal Preview, so we get the diagnostics from 1.12. 3. (Preferably, close all other Terminal & console windows. That'll make the logging less noisy). 4. From an elevated commandline, run: ``` wpr -start C:\path\to\Terminal.wprp!Defterm.Verbose ``` 5. Try launching `powershell.exe` or `cmd.exe`. Could be from the Start Menu, the Run Dialog, anywhere. Doesn't matter. (It'll pop up in the vintage console window, but that's fine. We want to find out why that happened.) 6. Go back to the elevated commandline window and run: ``` wpr -stop defterm-trace.etl ``` 7. Take the `defterm-trace.etl` file, and send it to me (my email is on my GH profile). HOPEFULLY, the logging we added in #11537 should help clue us in as to why this is failing.

claunia commented

@ghost commented on GitHub (Oct 21, 2021):

ok I will try that

@ghost commented on GitHub (Oct 21, 2021): ok I will try that

claunia commented

@ghost commented on GitHub (Oct 21, 2021):

@zadjii-msft Where is the defterm-trace.etl file at?

@ghost commented on GitHub (Oct 21, 2021): @zadjii-msft Where is the defterm-trace.etl file at?

claunia commented

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

It's wherever you ran that command. So if you were in C:\Windows\System32, then the file was created at C:\Windows\System32\defterm-trace.etl

@zadjii-msft commented on GitHub (Oct 21, 2021): It's wherever you ran that command. So if you were in `C:\Windows\System32`, then the file was created at `C:\Windows\System32\defterm-trace.etl`

claunia commented

@ghost commented on GitHub (Oct 21, 2021):

ok

@ghost commented on GitHub (Oct 21, 2021): ok

claunia commented

@ghost commented on GitHub (Oct 21, 2021):

did not make the file

@ghost commented on GitHub (Oct 21, 2021): did not make the file ![image](https://user-images.githubusercontent.com/84385465/138311166-aa09e725-652d-4fcf-8f16-def56d09cf32.png)

claunia commented

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

Maybe:

@zadjii-msft commented on GitHub (Oct 21, 2021): Maybe: ![Inked138311166-aa09e725-652d-4fcf-8f16-def56d09cf32](https://user-images.githubusercontent.com/18356694/138312627-ea7917fb-75e9-448e-b032-49b10bf5db95.jpg)

claunia commented

@ghost commented on GitHub (Oct 21, 2021):

Maybe:

that is the fill I downloaded https://github.com/microsoft/terminal/blob/main/src/Terminal.wprp

@ghost commented on GitHub (Oct 21, 2021): > Maybe: > > ![Inked138311166-aa09e725-652d-4fcf-8f16-def56d09cf32](https://user-images.githubusercontent.com/18356694/138312627-ea7917fb-75e9-448e-b032-49b10bf5db95.jpg) that is the fill I downloaded https://github.com/microsoft/terminal/blob/main/src/Terminal.wprp

claunia commented

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

Derp. Not enough coffee. Try it again, with wpr -stop C:\defterm-trace.etl

@zadjii-msft commented on GitHub (Oct 21, 2021): Derp. Not enough coffee. Try it again, with `wpr -stop C:\defterm-trace.etl`

claunia commented

@ghost commented on GitHub (Oct 21, 2021):

@ghost commented on GitHub (Oct 21, 2021): ![image](https://user-images.githubusercontent.com/84385465/138314914-150af617-7129-4271-8351-9517418473ef.png)

claunia commented

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

Sorry, more correctly, run steps 4 through 7 again, but use wpr -stop C:\defterm-trace.etl as the commandline in step 6

@zadjii-msft commented on GitHub (Oct 21, 2021): Sorry, more correctly, run _steps 4 through 7_ again, but use `wpr -stop C:\defterm-trace.etl` as the commandline in step 6

claunia commented

@ghost commented on GitHub (Oct 23, 2021):

@zadjii-msft
sorry for not responding
after a restart it worked

@ghost commented on GitHub (Oct 23, 2021): @zadjii-msft sorry for not responding after a restart it worked

claunia commented

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

Somehow, that raises more questions. I suppose I'll use one of the other open threads to track this. Thanks for following up!

@zadjii-msft commented on GitHub (Oct 23, 2021): Somehow, that raises _more questions_. I suppose I'll use one of the other open threads to track this. Thanks for following up!

claunia commented

@happybear88 commented on GitHub (Oct 25, 2021):

@zadjii-msft the issue is still repro, and I sent you ETL on Friday. Reopen please.

@happybear88 commented on GitHub (Oct 25, 2021): @zadjii-msft the issue is still repro, and I sent you ETL on Friday. Reopen please.

claunia commented

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

@happybear88 thanks for the trace! From the looks of it, the problem is this entry:

"CallingContext:    
Code:   
File:   onecore\windows\core\console\open\src\server\iodispatchers.cpp
Function:   
HResult:    0x8007007E
LineNumber:     283
Message:    
Module:     conhost.exe
Site:   0x7FF7C8513F75"

Which is this line:

THROW_IF_FAILED(CoCreateInstance(Globals.handoffConsoleClsid.value(), nullptr, CLSCTX_LOCAL_SERVER, IID_PPV_ARGS(&handoff)));

0x8007007E is ERROR_MOD_NOT_FOUND. Interesting.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\ClassIndex\{86633F1F-6454-40EC-89CE-DA4EBA977EE2}
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe

@happybear88 Can I get you to export Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe in the registry as a txt file and share that here? Should look something like

expando for the output of exporting the reg key

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Class]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Class\{02DB545A-3E20-46DE-83A5-1329B1E88B6B}]
"ServerId"=dword:00000002
"DllPath"="WindowsTerminalShellExt.dll"
"Threading"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Class\{06EC847C-C0A5-46B8-92CB-7C92F6E35CD5}]
"ServerId"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Class\{86633F1F-6454-40EC-89CE-DA4EBA977EE2}]
"ServerId"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Interface]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Interface\{59D55CCE-FC8A-48B4-ACE8-0A9286C6557F}]
"ProxyStubCLSID"="{1833E661-CC81-4DD0-87C6-C2F74BD39EFA}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Interface\{E686C757-9A35-4A1C-B3CE-0BCC8B5C69F4}]
"ProxyStubCLSID"="{1833E661-CC81-4DD0-87C6-C2F74BD39EFA}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\ProxyStub]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\ProxyStub\{1833E661-CC81-4DD0-87C6-C2F74BD39EFA}]
"DisplayName"="OpenConsoleHandoffProxy"
"DllPath_x64"="OpenConsoleProxy.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Server]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Server\0]
"ApplicationId"="App"
"ApplicationDisplayName"="@{Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.WindowsTerminalPreview/Resources/AppNamePre}"
"DisplayName"="OpenConsole"
"Executable"="OpenConsole.exe"
"IsSystemExecutable"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Server\1]
"ApplicationId"="App"
"ApplicationDisplayName"="@{Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.WindowsTerminalPreview/Resources/AppNamePre}"
"DisplayName"="WindowsTerminal"
"Executable"="WindowsTerminal.exe"
"IsSystemExecutable"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Server\2]
"ApplicationId"="App"
"ApplicationDisplayName"="@{Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.WindowsTerminalPreview/Resources/AppNamePre}"
"DisplayName"="WindowsTerminalShellExt"
"SurrogateAppId"="{02DB545A-3E20-46DE-83A5-1329B1E88B6B}"

@zadjii-msft commented on GitHub (Oct 25, 2021): @happybear88 thanks for the trace! From the looks of it, the problem is this entry: ``` "CallingContext: Code: File: onecore\windows\core\console\open\src\server\iodispatchers.cpp Function: HResult: 0x8007007E LineNumber: 283 Message: Module: conhost.exe Site: 0x7FF7C8513F75" ``` Which is this line: ```c++ THROW_IF_FAILED(CoCreateInstance(Globals.handoffConsoleClsid.value(), nullptr, CLSCTX_LOCAL_SERVER, IID_PPV_ARGS(&handoff))); ``` `0x8007007E` is `ERROR_MOD_NOT_FOUND`. Interesting. ``` Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\ClassIndex\{86633F1F-6454-40EC-89CE-DA4EBA977EE2} Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe ``` @happybear88 Can I get you to export `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe` in the registry as a `txt` file and share that here? Should look something like ![image](https://user-images.githubusercontent.com/18356694/138691172-5a314561-50d8-4070-b09f-6fdd469b430c.png) <details> <summary>expando for the output of exporting the reg key</summary> ``` Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Class] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Class\{02DB545A-3E20-46DE-83A5-1329B1E88B6B}] "ServerId"=dword:00000002 "DllPath"="WindowsTerminalShellExt.dll" "Threading"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Class\{06EC847C-C0A5-46B8-92CB-7C92F6E35CD5}] "ServerId"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Class\{86633F1F-6454-40EC-89CE-DA4EBA977EE2}] "ServerId"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Interface] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Interface\{59D55CCE-FC8A-48B4-ACE8-0A9286C6557F}] "ProxyStubCLSID"="{1833E661-CC81-4DD0-87C6-C2F74BD39EFA}" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Interface\{E686C757-9A35-4A1C-B3CE-0BCC8B5C69F4}] "ProxyStubCLSID"="{1833E661-CC81-4DD0-87C6-C2F74BD39EFA}" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\ProxyStub] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\ProxyStub\{1833E661-CC81-4DD0-87C6-C2F74BD39EFA}] "DisplayName"="OpenConsoleHandoffProxy" "DllPath_x64"="OpenConsoleProxy.dll" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Server] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Server\0] "ApplicationId"="App" "ApplicationDisplayName"="@{Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.WindowsTerminalPreview/Resources/AppNamePre}" "DisplayName"="OpenConsole" "Executable"="OpenConsole.exe" "IsSystemExecutable"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Server\1] "ApplicationId"="App" "ApplicationDisplayName"="@{Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.WindowsTerminalPreview/Resources/AppNamePre}" "DisplayName"="WindowsTerminal" "Executable"="WindowsTerminal.exe" "IsSystemExecutable"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe\Server\2] "ApplicationId"="App" "ApplicationDisplayName"="@{Microsoft.WindowsTerminalPreview_1.12.2811.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.WindowsTerminalPreview/Resources/AppNamePre}" "DisplayName"="WindowsTerminalShellExt" "SurrogateAppId"="{02DB545A-3E20-46DE-83A5-1329B1E88B6B}" ``` </details>

claunia commented

@happybear88 commented on GitHub (Oct 25, 2021):

Hi @zadjii-msft. Thanks for getting back with me. I don't have the preview version installed. I don't remember if I had installed it while trying to see if the issue would be repro with preview. But there's no preview key in the registry, only those two:

That's why the preview is not found I guess.

@happybear88 commented on GitHub (Oct 25, 2021): Hi @zadjii-msft. Thanks for getting back with me. I don't have the preview version installed. I don't remember if I had installed it while trying to see if the issue would be repro with preview. But there's no preview key in the registry, only those two: ![image](https://user-images.githubusercontent.com/18210408/138692603-be984cf2-45da-4374-8e95-661ecc1b54ea.png) That's why the preview is not found I guess.

claunia commented

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

@happybear88 Oh, yea derp that makes sense. Can you export both of those actually? That might help.

@zadjii-msft commented on GitHub (Oct 25, 2021): @happybear88 Oh, yea derp that makes sense. Can you export both of those actually? That might help.

claunia commented

@happybear88 commented on GitHub (Oct 25, 2021):

@zadjii-msft the 1.10 key is gone already after reboot, probably got cleaned up. 1.11 is attached
terminal-package.txt

I can try installing preview and running a trace on preview, if you wish.
FWIW, the same issue is on another account, which is a local administrator (the one I'm reporting from is limited MSA).

@happybear88 commented on GitHub (Oct 25, 2021): @zadjii-msft the 1.10 key is gone already after reboot, probably got cleaned up. 1.11 is attached [terminal-package.txt](https://github.com/microsoft/terminal/files/7410260/terminal-package.txt) I can try installing preview and running a trace on preview, if you wish. FWIW, the same issue is on another account, which is a local administrator (the one I'm reporting from is limited MSA).

claunia commented

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

reposted here for ease, manually converted to .reg because it's a tad easier to parse

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Class]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Class\{2EACA947-7F5F-4CFA-BA87-8F7FBEEFBE69}]
"ServerId"=dword:0


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Class\{9F156763-7844-4DC4-B2B1-901F640F5155}]
"ServerId"=dword:0x2
"DllPath"='WindowsTerminalShellExt.dll'
"Threading"=dword:0


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Class\{E12CFF52-A866-4C77-9A90-F570A7AA2C6B}]
"ServerId"=dword:0x1


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Interface]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Interface\{59D55CCE-FC8A-48B4-ACE8-0A9286C6557F}]
"ProxyStubCLSID"="{3171DE52-6EFA-4AEF-8A9F-D02BD67E7A4F}"


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Interface\{E686C757-9A35-4A1C-B3CE-0BCC8B5C69F4}]
"ProxyStubCLSID"="{3171DE52-6EFA-4AEF-8A9F-D02BD67E7A4F}"


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\ProxyStub]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\ProxyStub\{3171DE52-6EFA-4AEF-8A9F-D02BD67E7A4F}]
"DisplayName"="OpenConsoleHandoffProxy"
"DllPath_x64"='OpenConsoleProxy.dll'


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Server]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Server\0]
"ApplicationId"="App"
"ApplicationDisplayName"="@{Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.WindowsTerminal/Resources/AppName}"
"DisplayName"="OpenConsole"
"Executable"="OpenConsole.exe"
"IsSystemExecutable"=dword:0


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Server\1]
"ApplicationId"="App"
"ApplicationDisplayName"="@{Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.WindowsTerminal/Resources/AppName}"
"DisplayName"="WindowsTerminal"
"Executable"="WindowsTerminal.exe"
"IsSystemExecutable"=dword:0


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Server\2]
"ApplicationId"="App"
"ApplicationDisplayName"="@{Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.WindowsTerminal/Resources/AppName}"
"DisplayName"="WindowsTerminalShellExt"
"SurrogateAppId"="{9F156763-7844-4DC4-B2B1-901F640F5155}"

the 1.10 key is gone already after reboot, probably got cleaned up.

Makes sense. Sometimes the app catalog just takes a little while to clean it all up.

I can try installing preview and running a trace on preview, if you wish.

I don't think that'll totally be necessary. The error we're getting was logged just fine on 1.11, and I don't think I added any logging for that specific case. I'm trying to figure out why COM is failing to instantiate the OpenConsole.exe to do the console handoff. The CoCreateInstance(Globals.handoffConsoleClsid.value(),... call is the one the OS does to try and delegate the creation of the console to another console host. in this case, we're trying to tell the OS "use the conhost that's in the package, rather than the one in the OS". The one that's in the package will then do the delegation to the Terminal that's also living in the package. it's a multi-step process, but we're failing the very first part.

Okay, one other thing to check too.

@happybear88 From an elevated PowerShell prompt, can you run

get-ChildItem "C:\Program Files\WindowsApps" | where {$_.name -like "*Terminal*"} | foreach-object { gci $_.fullname }

and post the output here? That'll be long, but might also help figure out why COM thinks it can't open OpenConsole.exe or OpenConsoleProxy.dll

@zadjii-msft commented on GitHub (Oct 25, 2021): <details> <summary>reposted here for ease, manually converted to .reg because it's a tad easier to parse</summary> ``` [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Class] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Class\{2EACA947-7F5F-4CFA-BA87-8F7FBEEFBE69}] "ServerId"=dword:0 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Class\{9F156763-7844-4DC4-B2B1-901F640F5155}] "ServerId"=dword:0x2 "DllPath"='WindowsTerminalShellExt.dll' "Threading"=dword:0 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Class\{E12CFF52-A866-4C77-9A90-F570A7AA2C6B}] "ServerId"=dword:0x1 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Interface] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Interface\{59D55CCE-FC8A-48B4-ACE8-0A9286C6557F}] "ProxyStubCLSID"="{3171DE52-6EFA-4AEF-8A9F-D02BD67E7A4F}" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Interface\{E686C757-9A35-4A1C-B3CE-0BCC8B5C69F4}] "ProxyStubCLSID"="{3171DE52-6EFA-4AEF-8A9F-D02BD67E7A4F}" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\ProxyStub] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\ProxyStub\{3171DE52-6EFA-4AEF-8A9F-D02BD67E7A4F}] "DisplayName"="OpenConsoleHandoffProxy" "DllPath_x64"='OpenConsoleProxy.dll' [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Server] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Server\0] "ApplicationId"="App" "ApplicationDisplayName"="@{Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.WindowsTerminal/Resources/AppName}" "DisplayName"="OpenConsole" "Executable"="OpenConsole.exe" "IsSystemExecutable"=dword:0 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Server\1] "ApplicationId"="App" "ApplicationDisplayName"="@{Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.WindowsTerminal/Resources/AppName}" "DisplayName"="WindowsTerminal" "Executable"="WindowsTerminal.exe" "IsSystemExecutable"=dword:0 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\Package\Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe\Server\2] "ApplicationId"="App" "ApplicationDisplayName"="@{Microsoft.WindowsTerminal_1.11.2921.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.WindowsTerminal/Resources/AppName}" "DisplayName"="WindowsTerminalShellExt" "SurrogateAppId"="{9F156763-7844-4DC4-B2B1-901F640F5155}" ``` </details> > the 1.10 key is gone already after reboot, probably got cleaned up. Makes sense. Sometimes the app catalog just takes a little while to clean it all up. > I can try installing preview and running a trace on preview, if you wish. I don't think that'll totally be necessary. The error we're getting was logged just fine on 1.11, and I don't think I added any logging for that specific case. I'm trying to figure out why COM is failing to instantiate the `OpenConsole.exe` to do the console handoff. The `CoCreateInstance(Globals.handoffConsoleClsid.value(),...` call is the one the OS does to try and delegate the creation of the _console_ to another console host. in this case, we're trying to tell the OS "use the conhost that's in the package, rather than the one in the OS". The one that's in the package will then do the delegation to the Terminal that's also living in the package. it's a multi-step process, but we're failing the very first part. Okay, one other thing to check too. @happybear88 From an elevated PowerShell prompt, can you run ```powershell get-ChildItem "C:\Program Files\WindowsApps" | where {$_.name -like "*Terminal*"} | foreach-object { gci $_.fullname } ``` and post the output here? That'll be long, but _might_ also help figure out why COM thinks it can't open `OpenConsole.exe` or `OpenConsoleProxy.dll`

claunia commented

@happybear88 commented on GitHub (Oct 25, 2021):

@zadjii-msft please see gci.txt

@happybear88 commented on GitHub (Oct 25, 2021): @zadjii-msft please see [gci.txt](https://github.com/microsoft/terminal/files/7410445/gci.txt)

claunia commented

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

Fudge. Okay. I don't see anything out of place there. Lemme reach out to our pals on the COM team, see if they have any ideas on how we could diagnose why we're getting a ERROR_MOD_NOT_FOUND there.

@zadjii-msft commented on GitHub (Oct 25, 2021): Fudge. Okay. I don't see anything out of place there. Lemme reach out to our pals on the COM team, see if they have any ideas on how we could diagnose why we're getting a `ERROR_MOD_NOT_FOUND` there.

claunia commented

@ghost commented on GitHub (Oct 25, 2021):

I think it affects after a restart

@ghost commented on GitHub (Oct 25, 2021): I think it affects after a restart

claunia commented

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

@happybear88 CRAZY question - Do you have Visual Studio installed? (same to @BajajAditya123)

@zadjii-msft commented on GitHub (Oct 25, 2021): @happybear88 CRAZY question - Do you have Visual Studio installed? (same to @BajajAditya123)

claunia commented

@ghost commented on GitHub (Oct 25, 2021):

I have Visual Studio Code

@ghost commented on GitHub (Oct 25, 2021): I have Visual Studio Code

claunia commented

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

We're thinking there's some dependent c runtime dll that might not necessarily be installed by default, but does get installed with VS. @BajajAditya123 Any chance if you remember if you installed something between the Terminal not working 4 days ago and starting to work 2 days ago?

@zadjii-msft commented on GitHub (Oct 25, 2021): We're thinking there's some dependent c runtime dll that might not necessarily be installed by default, but does get installed with VS. @BajajAditya123 Any chance if you remember if you installed something between the Terminal not working 4 days ago and starting to work 2 days ago?

claunia commented

@happybear88 commented on GitHub (Oct 25, 2021):

Hi @zadjii-msft,
You don't have to look for external factors. You should be able to repro with these steps, I just did. And that's the third time out of three I repro this with Windows 11 home and pro editions out of the box.

D/l the Windows 11 ISO from https://www.microsoft.com/en-us/software-download/windows11 (I used EN)
Install the OS [on Hyper-V VM] with networking off.
Enable the network adapter and make sure you get the App Installer installed from the Store.
Run winget upgrade "windows terminal" and ensure you have 1.11
Set WT as the default terminal in its settings and Save.
Run CMD or powershell
AR: both open separately, not inside the WT

P.S. I install w/o the network simply to speed things up. Takes under 10 minutes. Installing the latest updates and rebooting have no effect on the issue, still repro.

@happybear88 commented on GitHub (Oct 25, 2021): Hi @zadjii-msft, You don't have to look for external factors. You should be able to repro with these steps, I just did. And that's the third time out of three I repro this with Windows 11 home and pro editions **out of the box.** 1. D/l the Windows 11 ISO from https://www.microsoft.com/en-us/software-download/windows11 (I used EN) 2. Install the OS [on Hyper-V VM] with networking off. 3. Enable the network adapter and make sure you get the App Installer installed from the Store. 4. Run _winget upgrade "windows terminal"_ and ensure you have 1.11 5. Set WT as the default terminal in its settings and Save. 6. Run CMD or powershell AR: both open separately, not inside the WT P.S. I install w/o the network simply to speed things up. Takes under 10 minutes. Installing the latest updates and rebooting have no effect on the issue, still repro.

claunia commented

@miniksa commented on GitHub (Oct 25, 2021):

@lhecker and I are testing the CRT theory with advice about our proxy stub from @brialmsft.

@miniksa commented on GitHub (Oct 25, 2021): @lhecker and I are testing the CRT theory with advice about our proxy stub from @brialmsft.

claunia commented

@eryksun commented on GitHub (Oct 30, 2021):

We're thinking there's some dependent c runtime dll that might not necessarily be installed by default

This was an easy fix for my vanilla test VM. I just had to install the Visual C++ Redistributable, which installed the required "vcruntime140.dll" file to the system directory. This C runtime DLL is actually beside "OpenConsoleProxy.dll" in the Windows Terminal Preview directory in "%ProgramFiles%\WindowsApps", but I suppose the COM host doesn't load "OpenConsoleProxy.dll" using the flag LOAD_LIBRARY_SEARCH_DLL_LOAD_DIR.

@eryksun commented on GitHub (Oct 30, 2021): > We're thinking there's some dependent c runtime dll that might not necessarily be installed by default This was an easy fix for my vanilla test VM. I just had to install the Visual C++ Redistributable, which installed the required "vcruntime140.dll" file to the system directory. This C runtime DLL is actually beside "OpenConsoleProxy.dll" in the Windows Terminal Preview directory in "%ProgramFiles%\\WindowsApps", but I suppose the COM host doesn't load "OpenConsoleProxy.dll" using the flag `LOAD_LIBRARY_SEARCH_DLL_LOAD_DIR`.

claunia commented

@brialmsft commented on GitHub (Nov 1, 2021):

COM uses LOAD_WITH_ALTERED_SEARCH_PATH, which should be able to resolve dependencies on DLLs adjacent to the main DLL being loaded by LoadLibraryEx. See https://docs.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order#alternate-search-order-for-desktop-applications

@brialmsft commented on GitHub (Nov 1, 2021): COM uses LOAD_WITH_ALTERED_SEARCH_PATH, which should be able to resolve dependencies on DLLs adjacent to the main DLL being loaded by LoadLibraryEx. See https://docs.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order#alternate-search-order-for-desktop-applications

claunia commented