[SOLVED] CMD Error when running dism 0x800f081f

Gua · Oct 8, 2015

Hi, while trying to repair refreshment problems with my Windows 10 Machines I came across this Error: 0x800f081f when I was running the

dism /online /cleanup-image /scanHealth

On an elevated Cmd. Prompt.

Log is here:

https://www.wetransfer.com/downloads/dafbee1fcf7a03c33e8f5979f668f5aa20151008123120/831bdd

xilolee · Oct 8, 2015

Try the WindowsUpdateDiagnostic.diagcab

Gua · Oct 9, 2015

Thanks, it looks like this did the trick!

xilolee said:
Try the WindowsUpdateDiagnostic.diagcab

xilolee · Oct 9, 2015

:smile9:

I.e., did the DISM complete its task?
And what about the SFC result, now?

Gua · Oct 9, 2015

Yes the Dism completed with no errors.

SFC continues with the same results.

4 cannot repair errors:

Found: {l:32 b:6BlfjhjB8GArq4gx7XplKy5YYo32soAk03mrg1eaRRY=} Expected: {l:32 b:4MfTT3V5JEdirlo3HtVRoiged94J/wsbIs0bGYLXdog=}
2015-10-09 14:45:13, Info CSI 000048c9 [SR] Cannot repair member file [l:24{12}]"adcjavas.inc" of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-RDS-CE-JVS, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch

Found: {l:32 b:6BlfjhjB8GArq4gx7XplKy5YYo32soAk03mrg1eaRRY=} Expected: {l:32 b:4MfTT3V5JEdirlo3HtVRoiged94J/wsbIs0bGYLXdog=}
2015-10-09 14:45:14, Info CSI 00004900 [SR] Cannot repair member file [l:24{12}]"adcjavas.inc" of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-RDS-CE-JVS, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-10-09 14:45:14, Info CSI 00004901 [SR] This component was referenced by [l:370{185}]"Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-enduser~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-enduser-Deployment"
2015-10-09 14:45:14, Info CSI 00004902 Hashes for file member \??\C:\Program Files (x86)\Common Files\System\msadc\adcjavas.inc do not match actual file [l:24{12}]"adcjavas.inc" :

Found: {l:32 b:6BlfjhjB8GArq4gx7XplKy5YYo32soAk03mrg1eaRRY=} Expected: {l:32 b:4MfTT3V5JEdirlo3HtVRoiged94J/wsbIs0bGYLXdog=}
2015-10-09 14:46:09, Info CSI 00005162 [SR] Cannot repair member file [l:24{12}]"adcjavas.inc" of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-RDS-CE-JVS, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-10-09 14:46:09, Info CSI 00005163@2015/10/9:12:46:09.267 Primitive installers committed for repair
2015-10-09 14:46:09, Info CSI 00005164 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-m..nts-mdac-rds-ce-jvs_31bf3856ad364e35_10.0.10240.16384_none_0d9b4ea224376197\adcjavas.inc do not match actual file [l:24{12}]"adcjavas.inc" :

Found: {l:32 b:6BlfjhjB8GArq4gx7XplKy5YYo32soAk03mrg1eaRRY=} Expected: {l:32 b:4MfTT3V5JEdirlo3HtVRoiged94J/wsbIs0bGYLXdog=}
2015-10-09 14:46:09, Info CSI 00005165 [SR] Cannot repair member file [l:24{12}]"adcjavas.inc" of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-RDS-CE-JVS, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-10-09 14:46:09, Info CSI 00005166 [SR] This component was referenced by [l:370{185}]"Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-enduser~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-enduser-Deployment"
2015-10-09 14:46:09, Info CSI 00005167 Hashes for file member \??\C:\Program Files (x86)\Common Files\System\msadc\adcjavas.inc do not match actual file [l:24{12}]"adcjavas.inc" :

xilolee said:
:smile9:

I.e., did the DISM complete its task?
And what about the SFC result, now?

xilolee · Oct 9, 2015

Did you use the (dism) RestoreHealth parameter?
If yes, wait for someone of the Sysnative Staff (and they will help you with that sfc error).
If no, I'd re-try the dism command with the RestoreHealth parameter, this time.

Gua · Oct 9, 2015

Yes, same errors than before and the refresh is needed after I reboot

Aura · Oct 9, 2015

Hi Gua :)

My name is Aura and I'll be assisting you with your issue. There's only one file that needs to be replaced.

Code:

2015-10-08 14:12:56, Info                  CSI    0000514d Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-m..nts-mdac-rds-ce-jvs_31bf3856ad364e35_10.0.10240.16384_none_0d9b4ea224376197\adcjavas.inc do not match actual file [l:24{12}]"adcjavas.inc" :
  Found: {l:32 b:6BlfjhjB8GArq4gx7XplKy5YYo32soAk03mrg1eaRRY=} Expected: {l:32 b:4MfTT3V5JEdirlo3HtVRoiged94J/wsbIs0bGYLXdog=}
2015-10-08 14:12:56, Info                  CSI    0000514e [SR] Cannot repair member file [l:24{12}]"adcjavas.inc" of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-RDS-CE-JVS, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch

I'll source it and post a fix once I get home, since I don't have a Windows 10 computer at work.

Aura · Oct 10, 2015

Alright, follow the instructions below please.

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;
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

Gua · Oct 12, 2015

Hi Aura, thanks for the help, here are the results:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-10-12 11:02:24.102
Microsoft Windows 8.1 - amd64
Using .zip script file at E:\Freefall\Downloads\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\x86_microsoft-windows-m..nts-mdac-rds-ce-jvs_31bf3856ad364e35_10.0.10240.16384_none_0d9b4ea224376197\adcjavas.inc

Successfully copied file C:\Users\Freefall\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-m..nts-mdac-rds-ce-jvs_31bf3856ad364e35_10.0.10240.16384_none_0d9b4ea224376197\adcjavas.inc to C:\WINDOWS\winsxs\x86_microsoft-windows-m..nts-mdac-rds-ce-jvs_31bf3856ad364e35_10.0.10240.16384_none_0d9b4ea224376197\adcjavas.inc.

Successfully restored ownership for C:\WINDOWS\winsxs\x86_microsoft-windows-m..nts-mdac-rds-ce-jvs_31bf3856ad364e35_10.0.10240.16384_none_0d9b4ea224376197\adcjavas.inc
Successfully restored permissions on C:\WINDOWS\winsxs\x86_microsoft-windows-m..nts-mdac-rds-ce-jvs_31bf3856ad364e35_10.0.10240.16384_none_0d9b4ea224376197\adcjavas.inc
PowerCopy:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 10 datablocks.
Finish time: 2015-10-12 11:02:24.442
Script hash: ikq6aopkPeMr0VL6X1gVgIYzFvA2cMWQoyO0wnJxXLc=
----------------------EOF-----------------------

Aura said:
Alright, follow the instructions below please.

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;

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

Aura · Oct 12, 2015

Now, let's run SFC to see if the replacement is accepted.

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

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.

Gua · Oct 12, 2015

Please see the file here:

https://www.wetransfer.com/downloads/e6b0bd760928ba46f46045f1c72cc63620151012155222/2bb36b

Thx

Aura said:
Now, let's run SFC to see if the replacement is accepted.

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

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.

Aura · Oct 12, 2015

It seems like the replacement was accepted. DISM should return a success message now.

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.

Gua · Oct 13, 2015

Restore operation completed succesfully.

Here is the link to the files

https://www.wetransfer.com/downloads/3b40ea55882f07bcf36a4f55fbb55c6020151013085511/d9be14

Aura said:
It seems like the replacement was accepted. DISM should return a success message now.

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.

Aura · Oct 13, 2015

DISM indeed returns a clean SURT report.

Code:

=================================
Checking System Update Readiness.


Summary:
Operation: Detect and Repair 
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption:	0
	CBS Manifest Corruption:	0
	CBS Metadata Corruption:	0
	CSI Manifest Corruption:	0
	CSI Metadata Corruption:	0
	CSI Payload Corruption:	0
Total Repaired Corruption:	0
	CBS Manifest Repaired:	0
	CSI Manifest Repaired:	0
	CSI Payload Repaired:	0
	CSI Store Metadata refreshed:	True

Total Operation Time: 230 seconds.

Was there anything else? :)

Gua · Oct 13, 2015

Thanks a lot.

Yes, there is something else, I already started a threat about it and they told me to first solve this.

I have an annoying refresh problem with windows 10 and before that with W7, basically I have to hit F5 every time I create a folder, paste a document, download something to the desktop....etc...

Here is the link to the post:

https://www.sysnative.com/forums/wi...esh-desktop-folders-dont-work.html#post133827

Aura said:

DISM indeed returns a clean SURT report.

Code:

=================================
Checking System Update Readiness.


Summary:
Operation: Detect and Repair 
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption:    0
    CBS Manifest Corruption:    0
    CBS Metadata Corruption:    0
    CSI Manifest Corruption:    0
    CSI Metadata Corruption:    0
    CSI Payload Corruption:    0
Total Repaired Corruption:    0
    CBS Manifest Repaired:    0
    CSI Manifest Repaired:    0
    CSI Payload Repaired:    0
    CSI Store Metadata refreshed:    True

Total Operation Time: 230 seconds.

Was there anything else? :)

Aura · Oct 13, 2015

Alright, I'll take a look at your other thread today when I can, since I'm off to work now

For now, I'll be marking this one as solved :)

Search

Search

[SOLVED] CMD Error when running dism 0x800f081f

Gua

Contributor

xilolee

Moderator

Gua

Contributor

xilolee

Moderator

Gua

Contributor

xilolee

Moderator

Gua

Contributor

Aura

Sysnative Staff, Security Analyst

Aura

Sysnative Staff, Security Analyst

Gua

Contributor

Aura

Sysnative Staff, Security Analyst

Gua

Contributor

Aura

Sysnative Staff, Security Analyst

Gua

Contributor

Aura

Sysnative Staff, Security Analyst

Gua

Contributor

Aura

Sysnative Staff, Security Analyst