Windows Update broken - Component store repairable, but cannot repait it

Steffen Schmidt 1 Reputation point
2020-10-12T13:07:26.27+00:00

We have a Windows Server 2016 which cannot update any more.
Updates now fail to install for no appearent reason. dism scanhealth claims the store is corrupted but repairable.
the restore-health command fails though.

DISM.log:
2020-08-14 17:12:49, Warning DISM DISM Provider Store: PID=2900 TID=9928 Failed to Load the provider: C:\windows\SYSTEM32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

[2900] [0x8007007b] FIOReadFileIntoBuffer:(1250): The filename, directory name, or volume label syntax is incorrect.

[2900] [0xc142011c] UnmarshallImageHandleFromDirectory:(793)

[2900] [0xc142011c] WIMGetMountedImageHandle:(3047)

2020-08-14 17:12:49, Info DISM DISM WIM Provider: PID=2900 TID=9928 [C:] is not a WIM mount point. - CWimMountedImageInfo::Initialize

2020-08-14 17:12:49, Info DISM DISM VHD Provider: PID=2900 TID=9928 [C:] is not recognized by the DISM VHD provider. - CVhdImage::Initialize

2020-08-14 17:12:49, Info DISM DISM Provider Store: PID=2900 TID=9928 Getting Provider VHDManager - CDISMProviderStore::GetProvider

2020-08-14 17:12:49, Info DISM DISM Provider Store: PID=2900 TID=9928 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2020-08-14 17:12:49, Info DISM DISM VHD Provider: PID=2900 TID=9928 [C:] is not recognized by the DISM VHD provider. - CVhdImage::Initialize

2020-08-14 17:12:49, Info DISM DISM Imaging Provider: PID=2900 TID=9928 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage

2020-08-14 17:12:49, Info DISM DISM Provider Store: PID=2900 TID=9928 Getting Provider WimManager - CDISMProviderStore::GetProvider

2020-08-14 17:12:49, Info DISM DISM Provider Store: PID=2900 TID=9928 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

[2900] [0x8007007b] FIOReadFileIntoBuffer:(1250): The filename, directory name, or volume label syntax is incorrect.

[2900] [0xc142011c] UnmarshallImageHandleFromDirectory:(793)

[2900] [0xc142011c] WIMGetMountedImageHandle:(3047)

2020-08-14 17:12:49, Info DISM DISM WIM Provider: PID=2900 TID=9928 [C:] is not a WIM mount point. - CWimMountedImageInfo::Initialize

2020-08-14 17:12:49, Info DISM DISM Imaging Provider: PID=2900 TID=9928 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage

2020-08-14 17:12:49, Info DISM DISM Imaging Provider: PID=2900 TID=9928 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage

2020-08-14 17:12:49, Info DISM DISM Manager: PID=2900 TID=9928 physical location path: C:\ - CDISMManager::CreateImageSession

2020-08-14 17:12:49, Info DISM DISM Manager: PID=2900 TID=9928 Event name for current DISM session is Global{69128938-DDB3-4FF7-A935-B5F60AD8797B} - CDISMManager::CheckSessionAndLock

2020-08-14 17:12:49, Info DISM DISM Manager: PID=2900 TID=9928 Create session event 0x924 for current DISM session and event name is Global{69128938-DDB3-4FF7-A935-B5F60AD8797B} - CDISMManager::CheckSessionAndLock

2020-08-14 17:12:49, Info DISM DISM Manager: PID=2900 TID=9928 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation

2020-08-14 17:12:50, Info DISM DISM Manager: PID=2900 TID=9928 Successfully loaded the ImageSession at "C:\windows\TEMP\16D52A39-84D2-4365-8042-1B2DE1683D34" - CDISMManager::LoadRemoteImageSession

2020-08-14 17:12:50, Info DISM DISM Image Session: PID=9912 TID=9900 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore

2020-08-14 17:12:50, Info DISM DISM Provider Store: PID=9912 TID=9900 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect

2020-08-14 17:12:50, Info DISM DISM Provider Store: PID=9912 TID=9900 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2020-08-14 17:12:50, Info DISM DISM Provider Store: PID=9912 TID=9900 Loading Provider from location C:\windows\TEMP\16D52A39-84D2-4365-8042-1B2DE1683D34\OSProvider.dll - CDISMProviderStore::Internal_GetProvider

2020-08-14 17:12:50, Info DISM DISM Provider Store: PID=9912 TID=9900 Connecting to the provider located at C:\windows\TEMP\16D52A39-84D2-4365-8042-1B2DE1683D34\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2020-08-14 17:12:50, Info DISM DISM OS Provider: PID=9912 TID=9900 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect

2020-08-14 17:12:50, Info DISM DISM OS Provider: PID=9912 TID=9900 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect

2020-08-14 17:12:50, Info DISM DISM OS Provider: PID=9912 TID=9900 Host OS verion is 10.0 - CDISMOSServiceManager::SetDllSearchPath

2020-08-14 17:12:50, Warning DISM DISM OS Provider: PID=9912 TID=9900 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect

2020-08-14 17:12:50, Info DISM DISM Provider Store: PID=9912 TID=9900 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect

2020-08-14 17:12:50, Info DISM DISM Provider Store: PID=9912 TID=9900 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2020-08-14 17:12:50, Info DISM DISM Provider Store: PID=9912 TID=9900 Loading Provider from location C:\windows\TEMP\16D52A39-84D2-4365-8042-1B2DE1683D34\LogProvider.dll - CDISMProviderStore::Internal_GetProvider

2020-08-14 17:12:50, Info DISM DISM Provider Store: PID=9912 TID=9900 Connecting to the provider located at C:\windows\TEMP\16D52A39-84D2-4365-8042-1B2DE1683D34\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2020-08-14 17:12:50, Info DISM Try to initialize Panther logging 1 times, last error: 0x0

2020-08-14 17:12:50, Info DISM DISM Provider Store: PID=9912 TID=9900 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

2020-08-14 17:12:50, Info DISM DISM Provider Store: PID=9912 TID=9900 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2020-08-14 17:12:50, Info DISM DISM Provider Store: PID=9912 TID=9900 Loading Provider from location C:\windows\TEMP\16D52A39-84D2-4365-8042-1B2DE1683D34\PEProvider.dll - CDISMProviderStore::Internal_GetProvider

2020-08-14 17:12:50, Warning DISM DISM Provider Store: PID=9912 TID=9900 Failed to Load the provider: C:\windows\TEMP\16D52A39-84D2-4365-8042-1B2DE1683D34\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2020-08-14 17:12:50, Info DISM DISM Provider Store: PID=9912 TID=9900 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

...
more messages, but all classified as info
...

2020-08-14 18:15:54, Error DISM DISM Package Manager: PID=8652 TID=5268 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800706be)

2020-08-14 18:15:54, Error DISM DISM Package Manager: PID=8652 TID=5268 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800706be)

2020-08-14 18:15:54, Error DISM DISM Package Manager: PID=8652 TID=5268 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800706be)

2020-08-14 18:15:54, Error DISM DISM Package Manager: PID=8652 TID=5268 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800706be)

2020-08-14 18:15:54, Info DISM DISM Package Manager: PID=8652 TID=5268 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

2020-08-14 18:15:54, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800706BE

2020-08-14 18:15:54, Info DISM DISM Provider Store: PID=8652 TID=5268 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

CBS log:
2020-10-05 12:29:08, Error CSI 0000000c@2020 /10/5:10:29:08.595 (F) onecore\base\wcp\componentstore\storelayout.cpp(2617): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0

MissingFileSystemResource on resource '\winsxs\manifests\wow64_microsoft-windows-a..ionmodel-lockscreen_31bf3856ad364e35_10.0.14393.2969_none_38f6b4d5f66074b9.manifest'[gle=0x80004005]

2020-10-05 12:29:09, Info CBS Not able to add file C:\windows\winsxs\manifests\wow64_microsoft-windows-a..ionmodel-lockscreen_31bf3856ad364e35_10.0.14393.2969_none_38f6b4d5f66074b9.manifest: to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Does anybody know how to fix this?
Thanks a ton!

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,391 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,209 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.1K Reputation points MVP
    2020-10-12T13:32:32.237+00:00

    Some things to try;

    • sfc /scannow
    • dism /online /cleanup-image /restorehealth
    • https://support.microsoft.com/en-au/help/4027322/windows-update-troubleshooter
    • or possibly removing the most recent successful cumulative update. and try installing latest update again.
    • repair install by running setup.exe from the root of install media
    • or also by pouring over the \dism.log, \windowsupdate.log, \cbs.log looking for and replacing the missing, corrupt files from another server,

    More than likely the quicker thing to do is standup a new one, patch it fully, migrate roles over and move on.

    --please don't forget to Accept as answer if the reply is helpful--

  2. Joy Qiao 4,891 Reputation points Microsoft Employee
    2020-10-13T07:04:07.98+00:00

    Hi,

    What's your system build? (run "winver" command could check version number)
    Did the issue occur on your download process or install process?
    Does the occur on a specific computer or multiple computer?
    How did you update? Through Windows Update agent in Setting\update & Security, or download directly from Windows Update Catalog?

    Are there any error codes recorded in the Event Viewer(Windows Logs\Applications, Setup, System)?

    As I noticed ", Error CSI 0000000c@2020 /10/5:10:29:08.595 (F) onecore\base\wcp\componentstore\storelayout.cpp(2617): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0
    "

    So could try the following steps to repair component store.

    • Run the command below with administrator right to check the health of system files and repair corrupted system files.
    sfc /scannow

    DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

    DISM.exe /Online /Cleanup-image /Restorehealth

    • Disable firewall and antivirus temporarily.
    • Reset Windows Update components
    This script will completely reset the Windows Update client settings. It has been tested on Windows 7, 8, 10, and Windows Server 2012 R2.

    • Perform a Clean Boot and manually update again.

    After that download and install update package from Windows update catalog with 2020 Aug. update.

    Bests,

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  3. Dave Patrick 426.1K Reputation points MVP
    2020-10-17T18:01:54.563+00:00

    cannot afford to break it

    Then the much cleaner / safer method is to stand up a new one, patch fully and migrate the roles over to it.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments