WinGet Error 0x8a15000f on Fresh Windows 11 Builds

Why “Data required by the source is missing” Happens — and Why Running Elevated Is the Real Problem

If you’ve recently deployed a fresh install of Windows 11 (24H2 / 25H2) and tried to install software using WinGet, you may have hit the following error almost immediately:

Failed when opening source(s); try the 'source reset' command if the problem persists.
An unexpected error occurred while executing the command:
0x8a15000f: Data required by the source is missing

At first glance, this looks like a broken WinGet install, corrupted sources, or a networking issue.
In reality, the cause is far more subtle — and it catches even experienced Windows admins out.

This article explains what’s really happening, how to diagnose it properly, and why the fix is as simple as not running WinGet elevated.

The Scenario

A common setup looks like this:

Brand new Windows 11 25H2 installation
App Installer / WinGet freshly installed or bundled
Administrator PowerShell session
A simple command such as:

 winget install --id Microsoft.PowerShell --source winget

Instead of installing PowerShell 7, WinGet immediately fails with error 0x8a15000f.

Running winget source reset, reinstalling App Installer, or rebooting may not help — at least not consistently.

The Root Cause (The Part Most Docs Don’t Explain)

WinGet is a per‑user tool, not a system‑wide one

Although WinGet feels like a system package manager, it isn’t implemented like apt or yum.

Key facts that matter here:

WinGet is delivered via Microsoft App Installer
App Installer is a per-user AppX package
WinGet source configuration, cache, and agreements are stored per user profile

This means:

Running WinGet elevated switches context to the Administrator profile

On a fresh Windows build, that Administrator profile usually has:

No WinGet source agreement accepted
No local source metadata cache
No initial App Installer runtime state

When elevated WinGet tries to access the winget community source, it looks for data that simply does not exist in that profile yet — resulting in:

0x8a15000f: Data required by the source is missing

Nothing is actually “broken”.

Why It Works When Run as a Normal User

When you run the same WinGet command as a standard user, everything suddenly works.

This is because:

Interactive users trigger App Installer initialisation
The WinGet source agreement is accepted automatically
Source metadata is downloaded and cached
The user profile is fully prepared for WinGet operations

Once that user-level state exists, WinGet behaves exactly as expected.

This also explains why:

The error is far more common on fresh installs
The problem is more visible in Windows 11 24H2 / 25H2
Older machines “magically” don’t show the issue

Diagnosing the Issue Correctly

Before reinstalling anything, try this:

Step 1: Check whether you’re elevated

If your PowerShell window title includes Administrator, stop.

Step 2: Open a non‑elevated PowerShell

Step 3: Run the same command

 winget install Microsoft.PowerShell

If it works instantly, you’ve confirmed the diagnosis:

This is a per‑user WinGet state issue caused by elevation

Why This Became More Common in Recent Windows 11 Builds

Starting with later Windows 11 releases, Microsoft tightened:

AppX isolation
Per-user Store package registration
Source trust and agreement enforcement

As a result, WinGet no longer “self-heals” as easily when run under an uninitialised admin profile.
Fresh builds expose the problem immediately.

This isn’t a bug — it’s an architectural consequence.

Best Practice: How WinGet Should Be Used

✅ Default rule

Run WinGet non‑elevated.

Let WinGet request elevation only when required.

Example:

winget install Microsoft.PowerShell

If the installer needs admin rights, WinGet will prompt via UAC automatically.

✅ Interactive provisioning (recommended)

Ideal for manual builds and first‑run setups:

winget install Microsoft.PowerShell
winget install Microsoft.VisualStudioCode
winget install Google.Chrome

⚠️ Automation / RMM considerations

If you must run WinGet elevated (RMM tools, task sequences):

Ensure the admin profile has logged in interactively at least once
Or explicitly initialise WinGet sources for that profile:

winget source reset --force
winget source update

Even then, expect more edge cases than user‑context execution.

The Key Takeaway

This error:

0x8a15000f : Data required by the source is missing

does not mean:

WinGet is broken
App Installer is corrupt
Windows needs repairing

It means:

You ran WinGet in a user context that had never been initialised

Once you understand that WinGet is per-user first, system second, the behaviour makes complete sense.

If this article helped you, please leave a comment or consider making a donation to help keep this site running. Check out some of my other Windows 11 articles.