DISM, unexpected behavior

Kyhi · 18 Mar 2017

My Home version (winver = 14393.952) does not have either of these > windows\winsxs folders

CSI Payload Corrupt wow64_windows-staterepository_31bf3856ad364e35_10.0.10586.589_none_73e982455c99fff4\StateRepository.Core.dll

CSI Payload Corrupt x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.10586.589_none_def813130bab683e\gpedit.dll

It has

Code:

C:\Windows\WinSxS\wow64_windows-staterepository_31bf3856ad364e35_10.0.14393.953_none_40d03a269b6cd511\StateRepository.Core.dll
C:\Windows\WinSxS\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.14393.0_none_9f87fc8cc33c9bb6\gpedit.dll

ray5450 · 18 Mar 2017

fdegrove: yes, both iso's have \source\install.wim

kyhi: it seems to me that our folders are named differently according to the different version numbers each of us has. I would think they should be that way. Further, it seems that each Windows version knows the names and where they are,

TexasBandit · 20 Mar 2017

The DISM you entered has a syntax error. This could cause the 87 error condition. The command should read

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:E:\sources\install.wim:1

Omitting the LimitAccess parm will allow DISM to go to Windows Update for modules.

fdegrove · 20 Mar 2017

Hi,

Probably just a typo.

Cheers,

ray5450 · 20 Mar 2017

Hmm, yes....it looks like we all posted/reposted the line with the typo. However, my very first post shows the result of Error: 0x800f081f, without the typo. I tried it again, without the typo, with "install.wim:2" It still results in 'Error: 0x800f081f.

I think we can ignore Error 87. It is the one with the typo.

TexasBandit · 21 Mar 2017

In researching your problem ray5450, I came across something to try ...

From an admin command prompt, try running Chkdsk. If it finds errors, the problem files may be in corrupted sectors. If errors are found, then run Chkdsk /r if you have an HDD or Chkdsk /f if you have an SSD. After Chkdsk completes, then run sfc /scannow again. SSD's do not have sectors, so chkdsk /r will not work for them. It's a shot in the dark, but worth a try.

Kyhi · 21 Mar 2017

Seems to me > you are missing a few windows updates (version updates)

ray5450 · 21 Mar 2017

I have done many chkdsk and sfc before posting here.

Missing versions? Please, explain.

Thank-you.

ray5450 · 23 Mar 2017

I don't understand what you mean. The installed version is version 10586. The iso to do the repair is version 10586.

ray5450 · 29 Mar 2017

Review: I am using an iso file of Windows that is the same version I have. Said iso file is mounted. The path of the \sources folder in the said mounted iso file is used for DISM. DISM says that it cannot find the source files even though the path is correct. Why?