[SOLVED] Windows Server 2019 Standard with Exchange 2019 - Update Fail 0x80073712

[AAIC - David Lorenz]

Dear forum members,

my name is david lorenz from aaic soft systems gmbh in leipzig (germany). We have had problems with our windows server 2019 standard for a long time. An exchange server 2019 runs on this system. The updates for the exchange and .net run smoothly. However, the system no longer installs cumulative windows updates.

The error is 0x80073712. I've already read up on them and already put the "SFCFix.exe" file on the desktop. I have also attached the logs and the components file.

The installation attempt was on 03/23/2023 between 10:00 a.m. and 12:00 p.m.

We have already tried the following:
- Let the software distribution folder be recreated
- DISM and Chkdsk
- Manual update installation (msp)
- Installation of the last service stack update (ran successfully)
- Control of event viewer

Maybe one of you can help us here. Unfortunately, I can't make sense of the logs.

Thank you in advance and have a pleasant rest of the week!

 

[Gary R]

Hi I'm Gary R,


I'm a Security Analyst, and a Windows Update Trainee, and I'd like to help you with your problems.


As a trainee there may be times when my instructions must first be checked by a qualified update expert, before I post them. This will by necessity introduce some delay when/if that occurs, so please be patient.


I am looking over your logs now, and will be back as soon as I've finished analysing them. Could take me some time.

 

[Gary R]

Can you please do the following for me ...

• 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

 

[AAIC - David Lorenz]

Hello @Gary R , thanks for your awnser. You find the zip file in the attachments. Thanks in advance!

 

[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 ...
  • If it completes successfully please try updating.
  • If successful, please let me know.
  • If unsuccessful .....
  • 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

 

[AAIC - David Lorenz]

Hello @Gary R,

I am happy to confirm that you solved the problem with the server. We will look forward to donating some money.
How do you find the solution? We have customers with the same problem. Maybe I will create a new forum entry with there problems.

At the following I send you the SFCFix.txt:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-03-27 09:03:48.594
Microsoft Windows Server 10 Build 17763 - amd64
Using .zip script file at C:\Users\Administrator.AAIC\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS

Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_10.0.17763.1697_none_aa0d0f4cfe45735b.
Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_10.0.17763.1697_none_aa0d0f4cfe45735b\r.
Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_10.0.17763.1697_none_aa0d0f4cfe45735b\f.

Successfully copied file C:\Users\Administrator.AAIC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_10.0.17763.1697_none_aa0d0f4cfe45735b\windows.internal.shellcommon.shareexperience.dll to C:\Windows\WinSxS\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_10.0.17763.1697_none_aa0d0f4cfe45735b\windows.internal.shellcommon.shareexperience.dll.
Successfully copied file C:\Users\Administrator.AAIC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_10.0.17763.1697_none_aa0d0f4cfe45735b\r\windows.internal.shellcommon.shareexperience.dll to C:\Windows\WinSxS\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_10.0.17763.1697_none_aa0d0f4cfe45735b\r\windows.internal.shellcommon.shareexperience.dll.
Successfully copied file C:\Users\Administrator.AAIC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_10.0.17763.1697_none_aa0d0f4cfe45735b\f\windows.internal.shellcommon.shareexperience.dll to C:\Windows\WinSxS\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_10.0.17763.1697_none_aa0d0f4cfe45735b\f\windows.internal.shellcommon.shareexperience.dll.

Successfully restored ownership for C:\Windows\WinSxS
Successfully restored permissions on C:\Windows\WinSxS
PowerCopy:: directive completed successfully.




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\Components\DerivedData\VersionedIndex\10.0.17763.3641 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_none_0ef9edabca48188d\v!10.0.17763.1697.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\Components\DerivedData\VersionedIndex\10.0.17763.4121 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_none_0ef9edabca48188d\v!10.0.17763.1697.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_10.0.17763.1697_none_aa0d0f4cfe45735b.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\Components\DerivedData\VersionedIndex\10.0.17763.3641 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_none_0ef9edabca48188d\v!10.0.17763.1697.

Successfully imported registry key HKEY_LOCAL_MACHINE\Components\DerivedData\VersionedIndex\10.0.17763.3641 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_none_0ef9edabca48188d\v!10.0.17763.1697.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\Components\DerivedData\VersionedIndex\10.0.17763.4121 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_none_0ef9edabca48188d\v!10.0.17763.1697.

Successfully imported registry key HKEY_LOCAL_MACHINE\Components\DerivedData\VersionedIndex\10.0.17763.4121 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_none_0ef9edabca48188d\v!10.0.17763.1697.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_10.0.17763.1697_none_aa0d0f4cfe45735b.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\Components\DerivedData\VersionedIndex\10.0.17763.3641 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_none_0ef9edabca48188d\v!10.0.17763.1697.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\Components\DerivedData\VersionedIndex\10.0.17763.4121 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-i..mon-shareexperience_31bf3856ad364e35_none_0ef9edabca48188d\v!10.0.17763.1697.
RegistryScript:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2023-03-27 09:08:23.566
Script hash: AbOAU5w5EpxB4zbFL3uthuJOpZxYLPteSSW930Np7As=
----------------------EOF-----------------------


Thank you very much an have a nice week!

 

[Gary R]

The clue was in one of your earlier CBSPersist logs. My colleague Maxstar spotted it and kindly notified me about it.

Glad we were able to help you resolve things.

If you have further machines with a similar problem it is best that you open a new topic or topics for them. Problems that look very similar can very well have different causes, and applying an inappropriate fix will usually just cause more problems, so we prefer to deal with things on a case by case basis.