Unable to build on new system

[FroggieFrog]

Description

I have a new computer and tried to build my app, but I'm unable to do so.
Those messages are not helpful, because they do not work.

A dotnet workload update also does nothing.

Steps to Reproduce

No response

Link to public reproduction project repository

No response

Version with bug

8.0.7 SR2

Is this a regression from previous behavior?

Yes, this used to work in .NET MAUI

Last version that worked well

8.0.7 SR2

Affected platforms

Android, Windows

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

• Unable to build any maui apps (#4294), similarity score: 0.77
• Unable to build a project with net7 RC 1 (#10234), similarity score: 0.74
• After migrating to .NET8, mobile app has issues building on Visual Studio only on Windows (#19939), similarity score: 0.74
• Can't compile on Mac (#19039), similarity score: 0.74
• Empty MAUI project does not compile: dotnet workload install and restore for android workload fail in microsoft.android.sdk.windows.msi.x64::33.0.80 is not found in NuGet feeds https://api.nuget.org/v3/index.json (#16657), similarity score: 0.73

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[marcpopMSFT]

@FroggieFrog can you provide the output of dotnet workload --info and provide a binlog for the failure? Thanks. The binlog should point to which pack is missing and the --info command should give us details on what state your workloads are in.

[marcpopMSFT]

Per triage, having a diag output of the workload failure that list the specific missing packs would help us avoid having to ask for a binlog.

[marcpopMSFT]

dotnet build -getItem:MissingWorkloadPack collects the missing pack info and is fairly easy so going with that for now.

[FroggieFrog]

After an (automatic) update the issue is gone and I can't reproduce it.