[SOLVED] Windows (Cumulative) Updates failing to install [Server 2016]

bcmaze · Apr 19, 2022

Hi guys,

we are running into issues where installing the Cumulative Windows Updates are failing.

Running DISM with RestoreHealth fails with "CSI Payload" corruptions.
Running SFC is failing every run at 34% with "Windows Resource Protection could not perform the requested operation.".

We tried several things we found over the internet like everybody struggeling with this issue :)

At the moment we are focussing on running "dism /online /cleanup-image /restorehealth".
We tried also running "dism /online /cleanup-image /restorehealth /source:C:\Windows\WinSxS /limitaccess" and also copied the WinSxS folder from a fully patched Win2016 machine to the local D:\ drive and used "D:\temp\WinSxS" as source parameter.
We also tried using the .wim File method with a newish Win2016 ISO file without success.

Dism cannot complete and Cumulative Updates neither.
Installation went fine until the reboot, during startup phase windows is rolling back the updates.

Attached you'll find an CBS.log and DISM.log from an attempt to run "dism /online /cleanup-image /restorehealth" which is running into an out of memory error 14.

Do you have any hints?

x BlueRobot · Apr 22, 2022

Rich (BB code):

(p)    CSI Payload Corrupt            wow64_microsoft-windows-scripting-chakra_31bf3856ad364e35_11.0.14393.2312_none_87133e8792f029df\Chakradiag.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-scripting-chakra_31bf3856ad364e35_11.0.14393.2312_none_87133e8792f029df\Chakra.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.0.14393.2312_none_d6f7e1b4daa2618d\indexeddbserver.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.0.14393.2312_none_d6f7e1b4daa2618d\edgehtml.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-b..re-bootmanager-pcat_31bf3856ad364e35_10.0.14393.2312_none_dcb327d355769e61\bootmgr
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2368_none_5ef703a6300db42f\ExSMime.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2368_none_5ef703a6300db42f\UserDataPlatformHelperUtil.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2368_none_5ef703a6300db42f\POSyncServices.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2368_none_5ef703a6300db42f\VCardParser.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2368_none_5ef703a6300db42f\UserDataTypeHelperUtil.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2368_none_5ef703a6300db42f\AppointmentActivation.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2368_none_5ef703a6300db42f\UserDataLanguageUtil.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2368_none_5ef703a6300db42f\ContactActivation.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2368_none_5ef703a6300db42f\UserDataTimeUtil.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_microsoft-windows-b..re-bootmanager-pcat_31bf3856ad364e35_10.0.14393.2368_none_dcb7a0955572b6da\bootmgr
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-p..installerandprintui_31bf3856ad364e35_10.0.14393.2368_none_5655738784ecb1ed\puiapi.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-p..installerandprintui_31bf3856ad364e35_10.0.14393.2368_none_5655738784ecb1ed\puiobj.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-p..installerandprintui_31bf3856ad364e35_10.0.14393.2368_none_5655738784ecb1ed\DafPrintProvider.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-p..installerandprintui_31bf3856ad364e35_10.0.14393.2368_none_5655738784ecb1ed\compstui.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-p..installerandprintui_31bf3856ad364e35_10.0.14393.2368_none_5655738784ecb1ed\findnetprinters.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-win32k_31bf3856ad364e35_10.0.14393.2363_none_38f51f8a2986b09c\win32kfull.sys
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2312_none_5ef28ae430119bb6\ExSMime.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2312_none_5ef28ae430119bb6\UserDataPlatformHelperUtil.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2312_none_5ef28ae430119bb6\POSyncServices.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2312_none_5ef28ae430119bb6\VCardParser.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2312_none_5ef28ae430119bb6\UserDataTypeHelperUtil.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2312_none_5ef28ae430119bb6\AppointmentActivation.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2312_none_5ef28ae430119bb6\UserDataLanguageUtil.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2312_none_5ef28ae430119bb6\ContactActivation.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-u..ccess-userdatautils_31bf3856ad364e35_10.0.14393.2312_none_5ef28ae430119bb6\UserDataTimeUtil.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-scripting-chakra_31bf3856ad364e35_11.0.14393.2368_none_8717b74992ec4258\Chakradiag.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-scripting-chakra_31bf3856ad364e35_11.0.14393.2368_none_8717b74992ec4258\Chakra.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.0.14393.2368_none_d6fc5a76da9e7a06\indexeddbserver.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.0.14393.2368_none_d6fc5a76da9e7a06\edgehtml.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-p..installerandprintui_31bf3856ad364e35_10.0.14393.2312_none_5650fac584f09974\puiapi.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-p..installerandprintui_31bf3856ad364e35_10.0.14393.2312_none_5650fac584f09974\puiobj.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-p..installerandprintui_31bf3856ad364e35_10.0.14393.2312_none_5650fac584f09974\DafPrintProvider.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-p..installerandprintui_31bf3856ad364e35_10.0.14393.2312_none_5650fac584f09974\compstui.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-p..installerandprintui_31bf3856ad364e35_10.0.14393.2312_none_5650fac584f09974\findnetprinters.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_microsoft-windows-ui-shell-component_31bf3856ad364e35_10.0.14393.2312_none_c3499234652b8f5e\DefaultLayouts.xml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-win32k_31bf3856ad364e35_10.0.14393.2273_none_3900efc0297dae02\win32kfull.sys
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_netfx4-servicemodel_mof_files_b03f5f7f11d50a3a_4.0.14928.17110_none_c1d6cc7b90afb0f7\ServiceModel.mof
Repair failed: Missing replacement payload.

I'll look at sourcing these payload files for you.

bcmaze · May 2, 2022

Thank you sir!
Appreciate your feedback!

x BlueRobot · May 3, 2022

Unfortunately, that most of the corrupted payload files are unavailable since their respective updates have either have been pulled from the catalog or no longer install for some reason, therefore could you please remove them using the following instructions:

Remove Update Manually
1. Click on the Start button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following command into it, and press Enter
wusa /uninstall /KB:4284880

4. Let me know if it says it was successful or if there are any errors.

Updates to remove:

bcmaze · May 4, 2022

Hi,
many thanks for your feedback.

Unfortunately the removal is not working. There is a famous warning that both updates are not installed.

Its a German OS so sorry for the German screenshots but I think you get the point:

bcmaze · May 4, 2022

Find enclosed the list of installed Updates by "Get-Hoftix" and "Programs and Features":

x BlueRobot · May 5, 2022

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB4284880 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.

Please do the same time for the other update as well.

bcmaze · May 5, 2022

Hey BlueRob,
thanks for your support.

Find enclosed the two SearchReg.txt files.

x BlueRobot · May 6, 2022

Could you please run the attached FRST64 fix script using the following instructions, this will be for the KB4284880 update.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

x BlueRobot · May 6, 2022

Here's the one for KB4345418, please follow the same instructions as above.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

bcmaze · May 6, 2022

Thanks.

Find enclosed the fixlog files.

x BlueRobot · May 7, 2022

Thank you, could you please open an elevated command prompt and then enter the following command:

Rich (BB code):

DISM /Online /Cleanup-Image /RestoreHealth

If it fails, then please attach the latest CBS log.

bcmaze · May 9, 2022

Hi,
thank you very much.
DISM runs with 100% without errors.
In the CBS we have indeed improved to 4 "" :)

So I guess we need another FRST run?

x BlueRobot · May 9, 2022

These are just warnings and shouldn't affect your ability to update:

Rich (BB code):

(w)    CBS Package Index Package Missing    0x80070490    Package_for_RollupFix~31bf3856ad364e35~amd64~~0.0.0.0    Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2312.1.14    
(w)    CBS Package Index Package Missing    0x80070490    Package_for_RollupFix~31bf3856ad364e35~amd64~~0.0.0.0    Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2368.1.2    
(w)    CBS Watchlist Package Missing    0x80070490    Package_for_KB4132216~31bf3856ad364e35~amd64~~0.0.0.0    Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2312.1.14    
(w)    CBS Watchlist Package Missing    0x80070490    Package_for_KB4132216~31bf3856ad364e35~amd64~~0.0.0.0    Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2368.1.2

Could you please try and install an update again? Please provide the latest CBS log if it fails.

bcmaze · May 9, 2022

Thank you very much.

Unfortunately the update (online) still fails during reboot (rollback).
Because the CBS file got pretty big I zipped it and hope you are able to use the zipped one?

x BlueRobot · May 10, 2022

Rich (BB code):

2022-05-09 15:25:28, Info                  CBS    DriverUpdateStageUpdates failed [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-05-09 15:25:28, Error                 CBS    Doqe: Failed staging driver updates [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Thank you, could you please provide the following log file, it should be available here:

Rich (BB code):

%systemroot%\Inf\setupapi.dev.log

bcmaze · May 10, 2022

Sure thing.

Find attached...

x BlueRobot · May 10, 2022

Rich (BB code):

     sto:      {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 15:25:28.116
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_dual_usbport.inf_31bf3856ad364e35_10.0.14393.2339_none_94f9f7256bd988ad\usbhub.sys' to 'C:\Windows\System32\DriverStore\FileRepository\usbport.inf_amd64_48cb2f2481ad4968\usbhub.sys'.
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_dual_usbport.inf_31bf3856ad364e35_10.0.14393.2339_none_94f9f7256bd988ad\usbehci.sys' to 'C:\Windows\System32\DriverStore\FileRepository\usbport.inf_amd64_48cb2f2481ad4968\usbehci.sys'.
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_dual_usbport.inf_31bf3856ad364e35_10.0.14393.2339_none_94f9f7256bd988ad\usbport.inf' to 'C:\Windows\System32\DriverStore\FileRepository\usbport.inf_amd64_48cb2f2481ad4968\usbport.inf'.
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_dual_usbport.inf_31bf3856ad364e35_10.0.14393.2339_none_94f9f7256bd988ad\usbohci.sys' to 'C:\Windows\System32\DriverStore\FileRepository\usbport.inf_amd64_48cb2f2481ad4968\usbohci.sys'.
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_dual_usbport.inf_31bf3856ad364e35_10.0.14393.2339_none_94f9f7256bd988ad\usbuhci.sys' to 'C:\Windows\System32\DriverStore\FileRepository\usbport.inf_amd64_48cb2f2481ad4968\usbuhci.sys'.
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_dual_usbport.inf_31bf3856ad364e35_10.0.14393.2339_none_94f9f7256bd988ad\usbport.sys' to 'C:\Windows\System32\DriverStore\FileRepository\usbport.inf_amd64_48cb2f2481ad4968\usbport.sys'.
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_dual_usbport.inf_31bf3856ad364e35_10.0.14393.2339_none_94f9f7256bd988ad\usbd.sys' to 'C:\Windows\System32\DriverStore\FileRepository\usbport.inf_amd64_48cb2f2481ad4968\usbd.sys'.
     idb:      {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\usbport.inf_amd64_48cb2f2481ad4968\usbport.inf} 15:25:28.148
     idb:           Created driver package object 'usbport.inf_amd64_48cb2f2481ad4968' in SYSTEM database node.
     idb:           Driver INF file object 'usbport.inf' already exists in SYSTEM database node.
!!!  idb:           Failed to query processor architecture for 'usbport.inf_amd64_5422ad1fd389c7d8'. Error = 0x00000002
!!!  idb:           Failed to register driver package 'usbport.inf_amd64_48cb2f2481ad4968' against 'usbport.inf'. Error = 0x00000002
!!!  idb:           Failed to register driver package 'C:\Windows\System32\DriverStore\FileRepository\usbport.inf_amd64_48cb2f2481ad4968\usbport.inf'. Error = 0x00000002
     idb:      {Register Driver Package: exit(0x00000002)} 15:25:28.148
     sto:      {DRIVERSTORE IMPORT END} 15:25:28.148
     sto:      {DRIVERSTORE IMPORT END: exit(0x00000000)} 15:25:28.148
     sto:      Rolled back driver package import.
!!!  sto:      Failed to import driver package into Driver Store. Error = 0x00000002
     sto: {Stage Driver Package: exit(0x00000002)} 15:25:28.148
!!!  sto: Failed to stage all driver updates. Error = 0x00000002

Could you please export the following key as a registry hive?

Rich (BB code):

HKLM\SYSTEM\DriverDatabase

bcmaze · May 10, 2022

Thank you very much!

Find attached the requested file with a custom .txt extension...

x BlueRobot · May 10, 2022

Why have you saved it a .txt file? You need to export it as a registry hive file please.

[SOLVED] Windows (Cumulative) Updates failing to install [Server 2016]

Active member

Attachments

Administrator

Active member

Administrator

Active member

Active member

Administrator

Active member

Attachments

Administrator

Attachments

Administrator

Attachments

Active member

Attachments

Administrator

Active member

Attachments

Administrator

Active member

Attachments

Administrator

Active member

Attachments

Administrator

Active member

Attachments

Administrator