dotnet workload restore failing with 10.0.101

[mip1983]

Describe the bug

Running 'dotnet workload restore' is giving me this, both locally and in my Azure DevOps pipeline:

Updated advertising manifest microsoft.net.workloads.
Installing workload version 10.0.101.
Installing microsoft.net.workloads.10.0.100.msi.x64 ....... Done
Downloading microsoft.net.workload.emscripten.current.manifest-10.0.100.msi.x64 (10.0.101)
Workload installation failed. Rolling back installed packs...
Downloading microsoft.net.workload.emscripten.current.manifest-10.0.100.msi.x64 (10.0.101)
Installation rollback failed: One or more errors occurred. (Version 10.0.101 of package microsoft.net.workload.emscripten.current.manifest-10.0.100.msi.x64 is not found in NuGet feeds https://api.nuget.org/v3/index.json;C:\Program Files (x86)\Microsoft SDKs\NuGetPackages.)
Removing microsoft.net.workloads.10.0.100.msi.x64 ..... Done
Workload update failed: One or more errors occurred. (Version 10.0.101 of package microsoft.net.workload.emscripten.current.manifest-10.0.100.msi.x64 is not found in NuGet feeds https://api.nuget.org/v3/index.json;C:\Program Files (x86)\Microsoft SDKs\NuGetPackages.)

To Reproduce

run 'dotnet workload restore' in a dotnet 10 project with the 10.0.101 sdk installed on your machine

Exceptions (if any)

Workload update failed: One or more errors occurred. (Version 10.0.101 of package microsoft.net.workload.emscripten.current.manifest-10.0.100.msi.x64 is not found in NuGet feeds https://api.nuget.org/v3/index.json;C:\Program Files (x86)\Microsoft SDKs\NuGetPackages.)

Further technical details

details of dotnet --info

.NET SDK:
Version: 10.0.101
Commit: fad253f51b
Workload version: 10.0.100.1
MSBuild version: 18.0.6+fad253f51

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

.NET workloads installed:
[android]
Installation Source: SDK 10.0.100, VS 18.1.11304.174, VS 18.3.11304.161, VS 17.14.36804.6
Manifest Version: 36.1.2/10.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.sdk.android\36.1.2\WorkloadManifest.json
Install Type: Msi

[ios]
Installation Source: SDK 10.0.100, VS 18.1.11304.174, VS 18.3.11304.161, VS 17.14.36804.6
Manifest Version: 26.1.10494/10.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.sdk.ios\26.1.10494\WorkloadManifest.json
Install Type: Msi

[maccatalyst]
Installation Source: SDK 10.0.100, VS 18.1.11304.174, VS 18.3.11304.161, VS 17.14.36804.6
Manifest Version: 26.1.10494/10.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.sdk.maccatalyst\26.1.10494\WorkloadManifest.json
Install Type: Msi

[maui-windows]
Installation Source: SDK 10.0.100, VS 18.1.11304.174, VS 18.3.11304.161, VS 17.14.36804.6
Manifest Version: 10.0.0/10.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.sdk.maui\10.0.0\WorkloadManifest.json
Install Type: Msi

[wasm-tools]
Installation Source: SDK 10.0.100, VS 18.1.11304.174, VS 18.3.11304.161
Manifest Version: 10.0.100/10.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.workload.mono.toolchain.current\10.0.100\WorkloadManifest.json
Install Type: Msi

[wasm-tools-net9]
Installation Source: SDK 10.0.100, VS 18.3.11304.161
Manifest Version: 10.0.100/10.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.workload.mono.toolchain.net9\10.0.100\WorkloadManifest.json
Install Type: Msi

Configured to use workload sets when installing new manifests.

Host:
Version: 10.0.1
Architecture: x64
Commit: fad253f51b

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

.NET runtimes installed:
Microsoft.AspNetCore.App 8.0.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 10.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.21 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 10.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.21 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 10.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
Not set

global.json file:
Not found

Learn more:
https://aka.ms/dotnet/info

Download .NET:
https://aka.ms/dotnet/download

[ishisaka]

After installing 10.0.101 on Mac (ARM64), the dotnet --info command returns an error related to workloads.

It might be caused by the same bug.

Please note that the following is the Japanese version of the message.

dotnet --info
.NET SDK:
 Version:           10.0.101
 Commit:            fad253f51b
 Workload version:  10.0.100.1
 MSBuild version:   18.0.6+fad253f51

ランタイム環境:
 OS Name:     Mac OS X
 OS Version:  26.1
 OS Platform: Darwin
 RID:         osx-arm64
 Base Path:   /usr/local/share/dotnet/sdk/10.0.101/

インストール済みの .NET ワークロード:
System.IO.FileNotFoundException: ワークロード バージョン 10.0.100.1 のワークロード マニフェスト microsoft.net.workload.emscripten.current: 10.0.100/10.0.100 がインストールされませんでした。"dotnet workload repair" を実行すると、これを解決できる場合があります。
   at Microsoft.NET.Sdk.WorkloadManifestReader.SdkDirectoryWorkloadManifestProvider.GetManifests()
   at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.LoadManifestsFromProvider(IWorkloadManifestProvider manifestProvider)
   at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.InitializeManifests()
   at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.GetInstalledManifests()
   at Microsoft.DotNet.Cli.Commands.Workload.WorkloadCommandParser.ShowWorkloadsInfo(ParseResult parseResult, WorkloadInfoHelper workloadInfoHelper, IReporter reporter, String dotnetDir, Boolean showVersion)
   at Microsoft.DotNet.Cli.CommandLineInfo.PrintInfo()
   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, TimeSpan startupTime)
   at Microsoft.DotNet.Cli.Program.Main(String[] args)

Host:
  Version:      10.0.1
  Architecture: arm64
  Commit:       fad253f51b
  RID:          osx-arm64

.NET SDKs installed:
  10.0.101 [/usr/local/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 10.0.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 10.0.1 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  None

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

[pedro-leite]

I am facing the same issue on macOS (ARM64). On Windows on ARM, the workload set installed fine. Here are my commands:

$mauiVersion = dotnet --version
sudo dotnet workload install maui --version $mauiVersion

[mip1983]

Has started working now

[sergey-tihon]

what was the fix?

[ishisaka]

It has not been fixed in my environment.

[dusrdev]

It is still broken in my environment.

Everything is broken and it shows "running dotnet workload restore" might fix it, but it doesn't - it produces this:

sudo dotnet workload repair

Welcome to .NET 10.0!
---------------------
SDK Version: 10.0.101

Telemetry
---------
The .NET tools collect usage data in order to help us improve your experience. It is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.

Read more about .NET CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry

----------------
Installed an ASP.NET Core HTTPS development certificate.
To trust the certificate, run 'dotnet dev-certs https --trust'
Learn about HTTPS: https://aka.ms/dotnet-https

----------------
Write your first app: https://aka.ms/dotnet-hello-world
Find out what's new: https://aka.ms/dotnet-whats-new
Explore documentation: https://aka.ms/dotnet-docs
Report issues and find source on GitHub: https://github.com/dotnet/core
Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli
--------------------------------------------------------------------------------------
Workload repair failed: Workload manifest microsoft.net.workload.emscripten.current: 10.0.100/10.0.100 from workload version 10.0.100.1 was not installed. Running "dotnet workload repair" may resolve this.

Please re-open the issue or publish the fix.

[walnut-co]

I get this errors, somewhat related and also projects do not load in VS 2026

C:\Program Files\dotnet\sdk\10.0.101\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.ImportWorkloads.props(14,38): error MSB4242:
SDK Resolver Failure: "The SDK resolver "Microsoft.DotNet.MSBuildWorkloadSdkResolver" failed while attempting to resolve the SDK "Microsoft.NET.SDK.WorkloadAutoImportPropsLocator". Exception:
"System.IO.FileNotFoundException: Workload manifest microsoft.net.workload.mono.toolchain.net8: 10.0.100/10.0.100 from workload version 10.0.100.1 was not installed. Running "dotnet workload
repair" may resolve this.
at Microsoft.NET.Sdk.WorkloadManifestReader.SdkDirectoryWorkloadManifestProvider.GetManifests()
at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.LoadManifestsFromProvider(IWorkloadManifestProvider manifestProvider)
at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.InitializeManifests()
at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.GetInstalledWorkloadPacksOfKind(WorkloadPackKind kind)+MoveNext()
at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.CachingWorkloadResolver.Resolve(String sdkReferenceName, IWorkloadManifestProvider manifestProvider, IWorkloadResolver workloadResolver)
at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.CachingWorkloadResolver.Resolve(String sdkReferenceName, String dotnetRootPath, String sdkVersion, String userProfileDir, String globalJsonP
ath)
at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.WorkloadSdkResolver.Resolve(SdkReference sdkReference, SdkResolverContext resolverContext, SdkResultFactory factory)
at Microsoft.Build.BackEnd.SdkResolution.SdkResolverService.TryResolveSdkUsingSpecifiedResolvers(IReadOnlyList1 resolvers, Int32 submissionId, SdkReference sdk, LoggingContext loggingCont ext, ElementLocation sdkReferenceLocation, String solutionPath, String projectPath, Boolean interactive, Boolean isRunningInVisualStudio, SdkResult& sdkResult, IEnumerable1& errors, IEnumera
ble`1& warnings)""

Restore failed with 1 error(s) in 0.2s

[bddckr]

I've downloaded and installed SDK version 10.0.100 after installing 10.0.101 and that seems to have worked around the problem. dotnet --info shows both SDKs to be installed now, and the error is gone. In particular, --info shows that 10.0.101 is the SDK in use, but the workload installed is listing Installation Source: SDK 10.0.100 — note the version.

[dusrdev]

I've downloaded and installed SDK version 10.0.100 after installing 10.0.101 and that seems to have worked around the problem. dotnet --info shows both SDKs to be installed now, and the error is gone. In particular, --info shows that 10.0.101 is the SDK in use, but the workload installed is listing Installation Source: SDK 10.0.100 — note the version.

Thank you for the workaround. Although it's still problematic, especially if you have dotnet-sdk installed with homebrew, which doesn't let you have 2 versions side-by-side.

You could hack it by installing the other version outside of homebrew but it shouldn't be this way...

[RDI-Blake]

As a workaround, switching to manifests mode worked for me.

dotnet workload config --update-mode manifests