The error 0x8a15000f means winget cannot read the source index it needs to search — usually because the Microsoft Store source's index file is missing, stale, or corrupted, or because you're running winget in a context (SYSTEM account, restricted network, or an old Windows build) where that source can't refresh. The fix is to reset the source and refresh it before searching again.

Winget stores local copies of every configured source in %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState, and the search command reads those local index files rather than querying the remote endpoint live. If a Windows update, a failed background refresh, or a profile migration deleted or truncated the cached index, winget throws 0x8a15000f — "data required by the source is missing" — before it can return any package results. Resetting the source regenerates the cache from Microsoft's CDN.

This guide walks through diagnosis, the reset-and-refresh fix, per-source handling for msstore and winget, the failure cases that survive a reset, and the specific builds and account contexts where this error tends to reappear.

What error 0x8a15000f actually reports inside winget

Winget's error codes follow a structured HRESULT layout, and the low 16 bits here decode to the APPINSTALLER_CLI_ERROR_SOURCE_DATA_MISSING condition in the open-source winget-cli repository on GitHub. That code fires when the Search or Available operation loads a source, finds the SourceAgreements and index metadata present, but the actual index.db or packages.msix data file the search traverses is absent or unreadable.

The distinction matters because it separates 0x8a15000f from sibling errors. An 0x8a15000e (invalid source data) or an HTTP 0x80190194 (404 from the source) points at a remote or schema problem; 0x8a15000f is specifically local file absence. Microsoft's win-get documentation on the winget source command treats this class of error as fixable with source reset and source update, without requiring a reinstall of App Installer.

A second subtlety: the "source" named in the error is the friendly name (winget or msstore), not the path. The winget source resolves to https://cdn.winget.microsoft.com/cache and the msstore source resolves to https://storeedgefd.dsx.mp.microsoft.com/v9.0. When the error names msstore, the index that's missing is the Store's catalog projection, which is refreshed by a different endpoint than the community repository's index — so a fix for one source doesn't always heal the other.

A third point worth holding onto: the error can appear mid-upgrade, not only on search. If winget upgrade --all begins, then the source index rotates on Microsoft's CDN during the run, the in-memory source handle becomes stale and the next package resolution can throw 0x8a15000f even though the first several packages succeeded. That is a timing failure, not a persistent corruption, and a simple re-run after winget source update typically resumes.

Why the source index goes missing on an otherwise healthy PC

The most common trigger is a Windows cumulative update or App Installer auto-update that replaces the Microsoft.DesktopAppInstaller package while winget was mid-refresh. If the refresh process is killed between index write and index commit, the cache directory ends up with a zero-byte or absent index.db, and every subsequent search fails until a reset rewrites it. This is the same class of race condition that Microsoft's winget-cli issue tracker has logged repeatedly since the 1.4 release line.

The second trigger is running winget as a service or under a different user context. SYSTEM-context execution (common in Intune scripts, SCCM, or scheduled tasks running as LocalSystem) has a different %LOCALAPPDATA% profile, and that profile may never have initialized a source index. The error is not that the source is broken — it's that the SYSTEM profile's LocalState folder is empty.

The third trigger is network interception that returns an empty body with HTTP 200. Corporate proxies, TLS-inspecting middleboxes, and some VPN clients have been observed to satisfy the HEAD check winget performs against the source URL and then deliver a truncated GET response. Winget caches what it receives, so the next search reads a partial index and throws 0x8a15000f.

The fourth trigger is manual tampering or half-applied cleanup: tools like CCleaner, or a user manually deleting %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe, remove the index without clearing winget's source metadata in settings.json, so winget believes the source is configured but has no data behind it.

The reset-and-refresh sequence that clears most 0x8a15000f failures

Work in an elevated PowerShell or Command Prompt, and do not run winget from inside an IDE terminal that inherits a different user's environment. Sequencing matters — reset before update, and update both sources before any search.

1: Confirm winget's version and source list with winget --version then winget source list. Both must return without error; if source list itself fails, the App Installer package is damaged and you should repair it first via Settings > Apps > App Installer > Advanced options > Repair. 2: Run winget source reset --force to wipe every cached index and rebuild source metadata from scratch. 3: Run winget source update to re-download the winget and msstore indexes from their respective CDNs. 4: Run winget source list again to confirm both sources show a populated updated timestamp. A source with no timestamp has not re-fetched. 5: Retry the original search with the exact package ID, not just a keyword — winget search --id Microsoft.PowerToys — to confirm resolution works end-to-end.

If step 2 returns "This command is not available", you are on a build older than App Installer 1.1, where source reset was introduced. Update App Installer through the Microsoft Store first, since older builds also lack the --force flag.

If step 3 hangs for more than 60 seconds, the machine likely can't reach cdn.winget.microsoft.com or storeedgefd.dsx.mp.microsoft.com. Test each endpoint with Test-NetConnection cdn.winget.microsoft.com -Port 443 from the same elevated session. A proxy that allows browsing but blocks Microsoft update CDNs will reproduce 0x8a15000f on every reset because the refresh returns zero bytes; in that case, configure winget's proxy explicitly with winget --proxy source update or add the CDN hostnames to the allowlist.

Managing “winget” and “msstore” sources separately

Most users never need to reset both sources at once, and it's worth knowing which one the error is naming before you act, because the two indexes refresh on different cadences — the community winget source typically rotates many times daily, while the msstore catalog is refreshed at a slower, less published rate.

Action Effect on winget source Effect on msstore source When to use it
winget source reset --force Deletes and rebuilds both indexes Deletes and rebuilds both indexes Both sources failing, or error names both
winget source update Re-fetches community index from cdn.winget.microsoft.com Re-fetches Store catalog from storeedgefd.dsx.mp.microsoft.com Single source stale; error names one source
winget source remove msstore No change Drops msstore entirely Store source consistently unreachable in a locked-down network
winget source add msstore No change Restores default https://storeedgefd.dsx.mp.microsoft.com/v9.0 Re-enabling Store installs after removal
winget source reset --name winget Rebuilds only winget No change Confirmed corruption isolated to community source

If the error text names msstore, winget source reset --name msstore --force will rewrite only that index; --name was added alongside the --force flag in the App Installer 1.4 line, so on 1.3.x you'll need to remove and re-add msstore instead. Removing msstore is a legitimate permanent mitigation for hosts on air-gapped or heavily filtered networks — you lose Store-only packages but keep the entire community catalog and all manifest-driven installs, which covers the majority of winget install use cases.

Do not remove the winget source itself. Microsoft ships it as the default and re-adding it requires the correct --type Microsoft.PreIndexed.Package argument and the full CDN URL; a typo in the re-add produces a new class of error that looks similar but isn't the same code.

When winget runs under SYSTEM, Intune, or a scheduled task

If winget search works interactively but the same command throws 0x8a15000f when run from a deployment script or an Intune Platform Script, the problem is the SYSTEM profile's LocalState, not the source itself — you're comparing two different caches, and only the SYSTEM one is empty.

The documented workaround is to run winget source reset --force inside the SYSTEM context once, before any package operation. In an Intune Platform Script, that means scheduling a pre-run step that provisions the SYSTEM winget environment, waits for source update to complete, and only then executes the package install. Without that warm-up, every SYSTEM-context call to a source-dependent command hits the missing-index error.

A cleaner modern path is the Microsoft.WinGet.Client PowerShell module, which ships Repair-WinGetPackageManager and handles the per-user source bootstrap in a way that survives service context. If you're authoring new automation, target the module's cmdlets rather than the raw winget.exe binary; the module is maintained by the same team and its repair function is designed to resolve 0x8a15000f-class failures without manual intervention.

Beware of copying a LocalState directory from an admin profile into SYSTEM as a shortcut. The index files embed session-specific identifiers, and a transplanted cache will often pass the source-list check but fail the first search with a schema mismatch, which looks like a fresh 0x8a15000f and wastes a diagnostic cycle. Regenerate, don't copy.

Checking whether an outdated App Installer build is behind it

App Installer ships through two channels: the Microsoft Store (slowest, most stable) and direct MSIX bundle downloads from the microsoft/winget-cli GitHub releases page (fastest, occasionally ahead of the Store). Version skew between those channels creates reproducible 0x8a15000f failures on specific feature updates.

Build line source reset available --force flag --name selector Known 0x8a15000f reports
1.1.x and earlier No No No Rare, older schema
1.2.x Yes No No Occasional during CDN rotation
1.3.x Yes Yes No Confirmed in winget-cli issues
1.4.x through 1.8.x Yes Yes Yes Reduced after reset/update fix
1.9.x and later Yes Yes Yes No unique regression as of this writing

Run winget --version and compare the first three segments against the GitHub release history. If you're on 1.2.x or 1.3.x on a Windows 10 21H2 or 22H2 machine, the older index schema is more likely to collide with a Store-delivered catalog refresh, and moving to the current Store build resolves the collision cleanly. Windows 11 23H2 and later ship with App Installer versions modern enough that this skew rarely bites.

If the Store won't push an update — a common side effect of a corrupted Store cache — the App Installer MSIX bundle can be installed through Add-AppxPackage from an offline download. Do not mix a GitHub bundle with a Store-signed package on the same machine; sideloading requires the Developer Mode or the Trusted App sideloading policy, and an unsigned replacement will fail to register, which produces a different error than 0x8a15000f but a messier one.

Failure cases a source reset does not repair

Error handling matters here because not every 0x8a15000f is a cache problem, and running source reset on a machine that has a network or permission fault wastes time and, on a narrow subset of builds, can leave the settings.json in a state that requires manual editing to recover from.

The most common non-repairable case is the proxy-with-200-empty-body scenario: reset deletes the cache, update re-fetches the same empty response, and the next search fails identically. Diagnose by opening https://cdn.winget.microsoft.com/cache/source.msix in a browser from the affected machine; if the file downloads at normal size, the network is fine and the error is local; if it downloads as a zero-byte file or an HTML error page, the proxy is the fault.

The second non-repairable case is a disk-permission fault on %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState. If the current user lacks write rights on that folder — common after profile migrations or folder redirection — winget may create the index in memory, fail to persist it, and report missing data on the next invocation. Repair via Settings > Apps > App Installer > Advanced options > Reset, which restores default ACLs.

The third case is a corrupted settings.json at %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json. If that file has a truncated "Source" or "Sources" block, winget's source manager reads a malformed entry and refuses to refresh. Back it up, delete it, and run winget source reset --force — winget will regenerate a default settings file with the two default sources.

Verifying the fix and locking it in against repeats

After the reset, run winget search powertoys followed by winget search --id Microsoft.PowerToys. Both should return the same package, and the ID search should complete in under two seconds on a healthy local index. If only the keyword search fails, the issue isn't the source — it's a corrupt local package manifest cache, which you clear by deleting %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Microsoft\WinGet\State\defaultState and re-running winget source update.

To lock against repeats, schedule a weekly winget source update from Task Scheduler under the same user context that normally runs winget, not SYSTEM. The refresh takes seconds on a healthy connection and prevents the cache staleness that precedes most 0x8a15000f occurrences. Keep App Installer on the Store channel unless you need a specific feature from a GitHub pre-release, and avoid running winget mid-update on cumulative patch Tuesdays — either wait for the restart, or run winget source reset --force immediately after the first login following the update.

For fleet management, build the reset and update into the image or provisioning script rather than trusting per-machine state. Microsoft's own WinGet configuration files support a source update prerequisite, and running that prerequisite at first login eliminates the class of failure where a freshly imaged machine throws 0x8a15000f on the first search because the OOBE context never triggered an index fetch.

FAQ

Does 0x8a15000f mean winget is broken and needs reinstalling?

No — reinstalling App Installer is almost never required. The code reports a missing local source index, not a broken binary, and winget source reset --force followed by winget source update rewrites that index from Microsoft's CDN. Reinstall only if winget --version itself fails or winget source list cannot enumerate any source.

Can I use winget offline if the source index is missing?

Not for search or install from a named source. Winget requires a populated local index to resolve package IDs, and offline scenarios rely on winget install --manifest with a downloaded YAML file plus its installer, which bypasses the index. Pure offline winget search is not a supported operation on any released build.

Is 0x8a15000f specific to Windows 11 or does it happen on Windows 10?

It occurs on both. Windows 10 21H2 and 22H2 report it more often because they ship older App Installer builds and receive cumulative updates on a different cadence from Windows 11. The fix is identical on both platforms; the difference is how frequently the underlying index staleness happens.

Why does the error keep returning after a reset?

A recurring error after a clean reset points at network interception (proxy returning empty responses with HTTP 200) or a per-context cache problem (SYSTEM profile versus interactive profile). Test the CDN URL directly from the affected context; if it returns zero bytes, the proxy is the fault, not winget.

Does the msstore source need separate treatment?

Yes, because it refreshes from storeedgefd.dsx.mp.microsoft.com rather than the community CDN. If only msstore fails, winget source reset --name msstore --force on App Installer 1.4 or later rewrites only that index. On locked-down networks, removing msstore permanently is a supported trade-off that keeps the community catalog intact.

How large is the winget source index, and does that affect the error?

The community index is a compressed SQLite-backed package on the order of tens of megabytes and grows as manifests are added. A truncated download — common on flaky connections — is a common cause of 0x8a15000f; verify the download completed by checking that winget source list shows a fresh updated timestamp after source update.

Can I automate the reset in an Intune script?

Yes, but run it in the SYSTEM context first, before any install command, and wait for winget source update to return success before proceeding. The Microsoft.WinGet.Client PowerShell module's Repair-WinGetPackageManager cmdlet automates the bootstrap and is the documented path for managed deployment scenarios.

What expires first — the source index or the manifest cache?

The source index goes stale faster because it's rebuilt from CDN on each refresh and collides with cumulative updates more often than the manifest cache does. A weekly winget source update maintains the index; the manifest cache is cleared only when individual package installs fail, not on a schedule.