What .NET Is Rejecting
The RuntimeIdentifier you specified isn’t in the RID graph used by your SDK, so RID-specific resolution fails.
Fix the command
Replace the RID with a supported portable RID, following the NETSDK1083 docs.
Search the repo for RuntimeIdentifier settings in props, targets, and scripts.
Restore and build again:dotnet restore && dotnet build
Validation
Re-run the failing command and confirm the original code/message is gone, and confirm expected artifacts or outputs exist (packages restored, build/publish succeeds).
Typical Output
error NETSDK1083: The specified RuntimeIdentifier 'win10-x64' is not recognized. See https://aka.ms/netsdk1083 for more information.Why the Command Was Rejected
Usually this comes down to a deprecated or OS-version-specific RID such as win10-x64 was used instead of a portable RID such as win-x64, the RID is set indirectly by a package, props file, target, or script, or there is a typo in RuntimeIdentifier.
Re-run the Minimal Correct Command
NETSDK1083 no longer appears.
RID-specific publish produces the expected outputs.
Mechanism
Setting RuntimeIdentifier or RuntimeIdentifiers triggers RID-graph-based pack and asset selection. If the RID isn’t known, the SDK fails with NETSDK1083.
Avoid Command and Config Drift
To prevent this, standardize on portable RIDs and lint for deprecated ones, and pin SDK version and validate RID behavior during SDK upgrades.
Docs and source code
NETSDK1083 message template
User-facing RID not recognized message template. - GitHub
<data name="RuntimeIdentifierNotRecognized" xml:space="preserve">
<value>NETSDK1083: The specified RuntimeIdentifier '{0}' is not recognized. See https://aka.ms/netsdk1083 for more information.</value>
<comment>{StrBegins="NETSDK1083: "}</comment>
</data>