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

[marcpopMSFT]

The originally issue reported was likely a timing issue on release day since the issue went away. We'll review our release process to ensure there's a check that confirms that all dependent packages are available before we publish the workload set.

There are a few other issues reported in here and we can't reproduce any of them.

Were folks doing upgrades from .NET SDK 10.0.100 to 10.0.101 and that caused this problem? Can you try running dotnet workload update when you hit this? If that and restore are failing, try dotnet workload update --version 10.0.100? Can you ensure that the feeds you have configured include nuget.org? Do you have a workload set pinned in your global.json by any chance?

[walnut-co]

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

dotnet workload config --update-mode manifests

This solution worked for me, build is working and projects are loaded in VS 2026

[walnut-co]

The originally issue reported was likely a timing issue on release day since the issue went away. We'll review our release process to ensure there's a check that confirms that all dependent packages are available before we publish the workload set.

There are a few other issues reported in here and we can't reproduce any of them.

Were folks doing upgrades from .NET SDK 10.0.100 to 10.0.101 and that caused this problem? Can you try running dotnet workload update when you hit this? If that and restore are failing, try dotnet workload update --version 10.0.100? Can you ensure that the feeds you have configured include nuget.org? Do you have a workload set pinned in your global.json by any chance?

• this command dotnet workload update goes in circles, ask to use the command dotnet workload repair.
• I tried to upgrade projects from .net 8/9 to .net 10 after installing the latest VS 2026 update

[cysun]

I encountered this problem after using Homebrew to upgrade dotnet-sdk from 10.0.100 to 10.0.101 on a MacBook Air 13 M2. Uninstalling then installing dotnet-sdk again fixed the problem. Note that after you uninstall with "brew uninstall dotnet-sdk", you also need to manually remove the /usr/local/share/dotnet folder.

[sys27]

I encountered this problem after using Homebrew to upgrade dotnet-sdk from 10.0.100 to 10.0.101 on a MacBook Air 13 M2. Uninstalling then installing dotnet-sdk again fixed the problem. Note that after you uninstall with "brew uninstall dotnet-sdk", you also need to manually remove the /usr/local/share/dotnet folder.

Thanks, it solved the problem for me.

[bddckr]

Were folks doing upgrades from .NET SDK 10.0.100 to 10.0.101 and that caused this problem?

Yep, that's exactly what I was doing. But I'm getting the same issue now, even after uninstalling both versions, and then trying to install 10.0.101 again. I won't delete all files in /usr/local/share/dotnet, as I have older SDK versions installed that I need to continue to function.

dotnet workload update (with and without --version 10.0.100) and workload repair all give the following warning+error:

An issue was encountered verifying workloads. For more information, run "dotnet workload update".

Workload update 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.

dotnet --info shows the same error:

dotnet --info output

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

Runtime Environment:
 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 workloads installed:
System.IO.FileNotFoundException: 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.
   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:
  6.0.428 [/usr/local/share/dotnet/sdk]
  8.0.416 [/usr/local/share/dotnet/sdk]
  10.0.101 [/usr/local/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.36 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 8.0.22 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 10.0.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.8 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.33 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.35 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.36 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.8 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.10 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.11 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.12 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.13 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.14 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.15 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.16 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.17 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.18 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.19 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.20 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.21 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.22 [/usr/local/share/dotnet/shared/Microsoft.NETCore.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

[alexaka1]

I cannot use the .net SDK because of this. sudo dotnet workload update --version 10.0.100 doesn't work. sudo dotnet workload update doesn't work. sudo dotnet workload repair doesn't work.

Fully uninstalled 10.0.101, reinstalled. Same issue ☹️

I had to re-download .NET 9 for this and downgrade my projects.

[halllo]

Same problem.

[wazzamatazz]

The originally issue reported was likely a timing issue on release day since the issue went away. We'll review our release process to ensure there's a check that confirms that all dependent packages are available before we publish the workload set.

There are a few other issues reported in here and we can't reproduce any of them.

Were folks doing upgrades from .NET SDK 10.0.100 to 10.0.101 and that caused this problem? Can you try running dotnet workload update when you hit this? If that and restore are failing, try dotnet workload update --version 10.0.100? Can you ensure that the feeds you have configured include nuget.org? Do you have a workload set pinned in your global.json by any chance?

Same problem for me. SDK was updated from 10.0.100 to 10.0.101 via Homebrew. Running dotnet workload update and dotnet workload update --version 10.0.100 both fail:

Workload update 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.

Running dotnet workload repair fails with the same error, as do almost all other dotnet workload commands (e.g. dotnet workload clean). Running dotnet workload history does work, but doesn't give much to go on:

Id      Date                            Command           Workloads      Global.json Version      Workload Version
-----------------------------------------------------------------------------------------------------------------------------
1       01/01/0001 00:00:00 +00:00      InitialState                                              10.0.100-manifests.4c0ca8ba
2       12/11/2025 07:06:23 +02:00      update                                                    10.0.100.1
3       19/11/2025 22:26:36 +02:00      update                                                    10.0.100.1

dotnet --info output:

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:     Mac OS X
 OS Version:  26.1
 OS Platform: Darwin
 RID:         osx-arm64
 Base Path:   /usr/local/share/dotnet/sdk/10.0.101/

.NET workloads installed:
There are no installed workloads to display.
Configured to use workload sets when installing new manifests.

Host:
  Version:      10.0.1
  Architecture: arm64
  Commit:       fad253f51b

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

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.22 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.11 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 10.0.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.15 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.16 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.17 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.18 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.19 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.20 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.21 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.22 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.11 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 10.0.1 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  None

Environment variables:
  DOTNET_CLI_TELEMETRY_OPTOUT              [true]
  DOTNET_UPGRADEASSISTANT_TELEMETRY_OPTOUT [true]

global.json file:
  Not found

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

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

[xPaw]

Everyone is reporting this issue on macos, but I have the exact same issue on linux debian 13.

[candanbaykan]

I had the same issue on OpenSUSE Tumbleweed. I uninstalled all dotnet packages from my system then I deleted /usr/share/dotnet directory. Finally I installed dotnet-sdk-10.0 package again and I can work on my projects now.

[marcpopMSFT]

Triage: We're still not entirely sure what could be causing this. It sounds like every customer who hit this was upgrading from 10.0.100 to 10.0.101 and all were on Mac or Linux. We're wondering if one of our packages was malformed but it seems to be multiple different ones impacted.

Could you try deleting (save a copy first) the ./metadata folder under your sdk installs? That contains all the install records for workloads including manifests, workloads, and workload sets and on non-windows machines, should take you mostly back to a fresh state. That may also require deleting ./sdk-manifests/10.0.100/workloadsets which is the actual installed workload set if removing the metadata was not sufficient.

I'm just trying to get you back into a good state at least without having to fall back to manifest installs. Let us know if any of the above work and if you're willing to, please zip up your metadata folder so we can take a look.

You can also turn on Verbose mode when installing the workload to get more details. Set DOTNET_CLI_CONTEXT_VERBOSE=true

[HugoVG]

Had same issue on windows going from 10.0.0 -> 10.0.1

dotnet workload config --update-mode manifests

seemed to have fixed it

[wazzamatazz]

Had same issue on windows going from 10.0.0 -> 10.0.1

dotnet workload config --update-mode manifests

seemed to have fixed it

This fixed it for me as well on macOS!