Windows Server 2022 Monthly Cumulative Update Problem
- Thread starter FleX246
- Start date
- Aug 13, 2021
- 3,338
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.
Next ...
- 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.
- 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
SFCFix and DISM ran without errors.
Unfortunately, Windows Update KB5037782 still hasn't installed.
Logs are attached
Do you see a chance that we can fix the problem?
So do you see progress in the logs?
Unfortunately, I don't really understand the SFCFix and CBS log files
Unfortunately, Windows Update KB5037782 still hasn't installed.
Logs are attached
Do you see a chance that we can fix the problem?
So do you see progress in the logs?
Unfortunately, I don't really understand the SFCFix and CBS log files
- Aug 13, 2021
- 3,338
So what we've been doing so far is patching errors as they appear in your CBS.logs, this generally involves sourcing replacement files and registry entries from a working VM that are identical to how the corrupted items flagged in the logs should be.
Sadly the tools Microsoft supplies to do this do not usually give you a complete picture, and as I said earlier things generally are revealed piece by piece, each being dependant on you successfully patching the preceding one.
The failures of DISM are nothing to worry about, they were just caused by me not completely patching a previous error. One of the registry entries that needs patching is a ComponentFamilies entry, and sometimes there are more than one possible entry to use, and the CBS.log doesn't tell you which. However, if you patch everything else, then the following CBS.log does tell you, and you can then patch it. That's happened a few times now.
So in answer to your questions .... can we fix things, and are we progressing .... I would answer, yes we're progressing, and things are going the way that a great many update problems go, based on previous experience I would say there's a reasonable chance that we can fix things, I just can't say how long it might take.
Of course there's no guarantees. Sometimes (not very often) we come up against problems that we can't fix, or which we can't fix in an acceptable (to the person being helped) timeframe.
Anyway, looking over your latest logs now, will get back to you ASAP.
Sadly the tools Microsoft supplies to do this do not usually give you a complete picture, and as I said earlier things generally are revealed piece by piece, each being dependant on you successfully patching the preceding one.
The failures of DISM are nothing to worry about, they were just caused by me not completely patching a previous error. One of the registry entries that needs patching is a ComponentFamilies entry, and sometimes there are more than one possible entry to use, and the CBS.log doesn't tell you which. However, if you patch everything else, then the following CBS.log does tell you, and you can then patch it. That's happened a few times now.
So in answer to your questions .... can we fix things, and are we progressing .... I would answer, yes we're progressing, and things are going the way that a great many update problems go, based on previous experience I would say there's a reasonable chance that we can fix things, I just can't say how long it might take.
Of course there's no guarantees. Sometimes (not very often) we come up against problems that we can't fix, or which we can't fix in an acceptable (to the person being helped) timeframe.
Anyway, looking over your latest logs now, will get back to you ASAP.
- Aug 13, 2021
- 3,338
So ...... here's the latest patch.
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.
Next ...
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.
- 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
- Aug 13, 2021
- 3,338
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.
Next ...
- 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.
- 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
- Aug 13, 2021
- 3,338
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.
Next ...
Getting late here, so won't see your reply till tomorrow morning (my time GMT+1).
- Download the attachment SFCFixScript.txt and save it on your desktop.
- Save any work you have open, and close all programs.
- Drag the SFCFixScript.txt 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
Getting late here, so won't see your reply till tomorrow morning (my time GMT+1).
- Aug 13, 2021
- 3,338
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.
Next ...
- Download the attachment SFCFixScript.txt and save it on your desktop.
- Save any work you have open, and close all programs.
- Drag the SFCFixScript.txt 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
- Aug 13, 2021
- 3,338
To be honest, I never expected that it would, and really until I ask you to try updating, there's no real point in you trying, all it does is waste your time.
The last two fixes we've performed were just to patch the ComponentFamilies keys whose identity I was unable to discover 3 fixes back.
CBS wouldn't show anything "new" until they were patched. Now that they have been, CBS shows us a new bunch of things to patch.
Going to be busy for the rest of the morning, so won't be able to start sourcing the resources to patch these latest entries until this afternoon.
All right, then I will not try to install the update any further and will send the logs directly after the DISM command.
- Aug 13, 2021
- 3,338
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.
Next ...
- 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.
- 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
- Aug 13, 2021
- 3,338
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.
Next ...
- 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.
- 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
Has Sysnative Forums helped you? Please consider donating to help us support the site!