megathread: Known sudo issues in Windows insider builds

[zadjii-msft]

This is a megathread for all the issues that we had previously identified before sudo was made public. There's about a 3-week delay between us fixing issues, and the fixes being available to Insiders. This creates a bit of a backlog of issues that we've already fixed, but that are still present in the Insider builds.

Bugs fixed by 1.0.0-38, !10359415

Preview Give feedback

Tasklists will be sunset on April 30th, 2025

We encourage you to migrate your issue tasklist items to sub-issues. Learn more in our Changelog.

1. Sudo server listens for a single connection
2. sudo -N always starts Windows applications in C:\windows\system32 - this is by design, but mitigated with:
3. Please support -D/--chdir #22
   Issue-Task Resolution-Fix-Committed +2
4. Sudo events weren't showing up in Event Viewer
5. Regression from 26068: sudo pwsh reports an error about "Processing -File '' failed: The path is empty"
6. Sudo with an explicit mode will report an error instead of clamping to the available mode

In ge_release_we_adept_dev on 2/28. ETA ~3/20?

---

Bugs fixed by 1.0.0

Preview Give feedback

Tasklists will be sunset on April 30th, 2025

We encourage you to migrate your issue tasklist items to sub-issues. Learn more in our Changelog.

1. sudo seemingly doesn't return the exit code of the target application??
2. Localization is quite a bit better
3. Sudo does a better job of checking that the client process is sudo
4. The elevated sudo exits immediately after launching the target process
5. Please support --preserve-env as an alias for -E #21
   Issue-Bug Resolution-Fix-Committed Tracking-External +3
6. --newWindow was replaced with --new-window (!10282477)
7. Added -N for --new-window (!10282477)
8. --disableInput was replaced with --disable-input (!10282477)

Apparently this one is in ge_release 26068, 2/25

---

Bugs fixed by 0.1.6

Preview Give feedback

Tasklists will be sunset on April 30th, 2025

We encourage you to migrate your issue tasklist items to sub-issues. Learn more in our Changelog.

1. Localization is largely not available
2. Sudo doesn't log requests to the Event Viewer
3. sudo dir from powershell will do the cmd dir, not the powershell dir
4. sudo -E --newWindow cmd doesn't actually pass env vars to the target process
5. eleveated sudo doesn't check that the client process is sudo (MSFT:48520593, fixed in !10167063)

0.1.6 merged to OS.2020 in !10239101. It's in ge_release_we_adept as of 2/14, and ge_release as of 2/25, build 26068

---

Bugs fixed by 0.1.5 (Windows Insiders build 26052)

Preview Give feedback

Tasklists will be sunset on April 30th, 2025

We encourage you to migrate your issue tasklist items to sub-issues. Learn more in our Changelog.

1. The sudo icon is out of date
2. MSFT:48453238 Piping to files is broken

[MNLierman]

Hello,
I see this was targeted for 24H1, and indeed my laptop which I recently updated to 24H2, has the Sudo option in the Developer Settings. However, on my main production and dev workstation, which I use 10+ hours a day, it would be awesome to have Sudo, and the option is completely illusive and non-existent in the Dev Options of the Settings app. I am running build 22635.4440, released Nov 1 2024. Oddly, winver shows 23H2 – is this expected, and did Microsoft do away with updating winver on each release?

Either way, it should be expected that I have the Sudo command ready to enable and I cannot. I attempted to Google, Bing, and ask Copilot 365 about this disappearing, being removed, or otherwise not appearing, and have come up with no information. Any comments or insight would be immensely appreciated. Thank you!