CU Install on Server 2019 0x00f0986

[Nichole Kaligian]

Recently noticed that a number of machines have been failing their cumulative updates for several months already. I went through the troubleshooting guide but the logs don't list the errors mentioned. Out of 20ish machines, I spent about 2 days trying to fix one following some google, like this link: Redirecting
Also ran the sfcfix tool, and a bunch of rebooting. The machine suddenly started updating during one reboot, and then got stuck in a loop where it sat at 100% for a half hour and then restarted, doing the same thing. When I got back the next day it had apparently gotten through and installed the update. Unfortunately 2 days of random clicking isn't something I can do on 20 machines, so I'd like to find a root cause.

So on the 2nd machine I'm troubleshooting:
sfc /scannow reported no errors
ran sfcfix, ran dism, no issues found.
componentscanner lists no issues either.

The machines are on an 1809 build, and aren't showing the option to update to a more recent major version. I'm not sure why this is, they're Server 2019 Standard.

 

[Gary R]

Looking over your logs, back soon.

 

[Gary R]

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download SFCFix.exe and save it to your desktop.
• Download the attachment SFCFix.zip and also save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt
• Open the file, then copy and paste its content in your next reply.

Next ...

• Click Search button and type Command Prompt
• From the results, right click on the Command Prompt icon, and select Run as administrator
• A Command Window will open.
• Copy paste the command below into it, then press Enter
• Dism /Online /Cleanup-Image /RestoreHealth
• Once DISM has finished running ...
  • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
• If the file is too large, upload it to a file sharing service, and post me the link.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

 

[Gary R]

It's now over 3 days since I posted my "fix" and no reply from you. Do you still need help with your problem ?

If I don't hear back from you within 24 hours I will presume not, and will close this topic.

 

[Gary R]

This topic is now closed.

If you still need help, open a new topic and wait for a new helper.