Windows 10: dism fails to fix corruption with 0x800f081f error

Background: HP ENVY Desktop 750-514 running Windows 10 build 17134.112
System has experienced some problems in the past but I was able to fix them with DISM.

Current Problem: Windows update KB4338819 runs and results in a stopcode of 0xc000021a. Automatic Repair does not help. I am able to use DISM with the /revertpendingactions option to undo the changes and boot the system. However, I cannot repair apparent corruption with DISM.

Most DISM commands complete successfully, but restorehealth results in errors (see below). The problem seems to be the inability to read the install.wim file. Most help sites recommended using the install.wim file but my DVD only had an install.esd file. Per the recommendation at https://www.wintips.org/how-to-extract-install-esd-to-install-wim-windows-10-8/ I extracted the correct install.wim for my Windows 10 Home edition and have been using that.

More details are below. Any help would be appreciated.

------------------------------------------

sfc /scannow completes successfully:

PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

-------------------------------------------------------------------

dism checkhealth:

PS C:\WINDOWS\system32> dism /Online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.112

The component store is repairable.
The operation completed successfully.

------------------------------------------------------------------------

dism scanhealth:

PS C:\WINDOWS\system32> dism /Online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.112

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

------------------------------------------------------------------------

dism start componentcleanup:

PS C:\WINDOWS\system32> dism /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.112

[==========================100.0%==========================]
The operation completed successfully.

----------------------------------------------------------------------------

dism analyzecomponentstore:

PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.112

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 8.01 GB

Actual Size of Component Store : 6.96 GB

Shared with Windows : 4.71 GB
Backups and Disabled Features : 2.25 GB
Cache and Temporary Data : 3.11 MB

Date of Last Cleanup : 2018-07-21 10:37:13

Number of Reclaimable Packages : 0
Component Store Cleanup Recommended : No

The operation completed successfully.

--------------------------------------------------------------

Using dism restorehealth with .esd file:

PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth /Source:ESD:F:\Sources\install.esd /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.112

[===========================85.5%================= ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

From C:\WINDOWS\Logs\CBS\cbs.log:
2018-07-21 10:42:20, Info CBS Exec: Addsource called, Session: 30679297_121067182, Client: DISM Package Manager Provider, from GPO: No, Path: C:\WINDOWS\system32\ESD:F:\Sources\install.esd
2018-07-21 10:42:20, Warning CBS The alternate source path directory could not be accessed [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
...and...
2018-07-21 10:42:47, Info CSI 00000007 Hashes for file member [l:11]'shell32.dll' do not match.
Expected: {l:32 ml:4096 b:62c2ae48193d374b7cab066e66350ebe3d6ded68861c136cbf5a9f278dc11996}.
Actual: {l:32 b:864021ed4af31856a9802211da0b5441da0f71c4e2ba7119bc02006e9550225b}.
...and...
2018-07-21 10:44:19, Info CBS Repr: Not able to find replacement file for component wow64_microsoft-windows-shell32_31bf3856ad364e35_10.0.17134.137_none_5834f4839c658742, file shell32.dll from any local source

NOTE: shell32.dll always shows up. Occasionally some other apparently random file shows up.

----------------------------------------------------------------------------------------------

dism restore health results:

PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\install.wim

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.112

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

---------

The first error indications in cbs.log are always:

Provider, external staging directory: (null), external registry directory: (null
2018-07-21 11:12:52, Info CBS Exec: Addsource called, Session: 30679301_1263717693, Client: DISM Package Manager Provider, from GPO: No, Path: C:\install.wim
2018-07-21 11:12:52, Warning CBS The alternate source path directory could not be accessed [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2018-07-21 11:12:52, Info CBS Failed to add new file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2018-07-21 11:12:52, Info CBS Failed to add alternate file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2018-07-21 11:12:52, Info CBS Failed adding alternate source directory [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2018-07-21 11:12:52, Info CBS Failed to Add Source using worker session [HRESULT = 0x8007007b]


Full CBS.log: CBS.log


Full DISM.log: DISM.log

:)

 

Error 0x800f081f in Win 10


In case you have any doubt, here is the article issued by Microsoft..................

https://support.microsoft.com/en-us/gwt/10164

direct copy from the article...................... ( this method is applicable to Windows 10 )

Solution for error 0x800f081f for Windows 8.1 or Windows 8

If you receive Windows Update error 0x800f081f, it means that Windows Update cannot determine the cryptographic service provider, or a file that Windows Update requires (named catalog store) is corrupted.
To resolve this problem, follow these steps:
Step 1: Use System File Checker to repair damaged Windows files
Use the System File Checker tool to repair damaged Windows files, and then run Windows Update again. To do this, follow these steps:

• Open an elevated command prompt.
• Run the following command:
  sfc /scannow
• Try to install update again.

For more information about the System File Checker tool, view Use the System File Checker tool to repair missing or corrupted system files.
Step 2: Run the DISM tool
If the problem continues, use the Deployment Image Servicing and Management (DISM) tool to fix Windows corruption errors. To do this, follow these steps:

• Open an elevated command prompt.
• Run the following command: DISM.exe /Online /Cleanup-image /Restorehealth.

Important When you use the /online option, DISM uses Windows Update to provide the files that are required to fix corruptions. However, if Windows Update service is broken, don’t use the /online option. Instead, use a running Windows installation as the repair source, or use a Windows side-by-side folder from a network share or from a removable media, such as the Windows DVD, as the source of the files. To do this, run the following command instead:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
Note Replace the C:\RepairSource\Windows placeholder with the location of your repair source. For more information about using the DISM tool to repair Windows, reference Repair a Windows Image.
To learn more about this tool, go to Fix Windows corruption errors by using the DISM or System Update Readiness tool.

 

SFC and DISM failed error 0x800f081f

Hello Shaileh,

Thank you for posting your question on Microsoft community.

I appreciate you for providing details about the issue and your efforts towards resolving it.

This issue may occur due to corrupt or missing Windows files.

I would suggest you to try running DISM tool as an administrator
and check if it helps.

Refer this article:

Windows Update error 0x800F081F

http://windows.microsoft.com/en-us/windows-8/windows-update-error-0x800f081f

(Also holds good for Windows 10)

I hope this information helps.

Please do let us know if you need any further assistance.

Thank you

 

Windows File Corruption Can't Be Fixed with Sfc or DISM, 0x800F081F


I was trying to fix a problem with my laptop after upgrading to Windows 10 which caused updates to fail. I went and looked at Microsoft support and tried using sfc and dism. Sfc /scannow found corrupt file but couldn't fix them. Dism /online /cleanup-image /restorehealth and dism /online /cleanup-image /restorehealth /Source:esd:E:\Sources\Install.esd:1 /limitaccess both came up with the error 0x800F081F. Another issue is that my computer won't shut off completely. The screen goes blank and the hard drive light is blank after the computer turns off, but the fan and the power button is still on.