FIELD NOTES

0x800F081F - CBS Store corruption

blognote

Windows Update failing with 0x800F081F? Force a repair in-place upgrade (no feature jump)

If you still have devices failing monthly quality updates with 0x800F081F, one pragmatic way to unblock them is to trigger a Windows Update “repair” (in-place upgrade) and then let the device update normally again. This only if you have exhausted all other means and nothing works.

In 2025 there was a known issue, message published by Microsoft, recognizing an issue caused by the June CU Message ID: WI1173218.

When to use this

Typical signs:

  • Windows Update repeatedly fails with 0x800F081F
  • Remediation attempts (retries, reboot, standard troubleshooting) do not stick

Quick fix: set AllowInplaceUpgrade = 4 and scan for updates

Set the following registry value:

  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
  • Name: AllowInplaceUpgrade
  • Type: DWORD
  • Data: 4 (commonly treated as an admin-set “repair requested” trigger in the field; validate in your environment)

PowerShell (run elevated):

reg.exe add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion" `
  /v AllowInplaceUpgrade /t REG_DWORD /d 4 /f

Then on the device:

  • Settings → Windows Update → Check for updates

Result: the device should pick up an in-place repair action (no feature upgrade required) and resume normal servicing afterward.

Operational notes (read before you push broadly)

  • Treat as a remediation change: it can consume bandwidth, disk space, and typically requires one or more reboots.
  • The in-place repair may not start immediately after the key is set; allow time for Windows Update orchestration.
  • In many cases, the value will revert/reset after the repair completes.
  • Pilot first on a small ring, especially on:
    • low-bandwidth sites
    • kiosk/VDI endpoints with tight maintenance windows
    • devices with limited free disk

Intune / SCCM packaging suggestion

Keep it simple: deploy a remediation that sets the key, then rely on the next update scan (user-initiated or scheduled).

Intune (Proactive Remediations) / SCCM package core step:

reg.exe add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion" `
  /v AllowInplaceUpgrade /t REG_DWORD /d 4 /f

Operationally, consider:

  • Targeting only devices that are behind in CU for more than 2 months in a row (reporting/telemetry-driven scope)
  • Create an application and publish it to the CompanyPortal or SoftwareCenter so the service desk or power users can trigger it them selves
  • Monitoring completion and dont let it run in loop. Best executed 'once' to fix the issue

Verification

After the repair runs:

  • Windows Update history should show an upgrade/repair-style activity and subsequent quality updates should install.
  • Confirm the original failing cumulative update (or the next month’s LCU) installs successfully.
  • Optionally verify the registry value is gone or reset after completion.

Rollback / safety note

If you set the key but decide not to proceed, remove it:

reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion" /v AllowInplaceUpgrade /f
← All articles