Windows Server 2019 Failing March Updates

Joined
Mar 30, 2022
Posts
12
Run a windows shop with WSUS for patches. Hunting down troublesome servers, and this one just won't go. I've downloaded the update manually, but they all say "This update isn't for this Operating System", even though I follow the link given from Windows Updates or find the KB manually (KB 5011503)

In my searching for a solution, I came across sysnative...and I need some help.

I ran the initial dsim commands and they came out clean. I tried running the scfix tool, but it couldn't do anything without a script to run off of, it appears. Attached is my cbm logs and the output of the original scfix run. Any help is appreciated. My other alternative is to rebuild the whole server (we have a very small update window for compliance reasons and anything out of compliance gets rebuilt).
 

Attachments

Rich (BB code):
2022-03-30 13:38:21, Info                  CBS    Failed to load the COMPONENTS hive from 'C:\Windows\System32\config\COMPONENTS' into registry key 'HKLM\COMPONENTS'. [HRESULT = 0x800705aa - ERROR_NO_SYSTEM_RESOURCES]
2022-03-30 13:38:21, Info                  CBS    Failed to load component store [HRESULT = 0x800705aa - ERROR_NO_SYSTEM_RESOURCES]

How much free space do you have available?
 
It was a little short on space when i started, but as of 3/30, it has around 15G on the C drive. I tried the steps again this morning and got the same error messages.
 
15GB is not much free space at all, you want at least around 30GB. Could you please provide your COMPONENTS hive using the following instructions:

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. 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.
3. 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.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or WeTransfer and then just provide the link in your reply.
 
Thanks, your COMPONENTS hive appears to load with no problems on machine. Could you please try and update again?
 
I am still failing the update. Error code is 0x800705aa. I tried running sfc /scannow and it ended saying it couldn't perform the operation. I'm getting ready to perform a repair install of the server to get it back to good health.
 
SFCFixScript.txt
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.[/list]
 

Attachments

Last edited:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-04-08 10:10:12.567
Microsoft Windows Server 10 Build 17763 - amd64
Using .txt script file at C:\Users\jchilders\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.

Successfully imported registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2022-04-08 10:10:13.973
Script hash: xhN3Jf+2sovRS2YiiuEOnnLZVSf7x6cwz7ILsF1h82g=
----------------------EOF-----------------------
 
Let's try the following:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Brilliant :) I think I'm to the point of a rebuild...

Fix result of Farbar Recovery Scan Tool (x64) Version: 05-04-2022
Ran by jchilders (08-04-2022 15:13:07) Run:1
Running from C:\Users\jchilders\Desktop
Loaded Profiles: sa_docs_las_dev & jchilders
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
Reg: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
DeleteValue: HKLM\COMPONENTS|PendingXmlIdentifier
DeleteValue: HKLM\COMPONENTS|ExecutionState
*****************

Error: (0) Failed to create a restore point.

========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========

ERROR: Insufficient system resources exist to complete the requested service.



========= End of Reg: =========

"HKLM\COMPONENTS\\PendingXmlIdentifier" => not found
"HKLM\COMPONENTS\\ExecutionState" => not found

==== End of Fixlog 15:13:10 ====
 
Of course...hang on, I'll delete it from your COMPONENTS hive myself and then provide you with the amended version.
 
Please create a backup of your current COMPONENTS hive and then replace your current version with the one attached. Once that has been done, then please start Process Monitor using the following instructions:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try loading the COMPONENTS hive just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.
j8MhY5V.png

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.

Let's see if we can gather any useful information as to why the COMPONENTS hive is failing to load.
 

Attachments

Thank you, please open a command prompt and then enter the following commands:

Code:
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace
reg query "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" /s

Please post the output of both in your next post.
 
I've attached the reg query results. As an FYI, I also tried run a repair install (and have since rolled back the snapshot) that also failed. Today I'm starting to build a replacement. I've got a few more days to have this server up and running while I'm working on the replacement.
 

Attachments

Thank you, let's reset your memory management settings back to known working values.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Fix result of Farbar Recovery Scan Tool (x64) Version: 12-04-2022 03
Ran by jchilders (11-04-2022 13:11:53) Run:2
Running from C:\Users\jchilders\Desktop
Loaded Profiles: sa_docs_las_dev & jchilders
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
Reg: reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management" /v PagedPoolSize /t REG_DWORD /d 0x0
DeleteValue: "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management"|PagefileUsage
DeleteValue: "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management"|PoolUsageMaximum
DeleteValue: "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management"|da56a5e4-287c-4a5b-86da-140a12d814cd
*****************

Error: (0) Failed to create a restore point.

========= reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management" /v PagedPoolSize /t REG_DWORD /d 0x0 =========

The operation completed successfully.



========= End of Reg: =========

"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\\PagefileUsage" => removed successfully
"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\\PoolUsageMaximum" => removed successfully
"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\\da56a5e4-287c-4a5b-86da-140a12d814cd" => removed successfully

==== End of Fixlog 13:11:54 ====
 

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

Back
Top