Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
PGomersall opened this issue Oct 23, 2024 · 7 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Priority-1 A description (P1) Product-Terminal The new Windows Terminal.

Comments

@PGomersall
Copy link

PGomersall commented Oct 23, 2024

Windows Terminal version

1.21.2911.0
Happens also with previous versions both stable and preview but all portable.

Windows build number

10.0.26100.2033

Other Software

Default profile can be either Windows PowerShell or PowerShell

Steps to reproduce

Windows 11 24H2 fully patched and domain joined.
WT portable is in stalled to root of local drive e.g. C:\WT or D:\WT
Logon as a domain user
Start windowsterminal.exe > right-click > Run as a different user - account is in initiated with YubiKey smartcard logon.
Type a command e.g. get-adcomputer xxx123
Whole logon session for initiating users freezes and becomes unusable.
Sometime a remote logoff of frozen logon can be forced, and the computer returns to normal operation. User can log back on and work normally. Sometimes a hard reboot is needed.
We have verified this happens on several different computers and users.
This can happen after in place upgrade from 23H2 to 24H2 via Windows Update or with completely clean 24H2 install.
It does not happen on prior versions of the OS 23H2.
Running other applications as a different user does not provoke this behavior.
Next troubleshooting step will be to determine if it is related to just running as a different user or specifically to a different user using a smartcard.

Expected Behavior

WT works normally when run as another user and does not freeze the initiating account logon.

Actual Behavior

Whole logon session for initiating users freezes and becomes unusable.
Sometime a remote logoff of frozen logon can be forced, and the computer returns to normal operation. User can log back on and work normally. Sometimes a hard reboot is needed.

@PGomersall PGomersall added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Oct 23, 2024
@PGomersall
Copy link
Author

other notes.
The logon session is not completely dead. Mouse moves albeit slowly. Seems everything is delayed hugely. Sometimes Explorer crashes and does not restart.
This can happen with both a user sat at local desktop console or via a rdp session.

@PGomersall
Copy link
Author

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
Copy link
Author

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

@carlos-zamora carlos-zamora added Product-Terminal The new Windows Terminal. Priority-1 A description (P1) labels Oct 30, 2024
@carlos-zamora carlos-zamora added this to the Terminal v1.23 milestone Oct 30, 2024
@carlos-zamora carlos-zamora removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Oct 30, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Tag-Fix Doesn't match tag requirements label Oct 30, 2024
@carlos-zamora
Copy link
Member

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

@PGomersall
Copy link
Author

PGomersall commented Oct 30, 2024 via email

@aermak
Copy link

aermak commented 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.

@Flapu7
Copy link

Flapu7 commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Priority-1 A description (P1) Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

4 participants