Skip to content
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

DPAPI error messages since updating VS to 17.1.0 #23989

Closed
UweKeim opened this issue Feb 17, 2022 · 5 comments
Closed

DPAPI error messages since updating VS to 17.1.0 #23989

UweKeim opened this issue Feb 17, 2022 · 5 comments

Comments

@UweKeim
Copy link

UweKeim commented Feb 17, 2022

Since we updated VS 2022 to 17.1.0 yesterday, running this command:

dotnet tool update dotnet-outdated-tool -g

Results in this error message:

C:\Program Files\dotnet\sdk\6.0.200\NuGet.targets(130,5): error : Der Dienstindex für die Quelle "https://nuget.telerik.com/v3/index.json" konnte nicht geladen werden. [C:\Users\ukeim\AppData\Local\Temp\p1eijxar.5tx\restore.csproj]
C:\Program Files\dotnet\sdk\6.0.200\NuGet.targets(130,5): error :   Kennwortentschlüsselung wird für .NET Core für diese Plattform nicht unterstützt. Der folgende Feed verwendet ein verschlüsseltes Kennwort: "nuget.telerik.com". Sie können ein Klartextkennwort als Problemumgehung verwenden. [C:\Users\ukeim\AppData\Local\Temp\p1eijxar.5tx\restore.csproj]
C:\Program Files\dotnet\sdk\6.0.200\NuGet.targets(130,5): error :   Windows Data Protection API (DPAPI) is not supported on this platform. [C:\Users\ukeim\AppData\Local\Temp\p1eijxar.5tx\restore.csproj]
Fehler beim Update des Tools "dotnet-outdated-tool". Ursache:
Das Toolpaket konnte nicht wiederhergestellt werden.
Fehler bei der Installation des Tools "dotnet-outdated-tool". Dieser Fehler kann folgende Ursachen haben:

* Sie versuchen, eine Vorschauversion zu installieren und haben nicht die Option "--version" verwendet, um die Version anzugeben.
* Ein Paket mit diesem Namen wurde gefunden, aber es handelte sich nicht um ein .NET-Tool.
* Auf den erforderlichen NuGet-Feed kann nicht zugegriffen werden, möglicherweise aufgrund eines Problems mit der Internetverbindung.
* Sie haben den Namen des Tools falsch eingegeben.

Weitere Gründe sowie Informationen zum Erzwingen der Paketbenennung finden Sie unter https://aka.ms/failure-installing-tool.

(German error message, sorry).

Translated to English the error messages read:

The service index for source "https://nuget.telerik.com/v3/index.json" could not be loaded. [C:\Users\ukeim\AppData\Local\Temp\p1eijxar.5tx\restore.csproj]

Password decryption is not supported for .NET Core for this platform. The following feed uses an encrypted password: nuget.telerik.com. You can use a clear text password as a workaround.

Windows Data Protection API (DPAPI) is not supported on this platform.

On the PC of one of my co-workers the error occurs on a different NuGet feed, so I do think this is not related to the feed itself. And I also doubt that this is related to the dotnet-outdated tool itself.

My question

Is this a known issue? Are there any workaround?

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Request triage from a team member label Feb 17, 2022
@UweKeim
Copy link
Author

UweKeim commented Feb 17, 2022

Could be related to this SO question:

https://stackoverflow.com/q/64341361/107625

@UweKeim
Copy link
Author

UweKeim commented Feb 17, 2022

A workaround, based on this comment:

  1. Remove any custom NuGet sources that have a password set with the command dotnet nuget remove source "Name Of My Source".
  2. Add the sources again, specifying the --store-password-in-clear-text option.

Example:

dotnet nuget add source "https://example.com/index.json" -n "Example" -u Xyz -p Abc --store-password-in-clear-text

(With Xyz being the actual user name and Abc being the actual password).

This workaround seems to work well, but I still don't know why this happens, all of a sudden after updating VS 2022 to 17.1.0.

@wazzamatazz
Copy link

This is a duplicate of #23498.

Upgrading build tools on one of our build agents to VS2022 17.1 (from 17.0.x) this morning has broken everything that uses authenticated feeds.

@baronfel baronfel added Area-NuGet and removed untriaged Request triage from a team member labels Feb 23, 2022
@baronfel
Copy link
Member

Correct, this is a duplicate. Thank you for reporting, but I'll close this in favor of #23498.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants