Local source of nuget packages doesn't exist

The package source is probably defined in %appdata%\nuget\nuget.config. Edit this file in your favourite xml/text editor (VSCode perhaps?). You should see under a package sources element an add element that adds that file path. Comment out or delete that line.

If it's not in that file, try running dotnet restore --verbosity normal or just dotnet restore -v n. If you still only get an error message, try running dotnet new nugetconfig, or temporarily create the C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\ directory. NuGet, with normal verbosity, outputs the list of all nuget.config files that were read. Open each one until you find which one defines the local source that does not exist, so you can edit it and remove it. Or just keep the empty directory.

It's also possible that the package source is defined in a MSBuild file, rather than a nuget.config file. If that's the case, you might need to run dotnet msbuild -pp to generate a pre-processed file (the msbuild with all imports evaluated to create a single, "stand-alone" msbuild file). You then search that file for the path that doesn't exist, then scroll up until you find a comment saying what file it was defined in. You then then choose whether you edit that file.

However, it may just be easier to create an empty directory at the path.

I had a similar error preventing nuget restore command from working but with a different path:

C:\Program Files\dotnet\sdk\3.1.100\NuGet.targets(132,5): error : The local source C:\work\nuget doesn't exist.

I fixed it by removing that path from:

Visual Studio ▶ Tools ▶ Options ▶ Nuget Package Manager ▶ Package Sources

Open a PowerShell window and enter the following code: dotnet new nugetconfig

I have used more visual method for resolving this issue look

✍edit1: Possible reason, your project may have offline packages referenced to your very first computer. And than, when you go trough another computer, it cant recognise the local source path of your offline packages.

1. 
2. 
3. 
4. it is done!

Although the error seems not to be related to nuget, it is actually related.

Open PowerShell and run the following command:

dotnet new nugetconfig

Because the message says that the folder doesn't exist, I created it, and the problem disappeared. Yes, it was so simple like that.

BTW there is a discussion on GitHub on similar trouble, and Rob Relya from Microsoft wrote:

This is by design behavior. We fail restore if any of your sources are not reachable. We don't want to create a folder for you, in case it was a typo.

From my point of view, it's OK.

I also had the same issue on DevOps (image 1,2) .net core restore task. I resolved this by just removing the Offline package reference (image 3) from the NuGet.config file.

image 1

image 2

image 3

I had trouble understanding the answers, maybe some of them had the solution. What helped me in the end:

I edited C:\Windows\System32\config\systemprofile\AppData\Roaming\NuGet\NuGet.Config
and removed <packageSources> with the value "..\NuGet.Config"

Not sure how it got there, the actual value might be different for everyone.

I was upgrading my dontet MVC project from .Net core 2.2 to 3.1 and adding a reference to the Microsoft.Extensions.Configuration.AzureAppConfiguration. when I had this issue. All I did is removed the "add key="Local" value=".References" from nuget.config and the issue is solved. I was able to reference the package,