Windows 2022 failing cumulative updates with error (0x800f081f)

[Gary R]

Nothing being flagged on your latest CBS.log, but I don't see the "result" panel from running DISM, so I don't think the log is complete.

CBS logs get archived as "persist" files when they get to a certain size, so I need to see whether that's what's happened here, so ....

Please do the following ....

• Open Windows Explorer and browse to the ... C:\Windows\Logs\CBS ... folder.
• Right click on it, and select ... Send to > Compressed (zipped) folder
• A message will appear stating, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Answer Y to create a folder CBS.zip on your Desktop.
• Please attach it to your next post.
  • If the file is too large, please upload it to a file sharing service and provide the link to it in your next reply.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

 

[MrNorthWall]

Nothing being flagged on your latest CBS.log, but I don't see the "result" panel from running DISM, so I don't think the log is complete.

CBS logs get archived as "persist" files when they get to a certain size, so I need to see whether that's what's happened here, so ....

Please do the following ....

• Open Windows Explorer and browse to the ... C:\Windows\Logs\CBS ... folder.
• Right click on it, and select ... Send to > Compressed (zipped) folder
• A message will appear stating, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Answer Y to create a folder CBS.zip on your Desktop.
• Please attach it to your next post.
  • If the file is too large, please upload it to a file sharing service and provide the link to it in your next reply.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Ran Dism command once more before zipping the CBS-folder, attaching the zip.

 

[Gary R]

OK, so can you please do the following for me ....

First ...
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 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

Next, once that's finished ....
Can you please post me a new copy of your COMPONENTS hive file ....

• 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

 

[MrNorthWall]

Absolutely, thanks!

SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-06-18 19:53:32.042
Microsoft Windows Server 10 Build 20348 - amd64
Using .txt script file at C:\Users\jnadm\Desktop\SFCFixScript (13).txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-n..troller-ovsdbcommon_31bf3856ad364e35_none_9f9e5014e49042d9.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-n..roller-ovsdbclients_31bf3856ad364e35_none_cb57b47cbce189c6.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-n..oller-wmiv2provider_31bf3856ad364e35_none_2cddd566175181f9.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-n..troller-ovsdbcommon_31bf3856ad364e35_none_9f9e5014e49042d9\v!10.0.20348.558.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-n..roller-ovsdbclients_31bf3856ad364e35_none_cb57b47cbce189c6\v!10.0.20348.740.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-n..oller-wmiv2provider_31bf3856ad364e35_none_2cddd566175181f9\v!10.0.20348.803.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-n..troller-ovsdbcommon_31bf3856ad364e35_none_9f9e5014e49042d9\v!10.0.20348.558.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-n..troller-ovsdbcommon_31bf3856ad364e35_none_9f9e5014e49042d9.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-n..roller-ovsdbclients_31bf3856ad364e35_none_cb57b47cbce189c6\v!10.0.20348.740.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-n..roller-ovsdbclients_31bf3856ad364e35_none_cb57b47cbce189c6.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-n..oller-wmiv2provider_31bf3856ad364e35_none_2cddd566175181f9\v!10.0.20348.803.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-n..oller-wmiv2provider_31bf3856ad364e35_none_2cddd566175181f9.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 188 datablocks.
Finish time: 2024-06-18 19:53:32.354
Script hash: h0fnRehj263ApxLssJ2NrwndDdbKDCapPWId/4pn7kk=
----------------------EOF-----------------------

 

[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 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

 

[MrNorthWall]

Thanks! The result:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-06-18 22:48:05.025
Microsoft Windows Server 10 Build 20348 - amd64
Using .txt script file at C:\Users\jnadm\Desktop\SFCFixScript (14).txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-n..ller-sdnfwsi-common_31bf3856ad364e35_none_592772bf9e1e5f54.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-n..ller-sdnfwsi-common_31bf3856ad364e35_none_592772bf9e1e5f54\v!10.0.20348.1.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-n..ller-sdnfwsi-common_31bf3856ad364e35_none_592772bf9e1e5f54\v!10.0.20348.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.20348.2522 (WinBuild.160101.0800)\ComponentFamilies\msil_microsoft-windows-n..ller-sdnfwsi-common_31bf3856ad364e35_none_592772bf9e1e5f54.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 189 datablocks.
Finish time: 2024-06-18 22:48:05.306
Script hash: RDHquAOVxnIv+/gudUkl31p4H4qycctZe0nJaUagDS8=
----------------------EOF-----------------------

 

[Gary R]

A lot of things being flagged in your latest CBS.log that I know we've already patched. Going to have to consult with colleagues, but my best guess is that there's some process on your server that is reverting some or all of the patches we've installed.

Could be a group update policy, do you have any policies in place that you think may be responsible ???

 

[Gary R]

Sorry for the very long wait, I think I know what's happened, and why things have been flagged that we'd already patched.

Can you please do the following ....

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

 

[Gary R]

It's been a week since I last heard 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, please start a new topic and wait for a new helper.