Windows 10 DISM error with SFCFix.exe (first 0x800f081f but now 14091)

Joined
Jun 29, 2016
Posts
8
Here's the log that SFCFix generated. Not sure exactly what's going on for it to give me 0x800f081f and now 14091.

Any help would be appreciated.
 

Attachments

Hi Syhota :)

My name is Aura and I'll be assisting you with your issue. Follow the instructions below please.

EndqYRa.png
System File Checker (SFC)
Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply;
  • On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select
    Spcusrh.png
    Run as Administrator
  • On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
  • On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
  • Enter the command below and press on Enter;
    Code:
    sfc /scannow
    Note: There's a space between "sfc" and "/scannow";
  • Once the scan is complete, enter the command below and press on Enter
    Code:
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  • A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't have the information from the scan anymore. So archive it and upload it as soon as you can.
 
Seems like SFC repaired a corrupt opencl.dll (standard corruption under Windows 10 Update 1511). Let's see what DISM have to report.

EndqYRa.png
DISM - Fixing Component Store Corruption
Follow the instructions below to run a DISM operation on your system.
  • On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
  • On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
  • Enter the command below and press on Enter;
    Code:
    DISM /Online /Cleanup-Image /RestoreHealth
  • Let the scan run until the end (100%). Depending on your system, it can take some time;
  • Copy the C:\Windows\Logs\DISM folder and C:\Windows\Logs\CBS\CBS.log file on your Desktop, then right-click on it, go to Send to... and select Compressed .zip archive;
  • Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the DISM scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.
 
Alright, so DISM reported that it couldn't replace two payloads. Here goes.

myjIXnC.png
SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.
  • Download SFCFix and move the executable on your Desktop;
  • Download the attached SFCFix.zip and move the archive to your Desktop;
    Note: Make sure that the file is named SFCFix.zip, do not rename it.
  • Save any work you have open, and close every programs;
  • Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it;
    mMabJGT.gif
  • SFCFix will launch, let it complete;
  • Once done, a file will appear on your Desktop, called SFCFix.txt;
  • Open the file, then copy and paste its content in your next reply;
SFCFix.zip
 
Here's the output.

Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-07-01 02:57:47.280
Microsoft Windows 10 Build 10586 - amd64
Using .zip script file at C:\Users\Syhota\Desktop\SFCFix (1).zip [0]







PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-s..riencehost.appxmain_31bf3856ad364e35_10.0.10586.0_none_89600324a945b715
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-embedded-shelllauncher_31bf3856ad364e35_10.0.10586.0_none_d0de4edef19b4b94


Successfully copied file C:\Users\Syhota\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-s..riencehost.appxmain_31bf3856ad364e35_10.0.10586.0_none_89600324a945b715\ShellExperienceHost.exe to C:\WINDOWS\winsxs\amd64_microsoft-windows-s..riencehost.appxmain_31bf3856ad364e35_10.0.10586.0_none_89600324a945b715\ShellExperienceHost.exe.
Successfully copied file C:\Users\Syhota\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-embedded-shelllauncher_31bf3856ad364e35_10.0.10586.0_none_d0de4edef19b4b94\ShellLauncherConfig.exe to C:\WINDOWS\winsxs\amd64_microsoft-windows-embedded-shelllauncher_31bf3856ad364e35_10.0.10586.0_none_d0de4edef19b4b94\ShellLauncherConfig.exe.


Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-s..riencehost.appxmain_31bf3856ad364e35_10.0.10586.0_none_89600324a945b715
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-s..riencehost.appxmain_31bf3856ad364e35_10.0.10586.0_none_89600324a945b715
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-embedded-shelllauncher_31bf3856ad364e35_10.0.10586.0_none_d0de4edef19b4b94
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-embedded-shelllauncher_31bf3856ad364e35_10.0.10586.0_none_d0de4edef19b4b94
PowerCopy:: directive completed successfully.







Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-07-01 02:57:47.671
Script hash: /X0FeFZ6M7rRUgSk466F0OYsz4cANHNbWJ3lb5J/+/I=
----------------------EOF-----------------------
 
Alright :) Now please run SFC and DISM again. You only need to provide me the CBS.log after running DISM.
 
DISM didn't return any corrupt payload or manifest, so it looks okay to me as well! No problem Syhota, you're welcome :)
 

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

Back
Top