Windows 10: DISM, unexpected behavior

Hi,



With the ISO mounted, run Explorer and look for the "Sources" folder in the mounted ISO. Select size from Explorer's menu bar.
Also select to show file extensions by clicking "View" and checking the "File name extensions" box if you haven't done so yet.

The first file in the list should be Install.wim or Install.esd.
In case it has the .esd extension you need to adjust the dism command line accordingly.
In my experience dism and .esd extentions do not work well together so I invariably convert .esd file to .wim ones.


Cheers, *Wink

 

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[/quote]

 

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,

 

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.

 

Hi,

Probably just a typo.

Cheers, *Wink

 

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.

 

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.

 

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

 

I have done many chkdsk and sfc before posting here.

Missing versions? Please, explain.

Thank-you.

 

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

 

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?

 

Hi,

Probably because the identifier package is missing.

Cheers, *Wink

 

Hi,

Missing from install.wim.
Try downloading from an official MS site.

Cheers, *Wink

 

The iso image was downloaded through the batch file offered by Kyhi: Downloads - Image Health - ToolsLib
I don't think Kyhi would be offering it if something was wrong with it.

Khyi: when/if you read this post, please, confirm that the iso image that your batch file downloads contains an identifier package in the install.wim file. Thanks

 

Hi,

Sorry, I thought you were using the one mentioned in post #1.

The one from Kyhi's tool should be fine.

Cheers, *Wink