Getting a Failed to install dotnet error when using a self-hosted runner

[rfalanga]

Select Topic Area

Question

Body

Over a year ago I set up a self-hosted runner on my Windows 11 Pro desktop. I used it back then, fine. However, I haven't used it in over a year. Yesterday, I tried using it again and discovered that the repo I had set up to use a self-hosted runner, was no longer associated with a self-hosted runner. So, I set it up with a self-hosted runner, then tried to use it. However, it gave me this error:

Failed to install dotnet, exit code: 1. dotnet-install: The current user doesn't have write access to the installation root 'C:\Program Files\dotnet' to install .NET. Please try specifying a different installation directory using the -InstallDir parameter, or ensure the selected directory has the appropriate permissions.

Looking at my C:\Program Files folder, I do see a folder there named dotnet. And it has files within it that were created yesterday. I'm confused; it looks like running the GitHub Workflow that would invoke the self-hosted runner, worked. So, why does it tell me this? Here's a snippet from the YAML file:

on:
  push:
    branches: [ "main" ]
  pull_request:
    branches: [ "main" ]

jobs:

  build:

    strategy:
      matrix:
        configuration: [Release] # This was [Debug, Release]

    runs-on: self-hosted  # For a list of available runner types, refer to

[imDarshanGK]

Hi @rfalanga,

The error you're seeing typically happens because the user running the self-hosted runner doesn't have the required permissions to install .NET in C:\Program Files\dotnet.

1. Run the runner as Administrator: This will give it the necessary permissions to install .NET.
2. Change the installation directory: Use the -InstallDir parameter to specify a directory where the user has write access, like a folder in the user's profile.

dotnet-install --InstallDir C:\Users\YourUser\dotnet

[rfalanga]

I'm getting an error that says 'dotnet-install' is not a recognized command. I also tried using just 'dotnet', but that didn't work, either, although it gave me this response:

Could not execute because the specified command or file was not found.
Possible reasons for this include:

• You misspelled a built-in dotnet command.
• You intended to execute a .NET program, but dotnet---InstallDir does not exist.
• You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.

[imDarshanGK]

It looks like dotnet-install isn’t recognized because the .NET SDK might not be installed.

1. Install the .NET SDK: Download and install
2. Check your PATH: Make sure dotnet is added to your PATH so your system can find it.

Once done, try the dotnet-install command again.

[rfalanga]

(I'm sorry to keep bothering you with these questions.)

I've downloaded the SDK for .NET 9. Then I tried running the dotnet-install command again, but it couldn't find it. I went to C:\Program Files\dotnet and tried running dotnet-install from there, but it couldn't find it. I searched for dotnet-install.ps1 within that directory and all subdirectories, but it couldn't find it.

[imDarshanGK]

1. dotnet-install is not included with the SDK >> The dotnet-install.ps1 script doesn’t come with the SDK. You need to download it separately.

2. Check if .NET SDK is installed>>
   Run this command to see if .NET is installed>>
   dotnet --list-sdks

3. Reinstall the SDK>> If the above steps don’t work, try reinstalling the .NET SDK

4. Run as Administrator>> Make sure you're running the command prompt as an Administrator.

@rfalanga

[rfalanga]

Running the dotnet --list-sdks command yielded this result:

3.1.426 [C:\Program Files\dotnet\sdk]
5.0.403 [C:\Program Files\dotnet\sdk]
5.0.408 [C:\Program Files\dotnet\sdk]
5.0.416 [C:\Program Files\dotnet\sdk]
6.0.321 [C:\Program Files\dotnet\sdk]
9.0.102 [C:\Program Files\dotnet\sdk]

I know I've recently downloaded a dotnet-install.ps1 file. I'm looking for it. Will get back to you ASAP.

Addendum

BTW, I noticed, looking at the list of installed .NET SDKs on my machine, I do not have either .NET 7 or 8 SDKs installed, but I do have .NET 9. Could this have anything to do with what I am experiencing?