Terminal or Terminal Preview crashes when dragging a tab #20831

@marcosjahn commented on GitHub (Nov 17, 2023):

Hello @zadjii-msft! Thanks for your help.

If I launch the Terminal or the Terminal Preview from the Start Menu or Store, the app fails to launch and generates an item in the Event Viewer.

However, if I run "cmd" in the "Run" option (Win + R), the Terminal (or Terminal Preview) opens the prompt correctly. But, I cannot open more tabs - the app closes unexpectedly.

I don't have BeyondTrust installed on my machine. Before I tried disabling WER, the Terminal or Terminal Preview app was working correctly.

How can I check if my Terminal was configured to open the previous session? I don't remember enabling this feature...

@marcosjahn commented on GitHub (Nov 17, 2023): Hello @zadjii-msft! Thanks for your help. If I launch the Terminal or the Terminal Preview from the Start Menu or Store, the app fails to launch and generates an item in the Event Viewer. However, if I run "cmd" in the "Run" option (Win + R), the Terminal (or Terminal Preview) opens the prompt correctly. But, I cannot open more tabs - the app closes unexpectedly. I don't have BeyondTrust installed on my machine. Before I tried disabling WER, the Terminal or Terminal Preview app was working correctly. How can I check if my Terminal was configured to open the previous session? I don't remember enabling this feature...

claunia commented

@zadjii-msft commented on GitHub (Nov 29, 2023):

This for sure is a confusing one! Especially something like

But, I cannot open more tabs - the app closes unexpectedly

That's definitely not something that should be happening! Can you try filing /feedback with Feedback Hub, and make sure to "Recreate my problem"? Hopefully that'll give us a dump that's got more info in it

@zadjii-msft commented on GitHub (Nov 29, 2023): This for sure is a confusing one! Especially something like > But, I cannot open more tabs - the app closes unexpectedly That's definitely not something that should be happening! Can you try filing /feedback with Feedback Hub, and make sure to "Recreate my problem"? Hopefully that'll give us a dump that's got more info in it

claunia commented

@marcosjahn commented on GitHub (Dec 4, 2023):

Hello @zadjii-msft!

I just reproduced the issue again and submitted it via the "Feedback Hub": https://aka.ms/AAny7ni

Here are some additional pieces of information that I believe are important:

I had to format my computer and reinstall Windows because other strange issues started occurring after a Windows Insider update failed to install.

After reinstalling Windows, I did not enable Windows Insider, and I did not attempt to disable Windows Error Reporting. Unfortunately, the problem I reported in this issue has recurred.

Details of my computer are as follows:
Windows 11.22621.2715
Terminal Preview 1.19.3172.0
Terminal 1.18.3181.0

Thank you!

@marcosjahn commented on GitHub (Dec 4, 2023): Hello @zadjii-msft! I just reproduced the issue again and submitted it via the "Feedback Hub": https://aka.ms/AAny7ni Here are some additional pieces of information that I believe are important: I had to format my computer and reinstall Windows because other strange issues started occurring after a Windows Insider update failed to install. After reinstalling Windows, I did not enable Windows Insider, and I did not attempt to disable Windows Error Reporting. Unfortunately, the problem I reported in this issue has recurred. Details of my computer are as follows: Windows 11.22621.2715 Terminal Preview 1.19.3172.0 Terminal 1.18.3181.0 Thank you!

claunia commented

@marcosjahn commented on GitHub (Mar 15, 2024):

Hello guys!

Is there an estimated timeline for the resolution of the Windows Terminal issue? Additionally, is any further information required to assist in the troubleshooting process?

Thanks,
Marcos

@marcosjahn commented on GitHub (Mar 15, 2024): Hello guys! Is there an estimated timeline for the resolution of the Windows Terminal issue? Additionally, is any further information required to assist in the troubleshooting process? Thanks, Marcos

claunia commented

@marcosjahn commented on GitHub (Mar 15, 2024):

@zadjii-msft @carlos-zamora

@marcosjahn commented on GitHub (Mar 15, 2024): @zadjii-msft @carlos-zamora

claunia commented

@zadjii-msft commented on GitHub (Mar 18, 2024):

Sorry no, we don't have any sort of timeframe for a fix here. As it stands, it kinda seems like you're the only one hitting this, and I couldn't figure it out just looking at the crash dumps we got. Ironically, with error reporting disabled, there's no real dumps or... seemingly anything I can find from your machine 🤷

note to self:

open-feedback ddf71f95-efb8-4f2d-b1bf-1f5411d97453
g:6896189095147101 gave me nothing

@zadjii-msft commented on GitHub (Mar 18, 2024): Sorry no, we don't have any sort of timeframe for a fix here. As it stands, it kinda seems like you're the only one hitting this, and I couldn't figure it out just looking at the crash dumps we got. Ironically, with error reporting disabled, there's no real dumps or... seemingly anything I can find from your machine 🤷 note to self: * `open-feedback ddf71f95-efb8-4f2d-b1bf-1f5411d97453` * `g:6896189095147101` gave me nothing

claunia commented

@marcosjahn commented on GitHub (Mar 19, 2024):

Hello @zadjii-msft.

Thanks a lot for your help.
I will try to send new feedback.

About the error message in the Event Log:

Nome do aplicativo com falha: WindowsTerminal.exe, versão: 1.19.2402.26003, carimbo de data/hora: 0x65dce3ea
Nome do módulo com falha: Windows.UI.Xaml.dll, versão: 10.0.22621.3350, carimbo de data/hora: 0x01eae29f
Código de exceção: 0xc000027b
Deslocamento da falha: 0x0000000000872c90
ID do processo com falha: 0x7104
Hora de início do aplicativo com falha: 0x1DA7A240988A23A
Caminho do aplicativo com falha: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.19.10573.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Caminho do módulo com falha: C:\Windows\System32\Windows.UI.Xaml.dll
ID do Relatório: 609ac06d-59e9-4191-b851-fe6deaa7ce8e
Nome completo do pacote com falha: Microsoft.WindowsTerminal_1.19.10573.0_x64__8wekyb3d8bbwe
ID do aplicativo relativo ao pacote com falha: App

Is there anything I can do to resolve this? For example: reinstall the XAML library, register the .dll again...

Thanks!

@marcosjahn commented on GitHub (Mar 19, 2024): Hello @zadjii-msft. Thanks a lot for your help. I will try to send new feedback. About the error message in the Event Log: > Nome do aplicativo com falha: WindowsTerminal.exe, versão: 1.19.2402.26003, carimbo de data/hora: 0x65dce3ea > Nome do módulo com falha: Windows.UI.Xaml.dll, versão: 10.0.22621.3350, carimbo de data/hora: 0x01eae29f > Código de exceção: 0xc000027b > Deslocamento da falha: 0x0000000000872c90 > ID do processo com falha: 0x7104 > Hora de início do aplicativo com falha: 0x1DA7A240988A23A > Caminho do aplicativo com falha: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.19.10573.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe > Caminho do módulo com falha: C:\Windows\System32\Windows.UI.Xaml.dll > ID do Relatório: 609ac06d-59e9-4191-b851-fe6deaa7ce8e > Nome completo do pacote com falha: Microsoft.WindowsTerminal_1.19.10573.0_x64__8wekyb3d8bbwe > ID do aplicativo relativo ao pacote com falha: App Is there anything I can do to resolve this? For example: reinstall the XAML library, register the .dll again... Thanks!

claunia commented

@marcosjahn commented on GitHub (Mar 19, 2024):

Hello @zadjii-msft! Thanks for your help.

If I launch the Terminal or the Terminal Preview from the Start Menu or Store, the app fails to launch and generates an item in the Event Viewer.

However, if I run "cmd" in the "Run" option (Win + R), the Terminal (or Terminal Preview) opens the prompt correctly. But, I cannot open more tabs - the app closes unexpectedly.

I don't have BeyondTrust installed on my machine. Before I tried disabling WER, the Terminal or Terminal Preview app was working correctly.

How can I check if my Terminal was configured to open the previous session? I don't remember enabling this feature...

This is my problem:

@marcosjahn commented on GitHub (Mar 19, 2024): > Hello @zadjii-msft! Thanks for your help. > > If I launch the Terminal or the Terminal Preview from the Start Menu or Store, the app fails to launch and generates an item in the Event Viewer. > > However, if I run "cmd" in the "Run" option (Win + R), the Terminal (or Terminal Preview) opens the prompt correctly. But, I cannot open more tabs - the app closes unexpectedly. > > I don't have BeyondTrust installed on my machine. Before I tried disabling WER, the Terminal or Terminal Preview app was working correctly. > > How can I check if my Terminal was configured to open the previous session? I don't remember enabling this feature... This is my problem: ![terminal-bug](https://github.com/microsoft/terminal/assets/3923090/1b5ecbfd-e2ad-4a70-b9ec-cce8fea84ec7)

claunia commented

@zadjii-msft commented on GitHub (Mar 19, 2024):

Okay that looks like "open with tabs from previous session" and "make a new window" (if my high school spanish is applicable literally at all here 🙄)

So this isn't just "Terminal crashes when dragging a tab", it's fully "Terminal crashes when opening a second tab". But this also started in 2023 so it's not the latest crop of compiler issues we've been fighting through. Hmm.

@zadjii-msft commented on GitHub (Mar 19, 2024): ![image](https://github.com/microsoft/terminal/assets/18356694/cde3ac6a-559e-4572-9fee-651acce733ab) Okay that looks like "open with tabs from previous session" and "make a new window" (if my high school spanish is applicable literally at all here 🙄) So this isn't just "Terminal crashes when dragging a tab", it's fully "Terminal crashes when opening a second tab". But this also started in 2023 so it's not the latest crop of compiler issues we've been fighting through. Hmm.

claunia commented

@marcosjahn commented on GitHub (Mar 19, 2024):

@zadjii-msft I'm using the default configuration, because I had uninstalled the Terminal last week and reinstalled it today. See my settings, now in English (previously in pt-br):

This issue has two behaviors:

If I launch the Terminal app from the Windows Store or Start menu, nothing happens - the Terminal does not open, and I get an error message in the Event Viewer.
If I run "cmd" using Winkey + R, the Terminal opens with the Command Prompt. Here, when I try to open a new tab, the app closes unexpectedly. The Terminal crashes with any profile - Azure, Prompt, WSL...

@marcosjahn commented on GitHub (Mar 19, 2024): @zadjii-msft I'm using the default configuration, because I had uninstalled the Terminal last week and reinstalled it today. See my settings, now in English (previously in pt-br): ![image](https://github.com/microsoft/terminal/assets/3923090/e0347570-771c-4862-aebc-381fe0b2757b) This issue has two behaviors: * If I launch the Terminal app from the Windows Store or Start menu, nothing happens - the Terminal does not open, and I get an error message in the Event Viewer. * If I run "cmd" using Winkey + R, the Terminal opens with the Command Prompt. Here, when I try to open a new tab, the app closes unexpectedly. The Terminal crashes with any profile - Azure, Prompt, WSL...

claunia commented

@zadjii-msft commented on GitHub (Mar 19, 2024):

Well okay that does differentiate at least one part here. Connections that are created for "default terminal" ("defterm") invocations seem to work for you. But Terminal-initiated connections don't.

This vaguely makes me think of #16747 for whatever reason. From that thread:

Can you run conhost -- cmd from the Run dialog, then run set, and copy-paste the output here¹? Looks like there's some env var somewhere in there that's blowing up our env var loader/?

Alternatively, testing if this repros the same in 1.20 preview

Another idea: does wt -w 0 new-tab --inheritEnvironment work to open a new tab?

this may have some amount of PII in it ↩︎

@zadjii-msft commented on GitHub (Mar 19, 2024): Well okay that does differentiate at least one part here. Connections that are created for "default terminal" ("defterm") invocations seem to work for you. But Terminal-initiated connections don't. This vaguely makes me think of #16747 for whatever reason. From that thread: > Can you run `conhost -- cmd` from the Run dialog, then run `set`, and copy-paste the output here[^1]? Looks like there's some env var somewhere in there that's blowing up our env var loader/? > > Alternatively, testing if this repros the same in [1.20 preview](https://github.com/microsoft/terminal/releases/tag/v1.20.10572.0) Another idea: does `wt -w 0 new-tab --inheritEnvironment` work to open a new tab? [^1]: this may have some amount of PII in it

claunia commented

@marcosjahn commented on GitHub (Mar 19, 2024):

Result of conhost -- cmd + set:

ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\marcos.jahn\AppData\Roaming
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=J05811
ComSpec=C:\Windows\system32\cmd.exe
DriverData=C:\Windows\System32\Drivers\DriverData
EFC_2388=1
FPS_BROWSER_APP_PROFILE_STRING=Internet Explorer
FPS_BROWSER_USER_PROFILE_STRING=Default
HOMEDRIVE=C:
HOMEPATH=\Users\marcos.jahn
IntelliJ IDEA Community Edition=C:\Program Files\JetBrains\IntelliJ Community\bin;
JAVA_HOME=C:\Work\Programas\openjdk-11.0.6-windows-x64
JENV_HOME=C:\Work\Programas\JEnv\latest
LOCALAPPDATA=C:\Users\marcos.jahn\AppData\Local
LOGONSERVER=\\IRIR
M2_HOME=C:\Work\Programas\Apache\Maven\3.6.0
MAVEN_OPTS=-Xms2g -Xmx12g -XX:MaxDirectMemorySize=4096m
NUMBER_OF_PROCESSORS=8
NVM_HOME=C:\Work\Programas\nvm
NVM_SYMLINK=C:\Program Files\nodejs
OneDrive=C:\Users\marcos.jahn\OneDrive
OS=Windows_NT
Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\RedHat\Podman\;C:\Program Files\Git\cmd;C:\Work\Programas\JEnv\latest;C:\Work\Programas\Apache\Maven\3.6.0\bin;C:\Work\Programas\nvm;C:\Program Files\nodejs;C:\Users\marcos.jahn\AppData\Local\Microsoft\WindowsApps;C:\Users\marcos.jahn\AppData\Local\Programs\Microsoft VS Code\bin;C:\Work\Programas\nvm;C:\Program Files\nodejs;C:\Program Files\JetBrains\IntelliJ Community\bin
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 140 Stepping 1, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=8c01
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules
PUBLIC=C:\Users\Public
SciTE_HOME=C:\ProgramData\SciTE
SciTE_USERHOME=C:\Users\marcos.jahn\AppData\Roaming\SciTE
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Users\MARCOS~1.JAH\AppData\Local\Temp
TMP=C:\Users\MARCOS~1.JAH\AppData\Local\Temp
USERDNSDOMAIN=J1.LOCAL
USERDOMAIN=J1
USERDOMAIN_ROAMINGPROFILE=J1
USERNAME=marcos.jahn
USERPROFILE=C:\Users\marcos.jahn
windir=C:\Windows
ZES_ENABLE_SYSMAN=1

Running wt -w 0 new-tab --inheritEnvironment, the Terminal opens using the Default Profile. I tried changing the Default Profile to Powershell and WSL, which worked. But the Terminal crashes when I try to open a second tab.

Using the 1.20 preview, the problem also occurs.

@marcosjahn commented on GitHub (Mar 19, 2024): Result of `conhost -- cmd` + `set`: ``` ALLUSERSPROFILE=C:\ProgramData APPDATA=C:\Users\marcos.jahn\AppData\Roaming CommonProgramFiles=C:\Program Files\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files CommonProgramW6432=C:\Program Files\Common Files COMPUTERNAME=J05811 ComSpec=C:\Windows\system32\cmd.exe DriverData=C:\Windows\System32\Drivers\DriverData EFC_2388=1 FPS_BROWSER_APP_PROFILE_STRING=Internet Explorer FPS_BROWSER_USER_PROFILE_STRING=Default HOMEDRIVE=C: HOMEPATH=\Users\marcos.jahn IntelliJ IDEA Community Edition=C:\Program Files\JetBrains\IntelliJ Community\bin; JAVA_HOME=C:\Work\Programas\openjdk-11.0.6-windows-x64 JENV_HOME=C:\Work\Programas\JEnv\latest LOCALAPPDATA=C:\Users\marcos.jahn\AppData\Local LOGONSERVER=\\IRIR M2_HOME=C:\Work\Programas\Apache\Maven\3.6.0 MAVEN_OPTS=-Xms2g -Xmx12g -XX:MaxDirectMemorySize=4096m NUMBER_OF_PROCESSORS=8 NVM_HOME=C:\Work\Programas\nvm NVM_SYMLINK=C:\Program Files\nodejs OneDrive=C:\Users\marcos.jahn\OneDrive OS=Windows_NT Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\RedHat\Podman\;C:\Program Files\Git\cmd;C:\Work\Programas\JEnv\latest;C:\Work\Programas\Apache\Maven\3.6.0\bin;C:\Work\Programas\nvm;C:\Program Files\nodejs;C:\Users\marcos.jahn\AppData\Local\Microsoft\WindowsApps;C:\Users\marcos.jahn\AppData\Local\Programs\Microsoft VS Code\bin;C:\Work\Programas\nvm;C:\Program Files\nodejs;C:\Program Files\JetBrains\IntelliJ Community\bin PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC PROCESSOR_ARCHITECTURE=AMD64 PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 140 Stepping 1, GenuineIntel PROCESSOR_LEVEL=6 PROCESSOR_REVISION=8c01 ProgramData=C:\ProgramData ProgramFiles=C:\Program Files ProgramFiles(x86)=C:\Program Files (x86) ProgramW6432=C:\Program Files PROMPT=$P$G PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules PUBLIC=C:\Users\Public SciTE_HOME=C:\ProgramData\SciTE SciTE_USERHOME=C:\Users\marcos.jahn\AppData\Roaming\SciTE SESSIONNAME=Console SystemDrive=C: SystemRoot=C:\Windows TEMP=C:\Users\MARCOS~1.JAH\AppData\Local\Temp TMP=C:\Users\MARCOS~1.JAH\AppData\Local\Temp USERDNSDOMAIN=J1.LOCAL USERDOMAIN=J1 USERDOMAIN_ROAMINGPROFILE=J1 USERNAME=marcos.jahn USERPROFILE=C:\Users\marcos.jahn windir=C:\Windows ZES_ENABLE_SYSMAN=1 ``` Running `wt -w 0 new-tab --inheritEnvironment`, the Terminal opens using the Default Profile. I tried changing the Default Profile to Powershell and WSL, which worked. But the Terminal crashes when I try to open a second tab. Using the 1.20 preview, the problem also occurs.

claunia commented

@zadjii-msft commented on GitHub (Mar 19, 2024):

Running wt -w 0 new-tab --inheritEnvironment, the Terminal opens using the Default Profile

WEIRD. I bet this IS the same thing!

 TEMP=C:\Users\MARCOS~1.JAH\AppData\Local\Temp
 TMP=C:\Users\MARCOS~1.JAH\AppData\Local\Temp

These guys stand out on a first scan - they're not just C:\Users\marcos.jahn\AppData\Local\Temp, they're 8.3 paths?^?_??

@zadjii-msft commented on GitHub (Mar 19, 2024): > Running `wt -w 0 new-tab --inheritEnvironment`, the Terminal opens using the Default Profile WEIRD. I bet this IS the same thing! > ``` > TEMP=C:\Users\MARCOS~1.JAH\AppData\Local\Temp > TMP=C:\Users\MARCOS~1.JAH\AppData\Local\Temp > ``` > These guys stand out on a first scan - they're not just `C:\Users\marcos.jahn\AppData\Local\Temp`, they're 8.3 paths?<sup>?</sup><sub>?</sub>?

claunia commented

@DHowett commented on GitHub (Mar 19, 2024):

open a second tab.

Are you a MacType user per chance?

@DHowett commented on GitHub (Mar 19, 2024): > open a second tab. Are you a MacType user per chance?

claunia commented

@marcosjahn commented on GitHub (Mar 19, 2024):

Hello @zadjii-msft! Thanks for your help.

What's the correct or recommended folders for these user environment variables: TEMP and TMP?

WEIRD. I bet this IS the same thing!

"8.3 paths"? Can you explain, please?

These guys stand out on a first scan - they're not just C:\Users\marcos.jahn\AppData\Local\Temp, they're 8.3 paths????

@marcosjahn commented on GitHub (Mar 19, 2024): Hello @zadjii-msft! Thanks for your help. What's the correct or recommended folders for these user environment variables: TEMP and TMP? > WEIRD. I bet this IS the same thing! "8.3 paths"? Can you explain, please? > These guys stand out on a first scan - they're not just `C:\Users\marcos.jahn\AppData\Local\Temp`, they're 8.3 paths????

claunia commented

@marcosjahn commented on GitHub (Mar 19, 2024):

open a second tab.

Are you a MacType user per chance?

Hello @DHowett!

Are you referring to this MacType? https://www.mactype.net/

No, I don't use it.

@marcosjahn commented on GitHub (Mar 19, 2024): > > open a second tab. > > Are you a MacType user per chance? Hello @DHowett! Are you referring to this MacType? https://www.mactype.net/ No, I don't use it.

claunia commented

@zadjii-msft commented on GitHub (Mar 19, 2024):

"8.3 paths"? Can you explain, please?

Honestly, I don't even know. These predate my own familiarity with computers. But wikipedia's got a overview: https://en.wikipedia.org/wiki/8.3_filename

What's the correct or recommended folders for these user environment variables

tbh I would have thought that those paths should work. I'm more gluing together two half thoughts:

Your TMP variables are curious
https://github.com/microsoft/terminal/issues/16747#issuecomment-1981981063 tracked down some weird debug logs that pointed at TMP variables, but we didn't know why
disabling our env var generation (with --inheritEnvironment) did work to open a new tab

Hence why I'm thinking there's a bug here in the nexus of all this.

I honestly wouldn't expect the TMP vars to be 8.3 paths, I thought they'd just be normal paths? So switching them to C:\Users\marcos.jahn\AppData\Local\Temp instead might just work. But also, we shouldn't crash if we do encounter one of those...

@zadjii-msft commented on GitHub (Mar 19, 2024): > "8.3 paths"? Can you explain, please? Honestly, I don't even know. These predate my own familiarity with computers. But wikipedia's got a overview: https://en.wikipedia.org/wiki/8.3_filename > What's the correct or recommended folders for these user environment variables tbh I would have thought that those paths _should_ work. I'm more gluing together two half thoughts: * Your TMP variables are curious * https://github.com/microsoft/terminal/issues/16747#issuecomment-1981981063 tracked down some weird debug logs that pointed at TMP variables, but we didn't know _why_ * disabling our env var generation (with `--inheritEnvironment`) did work to open a new tab Hence why I'm thinking there's a bug here in the nexus of all this. I honestly wouldn't expect the TMP vars to be 8.3 paths, I thought they'd just be normal paths? So switching them to `C:\Users\marcos.jahn\AppData\Local\Temp` instead might just work. But also, we shouldn't crash if we do encounter one of those...

claunia commented

@marcosjahn commented on GitHub (Mar 19, 2024):

@zadjii-msft Apparently, my user environment variables are configured correctly:

I took this screenshot in the 'System Properties' dialog box, under the 'Advanced' tab, by clicking the 'Environment Variables' button.

@marcosjahn commented on GitHub (Mar 19, 2024): @zadjii-msft Apparently, my user environment variables are configured correctly: ![image](https://github.com/microsoft/terminal/assets/3923090/9e78d5b9-06c4-4fb8-ac91-88dfbd419f9b) I took this screenshot in the 'System Properties' dialog box, under the 'Advanced' tab, by clicking the 'Environment Variables' button.

claunia commented

@zadjii-msft commented on GitHub (Mar 19, 2024):

Hmm.

tried this with a user with a very long name - that didn't repro locally.
Tried one with dots: that didn't work either. weird weird weird.

@zadjii-msft commented on GitHub (Mar 19, 2024): Hmm. * [x] tried this with a user with a very long name - that didn't repro locally. * [x] Tried one with dots: that didn't work either. weird weird weird.

claunia commented