Running WT portable as a different user on W11 24H2 completely freezes initiating users logon session #22457

@PGomersall commented on GitHub (Oct 23, 2024):

I can confirm that this seems to explicitly be related to run as a different user when smartcard is required for logon to the different user account.
Starting WT with run as a different user where account is normal logon (not smartcard) works.

@PGomersall commented on GitHub (Oct 23, 2024): I can confirm that this seems to explicitly be related to run as a different user when smartcard is required for logon to the different user account. Starting WT with run as a different user where account is normal logon (not smartcard) works.

claunia commented

@PGomersall commented on GitHub (Oct 24, 2024):

Also I can replicate the exact issue on Windows Server 2025 26100 with last stable cumulative patch.

@PGomersall commented on GitHub (Oct 24, 2024): Also I can replicate the exact issue on Windows Server 2025 26100 with last stable cumulative patch.

claunia commented

@carlos-zamora commented on GitHub (Oct 30, 2024):

Thanks for filing. There's a possibility this is some weird XAML deadlock. We'll look into it further.

@carlos-zamora commented on GitHub (Oct 30, 2024): Thanks for filing. There's a possibility this is some weird XAML deadlock. We'll look into it further.

claunia commented

@PGomersall commented on GitHub (Oct 30, 2024):

Carlos,
Thanks for the update. Not really sure how to troubleshoot further as the whole initiating session just freezes. It is consistent on multiple different computers (all physical that we saw issues on) and different users, but all running W11 24H2 or WS 2025.
Let me know if I can provide anything else to help.
Pete

Pete Gomersall

@PGomersall commented on GitHub (Oct 30, 2024): Carlos, Thanks for the update. Not really sure how to troubleshoot further as the whole initiating session just freezes. It is consistent on multiple different computers (all physical that we saw issues on) and different users, but all running W11 24H2 or WS 2025. Let me know if I can provide anything else to help. Pete Pete Gomersall

claunia commented

@aermak commented on GitHub (Oct 31, 2024):

I get it when running the local installed version after elevating it as admin after a while. Mouse moves slowly, can't click on anything, CTRL+Shift+Esc doesn't bring up task manager so i have to hard reboot every time to get it going again.

@aermak commented on GitHub (Oct 31, 2024): I get it when running the local installed version after elevating it as admin after a while. Mouse moves slowly, can't click on anything, CTRL+Shift+Esc doesn't bring up task manager so i have to hard reboot every time to get it going again.

claunia commented

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

It happens on every domain joined computer using 24H2 in my organisation.

If you run Terminal as an admin or other user, any next prompt for elevating privalages will not show resulting in frozen screen and moving cursor. You can't click anything, no keypress works.

Only hard reboot.

@Flapu7 commented on GitHub (Nov 22, 2024): It happens on every domain joined computer using 24H2 in my organisation. If you run Terminal as an admin or other user, any next prompt for elevating privalages will not show resulting in frozen screen and moving cursor. You can't click anything, no keypress works. Only hard reboot.

claunia commented

@navanshu commented on GitHub (Nov 23, 2024):

Facing the same issue here, I run elevated terminal app from a standard user account, after a minute only the mouse moves and nothing responds,

@navanshu commented on GitHub (Nov 23, 2024): Facing the same issue here, I run elevated terminal app from a standard user account, after a minute only the mouse moves and nothing responds,

claunia commented

@carlos-zamora commented on GitHub (Dec 4, 2024):

Does enabling this setting fix this? You can find it in the settings UI under the Rendering page.

@carlos-zamora commented on GitHub (Dec 4, 2024): Does enabling this setting fix this? You can find it in the settings UI under the Rendering page. ![Use software rendering (WARP)](https://github.com/user-attachments/assets/2e9dfd1c-f22e-4e50-b44e-a1c80aceacf3)

claunia commented

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

Does enabling this setting fix this? You can find it in the settings UI under the Rendering page.

@carlos-zamora I will test on affected systems when I am physically present, not over RDP and get back to this thread.

@PGomersall commented on GitHub (Dec 4, 2024): > Does enabling this setting fix this? You can find it in the settings UI under the Rendering page. > > ![Use software rendering (WARP)](https://github.com/user-attachments/assets/2e9dfd1c-f22e-4e50-b44e-a1c80aceacf3) @carlos-zamora I will test on affected systems when I am physically present, not over RDP and get back to this thread.

claunia commented

@Flapu7 commented on GitHub (Dec 5, 2024):

@carlos-zamora Nope. The setting didn't help

@Flapu7 commented on GitHub (Dec 5, 2024): @carlos-zamora Nope. The setting didn't help

claunia commented

@PGomersall commented on GitHub (Dec 6, 2024):

Does enabling this setting fix this? You can find it in the settings UI under the Rendering page.

@carlos-zamora Carlos, I can also confirm that this setting DOES NOT fix the issue.

@PGomersall commented on GitHub (Dec 6, 2024): > Does enabling this setting fix this? You can find it in the settings UI under the Rendering page. > > ![Use software rendering (WARP)](https://github.com/user-attachments/assets/2e9dfd1c-f22e-4e50-b44e-a1c80aceacf3) @carlos-zamora Carlos, I can also confirm that this setting DOES NOT fix the issue.

claunia commented

@Flapu7 commented on GitHub (Dec 17, 2024):

I think the problem with "invisible prompt" happens with "User Account Control: Switch to the secure desktop when prompting for elevation setting" GPO setting enabled.

@Flapu7 commented on GitHub (Dec 17, 2024): I think the problem with "invisible prompt" happens with "User Account Control: Switch to the secure desktop when prompting for elevation setting" GPO setting enabled.

claunia commented

@syst3m4 commented on GitHub (Dec 18, 2024):

I think the problem with "invisible prompt" happens with "User Account Control: Switch to the secure desktop when prompting for elevation setting" GPO setting enabled.

This setting is enabled by default. Does setting it to Disabled stop the issue occurring?

@syst3m4 commented on GitHub (Dec 18, 2024): > I think the problem with "invisible prompt" happens with "User Account Control: Switch to the secure desktop when prompting for elevation setting" GPO setting enabled. This setting is enabled by default. Does setting it to Disabled stop the issue occurring?

claunia commented

@PGomersall commented on GitHub (Dec 18, 2024):

This setting is enabled by default. Does setting it to Disabled stop the issue occurring?

So, I do not think this is an acceptable approach even if it worked; we should not be disabling security to fix an issue with Terminal. In my testing doing this (disabling secure desktop) did not fix the issue. Terminal works fine in 23H2, just not in 24H2. The problem needs to be investigated by those working on the project; it then needs fixing.
Given that Terminal is a key tool of most system administrators that regularly need to elevate or run as a different user this is a major issue that needs to be resolved.

@PGomersall commented on GitHub (Dec 18, 2024): > This setting is enabled by default. Does setting it to Disabled stop the issue occurring? So, I do not think this is an acceptable approach even if it worked; we should not be disabling security to fix an issue with Terminal. In my testing doing this (disabling secure desktop) did not fix the issue. Terminal works fine in 23H2, just not in 24H2. The problem needs to be investigated by those working on the project; it then needs fixing. Given that Terminal is a key tool of most system administrators that regularly need to elevate or run as a different user this is a major issue that needs to be resolved.

claunia commented

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

fwiw I think everyone agrees that disabling UAC is a terrible solution to a problem

(it's also the holidays and most all the team is out for the year)

@zadjii-msft commented on GitHub (Dec 18, 2024): fwiw I think everyone agrees that disabling UAC is a terrible solution to a problem (it's also the holidays and most all the team is out for the year)

claunia commented

@fsaccomandi-anza commented on GitHub (Jan 6, 2025):

I am experiencing this issue as well. If I have a windows terminal running as an admin (elevated session) and then I try to lock my screen, the screens will turn black and I will only see a mouse cursor. Control-alt-delete, etc fail to respond. The behavior is exactly identical to that described in https://github.com/microsoft/terminal/issues/18224 however it looks like that issue was marked as a duplicate of this issue. I am running windows 11 24H2 and I did not observe this behavior on 23H2.

@fsaccomandi-anza commented on GitHub (Jan 6, 2025): I am experiencing this issue as well. If I have a windows terminal running as an admin (elevated session) and then I try to lock my screen, the screens will turn black and I will only see a mouse cursor. Control-alt-delete, etc fail to respond. The behavior is exactly identical to that described in https://github.com/microsoft/terminal/issues/18224 however it looks like that issue was marked as a duplicate of this issue. I am running windows 11 24H2 and I did not observe this behavior on 23H2.

claunia commented

@PGomersall commented on GitHub (Feb 3, 2025):

@cruzian80 you said:
"Experienced the same issue when running terminal as admin after providing credentials. After changing Terminal host app to "Windows Console Host" from 'Windows Terminal" in 'Settings > System > For developers', I no longer experienced this.
Version 24H2 (OS Build 26100.2605)
Terminal Version: 1.21.3231.0"

These settings have always been set for me and have no effect on the outcome.
I can always induce the session locking and becoming un-usable up by doing the following:

Start Terminal as another user.
Open an application that requires elevation – at this point system locks up.

Pete Gomersall

@PGomersall commented on GitHub (Feb 3, 2025): @cruzian80 you said: "Experienced the same issue when running terminal as admin after providing credentials. After changing Terminal host app to "Windows Console Host" from 'Windows Terminal" in 'Settings > System > For developers', I no longer experienced this. Version 24H2 (OS Build 26100.2605) Terminal Version: 1.21.3231.0" These settings have always been set for me and have no effect on the outcome. I can always induce the session locking and becoming un-usable up by doing the following: 1) Start Terminal as another user. 2) Open an application that requires elevation – at this point system locks up. Pete Gomersall

claunia commented

@dperez83 commented on GitHub (Feb 3, 2025):

Same thing as #18428 and as described here https://answers.microsoft.com/en-us/windowsclient/forum/all/issues-with-24h2-and-uac-prompts-and-screen-lock/5df375ae-4a6a-474f-baa8-107881a2e15f

Have shutdown the computer by holding the power button is the only solution after freezing. How can an application do this? Seems an OS bug.

@dperez83 commented on GitHub (Feb 3, 2025): Same thing as #18428 and as described here https://answers.microsoft.com/en-us/windowsclient/forum/all/issues-with-24h2-and-uac-prompts-and-screen-lock/5df375ae-4a6a-474f-baa8-107881a2e15f Have shutdown the computer by holding the power button is the only solution after freezing. How can an application do this? Seems an OS bug.

claunia commented

@marcopixel commented on GitHub (Feb 12, 2025):

Similar problem for me, also locking up the whole computer...

I've reported my issue to #18428 as i'm not running on a portable instance but the issue is pretty much identical with the steps provided here.

@marcopixel commented on GitHub (Feb 12, 2025): Similar problem for me, also locking up the whole computer... I've reported my issue to #18428 as i'm not running on a portable instance but the issue is pretty much identical with the steps provided here.

claunia commented

@rickardsavrothFEV commented on GitHub (Feb 27, 2025):

Not running portable but I've a simular problem, if I start Terminal as another user and locks the computer the computer hangs with a cursor and a black screen. I can move the cursor but that's all. Need to hold the power button to restart.

Windows 11 24H2

Windows-terminal
Version: 1.21.10351.0

@rickardsavrothFEV commented on GitHub (Feb 27, 2025): Not running portable but I've a simular problem, if I start Terminal as another user and locks the computer the computer hangs with a cursor and a black screen. I can move the cursor but that's all. Need to hold the power button to restart. Windows 11 24H2 Windows-terminal Version: 1.21.10351.0

claunia commented

@navanshu commented on GitHub (Mar 3, 2025):

Any update on this bug fix?

@navanshu commented on GitHub (Mar 3, 2025): Any update on this bug fix?

claunia commented

@DHowett commented on GitHub (Mar 13, 2025):

I've looped in the right folks. Sorry to let this devastating bug go on for so long, but it appears to be squarely outside of our code and somewhere in user32.

@DHowett commented on GitHub (Mar 13, 2025): I've looped in the right folks. Sorry to let this devastating bug go on for so long, but it appears to be squarely outside of our code and somewhere in user32.

claunia commented

@PGomersall commented on GitHub (Mar 17, 2025):

For all who have this specific issue with session lock ups when running as different user and using portable versions.
I have been told by MS that they believe they have isolated the issue causing this and have suggested a work around.
This involves making sure that the Personalization Accent Color settings are set to exactly the same for all users i.e. the user initiating the use, and the one running under "run as a different user". This requires logging on interactively as all users that may be called by the run as process and setting those Personalization Colors to make them identical. I tested setting Accent color to Manual and color to "Storm".
I have tested this on a number of different W11 24H2 and Server 2025 systems and verified that I have not had the problem I initially described in this issue ticket.
It may also apply\improve running other tools that require elevation that are called via run as that raise a UAC prompt and see sessions lock ups.
Note that it seems to fix the issue for both Stable and Preview portables but seems to cause other negative issues with Preview portable so I would not recommend that version.

@PGomersall commented on GitHub (Mar 17, 2025): For all who have this specific issue with session lock ups when running as different user and using portable versions. I have been told by MS that they believe they have isolated the issue causing this and have suggested a work around. This involves making sure that the Personalization Accent Color settings are set to exactly the same for all users i.e. the user initiating the use, and the one running under "run as a different user". This requires logging on interactively as all users that may be called by the run as process and setting those Personalization Colors to make them identical. I tested setting Accent color to Manual and color to "Storm". I have tested this on a number of different W11 24H2 and Server 2025 systems and verified that I have not had the problem I initially described in this issue ticket. It may also apply\improve running other tools that require elevation that are called via run as that raise a UAC prompt and see sessions lock ups. Note that it seems to fix the issue for both Stable and Preview portables but seems to cause other negative issues with Preview portable so I would not recommend that version.

claunia commented

2026-01-31 08:13:49 +00:00

@Flapu7 commented on GitHub (Mar 24, 2025):

@PGomersall Unfortunately your workaround doesn't work for me. I've set up the same accent color on all users and PC still hangs on UAC prompt when elevated Terminal is running.

@Flapu7 commented on GitHub (Mar 24, 2025): @PGomersall Unfortunately your workaround doesn't work for me. I've set up the same accent color on all users and PC still hangs on UAC prompt when elevated Terminal is running.

claunia commented

@PGomersall commented on GitHub (Mar 24, 2025):

@Flapu7 - more work for MS where elevation is required.
In my test cases I have not been running Terminal elevated, just as a different user. I have opened other applications (e.g. ADUC) while multiple Terminal windows are running though where UAC is prompted, and these have not caused the issues for me that I previously had.

@PGomersall commented on GitHub (Mar 24, 2025): @Flapu7 - more work for MS where elevation is required. In my test cases I have not been running Terminal elevated, just as a different user. I have opened other applications (e.g. ADUC) while multiple Terminal windows are running though where UAC is prompted, and these have not caused the issues for me that I previously had.

claunia commented

2026-01-31 08:13:49 +00:00

@shenlong commented on GitHub (Mar 26, 2025):

Same issue highlighted here:
https://answers.microsoft.com/en-us/windows/forum/all/black-screen-with-only-cursor-upon-lock-with/cbb260ea-8aee-4f61-a9c2-50a74d23dcb2

It is frustrating for us developers when the Windows Update causes this issue.
Any workaround?

@shenlong commented on GitHub (Mar 26, 2025): Same issue highlighted here: https://answers.microsoft.com/en-us/windows/forum/all/black-screen-with-only-cursor-upon-lock-with/cbb260ea-8aee-4f61-a9c2-50a74d23dcb2 It is frustrating for us developers when the Windows Update causes this issue. Any workaround?

claunia commented

2026-01-31 08:13:49 +00:00

@DHowett commented on GitHub (Mar 26, 2025):

Any workaround?

I would encourage you to read the recent posts in this thread. Reading the highly-discussed thread reporting the same issue you found is the only way to determine whether there is a workaround for such issue.

@DHowett commented on GitHub (Mar 26, 2025): > Any workaround? I would encourage you to read the recent posts in this thread. Reading the highly-discussed thread reporting the same issue you found is the only way to determine whether there is a workaround for such issue.

claunia commented

@achobanov commented on GitHub (Mar 31, 2025):

Having same elevation issue as @Flapu7 - UAC prompts work fine until I start an elevated Terminal.

For additional context, I read somewhere that issue could be related to Windows Spotlight and want to confirm I'm using a static image, not spotlight. Additionally a similar thing happened when I tried to switch desktop to static color instead of image - mouse slowed down, fan started zooming and PC went unresponseive. Once I restarted the desktop was changed to static image

@achobanov commented on GitHub (Mar 31, 2025): Having same elevation issue as @Flapu7 - UAC prompts work fine until I start an elevated Terminal. For additional context, I read somewhere that issue could be related to Windows Spotlight and want to confirm I'm using a static image, not spotlight. Additionally a similar thing happened when I tried to switch desktop to static color instead of image - mouse slowed down, fan started zooming and PC went unresponseive. Once I restarted the desktop was changed to static image

claunia commented

@sktea1 commented on GitHub (Mar 31, 2025):

I run Windows 11 Enterprise and Windows Terminal (MSI install) current version; I routinely run an elevated instance of Windows Terminal under the context of a different AD username.

I recently received the 24H2 upgrade and began experiencing this issue; I was able to reproduce it reliably.

Today I found this thread, logged into Windows under each account, disabled transparency and set the same manually-selected accent color under each account; now I seem unable to reproduce the issue (so far).

@sktea1 commented on GitHub (Mar 31, 2025): I run Windows 11 Enterprise and Windows Terminal (MSI install) current version; I routinely run an elevated instance of Windows Terminal under the context of a different AD username. I recently received the 24H2 upgrade and began experiencing this issue; I was able to reproduce it reliably. Today I found this thread, logged into Windows under each account, disabled transparency and set the same manually-selected accent color under each account; now I seem unable to reproduce the issue (so far).

claunia commented

@brwilkinson commented on GitHub (Apr 3, 2025):

I was able to get control back by killing 'WindowsTerminal' remotely. Repro'd everytime, which is how I found this article.

enter-pssession mywin11machine
> stop-process WindowsTerminal

Then i got the lock screen back on the impacted host.

@brwilkinson commented on GitHub (Apr 3, 2025): I was able to get control back by killing 'WindowsTerminal' remotely. Repro'd everytime, which is how I found this article. ```powershell enter-pssession mywin11machine > stop-process WindowsTerminal ``` Then i got the lock screen back on the impacted host.

claunia commented

@timothy-gill commented on GitHub (Apr 23, 2025):

Just wanted to add here that we have done quite a bit of testing in our organization and have narrowed it down (like a few users explicitly state here) that the issue is reproduced by:

Open Terminal as ANOTHER user (different than the one logged into the PC)
Lock screen

We are NOT able to reproduce the problem when opening Terminal in Admin mode with the SAME user. Admin mode seems to NOT be relevant to the issue, at least from our testing.

@timothy-gill commented on GitHub (Apr 23, 2025): Just wanted to add here that we have done quite a bit of testing in our organization and have narrowed it down (like a few users explicitly state here) that the issue is reproduced by: 1. Open Terminal as ANOTHER user (different than the one logged into the PC) 2. Lock screen We are NOT able to reproduce the problem when opening Terminal in Admin mode with the SAME user. Admin mode seems to NOT be relevant to the issue, at least from our testing.

claunia commented

@sktea1 commented on GitHub (Apr 23, 2025):

Excellent clarification timothy-gill; my previous comment was not clear. For clarity: I login with a username which lacks local admin permissions and, when necessary, I run an elevated Windows Terminal using a distinct username with extra permissions.

@sktea1 commented on GitHub (Apr 23, 2025): Excellent clarification timothy-gill; my previous comment was not clear. For clarity: I login with a username which lacks local admin permissions and, when necessary, I run an elevated Windows Terminal using a distinct username with extra permissions.

claunia commented

@timothy-gill commented on GitHub (Apr 23, 2025):

For folks like @sktea1 and @PGomersall who have implemented the color-based workaround, is it possible you could give explicit step-by-steps for the workaround? I set a Color Scheme to match exactly between my regular and admin accounts, but still reproduce the issue when locking the screen. You both mention "accent color" but I didn't see those exact words anywhere in the Terminal settings panel. Any help would be greatly appreciated, since this issue has forced me to reboot in the 10's of times now and...frankly...is pushing me over the sanity edge at this point.

@timothy-gill commented on GitHub (Apr 23, 2025): For folks like @sktea1 and @PGomersall who have implemented the color-based workaround, is it possible you could give explicit step-by-steps for the workaround? I set a Color Scheme to match exactly between my regular and admin accounts, but still reproduce the issue when locking the screen. You both mention "accent color" but I didn't see those exact words anywhere in the Terminal settings panel. Any help would be greatly appreciated, since this issue has forced me to reboot in the 10's of times now and...frankly...is pushing me over the sanity edge at this point.

claunia commented

@jezuk commented on GitHub (Apr 24, 2025):

Here's how to find it:

Setting both accounts to the same manual accent colour has resolved the lockup for me.

I've also since tried changing them to different colours and can no longer reproduce the issue.

@jezuk commented on GitHub (Apr 24, 2025): Here's how to find it: ![Image](https://github.com/user-attachments/assets/19fb7a05-20af-4947-a13d-d21940ba32a3) ![Image](https://github.com/user-attachments/assets/9ba0dd98-7f7f-4daf-9ee4-6e74d1c53b30) Setting both accounts to the same manual accent colour has resolved the lockup for me. I've also since tried changing them to different colours and can no longer reproduce the issue.

claunia commented

2026-01-31 08:13:53 +00:00

@dannlozt commented on GitHub (Apr 24, 2025):

Here's how to find it:

Setting both accounts to the same manual accent colour has resolved the lockup for me.

I've also since tried changing them to different colours and can no longer reproduce the issue.

Sadly this workaround has not worked for me.

@dannlozt commented on GitHub (Apr 24, 2025): > Here's how to find it: > > ![Image](https://github.com/user-attachments/assets/19fb7a05-20af-4947-a13d-d21940ba32a3) > > ![Image](https://github.com/user-attachments/assets/9ba0dd98-7f7f-4daf-9ee4-6e74d1c53b30) > > Setting both accounts to the same manual accent colour has resolved the lockup for me. > > I've also since tried changing them to different colours and can no longer reproduce the issue. Sadly this workaround has not worked for me.

claunia commented

@PGomersall commented on GitHub (Apr 24, 2025):

All,
"accent color" is in a user's Settings app under personalization > color. It is not anything in Terminal's settings.
Logon as both users, the normal; user and the admin user. In the settings app > Personalization > Color - set it to "Manual" and choose a specific color - I used the one name "Storm". Set this to exactly the same in both accounts.
Pete

Pete Gomersall
Systems Administrator, Lead
Academic Computing - Datacenter Computing, Information Technology Services
MCSA, MCSE, MCDBA & MCT

@PGomersall commented on GitHub (Apr 24, 2025): All, "accent color" is in a user's Settings app under personalization > color. It is not anything in Terminal's settings. Logon as both users, the normal; user and the admin user. In the settings app > Personalization > Color - set it to "Manual" and choose a specific color - I used the one name "Storm". Set this to exactly the same in both accounts. Pete Pete Gomersall Systems Administrator, Lead Academic Computing - Datacenter Computing, Information Technology Services MCSA, MCSE, MCDBA & MCT

claunia commented

2026-01-31 08:13:53 +00:00

@timothy-gill commented on GitHub (Apr 24, 2025):

Thank you all for so many quick responses! This worked for me, and I can feel my sanity slowly returning. Here's a set of steps for copy-pasting if anyone needs it for user support in the future:

Workaround steps:

Log in to your PC using your regular Windows account
Click Start button, then type "accent"
In the results that appear, click "Choose your accent color"
The "Personalization > Colors" panel will open
Click the "Accent Color" section to expand it
Click the "Accent Color" dropdown to change the value from "Automatic" to "Manual"
Select a color, and remember its name (hover over the color square to see the name)
Log out
Repeat all steps using your other account (usually Administrator-level), ensuring you select the exact same color for step 7

@timothy-gill commented on GitHub (Apr 24, 2025): Thank you all for so many quick responses! This worked for me, and I can feel my sanity slowly returning. Here's a set of steps for copy-pasting if anyone needs it for user support in the future: Workaround steps: 1. Log in to your PC using your regular Windows account 2. Click Start button, then type "accent" 3. In the results that appear, click "Choose your accent color" 4. The "Personalization > Colors" panel will open 5. Click the "Accent Color" section to expand it 6. Click the "Accent Color" dropdown to change the value from "Automatic" to "Manual" 7. Select a color, and remember its name (hover over the color square to see the name) 8. Log out 9. Repeat all steps using your other account (usually Administrator-level), ensuring you select the exact same color for step 7

claunia commented

2026-01-31 08:13:53 +00:00

@timothy-gill commented on GitHub (Apr 24, 2025):

I also wanted to note that I tried to keep the workaround as minimal as possible, so I did NOT set Transparency to off, as folks had previously mentioned. Here is a screenshot of my Personalization > Colors panel for reference:

@timothy-gill commented on GitHub (Apr 24, 2025): I also wanted to note that I tried to keep the workaround as minimal as possible, so I did NOT set Transparency to off, as folks had previously mentioned. Here is a screenshot of my Personalization > Colors panel for reference: ![Image](https://github.com/user-attachments/assets/5a56e7ae-eb9d-4843-a6d8-a5a876030033)

claunia commented

@sktea1 commented on GitHub (Apr 24, 2025):

You captured it exactly @timothy-gill. Cheers to sanity! 🍻

@sktea1 commented on GitHub (Apr 24, 2025): You captured it exactly @timothy-gill. Cheers to sanity! :beers:

claunia commented

@syst3m4 commented on GitHub (Apr 27, 2025):

seeing copilot get added to notepad (RIP) while this remains an issue 6 months later 😐

@syst3m4 commented on GitHub (Apr 27, 2025): seeing copilot get added to notepad (RIP) while this remains an issue 6 months later 😐

claunia commented

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

seeing copilot get added to notepad (RIP) while this remains an issue 6 months later 😐

I don't oversee the Notepad team, or the team who owns uxtheme (which is at the root cause of this issue). I'm sorry that we are a company of many more engineers than you may have known.

@DHowett commented on GitHub (Apr 27, 2025): > seeing copilot get added to notepad (RIP) while this remains an issue 6 months later 😐 I don't oversee the Notepad team, or the team who owns uxtheme (which is at the root cause of this issue). I'm sorry that we are a company of many more engineers than you may have known.

claunia commented

2026-01-31 08:13:55 +00:00

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

To be clear: this issue tracker is not the place to air your grievances with Microsoft that do not also pertain to Windows Terminal or the console subsystem. I will remove any further commentary airing such grievances.

@DHowett commented on GitHub (Apr 27, 2025): **To be clear**: this issue tracker is not the place to air your grievances with Microsoft that do not also pertain to Windows Terminal or the console subsystem. I will remove any further commentary airing such grievances.

claunia commented

@rpremuz commented on GitHub (May 15, 2025):

I set color settings in both user accounts as shown below but still have freezing:

Windows 11 Pro. 24H2, Windows Terminal ver. 1.22.11141.0.

It seems I'll have to run cmd.exe and PowerShell as admin directly.

@rpremuz commented on GitHub (May 15, 2025): I set color settings in both user accounts as shown below but still have freezing: ![Image](https://github.com/user-attachments/assets/b820d164-4724-4f3a-938c-0521c61f3905) Windows 11 Pro. 24H2, Windows Terminal ver. 1.22.11141.0. It seems I'll have to run cmd.exe and PowerShell as admin directly.

claunia commented

2026-01-31 08:13:55 +00:00

@timothy-gill commented on GitHub (May 15, 2025):

I set color settings in both user accounts as shown below but still have freezing:

Windows 11 Pro. 24H2, Windows Terminal ver. 1.22.11141.0.

It seems I'll have to run cmd.exe and PowerShell as admin directly.

I'm sorry to hear that. Total longshot, but you might try a different color, since that blue color may be the default color used by Windows. Don't know why that would matter, but...

My versioning: Windows 11 Enterprise 23H2, Windows Terminal ver. 1.22.11141.0

@timothy-gill commented on GitHub (May 15, 2025): > I set color settings in both user accounts as shown below but still have freezing: > > Windows 11 Pro. 24H2, Windows Terminal ver. 1.22.11141.0. > > It seems I'll have to run cmd.exe and PowerShell as admin directly. I'm sorry to hear that. Total longshot, but you might try a different color, since that blue color may be the default color used by Windows. Don't know why that would matter, but... My versioning: Windows 11 Enterprise 23H2, Windows Terminal ver. 1.22.11141.0

claunia commented

2026-01-31 08:13:55 +00:00

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

Well, I changed the accent color and the freezing does not occur any more. Go figure!

@rpremuz commented on GitHub (May 16, 2025): Well, I changed the accent color and the freezing does not occur any more. Go figure!

claunia commented

@brian975 commented on GitHub (Jun 5, 2025):

Same issue here. Symptoms are exactly as the OP listed.
Domain joined
24H2 fully updated as of this post. Also happened with 23H2.
Defender for AV
Dual GPU (Intel Iris Xe (Core i7-1370P) and Nvidia MX550)
Terminal is v1.22.11141.0
If I set UAC to not dim, the issue goes away. However, GPO sets it back to dimming, causing the issue to occur again.

@brian975 commented on GitHub (Jun 5, 2025): Same issue here. Symptoms are exactly as the OP listed. Domain joined 24H2 fully updated as of this post. Also happened with 23H2. Defender for AV Dual GPU (Intel Iris Xe (Core i7-1370P) and Nvidia MX550) Terminal is v1.22.11141.0 If I set UAC to not dim, the issue goes away. However, GPO sets it back to dimming, causing the issue to occur again.

claunia commented

@timothy-gill commented on GitHub (Jun 5, 2025):

Same issue here. Symptoms are exactly as the OP listed. Domain joined 24H2 fully updated as of this post. Also happened with 23H2. Defender for AV Dual GPU (Intel Iris Xe (Core i7-1370P) and Nvidia MX550) Terminal is v1.22.11141.0 If I set UAC to not dim, the issue goes away. However, GPO sets it back to dimming, causing the issue to occur again.

Have you tried the accent color workaround? Since I made the change to the accent colors for each account involved, I have not experienced the black screen even once.

@timothy-gill commented on GitHub (Jun 5, 2025): > Same issue here. Symptoms are exactly as the OP listed. Domain joined 24H2 fully updated as of this post. Also happened with 23H2. Defender for AV Dual GPU (Intel Iris Xe (Core i7-1370P) and Nvidia MX550) Terminal is v1.22.11141.0 If I set UAC to not dim, the issue goes away. However, GPO sets it back to dimming, causing the issue to occur again. Have you tried the accent color workaround? Since I made the change to the accent colors for each account involved, I have not experienced the black screen even once.

claunia commented

@stojack commented on GitHub (Jun 21, 2025):

Also getting the issue where opened Terminal as administrator (using different credentials), everything works fine until the machine goes to sleep. On-wake, nothing but a black screen and the cursor. Win+ctrl+shift+B refreshes the cursor but ultimately achieves nothing. Only way out is to completely shut down the machine via the physical power button.

Thanks to the steps above, I set the accent colour to be the same for the main account and the administrator account and I since haven't been able to replicate the issue.

WT Version: 1.22.11141.0
Windows 11 24H2 - Domain Joined

@stojack commented on GitHub (Jun 21, 2025): Also getting the issue where opened Terminal as administrator (using different credentials), everything works fine until the machine goes to sleep. On-wake, nothing but a black screen and the cursor. Win+ctrl+shift+B refreshes the cursor but ultimately achieves nothing. Only way out is to completely shut down the machine via the physical power button. Thanks to the steps above, I set the accent colour to be the same for the main account and the administrator account and I since haven't been able to replicate the issue. WT Version: 1.22.11141.0 Windows 11 24H2 - Domain Joined

claunia commented