Can not reset/reinstall Windows Terminal #21108

Closed
opened 2026-01-31 07:33:17 +00:00 by claunia · 3 comments
Owner

Originally created by @ktzsolt on GitHub (Jan 18, 2024).

Windows Terminal version

1.18.31.81.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

My profiles are not working I get only basic PS prompt, when I try to launch the wsl profile I even get

[process exited with code 3221225495 (0xc0000017)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

I tried to repair, reset and even reinstall Windows Terminal, even though with uninstall it's directory C:\Users\myuser\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe is deleted but when I install it again the settings.json is recreated and it will miraculously contain my previous settings.json that I have no idea where it gets from. I even restarted the computer after uninstalling and before reinstalling, still the same.

I also did a winget install --id Microsoft.Powershell --source winget before today, maybe this messed up things somehow? Had no issues before with this.

Expected Behavior

No response

Actual Behavior

Not working as intended

Originally created by @ktzsolt on GitHub (Jan 18, 2024). ### Windows Terminal version 1.18.31.81.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce My profiles are not working I get only basic PS prompt, when I try to launch the wsl profile I even get ``` [process exited with code 3221225495 (0xc0000017)] You can now close this terminal with Ctrl+D, or press Enter to restart. ``` I tried to repair, reset and even reinstall Windows Terminal, even though with uninstall it's directory `C:\Users\myuser\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe` is deleted but when I install it again the settings.json is recreated and it will miraculously contain my previous settings.json that I have no idea where it gets from. I even restarted the computer after uninstalling and before reinstalling, still the same. I also did a `winget install --id Microsoft.Powershell --source winget` before today, maybe this messed up things somehow? Had no issues before with this. ### Expected Behavior _No response_ ### Actual Behavior Not working as intended
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 07:33:17 +00:00
Author
Owner

@ktzsolt commented on GitHub (Jan 18, 2024):

I started "C:\Program Files\PowerShell\7\pwsh.exe" from start run, and after that Terminal started to work again as it should. Strange.

@ktzsolt commented on GitHub (Jan 18, 2024): I started "C:\Program Files\PowerShell\7\pwsh.exe" from start run, and after that Terminal started to work again as it should. Strange.
Author
Owner

@carlos-zamora commented on GitHub (Jan 24, 2024):

That error code indicates that you might be out of memory. Glad the issue went away. Let us know if the issue comes back.

@carlos-zamora commented on GitHub (Jan 24, 2024): That error code indicates that you might be out of memory. Glad the issue went away. Let us know if the issue comes back.
Author
Owner

@ktzsolt commented on GitHub (Jan 25, 2024):

I doubt, I have 32 GB RAM and also I restarted the computer multiple times. What finally solved is that I started pwsh.exe from start menu, run. Maybe it's installation/setup/bootstrap didn't finished until I started it manually?

@ktzsolt commented on GitHub (Jan 25, 2024): I doubt, I have 32 GB RAM and also I restarted the computer multiple times. What finally solved is that I started pwsh.exe from start menu, run. Maybe it's installation/setup/bootstrap didn't finished until I started it manually?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21108