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

Opening "elevate-shim.exe" causes Computer to glitch #22401

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

Originally created by @ghost on GitHub (Oct 15, 2024).

Windows Terminal version

1.21.2701.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

It looks like a regression, this bug has been reported before in #16009

  1. In Windows Explorer, double-click on "elevate-shim.exe".
  2. In the UAC prompt window, click "Yes" to grant permissions.

Expected Behavior

No response

Actual Behavior

Same as #16009

Originally created by @ghost on GitHub (Oct 15, 2024). ### Windows Terminal version 1.21.2701.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce It looks like a regression, this bug has been reported before in #16009 1. In Windows Explorer, double-click on "elevate-shim.exe". 2. In the UAC prompt window, click "Yes" to grant permissions. ### Expected Behavior _No response_ ### Actual Behavior Same as #16009
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:12:08 +00:00
claunia commented 2026-01-31 08:12:09 +00:00
Author
Owner
Copy Link

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

Thanks for filing!

As a note, elevate-shim is an implementation detail. It is not intended to be run directly.

@DHowett commented on GitHub (Oct 15, 2024): Thanks for filing! As a note, elevate-shim is an implementation detail. It is not intended to be run directly.
claunia commented 2026-01-31 08:12:09 +00:00
Author
Owner
Copy Link

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

@DHowett If a person accidentally launched it, then now he should suffer? :)

@Zeroes1 commented on GitHub (Oct 15, 2024): @DHowett If a person accidentally launched it, then now he should suffer? :)
claunia commented 2026-01-31 08:12:10 +00:00
Author
Owner
Copy Link

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

Yyyyes? People who launch random EXE files with reckless abandon can learn not to do so! 😁

@DHowett commented on GitHub (Oct 15, 2024): Yyyyes? People who launch random EXE files with reckless abandon _can_ learn not to do so! 😁
claunia commented 2026-01-31 08:12:10 +00:00
Author
Owner
Copy Link

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

I suspect this was fixed by #15327 because it fixed the argument passing.

@lhecker commented on GitHub (Oct 15, 2024): I suspect this was fixed by #15327 because it fixed the argument passing.
claunia commented 2026-01-31 08:12:10 +00:00
Author
Owner
Copy Link

@Zeroes1 commented on GitHub (Oct 16, 2024):

@DHowett @lhecker

As a note, elevate-shim is an implementation detail. It is not intended to be run directly.

Why not use a file without the EXE extension for this? for example elevate-shim.run ?
You run elevate-shim with CreateProcessW (no need EXE extension for start process)

@Zeroes1 commented on GitHub (Oct 16, 2024): @DHowett @lhecker >As a note, elevate-shim is an implementation detail. It is not intended to be run directly. Why not use a file without the EXE extension for this? for example elevate-shim.run ? You run elevate-shim with CreateProcessW (no need EXE extension for start process)
claunia commented 2026-01-31 08:12:10 +00:00
Author
Owner
Copy Link

@Zeroes1 commented on GitHub (Oct 16, 2024):

@lhecker

TEST:
if user manually run elevate-shim.exe

terminal-1.21.2701.0 [latest release] - problem
terminal-1.22.2702.0 [latest preview] - no problem
terminal-1.23.2891.0 [latest canary] - no problem

in next version release will be OK?

@Zeroes1 commented on GitHub (Oct 16, 2024): @lhecker TEST: if user manually run elevate-shim.exe terminal-1.21.2701.0 [latest release] - problem terminal-1.22.2702.0 [latest preview] - no problem terminal-1.23.2891.0 [latest canary] - no problem in next version release will be OK?
claunia commented 2026-01-31 08:12:10 +00:00
Author
Owner
Copy Link

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

Yeah, sounds like it was fixed in that PR then. Thanks for testing this!

Why not use a file without the EXE extension for this? for example elevate-shim.run ?

If this issue comes up more often in the future we could explore that idea. 🙂

@lhecker commented on GitHub (Oct 16, 2024): Yeah, sounds like it was fixed in that PR then. Thanks for testing this! > Why not use a file without the EXE extension for this? for example elevate-shim.run ? If this issue comes up more often in the future we could explore that idea. 🙂
claunia commented 2026-01-31 08:12:11 +00:00
Author
Owner
Copy Link

@Sinazrp commented on GitHub (Jan 5, 2025):

I have same problem and I am in middle of installing something important

@Sinazrp commented on GitHub (Jan 5, 2025): I have same problem and I am in middle of installing something important
claunia commented 2026-01-31 08:12:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 5, 2025):

A question: why are you directly running elevate-shim? It is an internal helper tool. There's literally no reason to run that yourself directly, right?

@zadjii-msft commented on GitHub (Jan 5, 2025): A question: why are you directly running `elevate-shim`? It is an internal helper tool. There's literally no reason to run that yourself directly, _right_?
claunia commented 2026-01-31 08:12:11 +00:00
Author
Owner
Copy Link

@Sinazrp commented on GitHub (Jan 6, 2025):

Why would a Microsoft-produced application include an executable file that behaves in a way similar to a virus? Why is there an unnecessary .exe file included? I don’t randomly click on executable files, but this is a Microsoft product—I thought we could trust Microsoft. Why is the responsibility being shifted to users instead of addressing this by modifying or removing that .exe file?

@Sinazrp commented on GitHub (Jan 6, 2025): Why would a Microsoft-produced application include an executable file that behaves in a way similar to a virus? Why is there an unnecessary .exe file included? I don’t randomly click on executable files, but this is a Microsoft product—I thought we could trust Microsoft. Why is the responsibility being shifted to users instead of addressing this by modifying or removing that .exe file?
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-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#22401
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?