You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On some Windows machines (but not others), when installing workloads on the 7.0.40x band, the following error messages show up:
Failed to update the advertising manifest microsoft.net.workload.mono.toolchain.net7: Failed to validate package signing.
Verifying Microsoft.NET.Workload.Mono.ToolChain.net7.Manifest-7.0.100.Msi.x64.7.0.12
Signature type: Author
Subject Name: CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
SHA256 hash: 566A31882BE208BE4422F7CFD66ED09F5D4524A5994F50CCC8B05EC0528C1353
Valid from: 2023-07-26 8:00:00 PM to 2026-10-17 7:59:59 PM
Signature type: Repository
Subject Name: CN=NuGet.org Repository by Microsoft, O=NuGet.org Repository by Microsoft, L=Redmond, S=Washington, C=US
SHA256 hash: 5A2901D6ADA3D18260B9C6DFE2133C95D74B9EEF6AE0E5DC334C8454D1477DF4
Valid from: 2021-02-15 7:00:00 PM to 2024-05-15 7:59:59 PM
.
The relation to how Windows is causing issues is unclear at this point, since on all machines, Nuget Package Explorer is reporting the packages signatures to be correct.
Windows 10 machine which does not work: 22H2 (OS Build 19045.3570)
Windows 10 machine which works: 22H2 (OS Build 19045.3448)
Windows 11 machine which works: 22H2 (OS Build 22621.2428)
It's clear that the version number is the cause here, it may be something else.
Update: .NET 7.0.402 seems to be fixing this issue, though it has also started happening on much older versions, such as 7.0.102 which are still in use because of #30103.
@joeloff is this the new signing key thing? We pushed that key to all active SDK versions right? If so @jeromelaban you'd have to update to a newer .1xx to pick up the changed key.
Describe the bug
On some Windows machines (but not others), when installing workloads on the 7.0.40x band, the following error messages show up:
The relation to how Windows is causing issues is unclear at this point, since on all machines, Nuget Package Explorer is reporting the packages signatures to be correct.
To Reproduce
The following command is run:
The error happens when the workloads installer is running:
sdk/src/Cli/dotnet/NugetPackageDownloader/FirstPartyNuGetPackageSigningVerifier.cs
Line 79 in 6186796
Which returns
1
on some windows systems, when running the following using this package:Exceptions (if any)
Further technical details
Windows 10 machine which does not work:
22H2 (OS Build 19045.3570)
Windows 10 machine which works:
22H2 (OS Build 19045.3448)
Windows 11 machine which works:
22H2 (OS Build 22621.2428)
It's clear that the version number is the cause here, it may be something else.
Global.json contains
{ "sdk": {"allowPrerelease": false}}
.The text was updated successfully, but these errors were encountered: