Unable to install any Cumulative Updates on WS2016

mariolopjr

New member
Joined
Sep 23, 2019
Posts
3
Hi all,

I've troubleshot as much as I could for a specific Windows Server. Manually installed MSUs, extracting the CAB file and trying to ram it through with DISM, SFC /scannow, and DISM /restorehealth; nothing has fixed this server. I've even tried to see if I can "fix" the server by extracting the CAB files from the broken rollup and checking the manifest/cat/mum files to no avail.

Essentially, the server tried to install this specific update: KB4507460. However, I think it "half" installed. If I go to Control Panel -> Uninstall Windows Update: The update shows, but doesn't show an Installed On. The internal name of: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.3085.1.6 always comes up as not having an install time property yet. Packages in the CBS log show as absent, etc. I've never had a Windows Server break updates so terribly.

The error is always the same when installing any update: [HRESULT = 0x80070490 - ERROR_NOT_FOUND]. I've tried every single cumulative update since 2018 until 09-2019 to no avail. The really old updates end up saying not applicable (maybe bc of being superseded?).

I've gone through many forum posts and investigated the SFCFix.txt. How can I go about fixing this myself? I've extracted the (potential) broken KB (KB4507460), but how to translate that into SFCFix commands to repair registry, WinSxS, and servicing folders I am unsure of. How can I proceed??

Per the instructions, I freshly ran this morning sfc /scannow, dism restorehealth, and the SFCFix tool. I attached the resulting CBS logfile and SFCFix.txt to this post. Thanks!
 

Attachments

Hi!

Please do the following:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
i3yiUac.png


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
 
Thank you. This will take awhile as it's trying to download and install two cumulative updates (2019-07, 2019-09). Additionally, there's a few intensive IO/HTTPS processing running, so I'll filter those out of the resultant trace. Thanks again!
 
Are you able to let me know which executables you need me to not filter out in the ProcMon trace file?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top