# error NU1101: Unable to find package 'PackageName'. No packages exist with this id in source(s): nuget.org, local-cache

- **ID:** `dotnet/nuget-package-restore-failure`
- **Domain:** dotnet
- **Category:** build_error
- **Error Code:** `NU1101`
- **Verification:** ai_generated
- **Fix Rate:** 92%

## Root Cause

NuGet package restore cannot locate the specified package in any configured package source, either due to typo, missing package, or source misconfiguration.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| dotnet 6.0 | active | — | — |
| dotnet 8.0 | active | — | — |
| NuGet 6.0 | active | — | — |
| NuGet 6.8 | active | — | — |

## Workarounds

1. **Verify the package name and version in the .csproj file. Use dotnet list package --outdated to check available versions.** (90% success)
   ```
   Verify the package name and version in the .csproj file. Use dotnet list package --outdated to check available versions.
   ```
2. **Add the correct NuGet source (e.g., private feed) using dotnet nuget add source. Example:** (85% success)
   ```
   Add the correct NuGet source (e.g., private feed) using dotnet nuget add source. Example:
   ```
3. **If the package is internal, build and pack it first, then reference the local .nupkg file. Example:** (80% success)
   ```
   If the package is internal, build and pack it first, then reference the local .nupkg file. Example:
   ```

## Dead Ends

- **** — If the package doesn't exist in the source, clearing cache won't help; it just re-downloads the same error. (80% fail)
- **** — May introduce untrusted packages or malware; doesn't solve the missing package issue. (95% fail)
- **** — NuGet restore may still try to fetch from configured sources and ignore local files if not properly referenced. (70% fail)