Note that the above should have said x64.
Also, should probably go through and uninstall the updates one at a time starting with the newest, then reinstall from the oldest.
pete
sfc and DISM both fail, windows 10 version 1803
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Hi,
I'm running a Lenovo G510, originally delivered with Windows 8, but upgraded to 10 about 2 years ago. A failed update uncovered the fact that there may be a problem with the current installation of 1803. sfc /scannow fails with the message "windows resource protection could not perform the requested operation". DISM fails with "the WOF driver encountered a corruption in the compressed file’s resource table". CHKDSK appears to complete successfully.
thanks in advance,
pete vh
Windows for home | Windows 10 | Install and upgrade
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
47 answers
Sort by: Oldest
-
Anonymous
2019-11-22T20:03:52+00:00 -
Anonymous
2019-11-23T21:17:24+00:00 Hi,
Not sure you would have been notified of the later posts.
pete
-
Anonymous
2019-11-23T21:20:14+00:00 Hi,
Not sure you would have been notified of the later posts.
pete
-
Anonymous
2019-11-23T23:52:19+00:00 There is a dism log you could check. If you do that, keep in mind the log is a running listing so you need to check the date and time when it was run. Usually start from the bottom and go up since you only need the last two or three runs.
Your setupdiag utility did not see a reason for the failure. It has several scenarios it checks for and did not see one of those.
Do you have the install media for your current install? If you do, have you tried doing an in-place upgrade by running the setup file from the Windows desktop? Have you tried running DISM using that install.esd file as the source for those files?
You might look through this thread and see what was done there.
-
Anonymous
2019-11-24T19:06:14+00:00 Hi,
The fails in the dism logs are generally the same. The ones from 11/22 are above. On 11/19, starts with
2019-11-19 16:44:54, Warning DISM DISM Provider Store: PID=7876 TID=9812 Failed to load the provider: C:\Users\pete\AppData\Local\Temp\2772662B-DDA8-4255-89FD-08353866B685\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-11-20 09:57:47, Warning DISM DISM Provider Store: PID=7456 TID=4236 Failed to load the provider: C:$WINDOWS.~BT\Sources\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-11-20 09:57:47, Warning DISM DISM Provider Store: PID=7456 TID=4236 Failed to load the provider: C:$WINDOWS.~BT\Sources\FfuProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-11-20 09:57:47, Warning DISM DISM Provider Store: PID=7456 TID=4236 Failed to load the provider: C:$WINDOWS.~BT\Sources\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
and so on.
I have no distribution media. Tried using a downloaded iso of 1803 17134.1 as a source for dism, but had same results. It looks like a disconnect between i7 core rev and the Intel graphics driver is going to keep me at 1803.
Do you think there's any chance uninstalling the last few updates, then reinstalling them, and several missing ones, would work, or at least not blow up? Looks like there would be 2 windows & 2 .net framework updates to uninstall. 2 ssu updates can't be uninstalled. About 15 updates to install after.
thanks,
pete