Skip to content

Sidra.exe Prerequisites command

The sidra.exe prerequisites command checks or installs the needed dependencies for successfully executing the other commands. For this reason, this is usually the first command to be used when starting a Sidra installation. This command will check or install both external dependencies and the internal ones, the ones pertaining to the Sidra solution, such as needed templates.

The external dependencies needed are:

  • The .NET Core SDK
  • Git, the version control CLI tool
  • Azure CLI and extension

The usage options are:

    .\sidra.exe prerequisites verify
    .\sidra.exe prerequisites setup
    .\sidra.exe prerequisites [setup|verify] --help
This command needs elevated rights when it is used to download and install software and PowerShell scripts on the machine, as prerequisites for the further steps.

Known issues

Administrative execution

The command may block Sidra.exe if it is not run from an elevated-rights PowerShell console. Sidra.exe is calling the PowerShell engine, which may refuse to download and install the software without informing the caller.


From version 1.12 onwards, Sidra.exe will show an error message when executing this command without administrator roles.

PowerShell restarts may be needed

If external dependencies are installed with this command, restart of the PowerShell console will be needed, to allow the hosting process to reload the PATH environment variable. For example, after installing .NET SDK or Git, the tool needs to execute these the dotnet.exe or git.exe to check for the version installed. Without refreshed PATH, these commands cannot be run; this would result in false-positive reporting of missing dependencies when checking with prerequisites verify post software installation.


From version 1.12 onwards, this known issue will be solved.

PowerShell script execution policy

The PowerShell script execution policy must allow for the execution of remote scripts. Remember checking the execution policy and change it accordingly, if needed, prior to running the prerequisites command. Check and set using the below commands. If the Process scope is being used – the safest –, the execution policy may need to be re-set after a PowerShell console restart.

It is recommended to use the next execution policy:

    Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process

Blockage due to untrusted PowerShell modules

There are situations when some of the preloaded PowerShell modules may be untrusted for execution, especially the ones that are needed by Sidra.exe. In such conditions, when attempting to list or check for the required modules, the Sidra.exe may get blocked because the PowerShell engine in the background would silently wait for a user confirmation, with no feedback flowing through Sidra.exe. Hence, if the program seems to be stuck, this can be due to the existence of the untrusted PowerShell modules installed.

Blockage due to Azure CLI automatic upgrades enabled

The command 'az version' is being used to verify Azure CLI installation at 'Sidra.exe prerequisites verify'. In the case that Azure CLI automatic upgrades is enabled, when running 'az version' command, user will be asked to upgrade to latest version. Having auto-upgrade setting set to true will cause Sidra CLI to wait for a never given answer and it will stop the execution.

Change this setting to false by running the following code:

    az config set auto-upgrade.enable=no

Next: The Profile command

Last update: 2022-03-14
Back to top