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

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

Closed
richlander opened this issue Jan 21, 2025 · 2 comments
Assignees
Labels
Area-Workloads untriaged Request triage from a team member

Comments

@richlander
Copy link
Member

I just installed latest .NET 9 SDK on a clean machine. I get this message. Is there a way we can change the product to avoid this?

An issue was encountered verifying workloads. For more information, run "dotnet workload update".
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Workloads untriaged Request triage from a team member labels Jan 21, 2025
@marcpopMSFT marcpopMSFT assigned baronfel and MiYanni and unassigned baronfel Jan 28, 2025
@marcpopMSFT
Copy link
Member

The first time you run a command in a new SDK, we check to see if your workloads need to be updated (this is because we can't install workloads as part of acquisition today and becomes the runtime workloads churn every month).

This check is throwing an exception but it's not clear how you ended up having broken workloads on a clean install: https://github.com/dotnet/sdk/blob/main/src/Cli/dotnet/Program.cs#L354

The message can be ignored and won't show up again but I agree it shouldn't be showing up at all in your case. @MiYanni added this two years ago and this is the first report of this I've seen. Definitely not enough to go on from that message. It indicates you wouldn't be able to build a maui app without taking action.

@MiYanni
Copy link
Member

MiYanni commented Mar 4, 2025

The check was added to help with keeping workloads up-to-date when updating SDKs. You can read the description here: #34322

That being said, I added the environment variable DOTNET_SKIP_WORKLOAD_INTEGRITY_CHECK that you can set to true to never have this run, and thus never see an error like this. It just means there was a problem validating the workloads (even though you said it was a clean machine). The reason the error says to run dotnet workload update is because that process properly routes exceptions and problems to the surface. This first-run check doesn't do that as it shouldn't impede the user's actual action they're trying to perform.

There's just not enough information here to be actionable. Closing.

@MiYanni MiYanni closed this as not planned Won't fix, can't repro, duplicate, stale Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Workloads untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

4 participants