NuGet Package restore failed Unable to find version '1.13.2'

The error message suggests that the NuGet package 'jQuery.UI' with version '1.13.2' cannot be found in the specified sources. This could be due to a few reasons, such as incorrect package source configuration or the package being removed from the source.

To troubleshoot this issue, you can try the following steps:

Verify Package Source: Check if the package source is correctly configured in your NuGet package manager settings. Ensure that the package source contains the required package version. You can do this by going to Tools > Options > NuGet Package Manager > Package Sources in Visual Studio.
Clear NuGet Cache: Clearing the NuGet cache can help resolve issues related to package retrieval. To do this, go to Tools > NuGet Package Manager > Package Manager Settings > General in Visual Studio. Click on the Clear All NuGet Cache(s) button and then try restoring the packages again.
Update NuGet Package Manager: Ensure that you have the latest version of the NuGet Package Manager installed. You can update it by going to Tools > Extensions and Updates in Visual Studio and checking for updates under the Updates tab.
Use a Different Package Source: If the package is not available in the current package source, try adding a different package source that contains the required package version. You can add a new package source by going to Tools > Options > NuGet Package Manager > Package Sources in Visual Studio.
Manually Install the Package: If all else fails, you can manually download the package from a reliable source and add it to your project. You can do this by downloading the package from the official NuGet website (https://www.nuget.org/packages) and then adding it to your project using the Manage NuGet Packages option in Visual Studio.

By following these steps, you should be able to troubleshoot and resolve the NuGet package restore failed error. If the issue persists, it might be worth reaching out to the package maintainer or seeking further assistance from the community or support forums.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Jayraj Chhaya2y ago
Accepted answer
The error message suggests that the NuGet package 'jQuery.UI' with version '1.13.2' cannot be found in the specified sources. This could be due to a few reasons, such as incorrect package source configuration or the package being removed from the source.

To troubleshoot this issue, you can try the following steps:
1. Verify Package Source: Check if the package source is correctly configured in your NuGet package manager settings. Ensure that the package source contains the required package version. You can do this by going to Tools > Options > NuGet Package Manager > Package Sources in Visual Studio.
2. Clear NuGet Cache: Clearing the NuGet cache can help resolve issues related to package retrieval. To do this, go to Tools > NuGet Package Manager > Package Manager Settings > General in Visual Studio. Click on the Clear All NuGet Cache(s) button and then try restoring the packages again.
3. Update NuGet Package Manager: Ensure that you have the latest version of the NuGet Package Manager installed. You can update it by going to Tools > Extensions and Updates in Visual Studio and checking for updates under the Updates tab.
4. Use a Different Package Source: If the package is not available in the current package source, try adding a different package source that contains the required package version. You can add a new package source by going to Tools > Options > NuGet Package Manager > Package Sources in Visual Studio.
5. Manually Install the Package: If all else fails, you can manually download the package from a reliable source and add it to your project. You can do this by downloading the package from the official NuGet website (https://www.nuget.org/packages) and then adding it to your project using the Manage NuGet Packages option in Visual Studio.
By following these steps, you should be able to troubleshoot and resolve the NuGet package restore failed error. If the issue persists, it might be worth reaching out to the package maintainer or seeking further assistance from the community or support forums.
+1