Skip to content

[dotnet-sdk-8.0.311] dotnet tool install command get access denied error if tools already installed #47906

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Junjun-zhao opened this issue Mar 26, 2025 · 5 comments
Assignees
Labels
Area-Tools untriaged Request triage from a team member

Comments

@Junjun-zhao
Copy link
Member

Application Name: GlobalToolsNETCore21Part02
OS: Windows 10 21H2
CPU: X64
.NET Build Number: dotnet-sdk-8.0.311-win-64
Also can check the information from: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2428298

Verify Scenarios:
Windows10 21h2 x64 + dotnet-sdk-8.0.115: Pass
Windows10 21h2 x64 + dotnet-sdk-8.0.311: Fail
Windows10 21h2 x64 + dotnet-sdk-8.0.408: Fail

Issue Description:
When installing dotnet tools with "gti -c install" command, it tries to re-install the tools which already installed and gets access deny error for gti tool installation.

Repro steps:
The machine only has dotnet-sdk-8.0.311 installed. And environment variable DOTNET_ROLL_FORWARD_ON_NO_CANDIDATE_FX set as 2.

1.Open command prompt window.
2. Execute "dotnet tool install –g gti" command.
3. Navigate to a local folder with "cd {localfolderpath}" command
4. Execute "gti –c save" command.
5. Execute "gti –c install" command.

Expected Result:
"Tool is already installed" message should show if the tools were installed before.

Image

Actual Result:

Get access deny error as it tries to re-install the tools which already installed.

Image

Findings:

We filed this issue before, and it was closed with label "needs team triage" and seems out of track. So, file a new bug for tracking.

[dotnet-sdk-8.0.200] dotnet tool install command get access deny message · Issue #38354 · dotnet/sdk
This should be same as this issue dotnet tool install --global reinstalls even if the same version is already present which has been fixed since .NET 9 Preview 7 via PR Avoid reinstall tool already installed

DotNet Info:

.NET SDK:
 Version:           8.0.311
 Commit:            917c9fc06c
 Workload version:  8.0.300-manifests.22ac4dbc
 MSBuild version:   17.10.23+f3052339b

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19045
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\8.0.311\

.NET workloads installed:
There are no installed workloads to display.

Host:
  Version:      8.0.15
  Architecture: x64
  Commit:       50c4cb9fc3

.NET SDKs installed:
  8.0.311 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 8.0.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

@dotnet-actwx-bot @dotnet/compat

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Tools untriaged Request triage from a team member labels Mar 26, 2025
@Junjun-zhao
Copy link
Member Author

Hi @marcpopMSFT, could you please take a look at this issue and triage it? Thanks

@Forgind
Copy link
Member

Forgind commented Apr 2, 2025

In your other (closed) issue, it sounded like you were referring to #41746; is that right? And you just want that to be backported to 8.0.3xx and/or 8.0.4xx? I'm not convinced it's worth backporting that, but I'll add @baronfel in case he disagrees.

@Junjun-zhao
Copy link
Member Author

@Forgind Yes. We think it should be also backported to 8.0.3xx and 8.0.4xx. Originally, it reproduced on 8.0.2xx and 9.0, it had been fixed on .NET 9.0 by #41746, but not 8.0.2xx. Now it doesn't work on 8.0.3xx and 8.0.4xx either.

@Forgind
Copy link
Member

Forgind commented Apr 4, 2025

We talked about it a bit on our team and decided not to backport. Thanks for the report!

@Forgind Forgind closed this as not planned Won't fix, can't repro, duplicate, stale Apr 4, 2025
@marcpopMSFT
Copy link
Member

To add to forgind's comments, we don't feel like this meets the servicing bar. We'll watch for additional feedback in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Tools untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

3 participants