Terminal keeps disappearing after wake from sleep #16801

@zadjii-msft commented on GitHub (Feb 18, 2022):

"‎The power manager has not requested the deletion of all entries‎" / "‎The power manager has requested the deletion of all entries‎"

Hmm.

Do any other apps close? Something like, calculator? or MsPaint?

I've never seen sucha crazy thing so I'm just collecting links as I go.

Those seem to suggest that there's something in your power settings you might be able to change, but that also seems to imply that all apps would close when the laptop enters sleep mode.

@zadjii-msft commented on GitHub (Feb 18, 2022): "‎The power manager has not requested the deletion of all entries‎" / "‎The power manager has requested the deletion of all entries‎" Hmm. Do any other apps close? Something like, calculator? or MsPaint? I've never seen sucha crazy thing so I'm just collecting links as I go. * https://answers.microsoft.com/en-us/windows/forum/all/all-apps-closing-when-computer-is-in-sleep-mode/7ed3e52a-c92c-44f6-a585-5318da14afb5#:~:text=It%20could%20be%20due%20to,adjust%20your%20computer%27s%20power%20settings. * https://www.thewindowsclub.com/windows-10-closes-apps-when-going-to-sleep Those seem to suggest that there's something in your power settings you might be able to change, but that also seems to imply that _all_ apps would close when the laptop enters sleep mode.

claunia commented

@Eryx5502 commented on GitHub (Feb 18, 2022):

Ok, I just check and it does happen to other apps, I just didn't notice before. It happens at least with Calculator and also with Windows Configuration. I will watch if it happens to more apps, but there are other apps which never close such as Firefox, Thunderbird, pdf readers, etc. I tried to follow the suggestions on the links you sent and those options ("hybrid sleep" and "hibertate after") don't appear on the "Change plan settings" dialog. The Power Troubleshooter didn't solve it.

Also, since it looks that it is not a Windows Terminal thing, should I also report it anywhere else?

@Eryx5502 commented on GitHub (Feb 18, 2022): Ok, I just check and it does happen to other apps, I just didn't notice before. It happens at least with Calculator and also with Windows Configuration. I will watch if it happens to more apps, but there are other apps which never close such as Firefox, Thunderbird, pdf readers, etc. I tried to follow the suggestions on the links you sent and those options ("hybrid sleep" and "hibertate after") don't appear on the "Change plan settings" dialog. The Power Troubleshooter didn't solve it. Also, since it looks that it is not a Windows Terminal thing, should I also report it anywhere else?

claunia commented

@vietor commented on GitHub (Feb 25, 2022):

Try close the "Hide TitleBar".

"showTabsInTitlebar": true

@vietor commented on GitHub (Feb 25, 2022): Try close the "Hide TitleBar". "showTabsInTitlebar": true

claunia commented

@Eryx5502 commented on GitHub (Feb 25, 2022):

I do have that showTabsInTitlebar set to true. I've tried with both true and false and it makes no difference.

@Eryx5502 commented on GitHub (Feb 25, 2022): I do have that `showTabsInTitlebar` set to `true`. I've tried with both `true` and `false` and it makes no difference.

claunia commented

@vietor commented on GitHub (Feb 25, 2022):

"showTabsInTitlebar": false,
"showTerminalTitleInTitlebar": false

It's successed in my case. Windows 11.

@vietor commented on GitHub (Feb 25, 2022): "showTabsInTitlebar": false, "showTerminalTitleInTitlebar": false It's successed in my case. Windows 11.

claunia commented

@Eryx5502 commented on GitHub (Feb 25, 2022):

I just tried and didn't make a diference for me. Perhaps our problems wasn't the same.

@Eryx5502 commented on GitHub (Feb 25, 2022): I just tried and didn't make a diference for me. Perhaps our problems wasn't the same.

claunia commented

@zadjii-msft commented on GitHub (Feb 28, 2022):

Also, since it looks that it is not a Windows Terminal thing, should I also report it anywhere else?

Honestly, your best bet might just be the feedback hub at this point. That's not really a great option for getting answers, but it should at least get some traces to people who might be able to fix it. I'm not sure there's much else we'll be able to do on our end :/

If you do file feedback, share the aka.ms link here and I can make sure it gets promoted and follow-up with whatever the results are ☺️

@zadjii-msft commented on GitHub (Feb 28, 2022): > Also, since it looks that it is not a Windows Terminal thing, should I also report it anywhere else? Honestly, your best bet might just be the feedback hub at this point. That's not really a great option for getting _answers_, but it should at least get some traces to people who might be able to fix it. I'm not sure there's much else we'll be able to do on our end :/ If you do file feedback, share the `aka.ms` link here and I can make sure it gets promoted and follow-up with whatever the results are ☺️

claunia commented

@Eryx5502 commented on GitHub (Feb 28, 2022):

I did fill the feedback form: https://aka.ms/AAfza6a

Thanks for the help and let's see if i'm lucky and something comes out of the Feedback Hub.

@Eryx5502 commented on GitHub (Feb 28, 2022): I did fill the feedback form: https://aka.ms/AAfza6a Thanks for the help and let's see if i'm lucky and something comes out of the Feedback Hub.

claunia commented

@zadjii-msft commented on GitHub (Feb 28, 2022):

(this was promoted internally to MSFT:38334285, and I'll follow that for updates)

@zadjii-msft commented on GitHub (Feb 28, 2022): (this was promoted internally to MSFT:38334285, and I'll follow that for updates)

claunia commented

@puhazh commented on GitHub (Apr 20, 2022):

Having the same issue, but noted this is happening even if my laptop is left connected to the power supply. No clues in the windows event viewer log of any crash.

@puhazh commented on GitHub (Apr 20, 2022): Having the same issue, but noted this is happening even if my laptop is left connected to the power supply. No clues in the windows event viewer log of any crash.

claunia commented

@zadjii-msft commented on GitHub (Apr 20, 2022):

@puhazh Does this happen to you frequently? It's also possible that the Store may have noticed that there was an update available for the Terminal, and chose to update it for you right as it was going to sleep / resuming from sleep. The timing of your report does seem like it might be related to the latest build that we just pushed out.

@zadjii-msft commented on GitHub (Apr 20, 2022): @puhazh Does this happen to you frequently? It's also possible that the Store may have noticed that there was an update available for the Terminal, and chose to update it for you right as it was going to sleep / resuming from sleep. The timing of your report does seem like it might be related to the latest build that we just pushed out.

claunia commented

@Eryx5502 commented on GitHub (Apr 20, 2022):

@puhazh, now its also happening when connected to the power supply in my case. Something changed and now Terminal always go away when waking up. However, the same happens to other (all?) apps also (windows 10 apps from the Microsoft Store).

I'm not hoping for a solution any time soon, but if you're using Windows Terminal with wsl, what is working for my is to use tmux with an automatic session saver/loader pluggin so that I can recover everything I had running before it disapeared.

@Eryx5502 commented on GitHub (Apr 20, 2022): @puhazh, now its also happening when connected to the power supply in my case. Something changed and now Terminal always go away when waking up. However, the same happens to other (all?) apps also (windows 10 apps from the Microsoft Store). I'm not hoping for a solution any time soon, but if you're using Windows Terminal with wsl, what is working for my is to use tmux with an automatic session saver/loader pluggin so that I can recover everything I had running before it disapeared.

claunia commented

@puhazh commented on GitHub (Apr 20, 2022):

@zadjii-msft It happens every time I put my system to sleep and wake up after sometime, this doesn't happen if I wake up back in a short time, but if its more than 2 hours (the one I see is after 2 hours, not sure of the exact duration). Since the issue is consistent, let me know if I there is a debug flag that I can set to capture information that might be of help to debug the issue. I use terminal with WSL, not sure if its only when using WSL.

@puhazh commented on GitHub (Apr 20, 2022): @zadjii-msft It happens every time I put my system to sleep and wake up after sometime, this doesn't happen if I wake up back in a short time, but if its more than 2 hours (the one I see is after 2 hours, not sure of the exact duration). Since the issue is consistent, let me know if I there is a debug flag that I can set to capture information that might be of help to debug the issue. I use terminal with WSL, not sure if its only when using WSL.

claunia commented

@riteshkr54 commented on GitHub (Apr 22, 2022):

@zadjii-msft It happens every time I put my system to sleep and wake up after sometime, this doesn't happen if I wake up back in a short time, but if its more than 2 hours (the one I see is after 2 hours, not sure of the exact duration). Since the issue is consistent, let me know if I there is a debug flag that I can set to capture information that might be of help to debug the issue. I use terminal with WSL, not sure if its only when using WSL.

I'm seeing same behavior since last few days. Not sure about other windows app, but I have multiple chrome profiles with multiple tabs open and and all profiles but one closes down.

@riteshkr54 commented on GitHub (Apr 22, 2022): > @zadjii-msft It happens every time I put my system to sleep and wake up after sometime, this doesn't happen if I wake up back in a short time, but if its more than 2 hours (the one I see is after 2 hours, not sure of the exact duration). Since the issue is consistent, let me know if I there is a debug flag that I can set to capture information that might be of help to debug the issue. I use terminal with WSL, not sure if its only when using WSL. I'm seeing same behavior since last few days. Not sure about other windows app, but I have multiple chrome profiles with multiple tabs open and and all profiles but one closes down.

claunia commented

@drew-codes commented on GitHub (Apr 27, 2022):

Hey there, I'm also having a similar issue, with Ubuntu (via WSL2) running on Windows Terminal. Whether I am connected to power or not, when I close the lid of my laptop and then go back in, the Terminal is closed. I do not have any issues with other apps such as calculator.

Another interesting thing is that this does not happen to other command-line apps (Command Prompt, Windows Powershell) that run on Windows Terminal.

@drew-codes commented on GitHub (Apr 27, 2022): Hey there, I'm also having a similar issue, with Ubuntu (via WSL2) running on Windows Terminal. Whether I am connected to power or not, when I close the lid of my laptop and then go back in, the Terminal is closed. I do not have any issues with other apps such as calculator. Another interesting thing is that this does not happen to other command-line apps (Command Prompt, Windows Powershell) that run on Windows Terminal.

claunia commented

@drew-codes commented on GitHub (Apr 27, 2022):

Hey there, I'm also having a similar issue, with Ubuntu (via WSL2) running on Windows Terminal. Whether I am connected to power or not, when I close the lid of my laptop and then go back in, the Terminal is closed. I do not have any issues with other apps such as calculator.

Another interesting thing is that this does not happen to other command-line apps (Command Prompt, Windows Powershell) that run on Windows Terminal.

Update: I've turned off "Launch on Machine Startup" and it no longer seems to be closing on wake from sleep.

@drew-codes commented on GitHub (Apr 27, 2022): > Hey there, I'm also having a similar issue, with Ubuntu (via WSL2) running on Windows Terminal. Whether I am connected to power or not, when I close the lid of my laptop and then go back in, the Terminal is closed. I do not have any issues with other apps such as calculator. > > Another interesting thing is that this does not happen to other command-line apps (Command Prompt, Windows Powershell) that run on Windows Terminal. Update: I've turned off "Launch on Machine Startup" and it no longer seems to be closing on wake from sleep.

claunia commented

@R4cOOn commented on GitHub (May 12, 2022):

I'm experiencing the same issue with my Terminal (I've got it set up as Powershell).

Every time I put my laptop to sleep overnight, I come back the next morning to a missing Terminal window.
That happens also if I leave the laptop connected to the mains.

I can't see anything in the Event Viewer related to that.

@R4cOOn commented on GitHub (May 12, 2022): I'm experiencing the same issue with my Terminal (I've got it set up as Powershell). Every time I put my laptop to sleep overnight, I come back the next morning to a missing Terminal window. That happens also if I leave the laptop connected to the mains. I can't see anything in the Event Viewer related to that.

claunia commented

@conoro commented on GitHub (Aug 26, 2022):

Same problem here. Huawei Matebook 14S running latest Windows 11. Also happened before upgrading to Windows 11 from 10.

Every time laptop goes to sleep and I wake it up, all Terminal sessions are gone. It's basically unusable for me on a laptop.

@conoro commented on GitHub (Aug 26, 2022): Same problem here. Huawei Matebook 14S running latest Windows 11. Also happened before upgrading to Windows 11 from 10. Every time laptop goes to sleep and I wake it up, all Terminal sessions are gone. It's basically unusable for me on a laptop.

claunia commented

@zadjii-msft commented on GitHub (Aug 26, 2022):

If this happens 100% consistently, then can you follow the steps in: https://github.com/microsoft/terminal/issues/12513#issuecomment-1042998769 to send us a dump?

It's also 100% possible that there's a correlation with the Store force-killing the Terminal to install an update. We did just push out a 1.14 servicing build, so that probably just arrived. If it happens 100% of the time though, it's probably not the Store update situation.

(There hasn't been any progress on the internal bug to report)

@zadjii-msft commented on GitHub (Aug 26, 2022): If this happens 100% consistently, then can you follow the steps in: https://github.com/microsoft/terminal/issues/12513#issuecomment-1042998769 to send us a dump? It's also 100% possible that there's a correlation with the Store force-killing the Terminal to install an update. We did just push out a 1.14 servicing build, so that probably just arrived. If it happens 100% of the time though, it's probably not the Store update situation. (There hasn't been any progress on the internal bug to report)

claunia commented

@conoro commented on GitHub (Aug 26, 2022):

Thanks. It happens on every sleep/wake.

Running Terminal 1.14.2282.0

Laptop is always on mains power with external USB-C monitor and external mouse/keyboard. Power setting is Balanced with Screen off after 10 minutes and Sleep after 30 mins.

I just set up the DumpFolder key and left the laptop with Terminal running both a CMD tab and a Powershell tab. I let it go to sleep and then woke it up. Terminal was gone but no dmp file was created unfortunately.

As a test I also had separate standalone Powershell and CMD windows. They were unaffected.

@conoro commented on GitHub (Aug 26, 2022): Thanks. It happens on every sleep/wake. Running Terminal 1.14.2282.0 Laptop is always on mains power with external USB-C monitor and external mouse/keyboard. Power setting is Balanced with Screen off after 10 minutes and Sleep after 30 mins. I just set up the DumpFolder key and left the laptop with Terminal running both a CMD tab and a Powershell tab. I let it go to sleep and then woke it up. Terminal was gone but no dmp file was created unfortunately. As a test I also had separate standalone Powershell and CMD windows. They were unaffected.

claunia commented

@R4cOOn commented on GitHub (Aug 30, 2022):

I set up the dump folder and got some dump files.
The Terminal always disappears when the laptop goes to sleep.

I see 2 crash dumps (I had 2 sessions running).

CrashDumps.zip

@R4cOOn commented on GitHub (Aug 30, 2022): I set up the dump folder and got some dump files. The Terminal always disappears when the laptop goes to sleep. I see 2 crash dumps (I had 2 sessions running). [CrashDumps.zip](https://github.com/microsoft/terminal/files/9450838/CrashDumps.zip)

claunia commented

@zadjii-msft commented on GitHub (Aug 30, 2022):

Huh. Weird. Those are both pwsh.exe dumps, not Terminal ones. Can you try setting "closeOnExit": "never" in the settings? Maybe pwsh.exe is crashing, exiting, causing the Terminal to "crash".

@zadjii-msft commented on GitHub (Aug 30, 2022): Huh. Weird. Those are both `pwsh.exe` dumps, not Terminal ones. Can you try setting [`"closeOnExit": "never"`](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-advanced#profile-termination-behavior) in the settings? Maybe `pwsh.exe` is crashing, exiting, causing the Terminal to "crash".

claunia commented

@R4cOOn commented on GitHub (Aug 30, 2022):

@zadjii-msft I've added the setting, I'll see what happens tomorrow.

@R4cOOn commented on GitHub (Aug 30, 2022): @zadjii-msft I've added the setting, I'll see what happens tomorrow.

claunia commented

@R4cOOn commented on GitHub (Aug 31, 2022):

Exact same outcome: Terminal is gone and pwsh dump file.

pwsh.exe.44676.dmp.zip

@R4cOOn commented on GitHub (Aug 31, 2022): Exact same outcome: Terminal is gone and pwsh dump file. ![image](https://user-images.githubusercontent.com/1311219/187605833-6577bad4-fce5-4526-894d-7c79967cd1df.png) [pwsh.exe.44676.dmp.zip](https://github.com/microsoft/terminal/files/9458985/pwsh.exe.44676.dmp.zip)

claunia commented

@DHowett commented on GitHub (Aug 31, 2022):

Sorry -- it looks like you're referring to the "Windows Powershell" (powershell.exe) profile in your screenshot, but the dump you've provided is from a different version of PowerShell (pwsh.exe). Is that intentional? :)

@DHowett commented on GitHub (Aug 31, 2022): Sorry -- it looks like you're referring to the "Windows Powershell" (`powershell.exe`) profile in your screenshot, but the dump you've provided is from a different version of PowerShell (`pwsh.exe`). Is that intentional? :)

claunia commented

@R4cOOn commented on GitHub (Sep 1, 2022):

Sorry -- it looks like you're referring to the "Windows Powershell" (powershell.exe) profile in your screenshot, but the dump you've provided is from a different version of PowerShell (pwsh.exe). Is that intentional? :)

@DHowett I changed the command line to run PowerShell 7.

What the terminal executes is
C:\Program Files\PowerShell\7\pwsh.exe -noe -c "&{Import-Module """C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\Tools\Microsoft.VisualStudio.DevShell.dll"""; Enter-VsDevShell 39a14bae}"

So the dumps are coming from the running (and crashing Terminal).

Plase find attached yet another dump pwsh.exe.224.dmp.zip

@R4cOOn commented on GitHub (Sep 1, 2022): > Sorry -- it looks like you're referring to the "Windows Powershell" (`powershell.exe`) profile in your screenshot, but the dump you've provided is from a different version of PowerShell (`pwsh.exe`). Is that intentional? :) @DHowett I changed the command line to run PowerShell 7. What the terminal executes is `C:\Program Files\PowerShell\7\pwsh.exe -noe -c "&{Import-Module """C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\Tools\Microsoft.VisualStudio.DevShell.dll"""; Enter-VsDevShell 39a14bae}"` So the dumps are coming from the running (and crashing Terminal). Plase find attached yet another dump [pwsh.exe.224.dmp.zip](https://github.com/microsoft/terminal/files/9467852/pwsh.exe.224.dmp.zip)

claunia commented

@zb140 commented on GitHub (Oct 4, 2022):

I'm seeing this now too; I first noticed it a couple of days ago. I'm happy to try to collect some more dumps if it would help.

Edit: come to think of it, this may have started when I updated PSReadline -- that was also a few days ago. Unfortunately I no longer recall what issue I was encountering that made me do that 😁 I've changed my closeOnExit setting; if I'm still seeing this tomorrow, I'll look into downgrading PSReadline and see if that changes anything.

@zb140 commented on GitHub (Oct 4, 2022): I'm seeing this now too; I first noticed it a couple of days ago. I'm happy to try to collect some more dumps if it would help. Edit: come to think of it, this _may_ have started when I updated PSReadline -- that was also a few days ago. Unfortunately I no longer recall what issue I was encountering that made me do that :grin: I've changed my `closeOnExit` setting; if I'm still seeing this tomorrow, I'll look into downgrading PSReadline and see if that changes anything.

claunia commented

@conoro commented on GitHub (Oct 18, 2022):

Very happy to see that it has suddenly stopped happening this week after being 100% consistent in disappearing before that.

Windows: 11 Home, 22H2, 22623.746
Terminal: Preview Version: 1.16.2642.0

@conoro commented on GitHub (Oct 18, 2022): Very happy to see that it has suddenly stopped happening this week after being 100% consistent in disappearing before that. Windows: 11 Home, 22H2, 22623.746 Terminal: Preview Version: 1.16.2642.0

claunia commented

@MichalStrehovsky commented on GitHub (Oct 31, 2022):

For anyone else hitting this, I was getting a 100% repro of terminal disappearing after sleep. This One Weird Trick fixed it for me (run within PowerShell under a normal conhost (not Terminal), or it will complain that you have to close Terminal first):

Add-AppxPackage -DisableDevelopmentMode -Register  "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.2875.0_x64__8wekyb3d8bbwe\AppxManifest.xml"

Find the path to Terminal's AppxManifest through this if that AppxManifest doesn't exist:

Get-AppXPackage *Terminal*

The weird trick is from https://answers.microsoft.com/en-us/windows/forum/all/window-11-closes-my-apps-when-my-computer-goes-to/bd2e212c-a9b3-4bcb-8fe1-f1f95a72336e?page=2. Apparently this affects pretty much all apps installed from Store and has been a problem for almost a year.

@MichalStrehovsky commented on GitHub (Oct 31, 2022): For anyone else hitting this, I was getting a 100% repro of terminal disappearing after sleep. This One Weird Trick fixed it for me (run within PowerShell under a normal conhost (not Terminal), or it will complain that you have to close Terminal first): ```powershell Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.2875.0_x64__8wekyb3d8bbwe\AppxManifest.xml" ``` Find the path to Terminal's AppxManifest through this if that AppxManifest doesn't exist: ```powershell Get-AppXPackage *Terminal* ``` The weird trick is from https://answers.microsoft.com/en-us/windows/forum/all/window-11-closes-my-apps-when-my-computer-goes-to/bd2e212c-a9b3-4bcb-8fe1-f1f95a72336e?page=2. Apparently this affects pretty much all apps installed from Store and has been a problem for almost a year.

claunia commented

@pixiekat commented on GitHub (Nov 4, 2022):

Came here to say this suddenly happened to me too. Windows Terminal Preview.

I'll walk away for five minutes and the system will be in sleep mode. Wake it up, log back in, and Terminal is closed. It seems to be terminating WSL sessions too as I'll have to log back in to an Ubuntu window and start mysql and apache again.

I tried the steps in https://github.com/microsoft/terminal/issues/12513#issuecomment-1232502074 to make sure that wasn't the issue but we'll see.

Following.

@pixiekat commented on GitHub (Nov 4, 2022): Came here to say this suddenly happened to me too. Windows Terminal Preview. I'll walk away for five minutes and the system will be in sleep mode. Wake it up, log back in, and Terminal is closed. It seems to be terminating WSL sessions too as I'll have to log back in to an Ubuntu window and start mysql and apache again. I tried the steps in https://github.com/microsoft/terminal/issues/12513#issuecomment-1232502074 to make sure that wasn't the issue but we'll see. Following.

claunia commented

@AravindhKumarSivaramakrishnan commented on GitHub (Nov 12, 2022):

I am also facing the same issue after the recent windows update. Any solutions that worked ?

@AravindhKumarSivaramakrishnan commented on GitHub (Nov 12, 2022): I am also facing the same issue after the recent windows update. Any solutions that worked ?

claunia commented

@MichalStrehovsky commented on GitHub (Nov 14, 2022):

I am also facing the same issue after the recent windows update. Any solutions that worked ?

Did you try https://github.com/microsoft/terminal/issues/12513#issuecomment-1297821109?

@MichalStrehovsky commented on GitHub (Nov 14, 2022): > I am also facing the same issue after the recent windows update. Any solutions that worked ? Did you try https://github.com/microsoft/terminal/issues/12513#issuecomment-1297821109?

claunia commented

@Simran-B commented on GitHub (Dec 27, 2022):

Today, I noticed for the first time that my PowerShell (pwsh) sessions are gone after energy saving. The processes that these terminals were attached to still run in the background and hog the CPU for some reason (each 15% as per the Task manager even though they should be idling).

Other apps like Calculator are also affected, as others mentioned. It's a Lenovo laptop, and it doesn't make a difference whether it's plugged in or not.

Windows-Terminal, Version: 1.15.3466.0 (last change was on the 15th of December). PowerShell Core (pwsh) v7.3.1. Both installed via the Microsoft Store.

Registering the AppxManifest.xml (https://github.com/microsoft/terminal/issues/12513#issuecomment-1297821109) did not help.

The latest Windows 11 update was apparently ~~version 22H2 on the 17th of November~~, but as I wrote above, I just noticed this behavior for the first time today.

//edit: Between Nov 17 and Dec 27, there were actually several other updates:

(2022-12-17) Integrated Camera Driver - 10 (1903 or later)/11 (21H2 or later) - 10.0.22000.20261/10.13.22000.13/5.0.18.169 (via Lenovo Commercial Vantage)
(2022-12-16) 2022-12 Kumulatives Update für Windows 11 Version 22H2 für x64-basierte Systeme (KB5021255)
(2022-12-16) 2022-12 Kumulatives Update für .NET Framework 3.5 und 4.8.1 für Windows 11, version 22H2 für x64 (KB5020880)
(2022-12-15) Windows-Tool zum Entfernen bösartiger Software x64 - v5.108 (KB890830)
(2022-12-09) Update für Microsoft Defender Antivirus-Antischadsoftwareplattform – KB4052623 (Version 4.18.2211.5)
(2022-12-06) 2022-08 Sicherheitsupdate für Windows 11 22H2 für x64-basierte Systeme (KB5012170)
(2022-12-05) Lenovo - System - 10.6.2.1
(2022-11-21) Lenovo - System - 2.0.424.3
(2022-11-21) 2022-11 Kumulatives Update für .NET Framework 3.5 und 4.8.1 für Windows 11, version 22H2 für x64 (KB5020622)

@Simran-B commented on GitHub (Dec 27, 2022): Today, I noticed for the first time that my PowerShell (pwsh) sessions are gone after energy saving. The processes that these terminals were attached to still run in the background and hog the CPU for some reason (each 15% as per the Task manager even though they should be idling). Other apps like Calculator are also affected, as others mentioned. It's a Lenovo laptop, and it doesn't make a difference whether it's plugged in or not. Windows-Terminal, Version: 1.15.3466.0 (last change was on the 15th of December). PowerShell Core (pwsh) v7.3.1. Both installed via the Microsoft Store. Registering the AppxManifest.xml (https://github.com/microsoft/terminal/issues/12513#issuecomment-1297821109) did not help. The latest Windows 11 update was apparently ~version 22H2 on the 17th of November~, but as I wrote above, I just noticed this behavior for the first time today. **//edit:** Between Nov 17 and Dec 27, there were actually several other updates: - (2022-12-17) Integrated Camera Driver - 10 (1903 or later)/11 (21H2 or later) - 10.0.22000.20261/10.13.22000.13/5.0.18.169 (via Lenovo Commercial Vantage) - (2022-12-16) 2022-12 Kumulatives Update für Windows 11 Version 22H2 für x64-basierte Systeme (KB5021255) - (2022-12-16) 2022-12 Kumulatives Update für .NET Framework 3.5 und 4.8.1 für Windows 11, version 22H2 für x64 (KB5020880) - (2022-12-15) Windows-Tool zum Entfernen bösartiger Software x64 - v5.108 (KB890830) - (2022-12-09) Update für Microsoft Defender Antivirus-Antischadsoftwareplattform – KB4052623 (Version 4.18.2211.5) - (2022-12-06) 2022-08 Sicherheitsupdate für Windows 11 22H2 für x64-basierte Systeme (KB5012170) - (2022-12-05) Lenovo - System - 10.6.2.1 - (2022-11-21) Lenovo - System - 2.0.424.3 - (2022-11-21) 2022-11 Kumulatives Update für .NET Framework 3.5 und 4.8.1 für Windows 11, version 22H2 für x64 (KB5020622)

claunia commented

@IlayyaJohanson commented on GitHub (Dec 28, 2022):

Created thread with same problem here. https://answers.microsoft.com/en-us/windows/forum/windows_11-performance/win-11-microsoft-stores-apps-close-on-while-on/7afc907d-0ba8-4334-96ab-c5b9eec5b88a?page=2
Microsoft Store apps are closing. Started after last win11 updates. Any advices appreciated.

@IlayyaJohanson commented on GitHub (Dec 28, 2022): Created thread with same problem here. https://answers.microsoft.com/en-us/windows/forum/windows_11-performance/win-11-microsoft-stores-apps-close-on-while-on/7afc907d-0ba8-4334-96ab-c5b9eec5b88a?page=2 Microsoft Store apps are closing. Started after last win11 updates. Any advices appreciated.

claunia commented

@zadjii-msft commented on GitHub (Jan 3, 2023):

This came up in another thread[1], and was something I noticed myself after a clean reinstall. This might be something that the OS is doing itself, as a power-saver feature.

This is just a theory, but if you're encountering this regularly, go look in the Settings app for the Advanced Options for the Terminal.

Make sure that setting is set to Always. That might help here. Not sure when that ever changed - I was under the impression that win32 apps defaulted to always.

[1]: I think? I coulda swore I saw that mail while skimming emails over the holidays, but can't find it now.

@zadjii-msft commented on GitHub (Jan 3, 2023): This came up in another thread[1], and was something I noticed myself after a clean reinstall. This might be something that the OS is doing itself, as a power-saver feature. This is just a theory, but if you're encountering this regularly, go look in the Settings app for the Advanced Options for the Terminal. ![image](https://user-images.githubusercontent.com/18356694/210370550-8c59a5e0-0eca-4524-b206-372bfcb8ea60.png) ![image](https://user-images.githubusercontent.com/18356694/210367634-c4525ef2-fc0b-4b54-a8cf-89502dc95647.png) Make sure that setting is set to _Always_. That might help here. Not sure when that ever changed - I was under the impression that win32 apps defaulted to always. [1]: I think? I coulda swore I saw that mail while skimming emails over the holidays, but can't find it now.

claunia commented

@Simran-B commented on GitHub (Jan 5, 2023):

@zadjii-msft Thanks for the suggestion. I ran into some oddities when I tried the advanced app settings. I set the background apps permissions to Always and noticed that the paging of Git no longer works. The terminal responded to keyboard input fine in general, but running e.g. git log and then using the arrow down or page down keys had no effect, even after restarting Terminal. This problem disappeared after a reboot, so I guess it was unrelated. I then opened Terminal and Calculator and clicked the energy save option in the start menu. The screen turned black, but my laptop did not enter energy save mode. I reverted the background permissions option, but it would still not go to sleep. I installed a pending update for the Synaptics touchpad via Lenovo Commercial Update (a program that installs device-specific firmware etc.) and rebooted. Since then, the laptop enters energy save mode again without problems. No matter the background permissions setting, both the Terminal and Calculator app stay open?! It's fine now even if I unplug the power and activate the battery saver mode. Aside from the touchpad driver update, the only installed update in the meantime was Realtek Semiconductor Corp. - Extension - 10.0.22000.1 (2023-01-04) via Windows Update. I'll keep an eye on it and see if the Terminal begins to disappear again.

@Simran-B commented on GitHub (Jan 5, 2023): @zadjii-msft Thanks for the suggestion. I ran into some oddities when I tried the advanced app settings. I set the background apps permissions to Always and noticed that the paging of Git no longer works. The terminal responded to keyboard input fine in general, but running e.g. `git log` and then using the arrow down or page down keys had no effect, even after restarting Terminal. This problem disappeared after a reboot, so I guess it was unrelated. I then opened Terminal and Calculator and clicked the energy save option in the start menu. The screen turned black, but my laptop did not enter energy save mode. I reverted the background permissions option, but it would still not go to sleep. I installed a pending update for the Synaptics touchpad via Lenovo Commercial Update (a program that installs device-specific firmware etc.) and rebooted. Since then, the laptop enters energy save mode again without problems. No matter the background permissions setting, both the Terminal and Calculator app stay open?! It's fine now even if I unplug the power and activate the battery saver mode. Aside from the touchpad driver update, the only installed update in the meantime was Realtek Semiconductor Corp. - Extension - 10.0.22000.1 (2023-01-04) via Windows Update. I'll keep an eye on it and see if the Terminal begins to disappear again.

claunia commented

@nikitakot commented on GitHub (Jan 10, 2023):

The issue doesn't seem to be related to Terminal but to all MS Store apps. For me the same "auto-close during sleep" behavior happens to all apps I have from the store (Slack, Terminal, Spotify...). Is there a way to report it to the MS Store team somehow? I have a stable repro.
I've also tried the following command:

Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

It helped but the issue is back after 2 weeks.

@nikitakot commented on GitHub (Jan 10, 2023): The issue doesn't seem to be related to Terminal but to all MS Store apps. For me the same "auto-close during sleep" behavior happens to all apps I have from the store (Slack, Terminal, Spotify...). Is there a way to report it to the MS Store team somehow? I have a stable repro. I've also tried the following command: ``` Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”} ``` It helped but the issue is back after 2 weeks.

claunia commented

@zadjii-msft commented on GitHub (Jan 10, 2023):

@nikitakot That would seem to confirm my suspicions that this is By-Design, as a part of the "Background App Permissions" settings.

@zadjii-msft commented on GitHub (Jan 10, 2023): @nikitakot That would seem to confirm my suspicions that this is By-Design, as a part of the ["Background App Permissions" settings](https://github.com/microsoft/terminal/issues/12513#issuecomment-1369795207).

claunia commented

@nikitakot commented on GitHub (Jan 10, 2023):

@zadjii-msft I just tried to change these Background App Permissions for Terminal to Always and put my laptop into sleep. It didn't help, the terminal was closed when I woke up the laptop. Other Store apps also shut down itself (Slack and Spotify).

The repro on my machine is constant and I remember it first appeared after 2022-11 Cumulative Update for Windows 11 for x64-based Systems (KB5019157).
Couple weeks ago I run this PowerShell command Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”} and it helped. But today the issue started to happen again.

You're not aware how can I submit it to Store/Windows team? I've tried Feedback Hub but got no reply.

@nikitakot commented on GitHub (Jan 10, 2023): @zadjii-msft I just tried to change these `Background App Permissions` for Terminal to `Always` and put my laptop into sleep. It didn't help, the terminal was closed when I woke up the laptop. Other Store apps also shut down itself (Slack and Spotify). The repro on my machine is constant and I remember it first appeared after `2022-11 Cumulative Update for Windows 11 for x64-based Systems (KB5019157)`. Couple weeks ago I run this PowerShell command `Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}` and it helped. But today the issue started to happen again. You're not aware how can I submit it to Store/Windows team? I've tried Feedback Hub but got no reply.

claunia commented

@zadjii-msft commented on GitHub (Jan 10, 2023):

If it's a consistent repro, then try the following: /feedback

(I was mostly optimistic that this wasn't a crash of any sort, but was just a "Store doin Store things" issue.)

If there's anything in Event Viewer that looks sus, that might be helpful too.

@zadjii-msft commented on GitHub (Jan 10, 2023): If it's a consistent repro, then try the following: /feedback (I was mostly optimistic that this wasn't a crash of any sort, but was just a "Store doin Store things" issue.) If there's anything in Event Viewer that looks sus, that might be helpful too.

claunia commented

@ghost commented on GitHub (Jan 10, 2023):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

@ghost commented on GitHub (Jan 10, 2023): Hi there! Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end? Thanks! ![image](https://user-images.githubusercontent.com/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png) ![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)

claunia commented

@nikitakot commented on GitHub (Jan 11, 2023):

@zadjii-msft Well...the Feedback Hub app also shut down itself during sleep together with all other MS Store apps. Feedback Hub is also a MS Store application. So I wasn't able to record traces.

upd
the recording actually happened - https://aka.ms/AAj6ums

@nikitakot commented on GitHub (Jan 11, 2023): @zadjii-msft Well...the Feedback Hub app also shut down itself during sleep together with all other MS Store apps. Feedback Hub is also a MS Store application. So I wasn't able to record traces. **upd** the recording actually happened - https://aka.ms/AAj6ums

claunia commented

@nikitakot commented on GitHub (Jan 13, 2023):

@zadjii-msft did you have a chance to take a look at the traces?

@nikitakot commented on GitHub (Jan 13, 2023): @zadjii-msft did you have a chance to take a look at the traces?

claunia commented

@zadjii-msft commented on GitHub (Jan 13, 2023):

Huh. All the dumps are for conhost. There's no terminal dumps at all. So either the OS is cleanly closing Terminal (causing conhost to crash) or something else is going on.

I did find a couple error reports of pwsh crashing, but presumably, that's just what was in the tabs on the Terminal, and they "crashed" when their underlying conhosts died. All I could get out of those was a ExceptionCode=3762504530, FACILITY_SECUREBOOT, EXCEPTION_COMPLUS, not super useful.

The machine I'm on right now doesn't have access to pull the actual dumps themselves, but historically conhost dumps for something like this haven't been super useful. Maybe the tracing would have something?

@zadjii-msft commented on GitHub (Jan 13, 2023): Huh. All the dumps are for conhost. There's no terminal dumps at all. So either the OS is cleanly closing Terminal (causing conhost to crash) or something else is going on. I did find a couple error reports of pwsh crashing, but presumably, that's just what was in the tabs on the Terminal, and they "crashed" when their underlying conhosts died. All I could get out of those was a `ExceptionCode=3762504530`, `FACILITY_SECUREBOOT`, `EXCEPTION_COMPLUS`, not super useful. The machine I'm on right now doesn't have access to pull the actual dumps themselves, but historically conhost dumps for something like this haven't been super useful. Maybe the tracing would have something?

claunia commented

@nikitakot commented on GitHub (Jan 13, 2023):

@zadjii-msft which tracing? If you mean Event Viewer I didn't find anything suspicious there.

The script bellow doesn't solve the issue anymore btw.

Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

@nikitakot commented on GitHub (Jan 13, 2023): @zadjii-msft which tracing? If you mean Event Viewer I didn't find anything suspicious there. The script bellow doesn't solve the issue anymore btw. ``` Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”} ```

claunia commented

@Simran-B commented on GitHub (Jan 17, 2023):

I wrote earlier that the problem fixed itself. Well, it's broken again. I set the background app permissions to Always, and tried re-registering and repairing the app, but to no avail. Store apps just vanish. Interestingly, the one time the Calculator window was still there for a few seconds after waking (I don't have a recording of that, though). Another time I had Spotify play music, while also having Calc, Notepad, and Terminal open. None of them disappeared the first two tries. Then I went AFK for a few minutes and when I returned, they were also gone after waking including Feedback Hub.

Calc: https://aka.ms/AAj9bnw (did not appear under My feedback, second attempt: https://aka.ms/AAj7nfd)
Spotify: https://aka.ms/AAj7neo
Terminal: https://aka.ms/AAj7nf4
Notepad et al.: https://aka.ms/AAj7ft7

FWIW, the integrated terminal of VSCode reported this after wake:
The terminal process "C:\Users\<Username>\AppData\Local\Microsoft\WindowsApps\Microsoft.PowerShell_8wekyb3d8bbwe\pwsh.exe" terminated with exit code: 1.

@Simran-B commented on GitHub (Jan 17, 2023): I wrote earlier that the problem fixed itself. Well, it's broken again. I set the background app permissions to Always, and tried re-registering and repairing the app, but to no avail. Store apps just vanish. Interestingly, the one time the Calculator window was still there for a few seconds after waking (I don't have a recording of that, though). Another time I had Spotify play music, while also having Calc, Notepad, and Terminal open. None of them disappeared the first two tries. Then I went AFK for a few minutes and when I returned, they were also gone after waking including Feedback Hub. Calc: https://aka.ms/AAj9bnw (did not appear under My feedback, second attempt: https://aka.ms/AAj7nfd) Spotify: https://aka.ms/AAj7neo Terminal: https://aka.ms/AAj7nf4 Notepad et al.: https://aka.ms/AAj7ft7 FWIW, the integrated terminal of VSCode reported this after wake: `The terminal process "C:\Users\<Username>\AppData\Local\Microsoft\WindowsApps\Microsoft.PowerShell_8wekyb3d8bbwe\pwsh.exe" terminated with exit code: 1.`

claunia commented

@nikitakot commented on GitHub (Jan 31, 2023):

@zadjii-msft is there a way to propagate it somehow to the MS Store team? I know this bug is most probably not Terminal related but the issue seems to affect a lot of users - for ex. https://answers.microsoft.com/en-us/windows/forum/windows_11-performance/win-11-microsoft-stores-apps-close-on-while-on/7afc907d-0ba8-4334-96ab-c5b9eec5b88a.

I still have a stable repro.

@nikitakot commented on GitHub (Jan 31, 2023): @zadjii-msft is there a way to propagate it somehow to the MS Store team? I know this bug is most probably not Terminal related but the issue seems to affect a lot of users - for ex. https://answers.microsoft.com/en-us/windows/forum/windows_11-performance/win-11-microsoft-stores-apps-close-on-while-on/7afc907d-0ba8-4334-96ab-c5b9eec5b88a. I still have a stable repro.

claunia commented

2026-01-31 05:23:24 +00:00

@DHowett commented on GitHub (Feb 1, 2023):

@zadjii-msft is there a way to propagate it somehow

Ah, sorry. We're tracking this internally and it has gotten a lot of attention. 😄

@DHowett commented on GitHub (Feb 1, 2023): > @zadjii-msft is there a way to propagate it somehow Ah, sorry. We're tracking this internally and it has gotten a lot of attention. :smile:

claunia commented

@notuntoward commented on GitHub (Feb 2, 2023):

@DHowett, I hope MS fixes this soon. Where I work, quick responses are expected on Slack, but it is sometimes hours before I realize that Slack has been silently killed, and all the while, somebody has been trying to get in touch.

@notuntoward commented on GitHub (Feb 2, 2023): @DHowett, I hope MS fixes this soon. Where I work, quick responses are expected on Slack, but it is sometimes hours before I realize that Slack has been silently killed, and all the while, somebody has been trying to get in touch.

claunia commented

2026-01-31 05:23:24 +00:00

@zadjii-msft commented on GitHub (Feb 6, 2023):

Heyo look at that, there was progress on the internal bug report:

MSFT:38334285 got duped to MSFT:42248240 EDIT who got duped to MSFT:41020326 which is different? from MSFT:42831529, but I suspect one of those last two will be duped to the other.
From that bug:

HAM is terminating centennial processes because it seems to be applying UWP policies.
That second bug had a related PR in os.2020!8276099
42248240 looks like it's still open, so it might not be fully resolved yet, but clearly there's traction.

@zadjii-msft commented on GitHub (Feb 6, 2023): Heyo look at that, there was progress on the internal bug report: * MSFT:38334285 got duped to MSFT:42248240 EDIT who got duped to MSFT:41020326 which is different? from MSFT:42831529, but I suspect one of those last two will be duped to the other. * From that bug: > HAM is terminating centennial processes because it seems to be applying UWP policies. * That second bug had a related PR in os.2020!8276099 * 42248240 looks like it's still open, so it might not be fully resolved yet, but clearly there's traction.

claunia commented

2026-01-31 05:23:24 +00:00

@rodrigolourencofarinha commented on GitHub (Feb 8, 2023):

I also have this issue, and the problem occurs with all Windows Store apps (e.g., Phone Link, WhatsApp, Killer Intelligence Center).

In my case, the apps are closed only when the computer wakes from sleep when using battery power. When the laptop is plugged in, this problem does not occur. Maybe others can test to see if there is a relationship between battery/AC power with this issue.

If it is related, maybe it is a problem with Modern Standby?

@rodrigolourencofarinha commented on GitHub (Feb 8, 2023): I also have this issue, and the problem occurs with all Windows Store apps (e.g., Phone Link, WhatsApp, Killer Intelligence Center). In my case, the apps are closed only when the computer wakes from sleep **when using battery power**. When the laptop is plugged in, this problem does not occur. Maybe others can test to see if there is a relationship between battery/AC power with this issue. If it is related, maybe it is a problem with Modern Standby?

claunia commented

2026-01-31 05:23:25 +00:00

@jnzd commented on GitHub (Feb 16, 2023):

When the laptop is plugged in, this problem does not occur. Maybe others can test to see if there is a relationship between battery/AC power with this issue.

For me this issue happens no matter if the laptop is plugged in or not.

For me the most annoying thing about this is that WSL/ubuntu are store apps. Actually I am not sure if WSL closes or if just Ubuntu shuts down, because I have to go into task manager and shut down WSL separately before I can restart Ubuntu (and Docker, which relies on WSL for what it's worth)

I am happy to see that this issue is getting attention

@jnzd commented on GitHub (Feb 16, 2023): > When the laptop is plugged in, this problem does not occur. Maybe others can test to see if there is a relationship between battery/AC power with this issue. For me this issue happens no matter if the laptop is plugged in or not. For me the most annoying thing about this is that WSL/ubuntu are store apps. Actually I am not sure if WSL closes or if just Ubuntu shuts down, because I have to go into task manager and shut down WSL separately before I can restart Ubuntu (and Docker, which relies on WSL for what it's worth) I am happy to see that this issue is getting attention

claunia commented

2026-01-31 05:23:25 +00:00

@wisemanny commented on GitHub (Feb 17, 2023):

I had reported a similar problem before, tried various approaches, nothing turned out to be working. It seems to be now, that the root of problem is TextInputHost.exe. I see that this process disappears and restarts when the computer goes off the sleep mode and, in my case, both WT and Skype crashes. I see that Skype does not remove the icon from the notification's taskbar area, which happens when an app crashes.

Though in my case of WT - I constantly see pwsh.exe dmp files being generated. It seems to me like TextInputHost somehow causes pwsh.exe to crash on input, here is the clr stack:

0:000> !CLRStack 
OS Thread Id: 0x4350 (0)
        Child SP               IP Call Site
00000033797CB758 00007ff87118659f [HelperMethodFrame_2OBJ: 00000033797cb758] System.Environment.FailFast(System.String, System.Exception)
00000033797CB860 00007ff8d5e6de7b Microsoft.PowerShell.UnmanagedPSEntry.Start(System.String[], Int32)
00000033797CE2C8 00007ff870fd7c55 [HelperMethodFrame: 00000033797ce2c8] 
00000033797CE3C0 00007ff8d5e5b252 Microsoft.PowerShell.ConsoleControl.GetConsoleScreenBufferInfo(Microsoft.Win32.SafeHandles.SafeFileHandle)
00000033797CE420 00007ff8d5e63bef Microsoft.PowerShell.ConsoleHostRawUserInterface.get_CursorPosition()
00000033797CE470 00007ff8d5e73050 Microsoft.PowerShell.ConsoleHost+InputLoop.Run(Boolean)
00000033797CE520 00007ff8d5e72c73 Microsoft.PowerShell.ConsoleHost+InputLoop.RunNewInputLoop(Microsoft.PowerShell.ConsoleHost, Boolean)
00000033797CE570 00007ff8d5e60655 Microsoft.PowerShell.ConsoleHost.EnterNestedPrompt()
00000033797CE5D0 00007ff8d5e615fe Microsoft.PowerShell.ConsoleHost.DoRunspaceLoop(System.String, Boolean, System.Collections.ObjectModel.Collection`1<System.Management.Automation.Runspaces.CommandParameter>, Boolean, System.String, System.String)
00000033797CE670 00007ff8d5e614d2 Microsoft.PowerShell.ConsoleHost.Run(Microsoft.PowerShell.CommandLineParameterParser, Boolean)
00000033797CE6E0 00007ff8d5e5f745 Microsoft.PowerShell.ConsoleHost.Start(System.String, System.String, Boolean)
00000033797CE750 00007ff8d5e6ddb1 Microsoft.PowerShell.UnmanagedPSEntry.Start(System.String[], Int32)
00000033797CE7B0 00007ff8d5ee110d Microsoft.PowerShell.ManagedPSEntry.Main(System.String[])

Here is another one from today's morning:

0:000> !CLRStack 
OS Thread Id: 0x6a18 (0)
        Child SP               IP Call Site
0000004D9A17DAF8 00007ff8fd70f954 [HelperMethodFrame: 0000004d9a17daf8] System.Threading.WaitHandle.WaitOneCore(IntPtr, Int32)
0000004D9A17DC00 00007ff870706f0a System.Threading.WaitHandle.WaitOneNoCheck(Int32) [/_/src/libraries/System.Private.CoreLib/src/System/Threading/WaitHandle.cs @ 136]
0000004D9A17DC60 00007ff86f2da366 System.Management.Automation.Runspaces.PipelineBase.Invoke(System.Collections.IEnumerable)
0000004D9A17DCA0 00007ff86f3e93e6 System.Management.Automation.PowerShell+Worker.ConstructPipelineAndDoWork(System.Management.Automation.Runspaces.Runspace, Boolean)
0000004D9A17DD70 00007ff86f3e8ee4 System.Management.Automation.PowerShell+Worker.CreateRunspaceIfNeededAndDoWork(System.Management.Automation.Runspaces.Runspace, Boolean)
0000004D9A17DDE0 00007ff86f5b8a3c System.Management.Automation.PowerShell.CoreInvokeHelper[[System.__Canon, System.Private.CoreLib],[System.__Canon, System.Private.CoreLib]](System.Management.Automation.PSDataCollection`1<System.__Canon>, System.Management.Automation.PSDataCollection`1<System.__Canon>, System.Management.Automation.PSInvocationSettings)
0000004D9A17DE60 00007ff86f5b8ea5 System.Management.Automation.PowerShell.CoreInvoke[[System.__Canon, System.Private.CoreLib],[System.__Canon, System.Private.CoreLib]](System.Management.Automation.PSDataCollection`1<System.__Canon>, System.Management.Automation.PSDataCollection`1<System.__Canon>, System.Management.Automation.PSInvocationSettings)
0000004D9A17DEE0 00007ff86f13bfe5 System.Management.Automation.PowerShell.Invoke(System.Collections.IEnumerable, System.Management.Automation.PSInvocationSettings)
0000004D9A17DF40 00007ff8d5e6955f Microsoft.PowerShell.ConsoleHostUserInterface.TryInvokeUserDefinedReadLine(System.String ByRef)
0000004D9A17DF90 00007ff8d5e68cb7 Microsoft.PowerShell.ConsoleHostUserInterface.ReadLineWithTabCompletion(Microsoft.PowerShell.Executor)
0000004D9A17E0C0 00007ff8d5e730d9 Microsoft.PowerShell.ConsoleHost+InputLoop.Run(Boolean)
0000004D9A17E170 00007ff8d5e72c73 Microsoft.PowerShell.ConsoleHost+InputLoop.RunNewInputLoop(Microsoft.PowerShell.ConsoleHost, Boolean)
0000004D9A17E1C0 00007ff8d5e60655 Microsoft.PowerShell.ConsoleHost.EnterNestedPrompt()
0000004D9A17E220 00007ff8d5e615fe Microsoft.PowerShell.ConsoleHost.DoRunspaceLoop(System.String, Boolean, System.Collections.ObjectModel.Collection`1<System.Management.Automation.Runspaces.CommandParameter>, Boolean, System.String, System.String)
0000004D9A17E2C0 00007ff8d5e614d2 Microsoft.PowerShell.ConsoleHost.Run(Microsoft.PowerShell.CommandLineParameterParser, Boolean)
0000004D9A17E330 00007ff8d5e5f745 Microsoft.PowerShell.ConsoleHost.Start(System.String, System.String, Boolean)
0000004D9A17E3A0 00007ff8d5e6ddb1 Microsoft.PowerShell.UnmanagedPSEntry.Start(System.String[], Int32)
0000004D9A17E400 00007ff8d5ee110d Microsoft.PowerShell.ManagedPSEntry.Main(System.String[])

And here is what Event Log says from .NET, that is why I link the problem to TextInputHost.exe:

Application: pwsh.exe
CoreCLR Version: 7.0.222.60605
.NET Version: 7.0.2
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException: Cannot read keys when either application does not have a console or when console input has been redirected. Try Console.Read.
   at System.ConsolePal.ReadKey(Boolean intercept)
   at Microsoft.PowerShell.Internal.VirtualTerminal.ReadKey()
   at Microsoft.PowerShell.PSConsoleReadLine.ReadOneOrMoreKeys()
   at Microsoft.PowerShell.PSConsoleReadLine.ReadKeyThreadProc()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

TextInputHost.exe is a part of this appx:
C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy

I tried using procdump -t to capture its dump on exit. Indeed, it terminates when computer goes off the sleep (at least dump is generated then). But the reason was not clear from the dumps.

This is all I have so far. Hopefully it may help someone to track this down. For me it seems like something cause .net to crash, pwsh is done, WT is closing because there is nothing left. But I think I tried having tabs with cmd and not matter what, it is gone anyway. At the same time, I have Alacritty and wezterm open - they survive sleep just fine. Another idea was that this may be caused by something that impacts only apps installed from windows store. Both WT and Skype are such apps.

@wisemanny commented on GitHub (Feb 17, 2023): I had reported a similar problem before, tried various approaches, nothing turned out to be working. It seems to be now, that the root of problem is TextInputHost.exe. I see that this process disappears and restarts when the computer goes off the sleep mode and, in my case, both WT and Skype crashes. I see that Skype does not remove the icon from the notification's taskbar area, which happens when an app crashes. Though in my case of WT - I constantly see pwsh.exe dmp files being generated. It seems to me like TextInputHost somehow causes pwsh.exe to crash on input, here is the clr stack: ``` 0:000> !CLRStack OS Thread Id: 0x4350 (0) Child SP IP Call Site 00000033797CB758 00007ff87118659f [HelperMethodFrame_2OBJ: 00000033797cb758] System.Environment.FailFast(System.String, System.Exception) 00000033797CB860 00007ff8d5e6de7b Microsoft.PowerShell.UnmanagedPSEntry.Start(System.String[], Int32) 00000033797CE2C8 00007ff870fd7c55 [HelperMethodFrame: 00000033797ce2c8] 00000033797CE3C0 00007ff8d5e5b252 Microsoft.PowerShell.ConsoleControl.GetConsoleScreenBufferInfo(Microsoft.Win32.SafeHandles.SafeFileHandle) 00000033797CE420 00007ff8d5e63bef Microsoft.PowerShell.ConsoleHostRawUserInterface.get_CursorPosition() 00000033797CE470 00007ff8d5e73050 Microsoft.PowerShell.ConsoleHost+InputLoop.Run(Boolean) 00000033797CE520 00007ff8d5e72c73 Microsoft.PowerShell.ConsoleHost+InputLoop.RunNewInputLoop(Microsoft.PowerShell.ConsoleHost, Boolean) 00000033797CE570 00007ff8d5e60655 Microsoft.PowerShell.ConsoleHost.EnterNestedPrompt() 00000033797CE5D0 00007ff8d5e615fe Microsoft.PowerShell.ConsoleHost.DoRunspaceLoop(System.String, Boolean, System.Collections.ObjectModel.Collection`1<System.Management.Automation.Runspaces.CommandParameter>, Boolean, System.String, System.String) 00000033797CE670 00007ff8d5e614d2 Microsoft.PowerShell.ConsoleHost.Run(Microsoft.PowerShell.CommandLineParameterParser, Boolean) 00000033797CE6E0 00007ff8d5e5f745 Microsoft.PowerShell.ConsoleHost.Start(System.String, System.String, Boolean) 00000033797CE750 00007ff8d5e6ddb1 Microsoft.PowerShell.UnmanagedPSEntry.Start(System.String[], Int32) 00000033797CE7B0 00007ff8d5ee110d Microsoft.PowerShell.ManagedPSEntry.Main(System.String[]) ``` Here is another one from today's morning: ``` 0:000> !CLRStack OS Thread Id: 0x6a18 (0) Child SP IP Call Site 0000004D9A17DAF8 00007ff8fd70f954 [HelperMethodFrame: 0000004d9a17daf8] System.Threading.WaitHandle.WaitOneCore(IntPtr, Int32) 0000004D9A17DC00 00007ff870706f0a System.Threading.WaitHandle.WaitOneNoCheck(Int32) [/_/src/libraries/System.Private.CoreLib/src/System/Threading/WaitHandle.cs @ 136] 0000004D9A17DC60 00007ff86f2da366 System.Management.Automation.Runspaces.PipelineBase.Invoke(System.Collections.IEnumerable) 0000004D9A17DCA0 00007ff86f3e93e6 System.Management.Automation.PowerShell+Worker.ConstructPipelineAndDoWork(System.Management.Automation.Runspaces.Runspace, Boolean) 0000004D9A17DD70 00007ff86f3e8ee4 System.Management.Automation.PowerShell+Worker.CreateRunspaceIfNeededAndDoWork(System.Management.Automation.Runspaces.Runspace, Boolean) 0000004D9A17DDE0 00007ff86f5b8a3c System.Management.Automation.PowerShell.CoreInvokeHelper[[System.__Canon, System.Private.CoreLib],[System.__Canon, System.Private.CoreLib]](System.Management.Automation.PSDataCollection`1<System.__Canon>, System.Management.Automation.PSDataCollection`1<System.__Canon>, System.Management.Automation.PSInvocationSettings) 0000004D9A17DE60 00007ff86f5b8ea5 System.Management.Automation.PowerShell.CoreInvoke[[System.__Canon, System.Private.CoreLib],[System.__Canon, System.Private.CoreLib]](System.Management.Automation.PSDataCollection`1<System.__Canon>, System.Management.Automation.PSDataCollection`1<System.__Canon>, System.Management.Automation.PSInvocationSettings) 0000004D9A17DEE0 00007ff86f13bfe5 System.Management.Automation.PowerShell.Invoke(System.Collections.IEnumerable, System.Management.Automation.PSInvocationSettings) 0000004D9A17DF40 00007ff8d5e6955f Microsoft.PowerShell.ConsoleHostUserInterface.TryInvokeUserDefinedReadLine(System.String ByRef) 0000004D9A17DF90 00007ff8d5e68cb7 Microsoft.PowerShell.ConsoleHostUserInterface.ReadLineWithTabCompletion(Microsoft.PowerShell.Executor) 0000004D9A17E0C0 00007ff8d5e730d9 Microsoft.PowerShell.ConsoleHost+InputLoop.Run(Boolean) 0000004D9A17E170 00007ff8d5e72c73 Microsoft.PowerShell.ConsoleHost+InputLoop.RunNewInputLoop(Microsoft.PowerShell.ConsoleHost, Boolean) 0000004D9A17E1C0 00007ff8d5e60655 Microsoft.PowerShell.ConsoleHost.EnterNestedPrompt() 0000004D9A17E220 00007ff8d5e615fe Microsoft.PowerShell.ConsoleHost.DoRunspaceLoop(System.String, Boolean, System.Collections.ObjectModel.Collection`1<System.Management.Automation.Runspaces.CommandParameter>, Boolean, System.String, System.String) 0000004D9A17E2C0 00007ff8d5e614d2 Microsoft.PowerShell.ConsoleHost.Run(Microsoft.PowerShell.CommandLineParameterParser, Boolean) 0000004D9A17E330 00007ff8d5e5f745 Microsoft.PowerShell.ConsoleHost.Start(System.String, System.String, Boolean) 0000004D9A17E3A0 00007ff8d5e6ddb1 Microsoft.PowerShell.UnmanagedPSEntry.Start(System.String[], Int32) 0000004D9A17E400 00007ff8d5ee110d Microsoft.PowerShell.ManagedPSEntry.Main(System.String[]) ``` And here is what Event Log says from .NET, that is why I link the problem to TextInputHost.exe: ``` Application: pwsh.exe CoreCLR Version: 7.0.222.60605 .NET Version: 7.0.2 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidOperationException: Cannot read keys when either application does not have a console or when console input has been redirected. Try Console.Read. at System.ConsolePal.ReadKey(Boolean intercept) at Microsoft.PowerShell.Internal.VirtualTerminal.ReadKey() at Microsoft.PowerShell.PSConsoleReadLine.ReadOneOrMoreKeys() at Microsoft.PowerShell.PSConsoleReadLine.ReadKeyThreadProc() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) ``` TextInputHost.exe is a part of this appx: C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy I tried using procdump -t to capture its dump on exit. Indeed, it terminates when computer goes off the sleep (at least dump is generated then). But the reason was not clear from the dumps. This is all I have so far. Hopefully it may help someone to track this down. For me it seems like something cause .net to crash, pwsh is done, WT is closing because there is nothing left. But I think I tried having tabs with cmd and not matter what, it is gone anyway. At the same time, I have Alacritty and wezterm open - they survive sleep just fine. Another idea was that this may be caused by something that impacts only apps installed from windows store. Both WT and Skype are such apps.

claunia commented

2026-01-31 05:23:25 +00:00

@jnzd commented on GitHub (Feb 17, 2023):

Okay, so I may have found a viable fix to this problem in an answer by user ZupperClarke here: https://answers.microsoft.com/en-us/windows/forum/all/microsoft-stores-apps-close-on-while-on-sleeping/52e9c038-fa91-46b4-b3e8-d3f52ddf9811?page=3
and user troglo23 here: https://answers.microsoft.com/en-us/windows/forum/all/window-11-closes-my-apps-when-my-computer-goes-to/bd2e212c-a9b3-4bcb-8fe1-f1f95a72336e?page=2

They suggest running the following command in administrator mode in PowerShell:

Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

I have tried it yesterday, it didn't seem to work initially, but after a restart I could close my lid and the apps stayed open. Further, when I opened my laptop in the morning the apps were also still open.

I haven't restarted since and so I don't know how long term this fix is. (And as a disclaimer I have tried other things, like stopping the my phone app, and disabling auto start for it. This was suggested somewhere. I have since re-enabled it, but not restarted my laptop yet. I am far more confident that the above command was the fix and not changing something about a single app).

@jnzd commented on GitHub (Feb 17, 2023): Okay, so I may have found a viable fix to this problem in an answer by user ZupperClarke here: https://answers.microsoft.com/en-us/windows/forum/all/microsoft-stores-apps-close-on-while-on-sleeping/52e9c038-fa91-46b4-b3e8-d3f52ddf9811?page=3 and user troglo23 here: https://answers.microsoft.com/en-us/windows/forum/all/window-11-closes-my-apps-when-my-computer-goes-to/bd2e212c-a9b3-4bcb-8fe1-f1f95a72336e?page=2 They suggest running the following command in administrator mode in PowerShell: ```pwsh Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”} ``` I have tried it yesterday, it didn't seem to work initially, but after a restart I could close my lid and the apps stayed open. Further, when I opened my laptop in the morning the apps were also still open. I haven't restarted since and so I don't know how long term this fix is. (And as a disclaimer I have tried other things, like stopping the my phone app, and disabling auto start for it. This was suggested somewhere. I have since re-enabled it, but not restarted my laptop yet. I am far more confident that the above command was the fix and not changing something about a single app).

claunia commented

2026-01-31 05:23:26 +00:00

@wisemanny commented on GitHub (Feb 18, 2023):

@jnzd, FYI- I saw that trick some time ago and tried it, but for me it did not work. I did it for both WT and Skype. Both are still crashing/closing.

@wisemanny commented on GitHub (Feb 18, 2023): @jnzd, FYI- I saw that trick some time ago and tried it, but for me it did not work. I did it for both WT and Skype. Both are still crashing/closing.

claunia commented

2026-01-31 05:23:26 +00:00

@rodrigolourencofarinha commented on GitHub (Feb 21, 2023):

For me this issue happens no matter if the laptop is plugged in or not.

Today apps started closing whether the computer is plugged in or not.

It's really hard to pinpoint what changed since last week

@rodrigolourencofarinha commented on GitHub (Feb 21, 2023): > For me this issue happens no matter if the laptop is plugged in or not. Today apps started closing whether the computer is plugged in or not. It's really hard to pinpoint what changed since last week

claunia commented

2026-01-31 05:23:26 +00:00

@graymatter00 commented on GitHub (Feb 26, 2023):

The problem may be related to the Microsoft Phone Link app.

See [Win 11] Microsoft store's Apps close on while on sleeping

@graymatter00 commented on GitHub (Feb 26, 2023): The problem may be related to the Microsoft Phone Link app. See [[Win 11] Microsoft store's Apps close on while on sleeping](https://answers.microsoft.com/en-us/windows/forum/all/win-11-microsoft-stores-apps-close-on-while-on/7afc907d-0ba8-4334-96ab-c5b9eec5b88a?page=4)

claunia commented

@wisemanny commented on GitHub (Feb 26, 2023):

@graymatter00 I had it disabled and not running for a long time and crashes have happen every time during sleep, but decided to uninstall it completely. Will see how it changes the situation.

@wisemanny commented on GitHub (Feb 26, 2023): @graymatter00 I had it disabled and not running for a long time and crashes have happen every time during sleep, but decided to uninstall it completely. Will see how it changes the situation.

claunia commented

@wisemanny commented on GitHub (Mar 12, 2023):

Maybe this can be helpful, I used DebugDiag tool to try to get dump upon WT termination, but in the log I see such exceptions (I can provide the complete file):

1 ***********************
  2 *  EXCEPTION DETAILS  *
  3 ***********************
  4
  5 DetailID = 1
  6     Count:    2
  7     Exception #:  0X000006BF
  8     Stack:
  9         KERNELBASE!RaiseException+0x6c
 10         RPCRT4!RpcRaiseException+0x50
 11         RPCRT4!RpcRaiseException+0x14
 12         RPCRT4!NdrSendReceive+0x66
 13         RPCRT4!NdrClientCall3+0xc6a
 14         RPCRT4!NdrClientCall3+0xeb
 15         AppXDeploymentClient!Ordinal1+0x32e3
 16         AppXDeploymentClient!VerifyPackage+0x2b
 17         AppExtension!<lambda_b1ef69a29c93702515289cac97ab3bfc>::operator()+0x3f
 18         AppExtension!Windows::Internal::COperationLambdaVar<0,<lambda_b1ef69a29c93702515289cac97ab3bfc>,Windows::Internal::CMarshaledInterfaceResult<Windows::Storage::IStorageFolder> >::Run+0x23 19         AppExtension!Windows::Internal::AsyncOperation<Windows::Foundation::IAsyncOperation<Windows::Storage::StorageFolder * __ptr64>,Windows::Foundation::IAsyncOperationCompletedHandler<Window    s::Storage::StorageFolder * __ptr64>,Windows::Internal::CMarshaledInterfaceResult<Windows::Storage::IStorageFolder>,Windows::Internal::ComTaskPoolHandler,Windows::Internal::INilDelegate,Microsof    t::WRL::AsyncOptions<-1,0,&GUID_CAUSALITY_WINDOWS_PLATFORM_ID,2> >::_Run+0xfa
 20         AppExtension!Windows::Internal::AsyncOperation<Windows::Foundation::IAsyncOperation<Windows::Storage::StorageFolder * __ptr64>,Windows::Foundation::IAsyncOperationCompletedHandler<Window    s::Storage::StorageFolder * __ptr64>,Windows::Internal::CMarshaledInterfaceResult<Windows::Storage::IStorageFolder>,Windows::Internal::ComTaskPoolHandler,Windows::Internal::INilDelegate,Microsof    t::WRL::AsyncOptions<-1,0,&GUID_CAUSALITY_WINDOWS_PLATFORM_ID,2> >::Run+0x69
 21         shcore!WorkThreadManager::CThread::ThreadProc+0x26a
 22         shcore!WorkThreadManager::CThread::s_ExecuteThreadProc+0x22
 23         shcore!<lambda_9844335fc14345151eefcc3593dd6895>::<lambda_invoker_cdecl>+0x11
 24         KERNEL32!BaseThreadInitThunk+0x1d
 25         ntdll!RtlUserThreadStart+0x28

There are a few more:

1 DetailID = 2
  2     Count:    1
  3     Exception #:  0XE06D7363
  4     Stack:
  5         KERNELBASE!RaiseException+0x6c
  6         ucrtbase!CxxThrowException+0x9a
  7         Bcp47Langs!Bcp47Normalize+0xfe5c
  8         Bcp47Langs!NormalizeLanguageTag+0x81
  9         Bcp47Langs!ApplicationLanguages::GetApplicationLanguageOverride+0x58
 10         Bcp47Langs!GetApplicationLanguageOverride+0x43
 11         Windows_Globalization!Windows::Globalization::ApplicationLanguages::get_PrimaryLanguageOverride+0x11 [onecoreuap\base\win32\winnls\winrt\dll\applicationpreferences.cpp @ 44]
 12         TerminalApp!DllGetActivationFactory+0x1f150
 13         TerminalApp!DllGetActivationFactory+0x59c59
 14         TerminalApp!DllGetActivationFactory+0x425c4
 15         TerminalApp!DllCanUnloadNow+0xd7a6
 16         WindowsTerminal+0x3264c
 17         WindowsTerminal+0x8540
 18         WindowsTerminal+0x34d24
 19         WindowsTerminal+0x7d40
 20         WindowsTerminal+0x71d1
 21         WindowsTerminal+0xad97
 22         user32!DispatchMessageW+0x741
 23         user32!DispatchMessageW+0x3fc
 24         user32!IsRectEmpty+0x9a

and longer stack

and this one

  1 DetailID = 3
  2     Count:    1
  3     Exception #:  0XE06D7363
  4     Stack:
  5         KERNELBASE!RaiseException+0x6c
  6         ucrtbase!CxxThrowException+0x9a
  7         Bcp47Langs!Bcp47Normalize+0xfe5c
  8         Bcp47Langs!NormalizeLanguageTag+0x81
  9         Bcp47Langs!ApplicationLanguages::GetApplicationLanguageOverride+0x58
 10         Bcp47Langs!GetApplicationLanguageOverride+0x43
 11         Windows_Globalization!Windows::Globalization::ApplicationLanguages::get_PrimaryLanguageOverride+0x11 [onecoreuap\base\win32\winnls\winrt\dll\applicationpreferences.cpp @ 44]
 12         TerminalApp!DllGetActivationFactory+0x1f150
 13         TerminalApp!DllGetActivationFactory+0x59c59
 14         TerminalApp!DllGetActivationFactory+0x425c4
 15         TerminalApp!DllCanUnloadNow+0xd7a6
 16         WindowsTerminal+0x3264c
 17         WindowsTerminal+0x8540
 18         WindowsTerminal+0x34d24
 19         WindowsTerminal+0x7d40
 20         WindowsTerminal+0x71d1
 21         WindowsTerminal+0xad97
 22         user32!DispatchMessageW+0x741
 23         user32!DispatchMessageW+0x3fc
 24         user32!IsRectEmpty+0x9a
 25         ntdll!KiUserCallbackDispatcherContinue
 26         win32u!NtUserGetMessage+0x14
 27         user32!GetMessageW+0x2a
 28         InProcessClient64+0x97516
 29         InProcessClient64+0x97455
 30         WindowsTerminal+0x6877
 31         WindowsTerminal+0xef62
 32         KERNEL32!BaseThreadInitThunk+0x1d
 33         ntdll!RtlUserThreadStart+0x28

@wisemanny commented on GitHub (Mar 12, 2023): Maybe this can be helpful, I used DebugDiag tool to try to get dump upon WT termination, but in the log I see such exceptions (I can provide the complete file): ``` 1 *********************** 2 * EXCEPTION DETAILS * 3 *********************** 4 5 DetailID = 1 6 Count: 2 7 Exception #: 0X000006BF 8 Stack: 9 KERNELBASE!RaiseException+0x6c 10 RPCRT4!RpcRaiseException+0x50 11 RPCRT4!RpcRaiseException+0x14 12 RPCRT4!NdrSendReceive+0x66 13 RPCRT4!NdrClientCall3+0xc6a 14 RPCRT4!NdrClientCall3+0xeb 15 AppXDeploymentClient!Ordinal1+0x32e3 16 AppXDeploymentClient!VerifyPackage+0x2b 17 AppExtension!<lambda_b1ef69a29c93702515289cac97ab3bfc>::operator()+0x3f 18 AppExtension!Windows::Internal::COperationLambdaVar<0,<lambda_b1ef69a29c93702515289cac97ab3bfc>,Windows::Internal::CMarshaledInterfaceResult<Windows::Storage::IStorageFolder> >::Run+0x23 19 AppExtension!Windows::Internal::AsyncOperation<Windows::Foundation::IAsyncOperation<Windows::Storage::StorageFolder * __ptr64>,Windows::Foundation::IAsyncOperationCompletedHandler<Window s::Storage::StorageFolder * __ptr64>,Windows::Internal::CMarshaledInterfaceResult<Windows::Storage::IStorageFolder>,Windows::Internal::ComTaskPoolHandler,Windows::Internal::INilDelegate,Microsof t::WRL::AsyncOptions<-1,0,&GUID_CAUSALITY_WINDOWS_PLATFORM_ID,2> >::_Run+0xfa 20 AppExtension!Windows::Internal::AsyncOperation<Windows::Foundation::IAsyncOperation<Windows::Storage::StorageFolder * __ptr64>,Windows::Foundation::IAsyncOperationCompletedHandler<Window s::Storage::StorageFolder * __ptr64>,Windows::Internal::CMarshaledInterfaceResult<Windows::Storage::IStorageFolder>,Windows::Internal::ComTaskPoolHandler,Windows::Internal::INilDelegate,Microsof t::WRL::AsyncOptions<-1,0,&GUID_CAUSALITY_WINDOWS_PLATFORM_ID,2> >::Run+0x69 21 shcore!WorkThreadManager::CThread::ThreadProc+0x26a 22 shcore!WorkThreadManager::CThread::s_ExecuteThreadProc+0x22 23 shcore!<lambda_9844335fc14345151eefcc3593dd6895>::<lambda_invoker_cdecl>+0x11 24 KERNEL32!BaseThreadInitThunk+0x1d 25 ntdll!RtlUserThreadStart+0x28 ``` There are a few more: ``` 1 DetailID = 2 2 Count: 1 3 Exception #: 0XE06D7363 4 Stack: 5 KERNELBASE!RaiseException+0x6c 6 ucrtbase!CxxThrowException+0x9a 7 Bcp47Langs!Bcp47Normalize+0xfe5c 8 Bcp47Langs!NormalizeLanguageTag+0x81 9 Bcp47Langs!ApplicationLanguages::GetApplicationLanguageOverride+0x58 10 Bcp47Langs!GetApplicationLanguageOverride+0x43 11 Windows_Globalization!Windows::Globalization::ApplicationLanguages::get_PrimaryLanguageOverride+0x11 [onecoreuap\base\win32\winnls\winrt\dll\applicationpreferences.cpp @ 44] 12 TerminalApp!DllGetActivationFactory+0x1f150 13 TerminalApp!DllGetActivationFactory+0x59c59 14 TerminalApp!DllGetActivationFactory+0x425c4 15 TerminalApp!DllCanUnloadNow+0xd7a6 16 WindowsTerminal+0x3264c 17 WindowsTerminal+0x8540 18 WindowsTerminal+0x34d24 19 WindowsTerminal+0x7d40 20 WindowsTerminal+0x71d1 21 WindowsTerminal+0xad97 22 user32!DispatchMessageW+0x741 23 user32!DispatchMessageW+0x3fc 24 user32!IsRectEmpty+0x9a and longer stack ```` and this one ``` 1 DetailID = 3 2 Count: 1 3 Exception #: 0XE06D7363 4 Stack: 5 KERNELBASE!RaiseException+0x6c 6 ucrtbase!CxxThrowException+0x9a 7 Bcp47Langs!Bcp47Normalize+0xfe5c 8 Bcp47Langs!NormalizeLanguageTag+0x81 9 Bcp47Langs!ApplicationLanguages::GetApplicationLanguageOverride+0x58 10 Bcp47Langs!GetApplicationLanguageOverride+0x43 11 Windows_Globalization!Windows::Globalization::ApplicationLanguages::get_PrimaryLanguageOverride+0x11 [onecoreuap\base\win32\winnls\winrt\dll\applicationpreferences.cpp @ 44] 12 TerminalApp!DllGetActivationFactory+0x1f150 13 TerminalApp!DllGetActivationFactory+0x59c59 14 TerminalApp!DllGetActivationFactory+0x425c4 15 TerminalApp!DllCanUnloadNow+0xd7a6 16 WindowsTerminal+0x3264c 17 WindowsTerminal+0x8540 18 WindowsTerminal+0x34d24 19 WindowsTerminal+0x7d40 20 WindowsTerminal+0x71d1 21 WindowsTerminal+0xad97 22 user32!DispatchMessageW+0x741 23 user32!DispatchMessageW+0x3fc 24 user32!IsRectEmpty+0x9a 25 ntdll!KiUserCallbackDispatcherContinue 26 win32u!NtUserGetMessage+0x14 27 user32!GetMessageW+0x2a 28 InProcessClient64+0x97516 29 InProcessClient64+0x97455 30 WindowsTerminal+0x6877 31 WindowsTerminal+0xef62 32 KERNEL32!BaseThreadInitThunk+0x1d 33 ntdll!RtlUserThreadStart+0x28 ```

claunia commented

@playday3008 commented on GitHub (Mar 17, 2023):

"Instant hotspot" in "Phone Link" causing that strange behavior, just disable it

@playday3008 commented on GitHub (Mar 17, 2023): "Instant hotspot" in "Phone Link" causing that strange behavior, just disable it

claunia commented

@nikitakot commented on GitHub (Mar 21, 2023):

@DHowett @zadjii-msft any updates on the bug? I thought KB5022913 fixed it, but the issue is back.

After couple weeks of a properly working laptop (after KB5022913 update) I have the stable repro again. I'm happy to help, collect traces/logs. Does MS at least know what is causing the bug? It's so weird that it was working perfectly fine after KB5022913 and today it started to happen again. The bug is extremely annoying. It sill only affects MS store apps.

@nikitakot commented on GitHub (Mar 21, 2023): @DHowett @zadjii-msft any updates on the bug? I thought `KB5022913` fixed it, but the issue is back. After couple weeks of a properly working laptop (after `KB5022913` update) I have the stable repro again. I'm happy to help, collect traces/logs. Does MS at least know what is causing the bug? It's so weird that it was working perfectly fine after `KB5022913` and today it started to happen again. The bug is extremely annoying. It sill only affects MS store apps.

claunia commented

@wisemanny commented on GitHub (Mar 21, 2023):

"Instant hotspot" in "Phone Link" causing that strange behavior, just disable it

I removed Phone Link completely a few weeks ago and it did not improve the behavior.

@wisemanny commented on GitHub (Mar 21, 2023): > "Instant hotspot" in "Phone Link" causing that strange behavior, just disable it I removed Phone Link completely a few weeks ago and it did not improve the behavior.

claunia commented

@boxbot commented on GitHub (Mar 21, 2023):

Same problem. Terminal crashes every single time Windows 11 wakes up from sleep. And WSL2 stops responding.

Windows Terminal
Version: 1.16.10262.0

Windows 11
22621.1105

@boxbot commented on GitHub (Mar 21, 2023): Same problem. Terminal crashes every single time Windows 11 wakes up from sleep. And WSL2 stops responding. Windows Terminal Version: 1.16.10262.0 Windows 11 22621.1105

claunia commented

@unkn0wn-root commented on GitHub (Mar 22, 2023):

Same problem. Terminal crashes every single time Windows 11 wakes up from sleep. And WSL2 stops responding.

Windows Terminal Version: 1.16.10262.0

Windows 11 22621.1105

Same here.

@unkn0wn-root commented on GitHub (Mar 22, 2023): > Same problem. Terminal crashes every single time Windows 11 wakes up from sleep. And WSL2 stops responding. > > Windows Terminal Version: 1.16.10262.0 > > Windows 11 22621.1105 Same here.

claunia commented

2026-01-31 05:23:29 +00:00

@peterjuras commented on GitHub (Mar 22, 2023):

This issue should be reopened. This is a real blocker for productive development. We have teams relying on WSL2, this should be treated as an incident at Microsoft.

@peterjuras commented on GitHub (Mar 22, 2023): This issue should be reopened. This is a real blocker for productive development. We have teams relying on WSL2, this should be treated as an incident at Microsoft.

claunia commented

@IlayyaJohanson commented on GitHub (Mar 22, 2023):

This issue is not only terminal or WSL2 related. It is related to all Microsoft Store dependable software.

@IlayyaJohanson commented on GitHub (Mar 22, 2023): This issue is not only terminal or WSL2 related. It is related to all Microsoft Store dependable software.

claunia commented

2026-01-31 05:23:29 +00:00

@notuntoward commented on GitHub (Mar 22, 2023):

Yes, this is system-wide problem and it's not fixed. This should be reopened.

@notuntoward commented on GitHub (Mar 22, 2023): Yes, this is system-wide problem and it's not fixed. This should be reopened.

claunia commented

2026-01-31 05:23:29 +00:00

@zadjii-msft commented on GitHub (Mar 22, 2023):

To reiterate:

This is a system wide problem, not something the Terminal alone can fix.
This is not an OS-wide issue tracker, this is the Terminal issue tracker.

The BEST way to get this resolved is to file feedback using the Feedback Hub. Feedback Hub is a bit of a black box, I agree. However, it's the best chance for the relevant traces to end up in the hands of folks who can fix this. File feedback, share the links here, I can try promoting them so that they end up on someone's todo list. But since there's nothing for the terminal team to do here to fix the issue, we're gonna leave the thread closed. That doesn't mean the issue is fixed, it's just not work for us to do.

@zadjii-msft commented on GitHub (Mar 22, 2023): To reiterate: * This is a system wide problem, not something the Terminal alone can fix. * This is not an OS-wide issue tracker, this is the _Terminal_ issue tracker. The BEST way to get this resolved is to file feedback using the **Feedback Hub**. Feedback Hub is a bit of a black box, I agree. However, it's the best chance for the relevant traces to end up in the hands of folks who can fix this. File feedback, share the links here, I can try promoting them so that they end up on someone's todo list. But since there's nothing for the terminal team to do here to fix the issue, we're gonna leave the thread closed. That doesn't mean the issue is fixed, it's just not work for _us_ to do.

claunia commented

@nikitakot commented on GitHub (Mar 22, 2023):

To reiterate:

This is a system wide problem, not something the Terminal alone can fix.

This is not an OS-wide issue tracker, this is the Terminal issue tracker.

The BEST way to get this resolved is to file feedback using the Feedback Hub. Feedback Hub is a bit of a black box, I agree. However, it's the best chance for the relevant traces to end up in the hands of folks who can fix this. File feedback, share the links here, I can try promoting them so that they end up on someone's todo list. But since there's nothing for the terminal team to do here to fix the issue, we're gonna leave the thread closed. That doesn't mean the issue is fixed, it's just not work for us to do.

I've tried creating multiple Feedback Hub feedbacks but got no responses. I understand the bug is not Terminal related but maybe you can somehow address it to the correct team? MS store unfortunately doesn't have any github or other way to create a bug directly and Feedback Hub doesn't seem to get any attention.
I can collect traces again if you can send them to the right team.

@nikitakot commented on GitHub (Mar 22, 2023): > To reiterate: > > * This is a system wide problem, not something the Terminal alone can fix. > > * This is not an OS-wide issue tracker, this is the _Terminal_ issue tracker. > > > > > > The BEST way to get this resolved is to file feedback using the **Feedback Hub**. Feedback Hub is a bit of a black box, I agree. However, it's the best chance for the relevant traces to end up in the hands of folks who can fix this. File feedback, share the links here, I can try promoting them so that they end up on someone's todo list. But since there's nothing for the terminal team to do here to fix the issue, we're gonna leave the thread closed. That doesn't mean the issue is fixed, it's just not work for _us_ to do. I've tried creating multiple Feedback Hub feedbacks but got no responses. I understand the bug is not Terminal related but maybe you can somehow address it to the correct team? MS store unfortunately doesn't have any github or other way to create a bug directly and Feedback Hub doesn't seem to get any attention. I can collect traces again if you can send them to the right team.

claunia commented

@DHowett commented on GitHub (Mar 22, 2023):

The right team has already been informed, in quite a number of different duplicate bugs that they had to pick through. It would not help us or them to increase the amount of noise 😄

@DHowett commented on GitHub (Mar 22, 2023): The right team has already been informed, in quite a number of different duplicate bugs that they had to pick through. It would not help us or them to increase the amount of noise :smile:

claunia commented

@humiki commented on GitHub (Apr 27, 2023):

Windows 11 10.0.22621 here. I just open Windows Terminal 1.16.10262.0 with the default PowerShell 7.3.4 tab. Put my laptop to sleep. Wake up and Terminal is gone. It's really frustrating. Basically renders any work based on Windows Terminal very inefficient.

If it's a Microsoft Store issue, it's a complete shame that nothing is being done about this major system-wide problem.

The right team has already been informed

Can I elaborate what kind of team is it and is there any kind of ETA or status on this issue? Thank you.

@humiki commented on GitHub (Apr 27, 2023): Windows 11 10.0.22621 here. I just open Windows Terminal 1.16.10262.0 with the default PowerShell 7.3.4 tab. Put my laptop to sleep. Wake up and Terminal is gone. It's really frustrating. Basically renders any work based on Windows Terminal very inefficient. If it's a Microsoft Store issue, it's a complete shame that nothing is being done about this major system-wide problem. > The right team has already been informed Can I elaborate what kind of team is it and is there any kind of ETA or status on this issue? Thank you.

claunia commented

@DHowett commented on GitHub (Apr 27, 2023):

The fix for the issue mentioned in comments starting in February of this year was released in KB5023778.

@DHowett commented on GitHub (Apr 27, 2023): The fix for the issue mentioned in comments starting in February of this year was released in KB5023778.

claunia commented