WT can't start as limited user (trying to start forever) #20190

Open
opened 2026-01-31 07:06:10 +00:00 by claunia · 4 comments
Owner

Originally created by @Zeroes1 on GitHub (Jul 5, 2023).

Windows Terminal version

1.17.11461

Windows build number

10.0.19045.3086

Other Software

Process Explorer v17.04

Steps to reproduce

I as Admin, UAC OFF
under Process Explorer i chose run WT as limited user

Expected Behavior

Run WT , or stop trying after N fail start.

Actual Behavior

trying to start forever WT
i check
Microsoft.WindowsTerminal_1.17.11461.0_x64.zip
Microsoft.WindowsTerminalPreview_1.18.1462.0_x64.zip
with both trouble.

https://github.com/microsoft/terminal/assets/11919060/63362fe5-05c9-4531-b363-9026563fd006

Originally created by @Zeroes1 on GitHub (Jul 5, 2023). ### Windows Terminal version 1.17.11461 ### Windows build number 10.0.19045.3086 ### Other Software Process Explorer v17.04 ### Steps to reproduce I as Admin, UAC OFF under Process Explorer i chose run WT as limited user ### Expected Behavior Run WT , or stop trying after N fail start. ### Actual Behavior trying to start forever WT i check Microsoft.WindowsTerminal_1.17.11461.0_x64.zip Microsoft.WindowsTerminalPreview_1.18.1462.0_x64.zip with both trouble. https://github.com/microsoft/terminal/assets/11919060/63362fe5-05c9-4531-b363-9026563fd006
claunia added the Help WantedIssue-BugNeeds-Tag-FixProduct-Terminal labels 2026-01-31 07:06:11 +00:00
Author
Owner

@Zeroes1 commented on GitHub (Jul 5, 2023):

reproduced 100%, Some user can't stop easy this cycling process...

@Zeroes1 commented on GitHub (Jul 5, 2023): reproduced 100%, Some user can't stop easy this cycling process...
Author
Owner

@Zeroes1 commented on GitHub (Jul 5, 2023):

with default settings problem not exist

problem exist when in default profile option "run profile with admin rights"
aka:

settings.json
"profiles":
{
"defaults":
{
"elevate": true
},

or not default profile, but profile start as default...

@Zeroes1 commented on GitHub (Jul 5, 2023): with default settings problem not exist problem exist when in default profile option "run profile with admin rights" aka: settings.json "profiles": { "defaults": { "elevate": true }, or not default profile, but profile start as default...
Author
Owner

@zadjii-msft commented on GitHub (Jul 5, 2023):

Okay got it so:

  • You're running everything as admin (with UAC disabled)
  • You manually run the Terminal not as admin
  • But in the Terminal settings, it's set to auto-elevate.

And that causes it to crash loop on the start. FWIW, I think there was an auto-elevate crash loop that was fixed in 1.18 Preview.

We should probably not do this (but kinda neither should you 😜)

@zadjii-msft commented on GitHub (Jul 5, 2023): Okay got it so: * You're running everything as admin (with UAC disabled) * You manually run the Terminal _not_ as admin * But in the Terminal settings, it's set to auto-elevate. And that causes it to crash loop on the start. FWIW, I think there was an auto-elevate crash loop that was fixed in 1.18 Preview. We should probably not do this (but kinda neither should you 😜)
Author
Owner

@Zeroes1 commented on GitHub (Jul 6, 2023):

@zadjii-msft
public 1.18.230526002-preview with same problem

@Zeroes1 commented on GitHub (Jul 6, 2023): @zadjii-msft public 1.18.230526002-preview with same problem
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20190