New
#1
Win 10 1703; How to fix broken DISM and hence Windows Update?
Hello. My Win 10 Win Update auto upgraded to 1703 some time ago, but it stalls for 1703 => 1709, returning error 0x800700C1. SFC /scannow found errors but could not fix, so I went to DISM. But it fails too. Typical errors:
In case anyone knows how to read this LOL. Note that the 0x800700C1 error (which I find absent from MS error compendia) is in the first couple lines, which is why I'm guessing the failure of WinUpdate to do the upgrade is related to this. (WU does deliver the incidental patches to 1703.)Code:018-01-18 03:13:46, Warning DISM DISM Provider Store: PID=1352 TID=4424 There is a possible 32-bit versus 64-bit cross architecture issue with the provider (or one of its dependencies). - CDISMProviderStore::Internal_LoadProvider(hr:0x800700c1) 2018-01-18 03:13:46, Warning DISM DISM Provider Store: PID=1352 TID=4424 Failed to Load the provider: C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x800700c1) 2018-01-18 03:13:46, Info DISM DISM Provider Store: PID=1352 TID=4424 Connecting to the provider located at C:\Windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2018-01-18 03:13:46, Info DISM DISM Provider Store: PID=1352 TID=4424 Connecting to the provider located at C:\Windows\System32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2018-01-18 03:13:46, Info DISM DISM Provider Store: PID=1352 TID=4424 Connecting to the provider located at C:\Windows\System32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2018-01-18 03:13:46, Info DISM DISM Provider Store: PID=1352 TID=4424 Connecting to the provider located at C:\Windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2018-01-18 03:13:46, Info DISM DISM Provider Store: PID=1352 TID=4424 Connecting to the provider located at C:\Windows\System32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2018-01-18 03:13:46, Warning DISM DISM Provider Store: PID=1352 TID=4424 Failed to Load the provider: C:\Windows\System32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e) 2018-01-18 03:13:46, Warning DISM DISM Provider Store: PID=1352 TID=4424 Failed to Load the provider: C:\Windows\System32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e) [1352] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect. [1352] [0xc142011c] UnmarshallImageHandleFromDirectory:(639) [1352] [0xc142011c] WIMGetMountedImageHandle:(2893) 2018-01-18 03:13:46, Info DISM DISM WIM Provider: PID=1352 TID=4424 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize 2018-01-18 03:13:46, Info DISM DISM VHD Provider: PID=1352 TID=4424 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize 2018-01-18 03:13:46, Info DISM DISM VHD Provider: PID=1352 TID=4424 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize 2018-01-18 03:13:46, Info DISM DISM Imaging Provider: PID=1352 TID=4424 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage [1352] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect. [1352] [0xc142011c] UnmarshallImageHandleFromDirectory:(639) [1352] [0xc142011c] WIMGetMountedImageHandle:(2893) 2018-01-18 03:13:46, Info DISM DISM WIM Provider: PID=1352 TID=4424 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize 2018-01-18 03:13:46, Info DISM DISM Imaging Provider: PID=1352 TID=4424 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage 2018-01-18 03:13:46, Info DISM DISM Imaging Provider: PID=1352 TID=4424 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage 2018-01-18 03:13:46, Error DISM API: PID=1352 TID=4424 onecore\base\ntsetup\opktools\dism\api\lib\imagingcommandobject.cpp:499 - CAttachPathCommandObject::InternalExecute(hr:0x80070032) 2018-01-18 03:13:46, Error DISM API: PID=1352 TID=4424 InternalExecute failed - CBaseCommandObject::Execute(hr:0x80070032) 2018-01-18 03:13:46, Error DISM API: PID=1352 TID=5412 CAttachPathCommandObject failed - DismOpenSessionInternal(hr:0x80070032)
So I figure I need to repair DISM, but from my reading, it needs to be an "offline repair". Does the following plan seem correct.
1. Download an iso of Win 10 Pro 1703.
2. Mount it to virtual drive "X".
3. Boot from a burn of the downloaded iso.
3. Run "Dism /Image:C:\offline /Cleanup-Image /RestoreHealth /Source:X:\test\mount\windows"
where C is my normal boot drive. (I copied that and need to check the syntax.)
Questions: Does that approach seem correct? Does the offline switch mean indeed that you've booted from an external disc you've created from the fresh iso.
Am I right that I should NOT run
"Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:X:\sources\install.esd:1 /limitaccess" (or the equivalent where the source reference is to "install.wim"), because that would be like asking a broken system to repair itself? (I did try it once and it failed.)
How do you ensure that when you download - or use the Creation Tool to get - a Win 10 pro iso, you get only the 1703 version? That's what my source should be, right? Or does it not matter?
As you see, I'm a little confused. Ok, a lot confused. Would appreciate pointers or advice.
Many thanks. -Ron