![]() 14:25:29, Info CBS Winlogon: Deregistering for CreateSession notifications 14:25:29, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications ![]() 14:25:29, Info CBS Failed to run Detect and repair. 14:25:29, Info CBS Seconds between corruption and repair: -1 ![]() 14:25:29, Info CBS Seconds between initial corruption detections: -1 14:25:29, Info CBS Count of times corruption detected: 1 14:25:29, Info CBS Not all CSI corruption was fixed, create CorruptionDetectedDuringAcr flag for slow mode reset 14:25:29, Info CBS Ensure CBS corruption flag is clear 14:25:29, Info CBS Total Operation Time: 426 seconds. 14:25:29, Info CBS CSI Store Metadata refreshed: True 14:25:29, Info CBS CSI Payload Repaired: 0 14:25:29, Info CBS CSI Manifest Repaired: 0 14:25:29, Info CBS CBS Manifest Repaired: 0 14:25:29, Info CBS Total Repaired Corruption: 0 14:25:29, Info CBS CSI Payload Corruption: 4 14:25:29, Info CBS CSI Metadata Corruption: 0 14:25:29, Info CBS CSI Manifest Corruption: 0 14:25:29, Info CBS CBS Metadata Corruption: 0 14:25:29, Info CBS CBS Manifest Corruption: 0 14:25:29, Info CBS Total Detected Corruption: 4 14:25:29, Info CBS Last Successful Step: Entire operation completes. 14:25:29, Info CBS Operation: Detect and Repair ![]() 14:25:29, Info CBS Repair failed: Missing replacement payload. 14:25:29, Info CBS Checking System Update Readiness. 14:25:29, Info CBS Failed to repair store. 14:25:29, Info CBS Failed to collect payload and there is nothing to repair. 14:25:29, Info CBS Failed to download missing files 14:25:29, Info CBS Failed to enumerate online uup features 14:25:29, Info CBS FC: WindowsUpdateDownloadFromUUP returns. 14:25:29, Info CBS DWLD:Failed to do Windows update search The CBS.log file is about half a gig, but here is an excerpt of the end of the log that might give a clue re the issue. I just attempted running the September 2021 cumulative update, which failed. I feel this might be the reason that the cumulative updates are failing. The MS technician dealing with our case proposed various things that we tried, but none of them dealt with the CSI Payload Corruption showing in the logs. One of the DISM runs did fix two CSI Payload Corruptions, leaving four outstanding. We have run SFC, DISM (even with a copy of another Windows Server 2019 as the source), even paid MS for an incident support (which they have since refunded), but nothing has solved the problem. Here's an example of the failures in the Windows Update screen: Other updates install, just not the monthly cumulative updates. We've had issues with a Windows Server 2019 machine of ours, where for the last few months, we have not been able to successfully install the monthly cumulative updates. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |