Downloads of v 1.0.0:


Last Update:

13 Feb 2019

Package Maintainer(s):

Software Author(s):

  • Andrew Nosenko


sudo runas run shell command line powershell cmd admin administrator


This is not the latest version of wsudo available.

  • 1
  • 2
  • 3

1.0.0 | Updated: 13 Feb 2019



Downloads of v 1.0.0:



Software Author(s):

  • Andrew Nosenko

  • 1
  • 2
  • 3
wsudo 1.0.0

This is not the latest version of wsudo available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install wsudo, run the following command from the command line or from PowerShell:


To upgrade wsudo, run the following command from the command line or from PowerShell:


To uninstall wsudo, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade wsudo -y --source="'INTERNAL REPO URL'" --version="'1.0.0'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade wsudo -y --source="'INTERNAL REPO URL'" --version="'1.0.0'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install wsudo
    name: wsudo
    version: '1.0.0'
    state: present

See docs at

chocolatey_package 'wsudo' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.0.0'

See docs at

cChocoPackageInstaller wsudo
    Name     = "wsudo"
    Version  = "1.0.0"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'wsudo':
  ensure   => '1.0.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator mkevenaar on 14 Feb 2019.



Invoke a program with elevated rights (as Administrator) from a non-admin shell command prompt.
This implementation doesn't depend on the legacy Windows Script Host (CScript).
Instead, it uses a helper PowerShell 5 script that invokes "Start-Process -Wait -Verb runAs ..." cmdlet.
Your system most likely already has PowerShell 5.x installed, otherwise you'll be offered
to install it as a dependency.


wsudo runs a program or an inline command with elevated rights in the current directory:

C:\Users\User>wsudo del C:\Windows\Temp*.*

Internally, it invokes "%ComSpec% /K" elevated and passes the command line over to it for execution. It keeps the admin console open when the command has finished.

wsudox does the same besides using "%ComSpec% /C", so it closes the admin console as soon as the command has finished:

C:\Users\User>wsudox "del C:\Windows\Temp*.* && pause"

To run a GUI program as admin and close the admin console immediately, just launch it via the start inline command:

C:\Users\User>wsudox start notepad C:\Windows\System32\drivers\etc\hosts

@echo off
set wsudo_commandLine=%*
set wsudo_curDir=%CD%
powershell.exe -f "%~dp0.\wsudo.ps1" -stayOpen -title %~n0 -action prepare
exit /b %ERRORLEVEL%
#Requires -Version 5.0

  [Parameter(Mandatory = $true)] [ValidateSet('prepare','run')] [string] $action,
  [string] $title,
  [string] $command,
  [switch] $stayOpen)

Set-StrictMode -Version Latest
$ErrorActionPreference = 'Stop'

class CommandInfo {

switch($action) {
  'prepare' {
    # pack curDir, commandLine etc using JSON/base64 and re-launch itself as admin
    $commandInfo = [CommandInfo]::new()
    $commandInfo.comSpec = $env:ComSpec
    $commandInfo.commandLine = $env:wsudo_commandLine
    $commandInfo.curDir = $env:wsudo_curDir
    $commandInfo.title = $title
    $commandInfo.stayOpen = $stayOpen
    $commandInfoJson = ConvertTo-Json -Compress $commandInfo
    $commandInfoEncoded = [Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes($commandInfoJson))
    # get the powershell EXE name
    $powershell = [System.Diagnostics.Process]::GetCurrentProcess().MainModule.FileName
    $pi = Start-Process -PassThru -Verb runAs `
      -FilePath $powershell -ArgumentList "-f $PSCommandPath -action run -command $commandInfoEncoded"
    exit $pi.ExitCode
  'run' {
    # unpack curDir, commandLine etc and run the command under CMD
    if (!$command) { 
      throw 'Must provide commandInfo.'

    $commandInfoJson = [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($command));
    $commandInfo = [CommandInfo](ConvertFrom-Json $commandInfoJson)

    if ($commandInfo.title) { 
      $host.ui.RawUI.WindowTitle = $commandInfo.title

    Set-Location $commandInfo.curDir
    $opt = if ($commandInfo.stayOpen) { '/K' } else { '/C' }
    $pi = Start-Process -PassThru -NoNewWindow `
      -FilePath $commandInfo.comSpec -ArgumentList "$opt $($commandInfo.commandLine)"
    exit $pi.ExitCode
  default {
    throw 'Invalid action.'
@echo off
set wsudo_commandLine=%*
set wsudo_curDir=%CD%
powershell.exe -f "%~dp0.\wsudo.ps1" -title %~n0 -action prepare
exit /b %ERRORLEVEL%
Generate-BinFile 'wsudo' '..\lib\wsudo\bin\wsudo.cmd'
Generate-BinFile 'wsudox' '..\lib\wsudo\bin\wsudox.cmd'
Remove-BinFile 'wsudo' '..\lib\wsudo.1.0.0\bin\wsudo.cmd'
Remove-BinFile 'wsudox' '..\lib\wsudo.1.0.0\bin\wsudox.cmd'

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
wsudo 1.0.2 3736 Monday, March 25, 2019 Approved
wsudo 1.0.1 286 Thursday, February 28, 2019 Approved
wsudo 1.0.0 251 Wednesday, February 13, 2019 Approved

1.0.0 (Feb 12, 2019) - Initial release

Discussion for the wsudo Package

Ground Rules:

  • This discussion is only about wsudo and the wsudo package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or wsudo, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus