Windows Server 2022 Monthly Cumulative Update Problem

It's OK, we all have days like this. When you've been processing a lot of stuff it's easy to make a slip. We are after all, all human.

Looking over your latest logs now, I'll get back to you ASAP
 
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 the attachment SFCFix.zip and 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

There are a lot of things being flagged in this latest log, and it's going to take me quite some time to source what I need to patch them.

I'm going to be busy tomorrow, so it may be as late as Wednesday before I get back to you. If it's going to be any longer I will let you know.
 
Been having trouble sourcing some of the items I need to patch the latest fault items (there are a lot more of them than in our previous fixes), and I'm still working on finding what I need.

Hopefully I'll have things resolved by tomorrow, but for some of the items I may need to create a new VM and update it with the updates that are present on your machine, but which are not present on my current VM. If that's the case (and I fear that it may be my only option) then it will necessitate further delay.
 
Sorry for the long wait, sourcing everything needed was a good deal more complicated than usual, and I've been busy with other things, so it took longer than I'd have liked.

But anyway .....

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 the attachment SFCFix.zip and 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

Good Morning,

SFCFix run without Errors
DISM shows an Error 0x800f081f
I did not try to update cause the DISM failed...

Logs attached
 

Attachments

Only had a quick look over your log so far, but am going to have to consult with my colleagues, since it's flagging some things that I know we've already patched.

There's a lot going on, so it's going to take me a while to go through everything properly.

Will get back to you ASAP, but don't expect it will be quickly.
 
Sorry for the long wait, but I've been going back over what we've done so far, and consulting with my colleagues, and it's not really clear to us why the things we've already patched continue to be flagged.

Presumably there is some process in place that is reverting the changes that we've been making, but quite what that process is is unclear.

So at this point I think we need to consider what the best option is for resolving your problem, and the common concensus is that you perform a repair install/in place upgrade.

Perform a Feature Update of Windows Server
 
Hey,

Thank you very much for all the help and time you put into our problem!!!

We will now create a VM of the machine and use this VM in a separate environment to perform an in-place upgrade/repair to see if it actually leads to a solution.
 
You're welcome. Sorry we couldn't arrive at a better solution. Sadly, sometimes that just isn't possible.
 
You must log in or register to reply here.
Back
Top