Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, April 22, 2017 12:27 PM
Hi
I upgrade to creators update and after that Windows Update and Store Dont Work! in windows update Im getting this error " There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070057) "
and in store Just get me the same error code 0x80070057
I try update troubleshouter , did not work, rename SoftwareDistribution did not work, and a few othher tricks find in web and so far not helpful for me.
I do this and not helping
PS C:\WINDOWS\system32> DISM.exe /Online /Cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0
[===========================98.4%========================= ]
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
PS C:\WINDOWS\system32> sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
All replies (45)
Saturday, April 22, 2017 10:30 PM
Try Settings > Apps scroll down on the right to Store, select Advanced options, then Reset. See if that helps.
Saturday, April 22, 2017 11:30 PM
For windows 10 version 1607 the dism restorehealth is functioning normally. However for windows 10 version 1703 the dism restorehealth is currently malfunctioning.
In the left lower corner search type winver and post your windows version and build.
This is information on the error: 0x80070057 ERROR_INVALID_PARAMETER The parameter is incorrect.
See if this DISM command works:
Click windows and x simultaneously and in administrative command or powershell prompt enter:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccesshttps://support.microsoft.com/en-us/help/10164/fix-windows-update-errors
Sunday, April 23, 2017 1:05 AM
1707 build 15063.138
DISM command not helping!
Sunday, April 23, 2017 1:58 AM
1) Use msconfig to perform a clean boot.
https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows
2) Temporarily turn off antivirus.
3) in admin command or powershell prompt enter WSReset.exe
4) open control panel with large or small icons, then click troubleshooting, then in the left panel click view all, then run the troubleshooters for both windows update and store apps
5) run through this menu and perform any steps that were not yet performed: https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors
Tuesday, April 25, 2017 2:41 AM
Hi ,
DISM command does not work in Windows 10 version 1703, it is a known issue.
For Windows Update issue, here is a similar case for your reference. Refer to the marked answer in the following link to modify registry, check if it works.
Windows Update 0x80070057
https://social.technet.microsoft.com/Forums/windows/en-US/dc05266d-d80b-4817-988e-08005e3bb552/windows-update-0x80070057?forum=WinPreview2014Setup
If not help, follow the steps in this link to reset Windows Update components, then check again.
How do I reset Windows Update components?
https://support.microsoft.com/en-us/help/971058/how-do-i-reset-windows-update-components
Best regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Saturday, May 6, 2017 4:40 AM
Hi
thanks for your help but not helping for me then I clean install windows again BUT the error exist! so is there any solution?
Saturday, May 6, 2017 5:03 AM
Run the following commands in administrative command prompt and post the results: (right click top bar of the box, then edit, then select all, then right click top bar again, then edit, then copy, then paste into forum)
1) winver
2) chkdsk
3) sfc /scannow
4) dism /online /cleanup-image /restorehealth
5) C:\WINDOWS.~BT\Sources\Panther
After the above commands please locate these logs and use one drive to post the logs:
1) cbs log
2) dism log
3) setuperr.log
4) setupact.log
Are your files backed up so that you can format and delete partitions on the drive?
Saturday, May 6, 2017 6:53 PM
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Windows\system32>winver
C:\Windows\system32>chkdsk
The type of the file system is NTFS.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure ...
145152 file records processed.
File verification completed.
1635 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
197556 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
26203 data files processed.
CHKDSK is verifying Usn Journal...
33789752 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
125032447 KB total disk space.
26202196 KB in 116693 files.
86704 KB in 26204 indexes.
0 KB in bad sectors.
249375 KB in use by the system.
65536 KB occupied by the log file.
98494172 KB available on disk.
4096 bytes in each allocation unit.
31258111 total allocation units on disk.
24623543 allocation units available on disk.
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0
[===========================89.8%==================== ]
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
C:\Windows\system32>C:\WINDOWS.~BT\Sources\Panther
The system cannot find the path specified.
and link of those file https://1drv.ms/u/s!AoMNfhGZmJZpuVUM3-6exqhYRNmR
" Are your files backed up so that you can format and delete partitions on the drive?" yes i have ssd with only one partition but i just instaled windows!
Sunday, May 7, 2017 6:21 AM
There were many things (failure, corrupt, etc) within the logs.
https://1drv.ms/t/s!AhdfDD74t_q2jiOWc_YiUTfEsljs
2017-05-06 08:33:08, Warning DISM DISM Provider Store: PID=5600 TID=10472 Failed to Load the provider: C:\Windows\System32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-05-06 08:33:08, Warning DISM DISM Provider Store: PID=5600 TID=10472 Failed to Load the provider: C:\Windows\System32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-05-06 03:30:31, Warning DISM DISM Provider Store: PID=6468 TID=344 Failed to Load the provider: C:\Windows\TEMP\A7DD8468-BB95-4452-8F3D-5FBBB6A587A7\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
It may be possible to load these specifically from a bootable windows 10 iso
http://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image
There is a bug in dism restorehealth and lots are looking for fixes. This one was in another link and it is unclear whether is has been verified. When the USB windows 10 iso is attached try this command first to see if dism restorehealth can be fixed for all files: DISM /Image:D:\ /Cleanup-Image /RestoreHealth /Source:ESD:E:\sources\install.esd:1
For the above command modify the letter D and the letter E as needed for your drive:
D : system partition letter in WinRE
E : W10 ISO USB source letter
You currently have 10.0.15063.0 and the latest is 15063.230
Attempt another windows update.
Check for error messages within windows updates? Please post.
Were there specific KB numbers that failed to update? Please post.
Save these 10 commands to notepad as a txt file. Then re-save adding .bat instead of txt.
Run the bat file in administrative command or powershell command prompt.
net stop wuauserv
cd %systemroot%
ren SoftwareDistribution SoftwareDistributionold
net start wuauserv
net stop bits
net start bits
net stop cryptsvc
cd %systemroot%\system32
ren catroot2 catroot2old
net start cryptsvc
Please indicate which steps you did or didn't perform in this link: https://support.microsoft.com/en-us/help/971058/how-do-i-reset-windows-update-components
These are some additional steps that could be done:
Delete any incorrect values that may exist in the registry. To do this, follow these steps:
- Click Start, and then type regedit in the Start Search box.
- In the Programs list, click regedit.exe.
- Locate and then select the following registry subkey: HKEY_LOCAL_MACHINE\COMPONENTS
- Right-click COMPONENTS.
- Click Export.
- In the File Name box, type COMPONENTS.
- In the Save in box, click Desktop, click Save, and then save the file to your desktop.
- In the details pane, right-click PendingXmlIdentifier, and then click Delete. If this value does not exist, go to the next step.
- In the details pane, right-click NextQueueEntryIndex, and then click Delete. If this value does not exist, go to the next step.
- In the details pane, right-click AdvancedInstallersNeedResolving, and then click Delete. If the value does not exist, go to the next step.
- Restart the computer.
- Try to install the updates again.
Open an administrative Command Prompt window.
At the command prompt, type the following:
takeown /f C:\Windows\winsxs\pending.xml
Rename the c:\windows\winsxs\pending.xml path by using the following command:
Ren c:\windows\winsxs\pending.xml pending.old
Sunday, May 14, 2017 6:34 AM
1: DISM command with source option not helping, made this error
PS C:\WINDOWS\system32> DISM /online /Cleanup-Image /RestoreHealth /Source:K:\sources\install.wim:1
Deployment Image Servicing and Management tool
Version: 10.0.16193.1001
Image Version: 10.0.16193.1001
[===========================88.5%=================== ]
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
2: Update error just as always " There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070057)"
3:"Please indicate which steps you did or didn't perform in this link:" I did everything but againt not helping
4:and perform rest of you said again not helping
5:I download lattest insider build 16193 and upgrade my curently to it again not helping!!!
Im really confused!!!
and before all of this I again clean install windows once more again, and same as always
is there any chance this is hardware problem? by the way I have no problem in anniverssary build...
Monday, May 15, 2017 9:02 AM
Hey guys, any solution?
my system
Core i5 760
Asus p7p55d-e
amd 5850 1 gb
ssd plextor m5pro 120 gb
Monday, May 15, 2017 10:39 PM
Sometimes "clean install" is used as a general term.
What specifically did you do?
Did you delete the partitions on the drive?
Did you format the drive?
Can you perform a clean install now (only Microsoft provided drivers) and then check both windows updates and the windows store?
Please create a USB windows 10 bootable iso from:
https://www.microsoft.com/en-us/software-download/windows10
Each computer manufacture has a F key to choose the boot device. This is quicker than changing the bios boot order.
http://www.disk-image.com/faq-bootmenu.htm
https://www.desertcrystal.com/bootkeys
https://craftedflash.com/info/how-boot-computer-from-usb-flash-drive
Once you have created the bootable windows 10 iso you will boot using the flash drive. Then you will delete the partitions on the main drive, format the drive, then install windows 10 1703 from the bootable windows 10 iso.
https://www.howtogeek.com/224342/how-to-clean-install-windows-10/
All files will need to be backed up, applications recorded, and bookmarks saved.
Tuesday, May 16, 2017 3:32 AM
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
The better log to look at is CBS.log using the timestamp from the DISM.log to index into the CBS.log if you need to.
Robert Aldwinckle
Tuesday, May 16, 2017 5:14 AM
I did exactly what you said, on my ssd i have only one partition, i delete that and create one partition and install windows on that, Look im pretty expret in instaling windows , almost its my job! and this problem never happend before!
Wednesday, May 17, 2017 10:48 PM
UP! 😐😐
Friday, May 19, 2017 2:33 PM
The dism commands appear to have been fixed today:
In administrative command prompt run these commands:
1) sfc /scannow
2) dism /online /cleanup-image /checkhealth
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
Friday, May 19, 2017 11:48 PM
Hi Siamak5561, I have two questions (I don't know if you have Creators Update still installed and with the same issue):
- Do you have your graphics drivers already installed and updated in Creators Update?
- Do you have all information about hardware detailed in your BIOS menu?
I'm making these questions because after a hard search for solutions, I found someone reporting the same issue and resolved only after adding serial number, manufacturer and all the details in the BIOS. He tried all the responses that you received and nothing, only updating this information worked!
Just one more thing: What result displays the network troubleshooter?
I'm still waiting for a fix to this problem. In my case, BIOS information isn't complete and I can't make changes because my guarantee expired... So, I need a new device.
Monday, May 22, 2017 10:18 AM
The dism commands appear to have been fixed today:
In administrative command prompt run these commands:
1) sfc /scannow
2) dism /online /cleanup-image /checkhealth
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
No ot Fixed for me!
I also in 16193 build, but not any diffrente with stable build! Im desprate...
Monday, May 22, 2017 10:19 AM
Hi Siamak5561, I have two questions (I don't know if you have Creators Update still installed and with the same issue):
- Do you have your graphics drivers already installed and updated in Creators Update?
- Do you have all information about hardware detailed in your BIOS menu?
I'm making these questions because after a hard search for solutions, I found someone reporting the same issue and resolved only after adding serial number, manufacturer and all the details in the BIOS. He tried all the responses that you received and nothing, only updating this information worked!
Just one more thing: What result displays the network troubleshooter?
I'm still waiting for a fix to this problem. In my case, BIOS information isn't complete and I can't make changes because my guarantee expired... So, I need a new device.
1. no
2. yes my bios is fine
Monday, May 22, 2017 2:11 PM
The dism restorehealth command per your comments is still not working for the Insider 16193 build. It is now working for version 1703 (OS build 15063.296).
Please run a fresh sfc scannow and dism restorehealth
C:\Windows\Logs\DISM\dism.log
C:\Windows\Logs\CBS\cbs.log
When you attempted an upgrade the panther command ( C:\WINDOWS.~BT\Sources\Panther ) should have produced:
C:\Windows\setupact.log
C:\Windows\setuperr.log
Please post these 4 logs
Wednesday, May 24, 2017 9:40 AM
The dism restorehealth command per your comments is still not working for the Insider 16193 build. It is now working for version 1703 (OS build 15063.296).
Please run a fresh sfc scannow and dism restorehealth
C:\Windows\Logs\DISM\dism.log
C:\Windows\Logs\CBS\cbs.log
When you attempted an upgrade the panther command ( C:\WINDOWS.~BT\Sources\Panther ) should have produced:
C:\Windows\setupact.log
C:\Windows\setuperr.log
Please post these 4 logs
okay I update my os to 15063.296
but like always dism had error
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0
[===========================88.5%=================== ]
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.
this link for those logs https://1drv.ms/u/s!AoMNfhGZmJZpu0oE5HZVP-u8xcD2
Saturday, May 27, 2017 8:16 PM
UP!
Saturday, May 27, 2017 8:27 PM
UP!
Congratulations.
Robert Aldwinckle
Saturday, May 27, 2017 8:32 PM
"this link for those logs https://1drv.ms/u/s!AoMNfhGZmJZpu0oE5HZVP-u8xcD2"
This item might not exist or is no longer available
This item might have been deleted, expired, or you might not have permission to view it. Contact the owner of this item for more information.
Sunday, May 28, 2017 9:05 AM
"this link for those logs https://1drv.ms/u/s!AoMNfhGZmJZpu0oE5HZVP-u8xcD2"
This item might not exist or is no longer available
This item might have been deleted, expired, or you might not have permission to view it. Contact the owner of this item for more information.
Sorry New link
https://1drv.ms/u/s!AoMNfhGZmJZpu02UxVOX_79bUU8L
Sunday, May 28, 2017 7:35 PM
Google Chrome indicates that the download may be dangerous.
What is in the link?
Is it only logs?
Are there images?
What application would be needed to view the contents of the log?
See if you can post it in another form or post the logs so they can be opened with notepad.
Sunday, May 28, 2017 8:19 PM
Google Chrome indicates that the download may be dangerous.
What is in the link?
Is it only logs?
Are there images?
What application would be needed to view the contents of the log?
See if you can post it in another form or post the logs so they can be opened with notepad.
4 logs compressed with winrar!
Saturday, June 3, 2017 1:13 PM
Google Chrome indicates that the download may be dangerous.
What is in the link?
Is it only logs?
Are there images?
What application would be needed to view the contents of the log?
See if you can post it in another form or post the logs so they can be opened with notepad.
I'm still waiting for your answer
Saturday, June 3, 2017 8:40 PM
The documents I was not able to open. Can you post them using onedrive?
Sunday, June 4, 2017 12:28 AM
The documents I was not able to open. Can you post them using onedrive?
this is new link from one drive
zip archive
https://1drv.ms/u/s!AoMNfhGZmJZpu1qQVdBD12Te_0H5
Sunday, June 4, 2017 5:27 AM
2017-05-24 13:52:16, Info CBS DWLD: Failed to begin WU search [HRESULT = 0x80070057 - E_INVALIDARG]
2017-05-24 13:52:16, Info CBS Failed to search Windows update [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-05-24 13:52:16, Info CBS Failed to enumerate cloud capabilities [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-05-24 13:56:19, Info CBS Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-05-24 14:00:12, Info CBS DWLD: Failed to begin WU search [HRESULT = 0x80070057 - E_INVALIDARG]
2017-05-24 14:00:12, Info CBS Failed to search and collect all capabilities [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-05-24 14:00:12, Info CBS Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-05-24 14:00:12, Info CBS Failed to repair store. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-05-24 14:00:12, Info CBS Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-05-24 14:00:12, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-05-24 14:00:12, Error CBS Session: 30594159_3859420187 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-05-24 14:00:12, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800f0906]
2017-05-24 13:53:18, Info CBS Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 30594159_1629817620
2017-05-24 13:56:19, Info CSI 00000007@2017/5/24:09:26:19.575 Corruption detection complete. numCorruptions = 0, Disp = 1.
2017-05-24 13:56:19, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2017-05-24 13:56:19, Info CBS All CSI corruption was fixed, ensure CorruptionDetectedDuringAcr is clear
2017-05-24 13:56:19, Info CBS Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
(p) CBS MUM Corrupt Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
Summary:
Operation: Detect only
Operation result: 0x0
Last Successful Step: CSI store detection completes.
Total Detected Corruption: 1
CBS Manifest Corruption: 1
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
2017-05-11 02:44:04, Error DISM DISM Package Manager: PID=10228 TID=6252 The source files could not be found and download failed. Their location can be specified using the /source option to restore the feature. - GetCbsErrorMsg
2017-05-11 02:44:04, Error DISM DISM Package Manager: PID=10228 TID=6252 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f0906)
2017-05-11 02:44:04, Error DISM DISM Package Manager: PID=10228 TID=6252 The source files could not be found and download failed. Their location can be specified using the /source option to restore the feature. - GetCbsErrorMsg
2017-05-11 02:44:04, Error DISM DISM Package Manager: PID=10228 TID=6252 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f0906)
2017-05-11 02:44:04, Error DISM DISM Package Manager: PID=10228 TID=6252 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0906)
2017-05-11 22:25:45, Warning DISM DISM Provider Store: PID=1356 TID=9040 Failed to Load the provider: C:\WINDOWS\System32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-05-11 22:25:52, Warning DISM DISM Provider Store: PID=2228 TID=2212 Failed to Load the provider: C:\WINDOWS\System32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-05-11 22:25:52, Warning DISM DISM Provider Store: PID=2228 TID=2212 Failed to Load the provider: C:\WINDOWS\System32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
M DISM Provider Store: PID=10312 TID=10444 Failed to Load the provider: C:\Users\Siamak\AppData\Local\Temp\324ABFE8-1B45-433C-8532-D26BA8DE7330\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
M DISM Package Manager: PID=10956 TID=10784 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
M DISM Package Manager: PID=10956 TID=10784 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
2017-05-11 22:29:37, Error DISM DISM Package Manager: PID=10956 TID=10784 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2017-05-11 22:29:37, Error DISM DISM Package Manager: PID=10956 TID=10784 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
2017-05-11 22:29:37, Error DISM DISM Package Manager: PID=10956 TID=10784 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
DISM Provider Store: PID=7172 TID=1184 Failed to load the provider: C:\WINDOWS.~BT\Sources\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-05-14 09:38:11, Warning DISM DISM Provider Store: PID=7172 TID=1184 Failed to load the provider: C:\WINDOWS.~BT\Sources\FfuProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
M DISM Package Manager: PID=528 TID=3856 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0906)
2017-05-23 16:36:46, Error DISM DISM Package Manager: PID=528 TID=3856 The source files could not be found and download failed. Their location can be specified using the /source option to restore the feature. - GetCbsErrorMsg
2017-05-23 16:36:46, Error DISM DISM Package Manager: PID=528 TID=3856 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f0906)
2017-05-23 16:36:46, Error DISM DISM Package Manager: PID=528 TID=3856 The source files could not be found and download failed. Their location can be specified using the /source option to restore the feature. - GetCbsErrorMsg
2017-05-23 16:36:46, Error DISM DISM Package Manager: PID=528 TID=3856 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f0906)
2017-05-23 16:36:46, Error DISM DISM Package Manager: PID=528 TID=3856 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0906)
2017-05-23 16:36:46, Info DISM DISM Package Manager: PID=528 TID=3856 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
M DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070002
2017-05-24 14:00:12, Error DISM DISM Package Manager: PID=7552 TID=7788 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0906)
2017-05-24 14:00:12, Info DISM DISM Package Manager: PID=7552 TID=7788 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLi
2017-05-14 09:35:37, Warning CONX ConX::Compatibility::CCompatibilityController::DeserializeData: Failed to load compat scan data from provider wsc:setup: from the compat scan cache.[gle=0x00000490]
2017-05-14 09:38:07, Warning CONX 0x80070002 Failed to open service key: System\CurrentControlSet\Services\driver\acpi_hal
Summary of some of the prior steps:
sfc /scannow no integrity violations
Image Version: 10.0.15063.0
dism /online /cleanup-image /restorehealth The source files could not be downloaded. Error: 0x800f0906
0x80070057 ERROR_INVALID_PARAMETER The parameter is incorrect.
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess failed to fix dism restorehealth
Version: 10.0.16193.1001
Error: 0x800f0906
The source files could not be downloaded.
In the logs I have not found yet a specific finding that can fix windows update and store problems.
Let's try these steps to see if we can get it fixed or get more information.
Create a windows 10 iso making sure it is the appropriate 32 or 64 bit and making sure it has the same language settings as the current computer.
Boot to the windows 10 iso using the manufactures F key or set the boot order in the bios so that you can boot to the USB flash drive.
Perform a custom repair or in place up grade. Keep all files.
This step has worked for others that had similar problems with version: 10.0.16193.1001
Let us know if you have any problems during the in place upgrade or after you have completed the in place upgrade.
Sunday, June 4, 2017 5:53 PM
create windows iso? how? which version? im currently on 15063.296
and on boot you can only do clean install, only in windows we can do upgrade install
Monday, June 5, 2017 1:11 AM
http://www.wintips.org/repair-windows-10-with-in-place-upgrade/
https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html
Monday, June 5, 2017 6:53 PM
http://www.wintips.org/repair-windows-10-with-in-place-upgrade/
https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html
You really think im not trying this?! I do this several time with diffrent builds but not helping!
Monday, June 5, 2017 7:40 PM
The first link is text and images for an in place upgrade or repair.
The second link is text and images for a clean install
For these two links please report where you get stuck.
What is preventing the in place upgrade?
What is preventing the clean install?
https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html
https://www.tenforums.com/tutorials/1950-clean-install-windows-10-a.html
Tuesday, June 6, 2017 4:42 AM
The first link is text and images for an in place upgrade or repair.
The second link is text and images for a clean install
For these two links please report where you get stuck.
What is preventing the in place upgrade?
What is preventing the clean install?
https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html
https://www.tenforums.com/tutorials/1950-clean-install-windows-10-a.html
I succesfully perform this two methods and windows instaled or upgrade correctly with no error, but same as always windows updte and store dont work.
Tuesday, June 6, 2017 1:40 PM
I succesfully perform this two methods and windows instaled or upgrade correctly with no error, but same as always windows updte and store dont work.
Ready for some diagnosis now? You have already been given some suggestions on that tack but didn't really reply to them. As expected your CBS.log shows you have the one symptom that most others have which makes DISM less helpful as an integrity check but other than that you haven't shown us that there is a problem.
Have you tried looking at your WindowsUpdate.log for clues? (After getting whatever external problem symptom you have been complaining about.)
Robert Aldwinckle
Tuesday, June 6, 2017 7:55 PM
I succesfully perform this two methods and windows instaled or upgrade correctly with no error, but same as always windows updte and store dont work.
Ready for some diagnosis now? You have already been given some suggestions on that tack but didn't really reply to them. As expected your CBS.log shows you have the one symptom that most others have which makes DISM less helpful as an integrity check but other than that you haven't shown us that there is a problem.
Have you tried looking at your WindowsUpdate.log for clues? (After getting whatever external problem symptom you have been complaining about.)
Robert Aldwinckle
so what can i do now?
this is WindowsUpdate.log link in case of need https://1drv.ms/u/s!AoMNfhGZmJZpu1sxsIz9lb88srkE
Wednesday, June 7, 2017 12:15 AM
WindowsUpdate.log
shows you have some kind of configuration problem involving "SLS". What happens when you try to do a Windows Update repair?
Note that there are several ways to do it but being elevated is probably essential.
C.f.
https://answers.microsoft.com/message/60fa3810-cb06-40f3-b1a0-cfa0eb17710a
However, I don't know what a SLS is. In my WU log it is checking on this server with some Cookies (Etag value)
HTTPS://sls.update.microsoft.com/SLS/
You could try using the Network troubleshooter to be sure that you can reach that. It is not a "page" though so trying to open it with a browser would get you Access Denied. That would also prove that you could get connectivity there but it might be a bit ambiguous.
Perhaps enabling Verbose WU logging would help clarify what is not happening on yours. SLS isn't documented there either, so I guess it is something recent and not yet (as) publicly documented.
Running ProcMon to supplement the logging you are getting and discover any other logging you aren't aware of would be my tack but if someone has some more specific ideas about SLS that could be simplest.
Robert Aldwinckle
Wednesday, June 7, 2017 11:31 AM
sorry but i dont understand what you say, what should i do now?
Wednesday, June 7, 2017 1:51 PM
sorry but i dont understand what you say, what should i do now?
I asked you what you were doing for a Windows Update repair and what the results were. I also gave a link to post where I outlined various methods of doing the same thing.
I don't think you were getting as far as a test of that SLS host I gave but a Network troubleshooter is a standard tool which can be used to check if that could be a problem.
Here's a method of getting into it:
- Get into Administrator Windows PowerShell (e.g. press Win-x A and then if necessary enter powershell.exe)
- Enter Get-ControlPanelItem Tr* | Show-ControlPanelItem
- In the resulting Control Panel press Ctrl-e and type Network
- Choose the item which is called Internet Connections
- Use the Help me connect to a specific web page for the SLS host I showed
I also mentioned the possibility of getting more detail about the SLS messages via WU Verbose logging and gave a link to where there was a recent discussion about doing that which proved that although the instructions about how to do it and the exact logging they document may be old and obsolete, we can still usefully request more detail for a WindowsUpdate.log that way.
FWIW I think the SLS could be saying something about your Activation. So, please use System Properties (Win-Pause) to verify that your Windows is Activated. Also, related to this I think there may be some event logs or traces which could be enabled to supplement the diagnostics that you are already getting.
PS>netsh trace show providers | sls "lice|servici"
{A0AF438F-4431-41CB-A675-A265050EE947} Microsoft-Windows-Kernel-LicensingSqm
{B6CC0D55-9ECC-49A8-B929-2B9022426F2A} Microsoft-Client-Licensing-Platform
{BD12F3B8-FC40-4A61-A307-B7A013A069C1} Microsoft-Windows-Servicing
{ED76D77F-7FB5-4EE4-8268-EE46212CB2D3} Microsoft-WS-Licensing
{F5528ADA-BE5F-4F14-8AEF-A95DE7281161} Microsoft-Windows-Kernel-Licensing-StartServiceTrigger
Again, I would be activating those traces or logs not just for their own value (since I don't have access to the source or support documentation which would make them really valuable) but for the supplemental trace entries which ProcMon could capture from both the collection and writing of their details.
Related to this I noticed that you do not have SQM enabled. It's conceivable that enabling it could change your symptoms.
Robert Aldwinckle
Wednesday, June 7, 2017 9:43 PM
My windows is active
and this is what you said
it seems I cant reach "HTTPS://sls.update.microsoft.com/SLS/ " through Troubelthooting but i can accses in browser and show me error 404
Thursday, June 8, 2017 12:53 AM
it seems I cant reach "HTTPS://sls.update.microsoft.com/SLS/ " through Troubelthooting but i can accses in browser and show me error 404
That sounds like you have an interferer. As I indicated the response code I get is 403. I get it with just the host name too. Another way to doublecheck would be to use PowerShell Invoke-WebRequest
PS C:\> Invoke-WebRequest -URI "HTTPS://sls.update.microsoft.com/SLS/"
Invoke-WebRequest : Server Error
403 - Forbidden: Access is denied.
You do not have permission to view this directory or page using the credentials that you supplied.
So, if you have a third-party security product installed, try uninstalling it/them. Use its "cleanup program" if there is one to make sure no trace of its interference remains. Then retry these connectivity checks. Getting interference for new versions of the OS is very common. The interferer treats requests from it as if they were from suspected Trojans.
Otherwise, we could try looking at the "detailed information" to see how the troubleshooter's request was treated. Also, you could try using Message Analyzer to try to see how far the request goes and where it gets turned around. Message Analyzer will also allow you to take a look at the .etl file from that "detailed information" but not very comfortably.
Robert Aldwinckle
Friday, June 9, 2017 4:01 PM
Monday, June 12, 2017 3:43 AM
Mr Aldwinckle, any new instruction?