[SOLVED] Problems with Windows 10 Update including DISM Error: 0x800f081f

N

neXos

Member
Joined
Dec 13, 2015
Posts
7
Problems with Windows 10 Update including DISM Error: 0x800f081f
Noticed that sometimes on logine, i get the message "Failed to connect to a windows service...."

I tried running SFC /SCANNOW which gave me the following information:

Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.

I then found the suggestion to run the DISM command, which I did with the following parameters:

dism.exe /online /cleanup-image /scanhealth
dism.exe /online /cleanup-image /restorehealth

/scanhealth reported:
The component store is repairable.
The operation completed successfully.
/restorehealth reported:
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 Microsoft ? Official Home Page DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

This led me, eventually, to seeking your advice. I downloaded and ran SFCFix, but it never finished running. Here is the output:
Welcome to SFCFix by niemiro and sysnative.com.

Checking for updates . . .
No new update is available at this time.

Processing directive 1 of 1 (AutoAnalysis::)
Checking store directories . . .
Checking CBS.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .

Attempting repair . . .
Stage 1
Stage 2
Stage 3

Due to the nature of your corruptions, scan times have been extended by
approximately 15-20 minutes. Please be patient and allow the operation to
complete.

Deployment Image Servicing and Management tool
Version: 10.0.10586.0

Image Version: 10.0.10586.0
[==========================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 Configure a Windows Repair Source.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

I have attached the CBS folder. Any help would be appreciated.

Thank you.
 

Attachments

Hi and welcome to Sysnative. This is a common but easily resolved issue from updating to Windows 10 November update. Please do the following.

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

Step#2 - SFC Scan
1. Right-click on the Start
w8start.png
button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
 sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

4. Once this has completed please go to your Desktop and you will find CBS.txt => Right-click on this file and choose Send To...Compressed (zipped folder). Please upload this zipped file CBS.zip to this thread

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

Items for your next post
1. SFCFix.txt
2. CBS.txt
 

Attachments

First of all. I want to thank you for taking the time to help me.
I'm really appreciate it.


And second, here are the files.
 

Attachments

C:\WINDOWS\system32>dism.exe /online /cleanup-image /restorehealth


Deployment Image Servicing and Management tool
Version: 10.0.10586.0


Image Version: 10.0.10586.0


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


Thank u !
It worked !
 
Hi,

I seem to be having the same problem as neXos. Would you be able to assist me as well?

Thanks,
Valen
 
BrianDrab said:
Looks like everything is repaired. You are good to go.
Click to expand...

Well.... 4 month later and the problem returned..

Deployment Image Servicing and Management tool
Version: 10.0.10586.0


Image Version: 10.0.10586.0


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


Error: 0x800f081f


The source files could not be found.

Whay?? How?? Who??
I think i mait cry...:(
 
Ahhh, yes this is a different issue. This corruption is caused by the NVIDIA installer overwriting the opencl.dll file from Windows with its own. You can read more about this here and decide whether it's worth correcting.

Code: 
2016-03-02 20:00:54, Info                  CSI    00004ca3 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-03-02 20:00:54, Info                  CSI    00004ca4 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-02 20:00:54, Info                  CSI    00004ca5@2016/3/2:18:00:54.030 Primitive installers committed for repair
2016-03-02 20:00:54, Info                  CSI    00004ca6 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-03-02 20:00:54, Info                  CSI    00004ca7 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
 
Ok...read it.

For me it's effects Chrome
sometime (not all the time) chrome get really slow.. start in 10 minutes...download files in 10 minutes...
The only thing I found is this problem.
So i want to fix it...

I just follow the instruction in the other thread ?
Or i have to do something else?
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top