From VS 2026 Enterprise - Unable to local any of the Nuget packages

Question

From VS 2026 Enterprise - Unable to local any of the Nuget packages

Madhusudhan M Kammar 30

Hi,

I am unable to load any of the nuget packages from my class library. It just keeps loading, but never loads.

I am using Visual Studio 2026 Enterprise V 18.4.0. And Class library version 10.

0 comments

3 answers

Your answer

Answer 1

Madhusudhan M Kammar 30

I am doing good Varsha! Thank you. Hope you are doing well too.

Issue is resolved by deleting below nuget cache folder.

%APPDATA%\NuGet
%LOCALAPPDATA%\NuGet

Thanks for your valuable time.

Varsha Dundigalla(INFOSYS LIMITED) 4,785 Reputation points Microsoft External Staff

2026-04-07T11:52:37.4266667+00:00

Thank you for your response. We will now proceed with closure of the thread as per your confirmation. If you encounter any further issues, please feel free to raise a new thread.

Answer 2

Varsha Dundigalla(INFOSYS LIMITED) 4,785 Microsoft External Staff

Thank you for reaching out.

When NuGet keeps loading indefinitely in Visual Studio, it usually means Visual Studio is waiting on a background operation that isn’t completing, such as contacting a package source or resolving package metadata. Unfortunately, the UI does not always show an error when this happens.

To understand exactly what is causing the loop, could you please try the steps below and share the outcome:

Open View → Output, then select Package Manager from the “Show output from” dropdown and reopen Manage NuGet Packages. Any errors or repeated messages shown there help identify what NuGet is waiting on.
Temporarily disable all custom or private package sources and keep only nuget.org enabled, then try opening the NuGet Package Manager again. This helps check whether a specific feed is blocking the load.
From a command prompt in the solution folder, run dotnet restore and let us know if it succeeds or shows any errors. This helps determine whether the issue is with package resolution itself or only with the Visual Studio UI.
If possible, let us know whether the loading happens on the Browse, Installed, or Updates tab, or on all of them.

These checks will help narrow down whether the issue is related to a package source, project references, cache data, or a Visual Studio NuGet UI behavior. Once we have this information, we can guide you with the next steps more accurately.

Please let us know if you require any further assistance, we’re happy to help. If you found this information useful, kindly mark this as "Accept Answer". So that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

Madhusudhan M Kammar 30 Reputation points

2026-03-31T15:14:39.1666667+00:00
Thanks for quick response. I tried the options you suggested, and posted the output below.

Open View → Output, then select Package Manager from the “Show output from” dropdown and reopen Manage NuGet Packages. Any errors or repeated messages shown there help identify what NuGet is waiting on.

I don't see any error message as such. it just loading..

Temporarily disable all custom or private package sources and keep only nuget.org enabled, then try opening the NuGet Package Manager again. This helps check whether a specific feed is blocking the load.

Same behavior - I don't see any error message as such. it just loading..

From a command prompt in the solution folder, run dotnet restore and let us know if it succeeds or shows any errors. This helps determine whether the issue is with package resolution itself or only with the Visual Studio UI.

Restore succeeded with 5 warning(s) in 608.6s ~...Tests.csproj : warning NU1900: Error occurred while getting package vulnerability data: Unable to load the service index for source https://api.nuget.org/v3/index.json. ~...csproj : warning NU1900: Error occurred while getting package vulnerability data: Unable to load the service index for source https://api.nuget.org/v3/index.json. ~...csproj : warning NU1900: Error occurred while getting package vulnerability data: Unable to load the service index for source https://api.nuget.org/v3/index.json. ~...csproj : warning NU1900: Error occurred while getting package vulnerability data: Unable to load the service index for source https://api.nuget.org/v3/index.json. ~...csproj : warning NU1900: Error occurred while getting package vulnerability data: Unable to load the service index for source https://api.nuget.org/v3/index.json.

Build succeeded with 5 warning(s) in 608.9s

If possible, let us know whether the loading happens on the Browse, Installed, or Updates tab, or on all of them.

loading doesn't happen on any of these tabs
Varsha Dundigalla(INFOSYS LIMITED) 4,785 Reputation points Microsoft External Staff

2026-04-01T09:44:07.61+00:00
Thank you for reaching out.

This issue is not related to missing packages or to an actual security problem in your project.

When you open Manage NuGet Packages, the IDE performs some background checks before showing the package list. One of these checks is downloading additional package metadata from the package source. This metadata is used to show extra information (such as advisory or audit data) but it is separate from normal package restore.

In your case, package restore itself is working correctly. This is why:

dotnet restore completes successfully

The build succeeds

Only warnings are logged, and no restore errors are reported

However, the warnings you see (NU1900) indicate that NuGet is unable to retrieve extra metadata from the package source. The message you shared (ResourceNotFound) confirms that the request reaches the server, but the response is not what NuGet expects. When this happens, NuGet keeps waiting for that metadata instead of failing clearly.

Because the background request never completes successfully, the NuGet Package Manager UI stays in a loading state. The command‑line restore logs a warning and continues, but the UI blocks while waiting for the same check to finish. This is why you don’t see errors in the Output window and why disabling other feeds does not change the behavior.

This behavior is documented as NU1900, which means NuGet could not download additional metadata from the package source due to an unexpected or blocked response:

https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1900

https://learn.microsoft.com/en-us/nuget/concepts/auditing-packages

In short, the NuGet UI is waiting for a background metadata call that does not complete in this environment, which is why it never finishes loading, even though restore works.

Please let us know if you require any further assistance, we’re happy to help. If you found this information useful, kindly mark this as "Accept Answer". So that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
Varsha Dundigalla(INFOSYS LIMITED) 4,785 Reputation points Microsoft External Staff

2026-04-06T10:17:44.1466667+00:00

Hope you're doing well. Could you please let us know if the issue still persists or if it has been resolved? If everything is working fine now, we’d appreciate it if you could mark the response as answered. We will proceed with the thread closure by 6th April, so we are hoping for your reply before that.

Answer 3

Try the following checks and fixes in Visual Studio 2026 when NuGet packages never finish loading for a class library:

Verify package sources

Open Tools > NuGet Package Manager > Package Manager Settings.
Go to Package Sources and ensure at least one valid source is enabled (for example, the official https://api.nuget.org/v3/index.json feed if applicable).
In the Manage NuGet Packages window for the project, confirm the correct Package source is selected in the dropdown. Visual Studio will use whichever source responds first, so if a source is offline or blocked, loading can hang. For more details on how Visual Studio uses sources, see the Package sources section.

Check for NU1101 / missing packages If the project is referencing packages that cannot be found on any configured source, Visual Studio may appear to hang while resolving them.

In Solution Explorer, expand Dependencies > Packages for the class library and confirm the package IDs and versions are valid.
Make sure the packages exist on the configured sources and that the IDs and versions are correct.
If using Semantic Versioning 2.0.0 packages, ensure the V3 feed https://api.nuget.org/v3/index.json is configured as a source. When packages truly cannot be found, NuGet raises NU1101. The documented fix is to correct the package ID/version and/or configure the right sources in NuGet.Config.

Clear NuGet caches Corrupted or stale cache entries can cause package operations to hang.

Go to Tools > NuGet Package Manager > Package Manager Settings.
On the General page, select Clear NuGet local resources.
Wait for the operation to complete (cannot be cancelled). Check the Output window (Show output from: Package Manager) for any errors. This clears http-cache, global-packages, temp, and plugins-cache folders and often resolves stuck restore or loading behavior.

Try restore from command line If the UI still hangs, try restoring via CLI to see if errors are surfaced:

Open a Developer Command Prompt in the solution folder.
Run nuget restore or dotnet restore (depending on project type).
If errors appear (for example, missing packages or sources), fix them as in step 2.

Confirm project package format

In Visual Studio, open Tools > Options > NuGet Package Manager > General.
Check the Default package management format (PackageReference vs packages.config).
For SDK-style projects, PackageReference is recommended and better for dependency resolution.

Offline / restricted network scenarios If working without internet or behind a strict firewall, ensure a reachable local/enterprise feed is configured, or use an offline package source as described in the NuGet FAQ for working without internet connectivity.

If, after these steps, the package list still never loads, collect the Package Manager output (from the Output window) and check for timeouts or source errors; those messages usually indicate which source or package is causing the hang.

References:

Share via

From VS 2026 Enterprise - Unable to local any of the Nuget packages

3 answers

Your answer