Sudo for Windows
PathPrecedence
config setting (docs) ensuring that the system recognize the changes without requiring a log-off or restart. You still need to restart your consoles.Full Changelog: https://github.com/gerardog/gsudo/compare/v2.5.0...v2.5.1
With the release of Microsoft Sudo in Windows 11 24H2, both needs to coexist peacefully. When Microsoft Sudo is present, the sudo
command no longer redirects to gsudo
by default, so:
PathPrecedence
: When set to true
, it will ensure gsudo
appears first in the PATH
variable, ensuring the sudo
keyword starts gsudo
instead of Microsoft Sudo.
gsudo config PathPrecedence true
to activate. Please restart all your consoles to ensure the change makes effect.
false
to go back to normal.If a user with ms-sudo muscle memory, accidentally runs gsudo
, let's ensure gets a good user experience with:
--inline
, --disable-input
, --preserve-env
, --new-window
--chdir {directory}
(or uppercase -D {directory}
) in https://github.com/gerardog/gsudo/pull/355
Also:
gsudo config
command, so users can read each config use, in https://github.com/gerardog/gsudo/pull/354
SecurityEnforceUacIsolation
/DisableInput
handling also in Attached and TokenSwitch elevation Modes.Do Not Dim
. The fix (#85) makes gsudo focus the popup.Full Changelog: https://github.com/gerardog/gsudo/compare/v2.4.4...v2.5.0
WSL wrapper will not work if gsudo is on different drive
#337 #338Full Changelog: https://github.com/gerardog/gsudo/compare/v2.4.3...v2.4.4
vim
and nano
freezing when elevated directly (i.e. gsudo vim
). #248 #302Unauthorized. (Different gsudo.exe?)
. #300MediumPlus
integrity levelCacheDuration
> 24 days. #318Full Changelog: https://github.com/gerardog/gsudo/compare/v2.4.2...v2.4.3
Error: Invalid option: -noninteractive
using gsudo {command}
on Visual Studio code by @gerardog in https://github.com/gerardog/gsudo/pull/306
Full Changelog: https://github.com/gerardog/gsudo/compare/v2.4.0...v2.4.2
gsudo {command}
on VSCode.Full Changelog: https://github.com/gerardog/gsudo/compare/v2.4.0...v2.4.1-fixnoninteractive
--LogLevel
or --Duration
if cache was already activeError: Unable to connect to the elevated service
/NullReferenceException
by @gerardog in https://github.com/gerardog/gsudo/pull/292
Full Changelog: https://github.com/gerardog/gsudo/compare/v2.3.0...v2.4.0
Full Changelog: https://github.com/gerardog/gsudo/compare/v2.3.0...v2.3.1-beta
gsudo status --json
by @gerardog in https://github.com/gerardog/gsudo/pull/276
gsudo status {key}
gsudo status CacheAvailable
Full Changelog: https://github.com/gerardog/gsudo/compare/v2.2.0...v2.3.0
Import-Module gsudoModule
, eliminating the requirement for a full absolute path. Existing scripts using absolute paths will continue to work as expected.
.MSI
and Chocolatey
installers now deploy the module files also to %ProgramFiles%\PowerShell\Modules\gsudoModule\
.Full Changelog: https://github.com/gerardog/gsudo/compare/v2.1.0...v2.2.0