cmderdev / cmderdev/cmder

[Bug] Cmder ceases to be compatible with program Admin by Request

Open
#2,935 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🐛 Type: Bug 🤝 Help wanted
Dominant language
PowerShell
Stars
27k
Forks
2.1k
PR merge metrics
No merged PRs in 30d

Description

Version Information
Cmder version: 230724 stable
Operating system: Windows 10 19045.4355
Cmder Edition

Cmder Full (with Git)

Description of the issue

A while back our company installed a Program called "Admin by Request", where the standard UAC is replaced by a requirement to have a Domain account, and then the only way to do things like install programs, update environmental variables, run programs elevated etc is to trigger it through "Admin By Request", running an Elevated Cmd prompt automatically triggers "Admin by Request.", but other things like launching the Environmental Variable editor have to be launched directly by the tool.

When it was first installed I could run both normal or elevated prompts, and by the time the Cmder tab had finished loading you would be able to type.

However a couple of months ago I found that if I run an elevated prompt in Cmder it does indeed trigger "Admin by Request", and you OK the elevation and the typical Cmder tab loading happens, however when it stops running other programs such as where, findstr, locale and git.exe we then see the Lamda λ symbol and a flashing I cursor, at that point when you start typing nothing ever appears.

How to reproduce
  1. Run Cmder
  2. Choose cmd{Cmder as Admin}
  3. Wait for a prompt
  4. Start typing

Expected: whatever typed at step 4 appears, Actual, Insertion point cursor flashes but no text appears

Additional context

Admin by Request: Workstation Edition 8.1.6 (Build 28284)

Checklist
  • I have read the documentation.
  • I have searched for similar issues and found none that describe my issue.
  • I have reproduced the issue on the latest version of Cmder.
  • I am certain my issues are not related to ConEmu, Clink, or other third-party tools that Cmder uses.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the elevated prompt through cmd{Cmder as Admin} with Admin by Request enabled, then observe the Cmder tab startup while where, findstr, locale, and git.exe run. Done means the elevated prompt accepts and displays typed input normally after loading; the payload names no source files or tests to inspect.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, shell
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.