starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal Unresponsive when Playing Games #22387

New Issue
Open
opened 2026-01-31 08:11:41 +00:00 by claunia · 34 comments
claunia commented 2026-01-31 08:11:41 +00:00
Owner
Copy Link

Originally created by @acelinkio on GitHub (Oct 12, 2024).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.20.11781.0

Windows build number

10.0.26100.0

Other Software

Steam
Any game launched through steam

Steps to reproduce

Start a video game and open Windows Terminal. Windows Terminal becomes unresponsive. This is true for any shell that terminal launches. powershell, cmd, wsl. This is on a fresh install of Windows 11 2024H2 on my Desktop with AMD Ryzen 7950x3d. I have disabled Game Mode and ensured power settings were set to performance.

Please note that a terminal inside of VSCode works without issue while Windows Terminal is entirely unresponsive.

Expected Behavior

No change in Windows Terminal performance when other programs are launching.

Actual Behavior

Windows Terminal freezes. After 3-5 minutes the terminal will accept keystrokes but quickly freeze again.

Originally created by @acelinkio on GitHub (Oct 12, 2024). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.20.11781.0 ### Windows build number 10.0.26100.0 ### Other Software Steam Any game launched through steam ### Steps to reproduce Start a video game and open Windows Terminal. Windows Terminal becomes unresponsive. This is true for any shell that terminal launches. powershell, cmd, wsl. This is on a fresh install of Windows 11 2024H2 on my Desktop with AMD Ryzen 7950x3d. I have disabled Game Mode and ensured power settings were set to performance. Please note that a terminal inside of VSCode works without issue while Windows Terminal is entirely unresponsive. ### Expected Behavior No change in Windows Terminal performance when other programs are launching. ### Actual Behavior Windows Terminal freezes. After 3-5 minutes the terminal will accept keystrokes but quickly freeze again.
claunia added the Area-RenderingIssue-BugProduct-Terminal labels 2026-01-31 08:11:42 +00:00
claunia commented 2026-01-31 08:11:42 +00:00
Author
Owner
Copy Link

@acelinkio commented on GitHub (Oct 12, 2024):

Turning the setting Use the new text renderer ("AtlasEngine") to Off and relaunching appears to be a workaround.

@acelinkio commented on GitHub (Oct 12, 2024): Turning the setting `Use the new text renderer ("AtlasEngine")` to Off and relaunching appears to be a workaround.
claunia commented 2026-01-31 08:11:43 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 14, 2024):

This isn't an issue that's exclusive to Windows Terminal as it also occurs with Discord for instance. Given that you've got a 7950X3D, I suspect you're not gaming on the iGPU. Can you tell us what GPU you have? I suspect it's an Nvidia one, because I have that issue as well and also have an Nvidia GPU.

My suspicion is that this is a bug in the Nvidia driver and/or with the interaction with DWM. Windows 11 24H2 has the new WDDM 3.2 model after all, plus a ton of new DWM features. It's definitely not a bug in Windows Terminal itself.

@lhecker commented on GitHub (Oct 14, 2024): This isn't an issue that's exclusive to Windows Terminal as it also occurs with Discord for instance. Given that you've got a 7950X3D, I suspect you're not gaming on the iGPU. Can you tell us what GPU you have? I suspect it's an Nvidia one, because I have that issue as well and also have an Nvidia GPU. My suspicion is that this is a bug in the Nvidia driver and/or with the interaction with DWM. Windows 11 24H2 has the new WDDM 3.2 model after all, plus a ton of new DWM features. It's definitely not a bug in Windows Terminal itself.
claunia commented 2026-01-31 08:11:43 +00:00
Author
Owner
Copy Link

@acelinkio commented on GitHub (Oct 14, 2024):

This isn't an issue that's exclusive to Windows Terminal as it also occurs with Discord for instance. Given that you've got a 7950X3D, I suspect you're not gaming on the iGPU. Can you tell us what GPU you have? I suspect it's an Nvidia one, because I have that issue as well and also have an Nvidia GPU.

My suspicion is that this is a bug in the Nvidia driver and/or with the interaction with DWM. Windows 11 24H2 has the new WDDM 3.2 model after all, plus a ton of new DWM features. It's definitely not a bug in Windows Terminal itself.

Running a Nvidia 3090ti. Didn't really consider the terminal was leveraging the dGPU. Your explaination makes sense.

On my prior Windows 11 install I faced a lot of bugs where programs launched with the iGPU. Windows Management and other apps like CPUz for example would take minutes to launch. On that previous install I disabled the iGPU in Device Manager would fix some issues but cause other GUI funkyness. So far Win11 24h2 has been solid without disabling the iGPU in Device Manager outside of Windows Terminal.

Is there a better way to disable the iGPU? I didn't see an option in my motherboard bios. Back in my day as long as you plugged the monitor into the dGPU, you were good.

@acelinkio commented on GitHub (Oct 14, 2024): > This isn't an issue that's exclusive to Windows Terminal as it also occurs with Discord for instance. Given that you've got a 7950X3D, I suspect you're not gaming on the iGPU. Can you tell us what GPU you have? I suspect it's an Nvidia one, because I have that issue as well and also have an Nvidia GPU. > > My suspicion is that this is a bug in the Nvidia driver and/or with the interaction with DWM. Windows 11 24H2 has the new WDDM 3.2 model after all, plus a ton of new DWM features. It's definitely not a bug in Windows Terminal itself. Running a Nvidia 3090ti. Didn't really consider the terminal was leveraging the dGPU. Your explaination makes sense. On my prior Windows 11 install I faced a lot of bugs where programs launched with the iGPU. Windows Management and other apps like CPUz for example would take minutes to launch. On that previous install I disabled the iGPU in Device Manager would fix some issues but cause other GUI funkyness. So far Win11 24h2 has been solid without disabling the iGPU in Device Manager outside of Windows Terminal. Is there a better way to disable the iGPU? I didn't see an option in my motherboard bios. Back in my day as long as you plugged the monitor into the dGPU, you were good.
claunia commented 2026-01-31 08:11:43 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 14, 2024):

Didn't really consider the terminal was leveraging the dGPU.

Text was always rendered using the GPU, even on ancient versions of Windows (Windows 2000, etc.), so in that regard nothing has changed. And it doesn't outright use the dGPU either: Instead, it uses your "primary" GPU, which is the GPU where your primary display is connected to. If you were to plug your display into your mainboard instead of your Nvidia GPU we'd use the iGPU.

I don't really recommend disabling the iGPU in Windows as doing so does not save power. It just hides it from Windows while keeping it fully powered, and you don't even get the benefits of having an iGPU anymore. Disabling it in the BIOS on the other hand should have an effect and reduce power draw. There's nothing that the RDNA2 iGPU can do that your dGPU can't so doing that should be safe (since both are about the same age). (But if anything goes wrong, please keep in mind that I can't visit you to fix it. 😄 Everything I'm writing here should not be taken as advice to actually do it.)

I didn't see an option in my motherboard bios.

There are many different locations for that setting, depending on the customization from your mainboard vendor. It's always in the "Advanced" tab, and then sometimes in a "Chipset" or "Onboard" configuration submenu. If it's in none of the submenus in the "Advanced" tab, you can go to "AMD CBS" and then either "NBIO Common Options" or "GFX Configuration" or similar. Within those, there should be a setting to disable the iGPU. Only use the AMD CBS menu if it's not anywhere else. Keep in mind that afterwards you'll need your Nvidia GPU to see anything. If it's ever missing or broken you need to reset your BIOS completely.

That will not solve your issue though. In fact, I don't even have an iGPU. I'll have to report a bug against DWM most likely, and they'll have to investigate this.

Back in my day as long as you plugged the monitor into the dGPU, you were good.

I'm not sure how long those days are past, but I there have been countless major issues over the last 2 decades with both Nvidia and AMD. Here's an example of a longstanding Nvidia bug with ~200 comments: https://github.com/microsoft/terminal/issues/649

@lhecker commented on GitHub (Oct 14, 2024): > Didn't really consider the terminal was leveraging the dGPU. Text was always rendered using the GPU, even on ancient versions of Windows (Windows 2000, etc.), so in that regard nothing has changed. And it doesn't outright use the dGPU either: Instead, it uses your "primary" GPU, which is the GPU where your primary display is connected to. If you were to plug your display into your mainboard instead of your Nvidia GPU we'd use the iGPU. I don't really recommend disabling the iGPU in Windows as doing so does not save power. It just hides it from Windows while keeping it fully powered, and you don't even get the benefits of having an iGPU anymore. Disabling it in the BIOS on the other hand should have an effect and reduce power draw. There's nothing that the RDNA2 iGPU can do that your dGPU can't so doing that should be safe (since both are about the same age). (But if anything goes wrong, please keep in mind that I can't visit you to fix it. 😄 Everything I'm writing here should not be taken as advice to actually do it.) > I didn't see an option in my motherboard bios. There are many different locations for that setting, depending on the customization from your mainboard vendor. It's always in the "Advanced" tab, and then sometimes in a "Chipset" or "Onboard" configuration submenu. If it's in none of the submenus in the "Advanced" tab, you can go to "AMD CBS" and then either "NBIO Common Options" or "GFX Configuration" or similar. Within those, there should be a setting to disable the iGPU. Only use the AMD CBS menu if it's not anywhere else. Keep in mind that afterwards you'll need your Nvidia GPU to see anything. If it's ever missing or broken you need to reset your BIOS completely. That will not solve your issue though. In fact, I don't even have an iGPU. I'll have to report a bug against DWM most likely, and they'll have to investigate this. > Back in my day as long as you plugged the monitor into the dGPU, you were good. I'm not sure how long those days are past, but I there have been countless major issues over the last 2 decades with both Nvidia and AMD. Here's an example of a longstanding Nvidia bug with ~200 comments: https://github.com/microsoft/terminal/issues/649
claunia commented 2026-01-31 08:11:44 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 15, 2024):

We should leave this issue open so that others won't create duplicates accidentally. I expect this to be a common bug report as people continue to update to 24H2.

@lhecker commented on GitHub (Oct 15, 2024): We should leave this issue open so that others won't create duplicates accidentally. I expect this to be a common bug report as people continue to update to 24H2.
claunia commented 2026-01-31 08:11:45 +00:00
Author
Owner
Copy Link

@bptrsn commented on GitHub (Nov 9, 2024):

Turning the setting Use the new text renderer ("AtlasEngine") to Off and relaunching appears to be a workaround.

Hello, I do not have this setting and my Windows Terminal freezes/crashes since updating to 24H2 a couple days ago :(

Is there any other fix? I use Windows Terminal daily. I am on Windows Terminal Version: 1.21.2911.0

@bptrsn commented on GitHub (Nov 9, 2024): > Turning the setting `Use the new text renderer ("AtlasEngine")` to Off and relaunching appears to be a workaround. Hello, I do not have this setting and my Windows Terminal freezes/crashes since updating to 24H2 a couple days ago :( Is there any other fix? I use Windows Terminal daily. I am on Windows Terminal Version: 1.21.2911.0
claunia commented 2026-01-31 08:11:45 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 10, 2024):

I have a theory that it may be fixed if you set the background opacity of the window to less than 100 (Settings > Defaults > Appearance).
Edit: It seems my theory is correct.

@lhecker commented on GitHub (Nov 10, 2024): I have a theory that it may be fixed if you set the background opacity of the window to less than 100 (Settings > Defaults > Appearance). Edit: It seems my theory is correct.
claunia commented 2026-01-31 08:11:46 +00:00
Author
Owner
Copy Link

@bptrsn commented on GitHub (Nov 12, 2024):

I have a theory that it may be fixed if you set the background opacity of the window to less than 1 (Settings > Defaults > Advanced). Edit: It seems my theory is correct.

I don't have that setting:
Image

@bptrsn commented on GitHub (Nov 12, 2024): > I have a theory that it may be fixed if you set the background opacity of the window to less than 1 (Settings > Defaults > Advanced). Edit: It seems my theory is correct. I don't have that setting: ![Image](https://github.com/user-attachments/assets/ea2c564d-777f-4381-81b0-3851f8b28bc0)
claunia commented 2026-01-31 08:11:47 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 12, 2024):

Oh, I apologize. I meant to write "Appearance" instead of "Advanced". I fixed my comment.

@lhecker commented on GitHub (Nov 12, 2024): Oh, I apologize. I meant to write "Appearance" instead of "Advanced". I fixed my comment.
claunia commented 2026-01-31 08:11:48 +00:00
Author
Owner
Copy Link

@bptrsn commented on GitHub (Nov 12, 2024):

Oh, I apologize. I meant to write "Appearance" instead of "Advanced". I fixed my comment.

Ahh I see. Well that just gives a transparent Terminal :D Can't work with that :D
I'll try reverting Nvidia driver to older version and see if that fixes it :)

@bptrsn commented on GitHub (Nov 12, 2024): > Oh, I apologize. I meant to write "Appearance" instead of "Advanced". I fixed my comment. Ahh I see. Well that just gives a transparent Terminal :D Can't work with that :D I'll try reverting Nvidia driver to older version and see if that fixes it :)
claunia commented 2026-01-31 08:11:48 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 22, 2024):

This has been reported as MSFT-55182474 internally.

Personally, I've found that disabling this setting fixed it for me, as another possible workaround:
Image

@lhecker commented on GitHub (Nov 22, 2024): This has been reported as MSFT-55182474 internally. Personally, I've found that disabling this setting fixed it for me, as another possible workaround: ![Image](https://github.com/user-attachments/assets/11dc7cee-07bc-47f6-af8f-eee74d89ddf5)
claunia commented 2026-01-31 08:11:49 +00:00
Author
Owner
Copy Link

@bptrsn commented on GitHub (Nov 25, 2024):

I got it fixed by playing around with settings in Windows Terminal.
I think it was the "Use software rendering (WARP)" one under Rendering that did it. Haven't had WT freeze since.

@bptrsn commented on GitHub (Nov 25, 2024): I got it fixed by playing around with settings in Windows Terminal. I think it was the "Use software rendering (WARP)" one under Rendering that did it. Haven't had WT freeze since.
claunia commented 2026-01-31 08:11:49 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 25, 2024):

Ahh I see. Well that just gives a transparent Terminal :D Can't work with that :D

You can set it to 99 and it'll essentially appear as if it's not transparent at all.

I think it was the "Use software rendering (WARP)" one under Rendering that did it. Haven't had WT freeze since.

That will indeed fix it, but I strongly advise against doing that. It's really CPU intensive for no good reason when you have a perfectly fine GPU to use.

@lhecker commented on GitHub (Nov 25, 2024): > Ahh I see. Well that just gives a transparent Terminal :D Can't work with that :D You can set it to 99 and it'll essentially appear as if it's not transparent at all. > I think it was the "Use software rendering (WARP)" one under Rendering that did it. Haven't had WT freeze since. That will indeed fix it, but I strongly advise against doing that. It's _really_ CPU intensive for no good reason when you have a perfectly fine GPU to use.
claunia commented 2026-01-31 08:11:49 +00:00
Author
Owner
Copy Link

@bptrsn commented on GitHub (Nov 27, 2024):

Task Manager says 0 to 0.1% usage, but I'll try your opacity route solution.

You originally wrote "set the background opacity of the window to less than 1", which I thought you meant 0 by haha, I'm guessing it was supposed to say 100.

@bptrsn commented on GitHub (Nov 27, 2024): Task Manager says 0 to 0.1% usage, but I'll try your opacity route solution. You originally wrote "set the background opacity of the window to less than 1", which I thought you meant 0 by haha, I'm guessing it was supposed to say 100.
claunia commented 2026-01-31 08:11:50 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 27, 2024):

Task Manager says 0 to 0.1% usage [...]

It depends on what you're doing. If you print a lot of text, it'll be significantly higher. I have an AMD 5950X and it'll produce up to 40% load and consume >30W. If I use my GPU on the other hand, it produces <1% load and consumes <4W. Software rasterization, aka WARP, also runs across all CPU cores which is not ideal during gaming because it may steal the game's time slices. It should only ever be used as an option of last resort, because CPUs are simply not good at emulating GPUs.

You originally wrote "set the background opacity of the window to less than 1", which I thought you meant 0 by haha, I'm guessing it was supposed to say 100.

Oh, it's because the value is a percentage, so I meant "less than 1" as in "less than 100 percent". 😅 I apologize for that.

@lhecker commented on GitHub (Nov 27, 2024): > Task Manager says 0 to 0.1% usage [...] It depends on what you're doing. If you print a lot of text, it'll be significantly higher. I have an AMD 5950X and it'll produce up to 40% load and consume >30W. If I use my GPU on the other hand, it produces <1% load and consumes <4W. Software rasterization, aka WARP, also runs across all CPU cores which is not ideal during gaming because it may steal the game's time slices. It should only ever be used as an option of last resort, because CPUs are simply not good at emulating GPUs. > You originally wrote "set the background opacity of the window to less than 1", which I thought you meant 0 by haha, I'm guessing it was supposed to say 100. Oh, it's because the value is a percentage, so I meant "less than 1" as in "less than 100 percent". 😅 I apologize for that.
claunia commented 2026-01-31 08:11:50 +00:00
Author
Owner
Copy Link

@bptrsn commented on GitHub (Nov 29, 2024):

Task Manager says 0 to 0.1% usage [...]

It depends on what you're doing. If you print a lot of text, it'll be significantly higher. I have an AMD 5950X and it'll produce up to 40% load and consume >30W. If I use my GPU on the other hand, it produces <1% load and consumes <4W. Software rasterization, aka WARP, also runs across all CPU cores which is not ideal during gaming because it may steal the game's time slices. It should only ever be used as an option of last resort, because CPUs are simply not good at emulating GPUs.

You originally wrote "set the background opacity of the window to less than 1", which I thought you meant 0 by haha, I'm guessing it was supposed to say 100.

Oh, it's because the value is a percentage, so I meant "less than 1" as in "less than 100 percent". 😅 I apologize for that.

Okay thanks for the explanation :)

Is there an issue here on Github I can track regarding this bug? I have several other programs where I can't disable hardware acceleration and they freeze too. Is it on Nvidia or Microsoft to fix?

@bptrsn commented on GitHub (Nov 29, 2024): > > Task Manager says 0 to 0.1% usage [...] > > It depends on what you're doing. If you print a lot of text, it'll be significantly higher. I have an AMD 5950X and it'll produce up to 40% load and consume >30W. If I use my GPU on the other hand, it produces <1% load and consumes <4W. Software rasterization, aka WARP, also runs across all CPU cores which is not ideal during gaming because it may steal the game's time slices. It should only ever be used as an option of last resort, because CPUs are simply not good at emulating GPUs. > > > You originally wrote "set the background opacity of the window to less than 1", which I thought you meant 0 by haha, I'm guessing it was supposed to say 100. > > Oh, it's because the value is a percentage, so I meant "less than 1" as in "less than 100 percent". 😅 I apologize for that. Okay thanks for the explanation :) Is there an issue here on Github I can track regarding this bug? I have several other programs where I can't disable hardware acceleration and they freeze too. Is it on Nvidia or Microsoft to fix?
claunia commented 2026-01-31 08:11:50 +00:00
Author
Owner
Copy Link

@Squall-Leonhart commented on GitHub (Dec 1, 2024):

This is caused by Hardware Accelerated Graphics Scheduling option combined with high gpu load, its an old issue dating back to the initial implementation of HAGS in 2020 on NVIDIA drivers.

AMD is affected in the opposite direction on the RDNA parts that support it, gaming suffers disproportionately when activity is present on the other window.

@Squall-Leonhart commented on GitHub (Dec 1, 2024): This is caused by Hardware Accelerated Graphics Scheduling option combined with high gpu load, its an old issue dating back to the initial implementation of HAGS in 2020 on NVIDIA drivers. AMD is affected in the opposite direction on the RDNA parts that support it, gaming suffers disproportionately when activity is present on the other window.
claunia commented 2026-01-31 08:11:51 +00:00
Author
Owner
Copy Link

@bptrsn commented on GitHub (Dec 1, 2024):

This is caused by Hardware Accelerated Graphics Scheduling option combined with high gpu load, its an old issue dating back to the initial implementation of HAGS in 2020 on NVIDIA drivers.

AMD is affected in the opposite direction on the RDNA parts that support it, gaming suffers disproportionately when activity is present on the other window.

For me this is a brand new issue, only happening on 24H2. Considering reverting back cus it's damn annoying :(

@bptrsn commented on GitHub (Dec 1, 2024): > This is caused by Hardware Accelerated Graphics Scheduling option combined with high gpu load, its an old issue dating back to the initial implementation of HAGS in 2020 on NVIDIA drivers. > > AMD is affected in the opposite direction on the RDNA parts that support it, gaming suffers disproportionately when activity is present on the other window. For me this is a brand new issue, only happening on 24H2. Considering reverting back cus it's damn annoying :(
claunia commented 2026-01-31 08:11:51 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Dec 3, 2024):

The good news is that the issue is not caused by Accelerated Graphics Scheduling. Whatever issue you're seeing in that regard is unrelated to this issue.

This issue is currently being addressed internally, and if everything works out, a bug fix should be released in the near term (early next year?).

@lhecker commented on GitHub (Dec 3, 2024): The good news is that the issue is not caused by Accelerated Graphics Scheduling. Whatever issue you're seeing in that regard is unrelated to this issue. This issue is currently being addressed internally, and if everything works out, a bug fix should be released in the near term (early next year?).
claunia commented 2026-01-31 08:11:51 +00:00
Author
Owner
Copy Link

@Squall-Leonhart commented on GitHub (Dec 4, 2024):

The good news is that the issue is not caused by Accelerated Graphics Scheduling. Whatever issue you're seeing in that regard is unrelated to this issue.

Lmao, yes it is.

Discord, Terminal, Steam, Web browsers, all go to crap when HAGS is on and a GPU is under heavy load.

Let it run on a iGPU via the preferred gpu settings and its all fixed.

@Squall-Leonhart commented on GitHub (Dec 4, 2024): > The good news is that the issue is not caused by Accelerated Graphics Scheduling. Whatever issue you're seeing in that regard is unrelated to this issue. Lmao, yes it is. Discord, Terminal, Steam, Web browsers, all go to crap when HAGS is on and a GPU is under heavy load. Let it run on a iGPU via the preferred gpu settings and its all fixed.
claunia commented 2026-01-31 08:11:52 +00:00
Author
Owner
Copy Link

@bptrsn commented on GitHub (Dec 4, 2024):

The good news is that the issue is not caused by Accelerated Graphics Scheduling. Whatever issue you're seeing in that regard is unrelated to this issue.

Lmao, yes it is.

Discord, Terminal, Steam, Web browsers, all go to crap when HAGS is on and a GPU is under heavy load.

Let it run on a iGPU via the preferred gpu settings and its all fixed.

I'm getting freezes by alt-tabbing, I don't need high load on my GPU, just need to alt-tab between apps like Terminal, Apple Music, some game.

@bptrsn commented on GitHub (Dec 4, 2024): > > The good news is that the issue is not caused by Accelerated Graphics Scheduling. Whatever issue you're seeing in that regard is unrelated to this issue. > > Lmao, yes it is. > > Discord, Terminal, Steam, Web browsers, all go to crap when HAGS is on and a GPU is under heavy load. > > Let it run on a iGPU via the preferred gpu settings and its all fixed. I'm getting freezes by alt-tabbing, I don't need high load on my GPU, just need to alt-tab between apps like Terminal, Apple Music, some game.
claunia commented 2026-01-31 08:11:52 +00:00
Author
Owner
Copy Link

@kemayo commented on GitHub (Dec 26, 2024):

I'll confirm that the 99% opacity fix worked for me.

@kemayo commented on GitHub (Dec 26, 2024): I'll confirm that the 99% opacity fix worked for me.
claunia commented 2026-01-31 08:11:52 +00:00
Author
Owner
Copy Link

@namarrgon commented on GitHub (Dec 29, 2024):

This happens exclusively when the terminal is on the same monitor as the gpu-demanding application. Moving the terminal to a different monitor prevents the issue. This doesn't even need to be a "game", any high gpu load results in a freeze, e.g. firefox+webgl or blender. (AMD drivers, 24.12.1)

@namarrgon commented on GitHub (Dec 29, 2024): This happens exclusively when the terminal is on the same monitor as the gpu-demanding application. Moving the terminal to a different monitor prevents the issue. This doesn't even need to be a "game", any high gpu load results in a freeze, e.g. firefox+webgl or blender. (AMD drivers, 24.12.1)
claunia commented 2026-01-31 08:11:52 +00:00
Author
Owner
Copy Link

@mxi1 commented on GitHub (Feb 9, 2025):

I got it fixed by playing around with settings in Windows Terminal. I think it was the "Use software rendering (WARP)" one under Rendering that did it. Haven't had WT freeze since.

It works for me. Thx.

@mxi1 commented on GitHub (Feb 9, 2025): > I got it fixed by playing around with settings in Windows Terminal. I think it was the "Use software rendering (WARP)" one under Rendering that did it. Haven't had WT freeze since. It works for me. Thx.
claunia commented 2026-01-31 08:11:52 +00:00
Author
Owner
Copy Link

@valdotdev commented on GitHub (Feb 17, 2025):

+1 on the opacity fix. This was driving me crazy for months and I finally noticed this was only happening when I have a game open.

@valdotdev commented on GitHub (Feb 17, 2025): +1 on the opacity fix. This was driving me crazy for months and I finally noticed this was only happening when I have a game open.
claunia commented 2026-01-31 08:11:53 +00:00
Author
Owner
Copy Link

@xbbdc commented on GitHub (May 3, 2025):

+1 on the opacity fix. This was driving me crazy for months and I finally noticed this was only happening when I have a game open.

it worked for me as well but now my cursor is missing

@xbbdc commented on GitHub (May 3, 2025): > +1 on the opacity fix. This was driving me crazy for months and I finally noticed this was only happening when I have a game open. it worked for me as well but now my cursor is missing
claunia commented 2026-01-31 08:11:53 +00:00
Author
Owner
Copy Link

@xochtil-xerxes commented on GitHub (May 7, 2025):

this has been an issue for me

@xochtil-xerxes commented on GitHub (May 7, 2025): this has been an issue for me
claunia commented 2026-01-31 08:11:53 +00:00
Author
Owner
Copy Link

@dnzrx commented on GitHub (May 16, 2025):

Image
Changing this to Direct3D 11 fixes the issue for me.
7th Gen. Ryzen iGPU + NVIDIA dedicated GPU

@dnzrx commented on GitHub (May 16, 2025): ![Image](https://github.com/user-attachments/assets/b7c43528-d5b0-49cc-870f-1acfd561effc) Changing this to **Direct3D 11** fixes the issue for me. 7th Gen. Ryzen iGPU + NVIDIA dedicated GPU
claunia commented 2026-01-31 08:11:53 +00:00
Author
Owner
Copy Link

@xbbdc commented on GitHub (May 16, 2025):

Image Changing this to Direct3D 11 fixes the issue for me. 7th Gen. Ryzen iGPU + NVIDIA dedicated GPU

thanks, i got the cursor back!

@xbbdc commented on GitHub (May 16, 2025): > ![Image](https://github.com/user-attachments/assets/b7c43528-d5b0-49cc-870f-1acfd561effc) Changing this to **Direct3D 11** fixes the issue for me. 7th Gen. Ryzen iGPU + NVIDIA dedicated GPU thanks, i got the cursor back!
claunia commented 2026-01-31 08:11:54 +00:00
Author
Owner
Copy Link

@Squall-Leonhart commented on GitHub (Jun 27, 2025):

This has been reported as MSFT-55182474 internally.

Personally, I've found that disabling this setting fixed it for me, as another possible workaround: Image

This setting is a hack to enable VRR on the few D3D11 fullscreen windowed (not flipmode) games that shipped on the MS store, it should not have been enabled as a set-and-forget, it makes sense it breaks the windows terminal, and chrome based stuff.

Edit:
It does benefit a few fullscreen window games on steam too, but the argument stands, it's a hack and its default value is OFF.

@Squall-Leonhart commented on GitHub (Jun 27, 2025): > This has been reported as [MSFT-55182474](https://task.ms/55182474) internally. > > Personally, I've found that disabling this setting fixed it for me, as another possible workaround: ![Image](https://github.com/user-attachments/assets/11dc7cee-07bc-47f6-af8f-eee74d89ddf5) This setting is a hack to enable VRR on the few D3D11 fullscreen windowed (not flipmode) games that shipped on the MS store, it should not have been enabled as a set-and-forget, it makes sense it breaks the windows terminal, and chrome based stuff. Edit: It does benefit a few fullscreen window games on steam too, but the argument stands, [it's a hack and its default value is OFF](https://devblogs.microsoft.com/directx/os-variable-refresh-rate/).
claunia commented 2026-01-31 08:11:54 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Aug 11, 2025):

FYI the fix for this issue (MSFT-55182474) was enabled by default in the 2025-06 (June) update for Windows 11. If you have that update, you can try and undo your workarounds now.

@lhecker commented on GitHub (Aug 11, 2025): FYI the fix for this issue (MSFT-55182474) was enabled by default in the 2025-06 (June) update for Windows 11. If you have that update, you can try and undo your workarounds now.
claunia commented 2026-01-31 08:11:54 +00:00
Author
Owner
Copy Link

@Akarie64 commented on GitHub (Aug 11, 2025):

Thanks for clarifying. My latest cumulative update is KB5062660. Can you confirm if this is the one with the fix?

I'm asking because the terminal freeze issue still occurs on my system as of today. Disabling VRR remains the only effective workaround for me.

@Akarie64 commented on GitHub (Aug 11, 2025): Thanks for clarifying. My latest cumulative update is KB5062660. Can you confirm if this is the one with the fix? I'm asking because the terminal freeze issue still occurs on my system as of today. Disabling VRR remains the only effective workaround for me.
claunia commented 2026-01-31 08:11:54 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Aug 11, 2025):

I think it's in KB5060829, but it's under "gradual rollout" so it may not be enabled for you yet. 1 If you're curious, the feature IDs are 55182474 and 56625728.

  1. This is where I should give a definitive statement, but I tried to figure it out and couldn't. So, I cannot tell you how far the rollout is. Those new Windows feature rollouts are just a mystery. The only thing I know is that it at least seems like it should be enabled by default. ↩︎

@lhecker commented on GitHub (Aug 11, 2025): I think it's in KB5060829, but it's under "gradual rollout" so it may not be enabled for you yet. [^1] If you're curious, the feature IDs are 55182474 and 56625728. [^1]: This is where I should give a definitive statement, but I tried to figure it out and couldn't. So, I cannot tell you how far the rollout is. Those new Windows feature rollouts are just a mystery. The only thing I know is that it at least _seems_ like it should be enabled by default.
claunia commented 2026-01-31 08:11:54 +00:00
Author
Owner
Copy Link

@Squall-Leonhart commented on GitHub (Aug 12, 2025):

The only guarantee for the fix is being on 26200 right now, but that means opting into the dev channel.

@Squall-Leonhart commented on GitHub (Aug 12, 2025): The only guarantee for the fix is being on 26200 right now, but that means opting into the dev channel.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Rendering Issue-Bug Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22387
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?