[SOLVED] New load of a server not updating

7

7TechSamurai

Contributor
Joined
Aug 18, 2023
Posts
16
I am looking at a recent load of a Windows Server 2022. Updates are failing to install. So far I have:

-Used DISM, including component cleanup and a reset base
-Used SFC
-Used Windows built-in troubleshooter
-Renamed the catroot2 and software distribution folders to start fresh
-Reset BITS and Windows Update security descriptors
-Reregistered the update-related .dll files
-Reset Winsock
 

Attachments

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.
 
Hi,

Some questions:
- Which ISO did you use to install this server?
- If it was a evaluation version! Is this server already activated with an own product key?
- This because the following (highlighted) components are not official RTM keys as it seems!

Rich (BB code): 
2023-08-18 13:09:19, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Editions-ServerStandard-Package~31bf3856ad364e35~amd64~~10.0.20348.1, Update: Microsoft-Windows-Editions-ServerStandard-Deployment, PinDeployment: amd64_microsoft-windows-e..standard-deployment_31bf3856ad364e35_10.0.20348.1_none_44a7d7606884ae09
2023-08-18 13:09:19, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Security-SPP-Component-SKU-ServerStandard-License-Package~31bf3856ad364e35~amd64~~10.0.20348.1, Update: Microsoft-Windows-Security-SPP-Component-SKU-ServerStandard-License-Deployment, PinDeployment: amd64_microsoft-windows-s..-license-deployment_31bf3856ad364e35_10.0.20348.1_none_7ad68727f31d6e28

Rich (BB code): 
2023-08-18 13:09:21, Error                 CSI    000000ee (F) STATUS_SXS_ASSEMBLY_MISSING #1174894# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2023-08-18 13:09:21, Error                 CSI    000000ef (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #1174760# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = Microsoft-Windows-Editions-ServerStandard-Deployment, version 10.0.20348.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-Editions-ServerStandard-Package~31bf3856ad364e35~amd64~~10.0.20348.1.Microsoft-Windows-Editions-ServerStandard-Deployment', rah = (null), manpath = (null), catpath = (null), e[gle=0x80073701]
2023-08-18 13:09:21, Error                 CSI    d = 0, disp = 0)[gle=0x80073701]
2023-08-18 13:09:21, Info                  CBS    Failed to pin deployment while resolving Update: Microsoft-Windows-Editions-ServerStandard-Package~31bf3856ad364e35~amd64~~10.0.20348.1.Microsoft-Windows-Editions-ServerStandard-Deployment from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
 
Hi,

Do you have the ability to provide a copy of this iso? So I can setup a VM with this build to look at?
Note: Please send the link to the ISO file by PM.
 
Hi,

Thanks for sharing the ISO file, in the meantime I have installed a new VM. Please do the following first.

Open an elevated command prompt, run the following command and copy and paste the result in your next post.
Code: 
certutil -hashfile C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-e..standard-deployment_31bf3856ad364e35_10.0.20348.1_none_44a7d7606884ae09.manifest SHA256
 
Hi,

Step 1. Download
56f31e53c97da-SFCFix.PNG
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 SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

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


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Hi,

Step 1.
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.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-Eng.gif

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


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

We'll need to fix several keys into the registry, so here's the next fix:

Step 1.
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.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-Eng.gif

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


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Here are the results of the last run. Also, we have a server loaded from the same image having the same issues, I take it we should open another thread for that?
 

Attachments

Hi,

Yes, please start a new thread for the other server.

Step 1.
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.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-Eng.gif

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


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top