Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
DISM RestoreHealth is a repair command, not an error diagnosis. When it fails in Windows 11, first save the complete output and hexadecimal code. Run the command from an elevated Command Prompt, let DISM use Windows Update when available, and then run sfc /scannow. If the message says that source files could not be found—especially error 0x800f081f—provide a valid Windows repair source instead of retrying the same command blindly.
What a failed RestoreHealth command actually tells you
DISM.exe /Online /Cleanup-Image /RestoreHealth services the Windows image currently running on the PC. It checks the component store and attempts to replace damaged or missing files. The word “RestoreHealth” describes the operation; it does not identify why the operation stopped.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | Buy on Amazon |
Read the final lines of the console output before choosing a fix. Record the complete hexadecimal error code, the sentence immediately before it, and whether the progress stopped while checking, locating source files, or applying a repair. Two computers can show “RestoreHealth failed” for entirely different reasons, so a solution for one code should not be applied to every failure.
Free tools Windows power users keep installed
One-click scans. No signup required.
For an online image, Microsoft’s normal repair path is Windows Update. DISM asks Windows Update for the files needed to repair the component store. If Windows Update is unavailable, blocked by policy, unable to reach Microsoft’s servers, or does not contain the required payload, DISM may report that it cannot find source files. That is when an explicit local, network, or removable-media source becomes relevant.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Prepare Windows 11 before running the repair
- Use an elevated Command Prompt. Open Start, type Command Prompt, select Run as administrator, and approve the User Account Control prompt. An ordinary command window may not have the rights required to service the image.
- Capture the exact failure. Take a screenshot or copy the final output, including the code. Do not paraphrase
0x800f081fas a generic “DISM error”; its documented meaning is narrower. - Keep the PC powered. Servicing can take several minutes and progress may pause while files are checked or downloaded. There is no reliable universal duration, so avoid interrupting a seemingly stalled operation too quickly.
- Check connectivity if you expect Windows Update to supply files. A metered, offline, or policy-restricted connection can prevent the default source from working.
- Identify any alternate source you plan to use. It must contain the files DISM needs and come from a Windows installation running the same operating-system version as the PC being repaired. A random ISO or unrelated Windows edition is not a guaranteed source.
Run Microsoft’s baseline repair sequence
Use this sequence first unless the error output already tells you that a source is missing. DISM repairs the component store; System File Checker then uses that repaired store to replace protected system files.
- Open an elevated Command Prompt as described above.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
Wait for the command to finish and note whether it reports a successful restore or an error code.
- After DISM completes, run:
sfc /scannow
Microsoft places DISM before SFC because SFC may need files from the component store. If DISM ends with an error, keep that code and investigate the source or servicing problem rather than assuming that a second SFC run proves the image is healthy.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Understand where DISM gets repair files
| Repair route | How DISM finds files | Use it when | Important limitation |
|---|---|---|---|
| Windows Update (default for an online image) | DISM contacts Windows Update for the required components. | The PC can reach Windows Update and policy allows the service to provide repair content. | A blocked, broken, or incomplete Windows Update path can leave DISM without the files it needs. |
| Explicit local, network, or removable-media source | You supply a folder containing a suitable Windows repair image or installation files with /Source. |
Windows Update cannot provide the payload, or you have a known-good Windows installation available. | The source must contain the required files and match the operating-system version. An arbitrary folder or mismatched image may fail. |
These routes are alternatives, not proof that one is universally better. Windows Update is simplest when it works. An explicit source gives you control over where DISM looks, but it adds the responsibility of selecting compatible files and entering the path correctly.
Fix “source files could not be found” and error 0x800f081f
What 0x800f081f means
Microsoft defines 0x800f081f as CBS_E_SOURCE_MISSING: “source for package or file not found, ResolveSource() unsuccessful.” In practical terms, DISM could not locate a required package or file. The code does not, by itself, prove whether Windows Update was unreachable, the alternate path was wrong, or the supplied files were incompatible; it identifies the missing-source condition.
Supply a known, compatible source
Microsoft’s support example uses this pattern:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess
C:RepairSourceWindows is a placeholder. Replace it with the actual folder that contains the Windows repair files. The source can be on the same drive, a network share, or removable media. Use a path that the elevated command prompt can read; quote a path containing spaces, for example /Source:"D:Windows RepairWindows".
The source computer or installation should run the same Windows operating-system version as the target. “Windows 11” alone is not enough to establish compatibility when builds or servicing levels differ. If the source is another working Windows installation, verify its version before relying on it. If it is installation media, make sure the media actually contains the files required for the target image rather than assuming every disc or ISO is interchangeable.
Know what /LimitAccess changes
/LimitAccess tells DISM not to contact Windows Update. Use it when you deliberately want DISM to rely only on the path supplied with /Source, or when policy or connectivity makes Windows Update unusable. Without /LimitAccess, DISM can still try Windows Update in addition to the explicit source.
Do not add /LimitAccess merely because a first attempt was slow. It removes a possible source. Conversely, if an organization blocks Windows Update and you have a complete local source, using it makes the intended repair route explicit.
When more than one source is specified
Microsoft Learn states that, when multiple source locations are provided, DISM takes files from the first location in which it finds them. Order therefore matters. Put the source you trust and have verified first, and avoid mixing unrelated folders that could supply inconsistent files.
Use CheckHealth and ScanHealth as diagnostics
RestoreHealth is the repair operation, but DISM also provides two diagnostic modes:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
DISM.exe /Online /Cleanup-Image /CheckHealthreports whether the component store is healthy, repairable, or non-repairable based on existing servicing records. It is a quick status check, not a full scan.DISM.exe /Online /Cleanup-Image /ScanHealthperforms a more extensive scan for component-store corruption. It can take longer than CheckHealth.
Use these commands when you need to distinguish a healthy image from one marked repairable or non-repairable, or when you want diagnostic context before selecting a source. They are not mandatory extra steps for every user who already has a clear RestoreHealth failure. If CheckHealth or ScanHealth indicates that the image is repairable, RestoreHealth is the operation intended to repair it. A non-repairable result requires more careful recovery planning rather than repeated identical retries.
Read the servicing log when the repair still fails
When a second attempt fails, retain the code and inspect the servicing record instead of making broad registry or permissions changes. Microsoft identifies %windir%LogsCBSCBS.log as the log that records issues DISM found or fixed.
- Open File Explorer and enter
%windir%LogsCBSCBS.login the address bar, or open it with an editor that can handle a large text file. - Search near the time of the failed command and look for the recorded error code, missing package, or source path.
- Compare the path in the log with the path you supplied after
/Source:. A spelling error, inaccessible network share, or folder that lacks the required files can explain a missing-source result. - Keep the relevant log section with the exact console code if you need to escalate the issue to an administrator or Microsoft support channel.
The log is evidence for the next decision; it is not a reason to delete servicing files or alter permissions indiscriminately. Those actions can create additional damage and are not established fixes for an unspecified RestoreHealth code.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A practical decision path for common outcomes
DISM completes successfully
Run sfc /scannow in the same elevated window. Record SFC’s final message. If Windows still shows symptoms, use the recorded results and any new error code to choose the next diagnostic step rather than rerunning RestoreHealth indefinitely.
DISM reports missing source files
Confirm whether Windows Update is available. If it is not, identify a same-version working installation, network location, or removable-media source, then rerun RestoreHealth with the corrected /Source path. Add /LimitAccess only when you want to prevent Windows Update from being used.
The command fails with a code other than 0x800f081f
Do not assign the CBS_E_SOURCE_MISSING meaning to that different code. Save the complete output, run CheckHealth or ScanHealth if useful, and consult CBS.log for the specific servicing event. The exact code determines which branch is justified.
The source path is correct but the repair still fails
Check that the source is readable and actually contains the needed files, and verify that the source operating system version matches the target. If multiple sources are configured, remember that DISM uses the first location where it finds a file. Reorder or simplify the source list so the intended location is unambiguous.
Windows Update is unavailable by policy
Use an approved alternate source rather than attempting to bypass organizational controls. A network or removable-media source can work when it is complete, accessible, and compatible with the target installation. Preserve the error code and log if the controlled environment still cannot supply the component.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Common mistakes that make RestoreHealth failures harder to solve
- Running without elevation: servicing the online image requires an administrator command prompt.
- Guessing from the command name: RestoreHealth is not synonymous with “missing source.” Diagnose the code and output first.
- Using any available ISO: compatibility and required files matter; a random image is not a universal repair source.
- Leaving a placeholder path unchanged:
C:RepairSourceWindowsis an example, not a folder Windows creates automatically. - Adding /LimitAccess without understanding it: the switch blocks Windows Update, so use it only when that is intentional.
- Stopping at DISM: Microsoft’s baseline sequence runs SFC after DISM so protected system files can be checked with the repaired component store.
- Repeating the same failed command: if the code and source conditions have not changed, another identical attempt is unlikely to provide new information.
- Making unrelated system changes: registry edits, permission resets, and service deletions are not evidence-based responses to an unspecified RestoreHealth error.
What to record before seeking further help
A useful escalation report is specific enough for someone else to reproduce the decision:
- The exact Windows 11 version and build shown on the affected PC.
- The complete command used, including any
/Sourceand/LimitAccessswitches. - The full hexadecimal error code and final console message.
- Whether Windows Update was reachable or restricted.
- The type and location of the alternate source, if one was used, and the source computer’s Windows version.
- The relevant timestamped lines from
%windir%LogsCBSCBS.log. - The final result of
sfc /scannow, if DISM completed far enough for you to run it.
Those details separate a missing-source problem from a different servicing failure and prevent well-meaning but irrelevant fixes.
The Bottom Line
Start with an elevated Command Prompt, capture the exact DISM code, and run the Microsoft sequence: DISM first, then SFC. Windows Update is the normal source for an online image. For a missing-source result such as 0x800f081f, provide a readable repair source from the same Windows version and use /LimitAccess only when you intentionally want to exclude Windows Update. If the repair still fails, use CBS.log and the recorded code to guide the next step.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

