[SOLVED] Server 2019 not installing Updates, repair failed

T

timcp

Member
Joined
May 10, 2023
Posts
17
Hi there,

first off I'm very glad to have found this forum and I'm hopeful to find a solution here.
We have a Windows 2019 VM which has been unable to install any Windows Cumulative Updates for some time. SFC /Scannow finds errors it can't fix and Dism /Online /Cleanup-Image /RestoreHealth fails with Error Code 0x800f081f.
I have attached the ComponentScanner log as stated in the Windows Update Forum Posting Instructions and uploaded the CBS.zip to WeTransfer: CBS.zip
 

Attachments

Since I'm new here I'm not sure about the etiquette and don't want to step on any toes. But after two weeks I'm wondering whether this thread has been overlooked or it's a hopeless case. The server in question sadly runs some important applications, so reinstallation would not be fun at all. So any help would be greatly appreciated.
 
Have you been overlooked ..... probably ...... there's a limited number of helpers here working on update problems, and all of us tend to be busy, so sadly some topics do not get answered as quickly as we'd like. There's only so much time in a day, and all of us are volunteers with other "real world" commitments that have to be attended to.


Because of the delay, the file you uploaded to WeTransfer has expired, so if you can post your CBS files again, I'll look them over, and if I can help then I will.
 
Hi Gary, thank you for your reply. To Clarify, since English is not my first language: I'm aware that this is a forum of volunteers and I did not intent to complain or anything like that. I'm actually very grateful this forum exists at all.
Here's the new link to my cbs Log: CBS.zip
 
I didn't think you were complaining, I was just explaining why some topics don't always get replied to quickly. We try to answer everyone as promptly as we can, but sadly some topics do get overlooked.

Looking over your CBS logs now, depending on how much I need to research it may (or may not) take a while. I'll get back to you as soon as I can.
 
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.
1p8eDnI.gif

  • 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
 

Attachments

It's been 5 days since I posted, without a 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.
 
Hi Gary, I'm extremely sorry I didn't reply. I must have missed the notification and it's been a few very busy days. I will try out your Fix asap (but it will probably be tomorrow).
Thank you so much for your effort!
 
No problem, I'll talk to you tomorrow.
 
Hi Gary, so I decided to run the fix yesterday in the evening but I maybe screwed up a bit. After SFCFix completed, I ran DISM as instructed, which completed without any errors. I took this as a sign that everything is fine again and decided to also run Windows updates. Sadly Windows got stuck at "working on Updates 100%...". I left it there overnight in the hopes of it just needing some time (this server is very slow apparently). But this morning it was still not booted up and I could see that it did at least one reboot in that time. I managed to kill TiWorker.exe via a background management tool we use and the server came up and works ok, but obviously the update has not been fully processed.
I attached the cbs.log and the most recent CbsPersist_x.log, because there has been a lot going on.
 

Attachments

Thanks, looking over your latest logs now, will get back to you ASAP.
 
Please try re-booting your machine, and see if that resolves things.

If not (and to be honest I expect this will be the case) .... please post your latest CBS.log
 
Hi Gary, thanks for getting back to me so quickly. I forgot to mention earlier that I rebooted the server after forcefully killing tiworker.exe. That reboot was at 6:42 this morning and should be covered in the cbs.log in my zip file. Of course I can do another reboot, but since this server is in production it will probably not be possible before 16:00 (UTC +2).
Should I try another run of DISM or anything before creating the next log?
Is it possible that the update fails due to some sort of timeout? as I said this server is really very slow because someone thought it was a good idea to only assign a single CPU core to the VM (I'm currently trying to get them to add at least one more).
 
No, the reason I asked you to perform a reboot is because there are a fair number of the following type of errors in your CBS.log

Code: 
2023-06-01 08:10:04, Info                  CBS    Failed to evaluate external applicability for package update: 5022504-355_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]

So just wanted to make sure that you'd rebooted to eliminate that as a possible cause. Since you have, then they're not being created because you need to reboot, which means there's a different reason for them being present.

There's a whole bunch of other things being flagged as well, but I'm going to have to consult on what I've found, which means it might be a while before I get back to you. I will be as quick as I can, but don't expect it to be soon.


In the meantime, can you please post me copies of your Components Hive, and your CBS Hive ....


COMPONENTS Hive ...
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • The file will likely be too large to upload here, if so please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file


CBS Hive ...

  • Click on the Start button and in the search box, type regedit
    • When you see regedit on the list, right-click on it and select Run as administrator
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

  • Once selected, click File > Export....
    • Change the Save as type: to Registry Hive Files (.)
    • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 
Hi Gary, thanks for all your effort!
I uploaded both hives in one zip-file here: hives.zip
I also scheduled a reboot for 23:00 (UTC+2). If needed I could then post another cbs.log tomorrow.
 
Thanks.

Yes, post a new CBS.log after you've rebooted please. I don't expect anything will have changed, but you never know.
 
Hi Gary, I had to kill tiworker.exe again this morning, because after reboot the server was stuck at "working on updates 100%" again.
CBS log is attached to this post.
 

Attachments

OK, no problem.

Let's see if this CBS.log looks any different from your last one.
 
Please can you attach the following file .... C:\Windows\INF\setupapi.dev.log .... to your next reply.
 
You must log in or register to reply here.

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

Back
Top