Windows 10: DISM, unexpected behavior

@TexasBandit

Thank you but WIM solution didn't worked...now and then... i started to tjink it's a problem related to Insider 10.0.15048.0 with MISSING Microsoft-Windows-TestRoot-and-FlightSigning-package~31bf3856ad364e35~amd64~~10.0.15048.0

Here's results:

Same problem....If you read carefully i've ALSO tested with a MOUNTED Install.wim and..failed...

 

When I put Dism /online /cleanup-image /restorehealth /source:wim:e: \sources\install.wim:1 /limitaccess (mounted e: ) this is what happens:
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
[==========================100.0%==========================]
Error: 0x800f081fThe 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 MSN France: Hotmail, Outlook, actualités, météo, divertissement DISM log file can be found at C:\windows\Logs\DISM\dism.log

Why will this not work?

 

If the Install.wim ( mounted or not) does not contain the original copy of the corrupted file or package..

The source file will not be found...

Image-Health creates Detailed txt file on your desktop - detailing the corrupt files names

If it really bothers you - you can do an in-place repair, upgrade or a system Refresh..

Just run the setup.exe of your windows setup media from within your current OS.

Windows will upgrade itself with a fresh copy of the windows OS, keeping your files and settings..
And placing the corrupted windows OS in the windows.old folder

 

I've read on latest Insider builds it's MISSING Microsoft-Windows-TestRoot-and-FlightSigning-package

 

Thus source file not found...

Problem is, you hijacked this support thread with your insider preview issues...
Your issue is not the same, you are using Testing Software...
He is using Retail Release Software...

 

kyhi: are you saying that even though my installed version and the iso version are both 10.0.10586.0, they still do not match?

 

No, I was not referring to you...
I have not seen your log (txt file) of the corrupted files..
Just a summary stating 14 corrupt packages..

My Image-Health script runs all proper commands and create detail.txt files on your desktop..
then just attach the txt file to your post..

Image Health




The Preferred Method Of Use To Fix file Corruption Would Be To Select

Option 1 - /ScanHealth > if shows as Repairable,
then
Option 2 - /RestoreHealth > if shows as Missing Source Files,
then
Option 3 - /RestoreHealth /source

Note:
Dism uses the component store as it's main source for Image Repair, so best to Select Option 2
Before Selecting Option 3 and redirecting the repair source, to the Windows Setup Media..

 

Options 1 says:
"[==========================100.0%==========================]
The component store is repairable.
The operation completed successfully.
1 file(s) copied."

Option 2 says:
"Error: 0x800f0906The source files could not be downloaded.
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
1 file(s) copied."


As I noted in #9, Option 3 gives two SubOptions: 0 and 1. Which is appropriate?

The contents of the text file created for Option 1 is below. The contents of the text file for Option 2 is posted in #5.

2017-03-16 23:52:34, Info CBS TI: --- Initializing Trusted Installer ---2017-03-16 23:52:34, Info CBS TI: Last boot time: 2017-03-10 08:47:28.4852017-03-16 23:52:34, Info CBS Starting TrustedInstaller initialization.2017-03-16 23:52:34, Info CBS Ending TrustedInstaller initialization.2017-03-16 23:52:34, Info CBS Starting the TrustedInstaller main loop.2017-03-16 23:52:34, Info CBS TrustedInstaller service starts successfully.2017-03-16 23:52:34, Info CBS No startup processing required, TrustedInstaller service was not set as autostart2017-03-16 23:52:34, Info CBS Startup processing thread terminated normally2017-03-16 23:52:35, Info CBS Starting TiWorker initialization.2017-03-16 23:52:35, Info CBS Ending TiWorker initialization.2017-03-16 23:52:35, Info CBS Starting the TiWorker main loop.2017-03-16 23:52:35, Info CBS TiWorker starts successfully.2017-03-16 23:52:35, Info CBS Universal Time is: 2017-03-17 06:52:35.8162017-03-16 23:52:35, Info CBS Loaded Servicing Stack v10.0.10586.570 with Core: C:\windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10586.570_none_7645b09c266beb53\cbscore.dll2017-03-16 23:52:35, Info CSI 00000001@2017/3/17:06:52:35.842 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffa150846d9 @0x7ffa153a2150 @0x7ffa153a1d2b @0x7ff60ef82ee0 @0x7ff60ef838e1 @0x7ffa4069d533)2017-03-16 23:52:35, Info CBS NonStart: Set pending store consistency check.2017-03-16 23:52:35, Info CBS Session: 30580459_257234059 initialized by client DISM Package Manager Provider, external staging directory: (null)2017-03-16 23:52:35, Info CBS Client specifies store corruption detect and repair.2017-03-16 23:52:36, Info CBS Exec: Session processing started. Client: DISM Package Manager Provider, Session(Store Corruption Detect/Repair): 30580459_2572340592017-03-16 23:52:36, Info CBS Reboot mark set2017-03-16 23:52:36, Info CBS Winlogon: Registering for CreateSession notifications2017-03-16 23:52:36, Info CBS Winlogon: Loading SysNotify DLL2017-03-16 23:52:36, Info CBS Winlogon: Starting notify server 2017-03-16 23:54:22, Info CBS Repr: CBS Store check completes2017-03-16 23:54:24, Info CSI 00000002 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0xd56a57fac02017-03-16 23:54:24, Info CSI 00000003 Creating NT transaction (seq 1), objectname [6]"(null)"2017-03-16 23:54:24, Info CSI 00000004 Created NT transaction (seq 1) result 0x00000000, handle @0x3b82017-03-16 23:54:24, Info CSI 00000005 Poqexec successfully registered in [l:12 ml:13]"SetupExecute"2017-03-16 23:54:24, Info CSI 00000006@2017/3/17:06:54:24.712 Beginning NT transaction commit...2017-03-16 23:54:24, Info CSI 00000007@2017/3/17:06:54:24.713 CSI perf trace:CSIPERF:TXCOMMIT;22982017-03-16 23:54:24, Info CSI 00000008 CSI Store 2257157135920 (0x0000020d890c9e30) initialized2017-03-16 23:54:24, Info CSI 00000009 StoreCorruptionRepair transaction begun. WcpVersion: [l:44]"10.0.10586.570 (th2_release_sec.160801-2011)".2017-03-16 23:54:24, Info CSI 0000000a@2017/3/17:06:54:24.722 Starting corruption detection (InnerFlags=5)2017-03-16 23:55:15, Info CSI 0000000b Hashes for file member \SystemRoot\WinSxS\wow64_windows-staterepository_31bf3856ad364e35_10.0.10586.589_none_73e982455c99fff4\StateRepository.Core.dll do not match actual file [l:24]"StateRepository.Core.dll" : Found: {l:32 lj08pP5PQVgZCupsJ49iDK/9SHUDyA9b1EcWFBp923Y=} Expected: {l:32 +qIgkK1tLUTngmt6q7wGHgAAis8ztBaSDlM+R3338sI=}2017-03-16 23:58:19, Info CSI 0000000c Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.10586.589_none_def813130bab683e\gpedit.dll do not match actual file [l:10]"gpedit.dll" : Found: {l:32 kr66STTQJj/SGCfMluAmidqauu1XH+iINrNGn3DUoo4=} Expected: {l:32 bPc9PeQDSCGVITCCwLkEmiTNkAOVKcCRBVgFJJS1HqI=}2017-03-17 00:08:34, Info CSI 0000000d@2017/3/17:07:08:34.448 Corruption detection complete. numCorruptions = 2, Disp = 1.2017-03-17 00:08:34, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.2017-03-17 00:08:34, Info CSI 0000000e@2017/3/17:07:08:34.480 CSI Transaction @0x20d8fa5a280 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id [25]"TI5.30580459_257234059:1/"2017-03-17 00:08:34, Info CSI 0000000f@2017/3/17:07:08:34.512 CSI Transaction @0x20d8fa5a280 destroyed2017-03-17 00:08:34, Info CBS Repr: CSI Store check completes2017-03-17 00:08:34, Info CBS Ensure CBS corruption flag is clear2017-03-17 00:08:34, Info CBS =================================Checking System Update Readiness.(p) CSI Payload Corrupt wow64_windows-staterepository_31bf3856ad364e35_10.0.10586.589_none_73e982455c99fff4\StateRepository.Core.dll(p) CSI Payload Corrupt x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.10586.589_none_def813130bab683e\gpedit.dllSummary:Operation: Detect only Operation result: 0x0Last Successful Step: CSI store detection completes.Total Detected Corruption: 2 CBS Manifest Corruption: 0 CBS Metadata Corruption: 0 CSI Manifest Corruption: 0 CSI Metadata Corruption: 0 CSI Payload Corruption: 2Total Repaired Corruption: 0 CBS Manifest Repaired: 0 CSI Manifest Repaired: 0 CSI Payload Repaired: 0 CSI Store Metadata refreshed: TrueTotal Operation Time: 958 seconds.2017-03-17 00:08:34, Info CBS CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]2017-03-17 00:08:34, Info CBS Count of times corruption detected: 12017-03-17 00:08:34, Info CBS Seconds between initial corruption detections: -12017-03-17 00:08:34, Info CBS Seconds between corruption and repair: -12017-03-17 00:08:34, Info CBS SQM: Package change report datapoints not populated because SQM is not initialized or not running online.2017-03-17 00:08:35, Info CBS Reboot mark cleared2017-03-17 00:08:35, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications2017-03-17 00:08:35, Info CBS Winlogon: Deregistering for CreateSession notifications2017-03-17 00:08:35, Info CBS Exec: Processing complete, session(Corruption Detecting): 30580459_257234059 [HRESULT = 0x00000000 - S_OK]2017-03-17 00:08:35, Info CBS Session: 30580459_257234059 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]2017-03-17 00:08:35, Info CBS Session: 30580461_1264670055 initialized by client DISM Package Manager Provider, external staging directory: (null)

 

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

Summary:Operation: Detect only Operation result: 0x0Last Successful Step: CSI store detection completes.
Total Detected Corruption: 2

 

Are you using Home or Pro OS ???

GPedit is a Pro Feature... Index 1 is for Pro Repair Source
Index 2 is for Home (Core) Repair Source

 

It's Home version.

What do you mean "index"? I don't know what you are referring to.

 

DISM /Online /Cleanup-Image /RestoreHealh /source:WIM:E:\sources\install.wim:2

 

Although you didn't say, from your line above, I can see what you mean by "index".

The command with an index of 2, results in the following:
DISM /Online /Cleanup-Image /RestoreHealh /source:WIM:E:\sources\install.wim:2

"Error: 0x800f0906
The source files could not be downloaded.
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 http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\windows\Logs\DISM\dism.log"


I tried adding limitaccess, and resulted in:
"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 http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\windows\Logs\DISM\dism.log"

 

e:\ is the mounted setup media drive letter??
as it was in your prior post..

The source of the file may not have come from the setup media,
but rather a windows update

/limitaccess = prevents dism from accessing the windows update service..
Although I still have never seen dism access windows update anyway

Anywho, you have gone from 14 corrupted files to 2 corrupted files...
so you making progress...

 

Yes, mounted drive letter is correct.

The source file is an iso that I downloaded using Option 16--see #6. I also tried an iso from here (see #1): Microsoft Windows 10 TH2 ISO Download • Windows ISO
The mounted iso has a "setup.exe" file. Does that not mean it is setup media?

If there are less corrupted files, it must be for some other reason as DISM has always failed and I don't know why, and Windows is still not fixed.