Fix VS Code Error: SDK Microsoft.NET.Sdk specified could not be found

You open Visual Studio Code, ready to dive into your latest C# project. You have your coffee, your playlist is on, and you hit build. But instead of a successful compilation, you're greeted with the dreaded red text: "The SDK 'Microsoft.NET.Sdk' specified could not be found."

If you are reading this, you are likely frustrated. I’ve been there. This error is one of the most common yet confusing roadblocks for .NET developers, especially when setting up a new environment or switching between project versions. It stops you dead in your tracks because, well, without the SDK, you can't build anything.

In this guide, I will walk you through exactly why this happens and providing the specific steps I use to fix it. We will get your IntelliSense back and your project building in no time.

Root Cause Analysis: Why is the SDK Missing?

Before we start pasting commands, it helps to understand why VS Code is throwing this fit. The error essentially means the .NET build tools (MSBuild) verify that you are trying to use a project type (like a Console App or Web API) that requires a specific Software Development Kit (SDK), but it cannot locate it on your machine.

In my experience, this usually boils down to three main culprits:

Bitness Mismatch: You have both x86 (32-bit) and x64 (64-bit) versions of .NET installed, and the priority in your system PATH is wrong.
global.json Conflict: Your project folder contains a global.json file pinning a specific SDK version that isn't installed.
Corrupted or Missing Installation: The SDK simply isn't there, or the installation didn't update the environment variables correctly.

The Solution: Step-by-Step Fix

Follow these steps in order. I have ordered them from the "most likely and easiest fix" to the "nuclear option."

1. Check Your Installed SDKs

First, let’s see what your computer thinks it has. Open your terminal (Command Prompt or PowerShell) and run:

dotnet --list-sdks

Scenario A: If the list is empty, you don't have the SDK installed. Go to the official .NET download page and grab the version your project targets (e.g., .NET 8.0).

Scenario B: If you see a list of SDKs, check if the version matches what your project needs (look at your .csproj file for <TargetFramework>).

2. The "x86 vs x64" PATH Conflict (Most Common Cause)

This is the sneaky one. On 64-bit Windows, if you accidentally installed the 32-bit (x86) version of the .NET SDK, it might register itself before the 64-bit version in your system's PATH variable.

Here is how I check for this:

Open terminal and type where.exe dotnet (on Windows).
Look at the order.
- Correct (usually): C:\Program Files\dotnet\dotnet.exe
- Problematic: C:\Program Files (x86)\dotnet\dotnet.exe appearing before the regular Program Files one.

The Fix:

Press Win key and type "Edit the system environment variables".
Click Environment Variables.
Under System variables, find Path and click Edit.
Look for C:\Program Files (x86)\dotnet\. If it is above C:\Program Files\dotnet\, move it down or delete it if you don't need 32-bit support.
Restart your terminal/VS Code for changes to take effect.

3. Inspect (or Delete) global.json

I once spent two hours debugging this error on a cloned repo, only to find a global.json file hiding in the root directory. This file tells the .NET CLI exactly which version to use. If it demands version 6.0.100 and you only have 8.0.100, it will fail with the "SDK not found" error.

What to do:

Check your project root for global.json.
Open it and check the "version" field.
Fix: Either install that exact version, or modify the file to match your installed version, or simply delete the file to let the tooling pick the latest installed version.

4. Restart the OmniSharp Server

Sometimes, VS Code just gets stuck. The underlying C# extension (OmniSharp) might have cached the "broken" state.

Open the Command Palette (Ctrl + Shift + P).
Type "Restart OmniSharp" (or "Developer: Reload Window").
Select it and wait for the project to load again.

Alternative Fixes

If the above didn't work, here are a few outliers I've encountered:

Visual Studio Installer: If you have full Visual Studio installed alongside VS Code, open the Visual Studio Installer, click Modify, and ensure the ".NET desktop development" or ".NET Core cross-platform development" workload is checked. Sometimes updating this repairs the global .NET instance.
The "Snap" Install (Linux Users): If you are on Ubuntu and installed dotnet via Snap, it can have alias issues. I recommend removing the snap package and installing via the Microsoft logic script or apt to ensure paths are standard.

[!TIP] Expert Insight: When in doubt, dotnet --info is your best friend. It gives you a detailed dump of the environment, including the generic runtime location and the architecture. If you see Base Path: C:\Program Files (x86)\dotnet\sdk... on a 64-bit machine, strictly follow Step 2 above. It solves 90% of the cases I see in forums.

Conclusion

The "SDK specified could not be found" error is annoying, but it is almost always a configuration or path issue rather than a broken project. By verifying your SDK path priority and checking for a restrictive global.json, you should be back to coding in C# within minutes.

Did this solve your issue? Or did you find a narrower edge case? Drop a comment below—I update this guide based on real-world feedback!