.NET: NETSDK1045: The current .NET SDK does not support targeting .NET 10.0

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

# Which SDK is picked for this folder, and which are installed?
dotnet --version
dotnet --list-sdks

# A global.json in this or a parent folder can pin an older SDK
find . .. -maxdepth 2 -name global.json -exec cat {} \;

# Install the SDK that matches the TargetFramework
# winget install Microsoft.DotNet.SDK.10
# Linux: https://dot.net/v1/dotnet-install.sh -c 10.0

# Or allow roll-forward to a newer installed SDK in global.json
# { "sdk": { "version": "10.0.100", "rollForward": "latestFeature" } }

# GitHub Actions: install it explicitly
# - uses: actions/setup-dotnet@v4
#   with: { dotnet-version: '10.0.x' }

How to diagnose C# errors

C# errors divide into compile-time and restore-time problems (NuGet resolution, target framework mismatches) and runtime problems dominated by null references and async misuse. The classic .NET production hazard is the sync-over-async deadlock, calling .Result or .Wait() on a task in a context with a synchronisation context, which manifests as a hang rather than an exception and is therefore much harder to spot.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

1. Run dotnet restore --verbosity detailed to see which feed each package resolved from. Most restore failures are a private feed with expired credentials, not a missing package.
2. Enable nullable reference types (<Nullable>enable</Nullable>) and treat the warnings as errors. This converts a whole class of production NullReferenceExceptions into compile failures.
3. For async hangs, search the codebase for .Result, .Wait() and .GetAwaiter().GetResult(). Replace with await all the way up, or use ConfigureAwait(false) in library code.
4. For EF Core, run dotnet ef migrations list to see which migrations the database believes are applied before generating a new one.
5. Capture a dump with dotnet-dump and inspect it with dotnet-gcdump / dotnet-counters when the process misbehaves without throwing.

Tools worth reaching for

• dotnet restore -v detailed
• dotnet ef migrations list
• dotnet-counters
• dotnet-dump

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

📖 learn.microsoft.com 📖 learn.microsoft.com

Related C# errors

• .NET: BinaryFormatter serialization and deserialization have been removed.NET 9 removed the BinaryFormatter implementation: the type still compiles, but every call…
• .NET: NuGet restore failedNuGet package restore failed. Network issues, invalid package source, or missing credentials.
• .NET: The framework 'Microsoft.NETCore.App', version '8.0.0' was not foundThe published application is framework dependent and the machine has no matching runtime…
• ASP.NET Core: Synchronous operations are disallowed. Call ReadAsync or setKestrel and IIS block synchronous reads and writes on the request and response bodies…
• ASP.NET Core: Unable to resolve service for type while activatingThe container was asked for a dependency nobody registered, so the controller or hosted…
• ASP.NET: Connection string not found in configurationThe application cannot find the database connection string in appsettings.json or environment…
• Blazor: JavaScript interop call failedA Blazor JS interop call threw an error because the JavaScript function was not found, threw…
• C#: Collection was modified; enumeration operation may not executeYou added or removed items in a List or Dictionary while a foreach was still walking it, and…

See all 18 C# errors →

Browse other categories

• HTTP 494xx client errors, 5xx server errors, redirects, headers and protocol problems.
• JavaScript 42npm resolution, async pitfalls, hydration, memory limits and runtime type…
• Database 41Connections, deadlocks, constraints, replication and memory limits.
• AI 35Rate limits, context windows, GPU memory and model-serving failures.
• Network 35Refused connections, timeouts, resets, MTU problems and port exhaustion.
• Python 35Imports, virtual environments, encoding, concurrency and dependency conflicts.
• Kubernetes 34CrashLoopBackOff, ImagePullBackOff, OOMKilled, RBAC, scheduling and storage.
• Docker 27Daemon connectivity, disk space, image pulls, ports and architecture mismatches.
• System 26Disk space, systemd units, file descriptors, OOM killer and scheduled jobs.
• Cloud 25IAM permissions, quotas, service limits and credential failures.
• Security 25JWT validation, CSRF, OAuth grants, SELinux, SSH host keys and CSP.
• TLS 24Untrusted authorities, expiry, hostname mismatch, chains and cipher negotiation.

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.