Technical Anshu
Tutorials Blog
🔄 Windows Update

Removing Windows Components Can Break Windows Update Here Is Why

The custom ISO installed perfectly. Then the first Patch Tuesday arrived and every cumulative update failed. This page explains the servicing mechanics behind that story — and the build strategy that avoids it.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 8 minute read
🎥 Watch the complete video — building a custom Windows ISO, removing unwanted components and setting the bypass options step by step

Windows Update failures are the number one long-term complaint about heavily stripped custom ISOs, and they are predictable, not bad luck. Modern Windows updates are not simple file patches — they are transactions against the component store, and they assume the store is complete. Remove the wrong pieces and the update machinery cannot assemble what it needs. The honest news: you do not have to choose between a lean image and working updates. You have to choose where you cut.

Windows Update — cumulative update failing on a stripped image

2025-XX Cumulative Update for Windows 11 (KBxxxxxxx)

Install error — 0x800f081f

The source files could not be found. The component store is missing files this update expects.

Status: Downloaded 100% — install failed, rolling back

Error 0x800f081f on a custom image usually means the update went looking for a component that the builder removed.
1

How a Cumulative Update Actually Works

  1. Each monthly cumulative update contains fixes for thousands of components at once
  2. The servicing engine (CBS, the Component Based Servicing layer) checks the store, stages the new versions, and swaps them in as one transaction
  3. If a component the update expects is absent — or its manifest is missing — the transaction cannot complete and the whole update rolls back
  4. Feature updates are even stricter: they run a full compatibility and inventory pass before upgrading

This is why a stripped image can feel perfect for weeks. Nothing is wrong until the servicing system is asked to do real work.

2

The Removals That Cause It

  1. Deleting packages instead of disabling features — DISM package removal takes the manifests with it; turning a feature off keeps them
  2. Removing the update and servicing components themselves, sometimes marketed as "disable Windows Update permanently"
  3. Aggressive component-store cleanup — running cleanup with the reset-base option on a live install makes removed updates and components permanent and can block later repair sources; on an offline image, reset-base is not even supported — that limitation is Microsoft quietly telling you it is a one-way door
  4. Removing WinSxS "backup" copies with third-party cleaners that do not understand the store
3

Reading the Failure Like a Technician

  1. 0x800f081f — source files not found: the update needs files your image no longer has
  2. 0x800f0831 — a prerequisite package or manifest is missing from the store
  3. Check servicing health on the running system with Dism /Online /Cleanup-Image /ScanHealth, then repair against a matching untouched image as the source — one more reason to keep your original Microsoft ISO forever
  4. If repairs fail repeatedly, the honest fix is an in-place repair install using your tested custom ISO (or the stock one), not another round of cleaners
4

The Strategy That Keeps Updates Working ⭐

  1. Remove apps and provisioned content freely; remove features by turning them off; remove system packages almost never
  2. Never touch the servicing stack, the component store plumbing, WinRE, or the update components — the red zone from the component map page
  3. Slipstream the latest cumulative update into the image before installing, so the machine starts life already serviced
  4. As part of testing every build, install it in a VM and run Windows Update to completion — an ISO that has never survived an update is not finished
  5. Rebuild or refresh your master image monthly, after Patch Tuesday, instead of expecting a stripped image to service itself forever

🎥 Watch the Complete Video Guide

Every checkbox, removal and bypass option from this page is shown live in the full video — watch it end to end before you build your own ISO.

▶️ Watch Full Video
❓ Frequently Asked Questions

Can a feature update fix a component store I broke by removing packages?

Sometimes — a feature update lays down a fresh component store, which can heal removal damage. But it also wipes most of your customisations in the process, and it may refuse to start if the inventory check fails. Treat it as a rescue, not a maintenance plan.

Is turning a feature off as good as removing it?

For updates, it is strictly better: the component and its manifests stay in the store, so cumulative updates keep working, and you can turn the feature back on in seconds. The space saved by true removal is small compared to the servicing risk.

My custom ISO fails updates with 0x800f081f. What is the fastest honest fix?

Try a DISM repair using an untouched image of the same build as the source. If that fails, do an in-place repair install with a known-good ISO and rebuild your custom image using the layered strategy — disable and tune instead of deleting system packages.

This guide is based on the Technical Anshu video on building your own Windows ISO and removing unwanted components • Stuck on a step? Ask in the video comments — you will get help 🙏