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

Dimmed UAC-prompt in Windows freezes it when logged in Windows terminal with user other than the one logged in #22764

New Issue
Closed
opened 2026-01-31 08:22:48 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 08:22:48 +00:00
Owner
Copy Link

Originally created by @mabo003 on GitHub (Jan 15, 2025).

Windows Terminal version

1.21.3231.0

Windows build number

10.0.26100.0

Other Software

UAC-prompt that dims Windows causes this issue that freezes the entire OS.

Steps to reproduce

  1. Start Windows Terminal either as Administrator (if the logged in user account does not have admin privileges) or as other user and use an account other than the one logged in.
  2. Perform any action that triggers a UAC-promt in Windows. The setting needs to be set so it dims Windows.

Expected Behavior

UAC-prompt should appear as normal when Windows Terminal is started with a different account than the one logged in Windows.

Actual Behavior

Windows freezes when a UAC-prompt pops up for any reason, even when not concerning Windows Terminal. This happens when Windows Terminal is started with a different user than the one logged in Windows. This is recreated with a user that has admin privileges and unsure if this happens with accounts without admin privileges. When doing anything that triggers a UAC-prompt where it dims Windows it freezes it completely. The screen dims, but no UAC-prompt is displayed. You can CTRL+ALT+DEL back to Windows, but all windows and taskbar is almost non-responsive. You can control the cursor, but it seem to not register any clicks and nothing from the keyboard as well. The CPU works extra hard as it’s fan speeds up to max and there is a considerably delay when clicking on different windows like the are responding, but heavily delayed so Windows is not usable.

The only way to resolve the issue is to turn off the computer on the power button.

Cannot find any issue within the Event viewer. This issue has been reproduced on two different laptops with multiple reinstalls of Windows.

Originally created by @mabo003 on GitHub (Jan 15, 2025). ### Windows Terminal version 1.21.3231.0 ### Windows build number 10.0.26100.0 ### Other Software UAC-prompt that dims Windows causes this issue that freezes the entire OS. ### Steps to reproduce 1. Start Windows Terminal either as Administrator (if the logged in user account does not have admin privileges) or as other user and use an account other than the one logged in. 2. Perform any action that triggers a UAC-promt in Windows. The setting needs to be set so it dims Windows. ### Expected Behavior UAC-prompt should appear as normal when Windows Terminal is started with a different account than the one logged in Windows. ### Actual Behavior Windows freezes when a UAC-prompt pops up for any reason, even when not concerning Windows Terminal. This happens when Windows Terminal is started with a different user than the one logged in Windows. This is recreated with a user that has admin privileges and unsure if this happens with accounts without admin privileges. When doing anything that triggers a UAC-prompt where it dims Windows it freezes it completely. The screen dims, but no UAC-prompt is displayed. You can CTRL+ALT+DEL back to Windows, but all windows and taskbar is almost non-responsive. You can control the cursor, but it seem to not register any clicks and nothing from the keyboard as well. The CPU works extra hard as it’s fan speeds up to max and there is a considerably delay when clicking on different windows like the are responding, but heavily delayed so Windows is not usable. The only way to resolve the issue is to turn off the computer on the power button. Cannot find any issue within the Event viewer. This issue has been reproduced on two different laptops with multiple reinstalls of Windows.
claunia added the Needs-TriageIssue-BugNeeds-Author-Feedback labels 2026-01-31 08:22:48 +00:00
claunia commented 2026-01-31 08:22:49 +00:00
Author
Owner
Copy Link

@jezuk commented on GitHub (Jan 15, 2025):

Also experiencing this issue, found via: https://answers.microsoft.com/en-us/windowsclient/forum/all/issues-with-24h2-and-uac-prompts-and-screen-lock/5df375ae-4a6a-474f-baa8-107881a2e15f?page=1, also see page 2

The v1.21.2701.0 release mentions this issue is affecting 23H2 and and a fix is coming via Windows update.

I'm running 24H2 and have just installed the January Windows updates and the issue is still present.

@jezuk commented on GitHub (Jan 15, 2025): Also experiencing this issue, found via: https://answers.microsoft.com/en-us/windowsclient/forum/all/issues-with-24h2-and-uac-prompts-and-screen-lock/5df375ae-4a6a-474f-baa8-107881a2e15f?page=1, also see page 2 The [v1.21.2701.0 release](https://github.com/microsoft/terminal/releases/tag/v1.21.2701.0) mentions this issue is affecting 23H2 and and a fix is coming via Windows update. I'm running 24H2 and have just installed the January Windows updates and the issue is still present.
claunia commented 2026-01-31 08:22:50 +00:00
Author
Owner
Copy Link

@lecram89 commented on GitHub (Jan 19, 2025):

I'm also experiencing the same issue. My system is up-to-date.

@lecram89 commented on GitHub (Jan 19, 2025): I'm also experiencing the same issue. My system is up-to-date.
claunia commented 2026-01-31 08:22:50 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jan 22, 2025):

Thanks for filing! Can you collect a full system performance trace of the issue /? You can use UIforETW. If you need help with using it, let us know. Happy to help 😊

@carlos-zamora commented on GitHub (Jan 22, 2025): Thanks for filing! Can you collect a full system performance trace of the issue /? You can use [UIforETW](https://github.com/google/UIforETW/releases). If you need help with using it, let us know. Happy to help 😊
claunia commented 2026-01-31 08:22:50 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jan 22, 2025):

Potentially related: #18105

@carlos-zamora commented on GitHub (Jan 22, 2025): Potentially related: #18105
claunia commented 2026-01-31 08:22:50 +00:00
Author
Owner
Copy Link

@jezuk commented on GitHub (Jan 23, 2025):

Hi @carlos-zamora, happy to collect a trace. Please let me know the instructions. Given the nature of the issue we may not be able to gracefully stop the trace when the system stops accepting input. Perhaps a scheduled reboot?

@jezuk commented on GitHub (Jan 23, 2025): Hi @carlos-zamora, happy to collect a trace. Please let me know the instructions. Given the nature of the issue we may not be able to gracefully stop the trace when the system stops accepting input. Perhaps a scheduled reboot?
claunia commented 2026-01-31 08:22:51 +00:00
Author
Owner
Copy Link

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

Having the same problem. It's a nasty problem, Windows freezes completely when the UAC prompt would be shown. How can an application completely freezes Windows like that?

It's easy to reproduce on Windows 11 24H2 like @mabo003 explained.

@dperez83 commented on GitHub (Feb 3, 2025): Having the same problem. It's a nasty problem, Windows freezes completely when the UAC prompt would be shown. How can an application completely freezes Windows like that? It's easy to reproduce on Windows 11 24H2 like @mabo003 explained.
claunia commented 2026-01-31 08:22:51 +00:00
Author
Owner
Copy Link

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

@carlos-zamora

I can consistently reproduce the same issue by following the same steps highlighted by @mabo003.
Notably, this issue occurs on specific Windows 11 builds here - everything below 26100.2894 seems to work just fine.

I couldn't get a trace from this via UIforETW, is there maybe another option we could help fix this issue?
This problem is really annoying, especially in a development context as multiple elevated windows is nothing unusual...

Terminal build:

1.21.10351.0 (on all machines)

Affected Windows Builds:

❌ Issue can be reproduced: 26100.3037, 26100.3194
✔️ Not reproducable: 26100.2894

@marcopixel commented on GitHub (Feb 12, 2025): @carlos-zamora I can consistently reproduce the same issue by following the same steps highlighted by @mabo003. Notably, this issue occurs on specific Windows 11 builds here - everything below 26100.2894 seems to work just fine. I couldn't get a trace from this via UIforETW, is there maybe another option we could help fix this issue? This problem is really annoying, especially in a development context as multiple elevated windows is nothing unusual... **Terminal build:** 1.21.10351.0 (on all machines) **Affected Windows Builds:** ❌ Issue can be reproduced: 26100.3037, 26100.3194 ✔️ Not reproducable: 26100.2894
claunia commented 2026-01-31 08:22:51 +00:00
Author
Owner
Copy Link

@TheCodeGeek-PPE commented on GitHub (Mar 13, 2025):

This hasn't been resolved, and it was closed? What gives? I'm experiencing the same on build: 26100.3476
I was having this problem for about a month before I found out that it was caused by Windows Terminal. I have uninstalled WT and found I do not have the issue with Powershell at all. I will try reinstalling, but if the issue returns I will not keep WT on my PC.

@TheCodeGeek-PPE commented on GitHub (Mar 13, 2025): This hasn't been resolved, and it was closed? What gives? I'm experiencing the same on build: 26100.3476 I was having this problem for about a month before I found out that it was caused by Windows Terminal. I have uninstalled WT and found I do not have the issue with Powershell at all. I will try reinstalling, but if the issue returns I will not keep WT on my PC.
claunia commented 2026-01-31 08:22:52 +00:00
Author
Owner
Copy Link

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

What gives?

As noted in prior comments, we think it's the same issue as #18105. Active discussion should be happening over there.

@DHowett commented on GitHub (Mar 13, 2025): > What gives? As noted in prior comments, we think it's the same issue as #18105. Active discussion should be happening over there.
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 Issue-Bug Needs-Author-Feedback Needs-Triage
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#22764
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?