[SOLVED] having a problem installing components and updates

[jvolence]

I am having trouble installing features and updates on windows server 2022. getting referenced assembly could not be found :: 0x80073701

This is the same problem as thread [SOLVED] - MSMQ-Server :: referenced assembly could not be found :: 0x80073701

I followed the initial steps from that thread and created the search registry log based on what it claims it can't find (Microsoft-Windows-msmq-server-Opt-Package). The other thread said it couldn't find a failed KB but that doesn't seem to be the case here.

When I try to enable-feature msmq-server using the command dism /online /enable-feature /featurename:msmq-server, I get the error "The referenced assembly could not be found.".

I don't understand what to try to uninstall, or how to install MSMQ manually if that is the problem?

Attached are the DISM and CBS logs. I also searched for "Microsoft-Windows-msmq-mmc-Opt-WOW64-Package" with FRST and attached the log.

What is the next step? Thanks!

 

[jvolence]

uploaded componentsscanner.txt

 

[Maxstar]

Hi and welcome to Sysnative,

Upload your 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.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[jvolence]

uploaded components.zip

 

[Maxstar]

Hi,

Please do the following.

Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFixScript.txt and save it to your desktop.
• 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.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Afterwards reboot the server and attempt to update. If it fails attach a new copy of the CBS logs.

 

[jvolence]

sfcfix.txt

 

[Maxstar]

The fix completed successfully, so let's hope the updates are also successfully applied after the reboot. If not please attach the latest CBS logs.

 

[jvolence]

windows update seems to be stuck at 0% installing/downloading after restarting. before restarting, it would try to install KB5033118 but fail at 20%

 

[jvolence]

nevermind, seems to be installing now will let you know if it completes

 

[Maxstar]

Okay! Let me know the result. If it fails attach a new copy of the CBS logs.

 

[jvolence]

it failed with error 0x80073701

seems to be looping at this section of cbs.log:

2024-01-02 13:00:58, Info CBS Enumerating Foundation package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.20348.1, this could be slow
2024-01-02 13:00:58, Info CBS Not able to find top owner for package Microsoft-Windows-RemoteFX-Server-Setup-Package~31bf3856ad364e35~amd64~~10.0.20348.1, assume it is self-owned
2024-01-02 13:00:58, Info CBS Not able to find top owner for package Microsoft-Windows-ServerCore-DX-Package-onecoreuapwindows~31bf3856ad364e35~amd64~~10.0.20348.1, assume it is self-owned
2024-01-02 13:00:58, Info CBS Not able to find top owner for package Microsoft-Windows-DNS-Server-Tools-NanoServer-Package~31bf3856ad364e35~amd64~~10.0.20348.1, assume it is self-owned
2024-01-02 13:00:58, Info CBS Not able to find top owner for package Microsoft-Windows-FailoverCluster-Mgmt-Nano-Package~31bf3856ad364e35~amd64~~10.0.20348.1, assume it is self-owned
2024-01-02 13:00:58, Info CBS Not able to find top owner for package Microsoft-Windows-FailoverCluster-FullServer-Nano-Package~31bf3856ad364e35~amd64~~10.0.20348.1, assume it is self-owned

wetransfer link - CBS.log

 

[Maxstar]

These lines are just INFO 'lines' so nothing to worry about! I will review your latest CBS logs tomorrow to provide a new fix...

 

[jvolence]

I understand that they are just info lines, but they are repeated multiple times... Does that mean it is unable to resolve the package dependencies it is referencing?

Will wait until tomorrow for an update. Thanks!

 

[Maxstar]

Hi,

Here's the next fix.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFixScript.txt and save it to your desktop.
• 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.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Afterwards attempt to update and post the result. If it fails attach a new copy of the CBS logs.

 

[jvolence]

failed again with 0x80073701

more sections referencing 31bf3856ad364e35

also at the top it is referencing that it cannot open KB3025096 but if I go into update history/uninstall updates, I don't see KB3025096 installed? How do I "uninstall" it or make it so that windows is not trying to find it if it is superseded by kb5033118?

Is that is what the problem is?

this is just a backup server with the backup data on a different drive. We can try to fix one more time - but I wonder if I just reinstall windows and update from the beginning again? Would that be more efficient or should we continue trying to troubleshoot?

latest cbs.log - CBS.log

 

[Maxstar]

more sections referencing 31bf3856ad364e35

This is just the "Public Key Token" which is used by Microsoft for each component.

The problem in this case has to due with a (huge) number of missing RTM keys into the registry! If this is a server you can easily rebuild, I definitely would do that to get it up and running. That said, a repair install (in-place-upgrade) will do the same and resolve the issue as well.

In-place upgrade Server 2022 with the MSDN (Retail) ISO.

• Navigate to the URL below and sign-in with your MSDN registered account.
• https://msdn.microsoft.com/subscriptions/securedownloads/
• Use the search field to find and download the correct ISO file.
• Mount the Windows Server ISO and run Setup.exe.
• Use the option Download updates, drivers, and optional features (recommended) and click Next.
• Note: If you don't want to update during the in-place upgrade, press Change how setup downloads updates and select Not right now - !!! Not recommended !!!
• When the following screen is prompted enter your (25 digit) product key. Note: Do not use the public KMS key as listed here.
  
  
  
  
  
• In the next screen, select the image of the installed Windows Server edition and click Next.
• Then accept the EULA. To perform a in-place upgrade, you need to check keep personal files and apps. Then click Next.
• After clicking Next, an upgrade process will start checking for updates, when this is ready click install to start the in-place upgrade.

 

[jvolence]

I reloaded the server and it installed KB5033118 directly from the beginning. I'm guessing that an earlier update failed or partially installed, which later updates were trying to reference.

Thank you for your effort and I will create a new thread if I need help again.

 

[Maxstar]

I'm guessing that an earlier update failed or partially installed...

This could be the issue, but in this case a number of registry keys were missing, which is more likely a bug - or compromised image - rather than an issue with later LCU's.