Windows Server 2016 Essentials updates fail with errors 0x80070057 and 0x80240016

Hi,

We'll need to fix a lot of things, so here are next fixes.

Step 1. Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.

Step 2. Download
6530fbb0f4101-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 3. 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

Step 1: Appeared to run OK, but the FixLog.txt file indicates an error accessing the registry.

Step 2: The SFCFix ended with: "Error: Failed to write final logfile (C:\Users\NAdmin\Desktop\SFCFix.txt) with error code 13. File may be in use." The resulting SFCFix.txt file only had a size of 1 KB and doesn't appear to contain anything.
Also attaching the C:\SFCFix\SFCFix (2024-03-15 14'05'29.925) file I found elsewhere on the disk.

Step 3: Same DISM error as before after reaching 100%: "Error:1734. The array bounds are invalid." CBS.log is attached.
 

Attachments

Hi,

Follow these instructions to import a registry file manually.
  • Download the attached REGFix.zip file and extract it, right click the
    reg-file.png
    REGFix.reg file and choose Merge.
  • When the Registry Editor warning appears with the message "Are you sure you want to continue?" press the Yes button to continue.
  • Let me know if it says it was successful or not, if it failed take a screenshot of the message and attach it into your next post.

If successful, run the following comand in an elevated prompt and copy and paste the result in your next post to verify this key.
Code: 
reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_7499_for_KB5005573~31bf3856ad364e35~amd64~~10.0.1.9" /s
 

Attachments

"Error accessing the registry." screenshot attached. I received this the first time I attempted it, but since it was Saturday and no one was in the facility to access the server, I rebooted the server and tried again. I received the same result after the reboot as well.

When I examine the permissions on the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages", only TrustedInstaller has "Full Control." All other users (including the NAdmin [Network Administrator]) account I am using have only "Read" permissions.
 

Attachments

  • Unable to access registry.jpg
    Unable to access registry.jpg
    62.3 KB · Views: 1
Since this is just an orphaned key of a partially removed update we can do the following first.

Please run the following commands in an elevated prompt and post the result for each KB number.
Code: 
wusa /uninstall /KB:4586830
wusa /uninstall /KB:5003197
wusa /uninstall /KB:5003638
wusa /uninstall /KB:5005563
wusa /uninstall /KB:5005573
wusa /uninstall /KB:5006669
wusa /uninstall /KB:5008207
 
wusa /uninstall /KB:4586830 - "Installer encountered an error: 0x8007000d. The data is invalid."
wusa /uninstall /KB:5003197 - "Installer encountered an error: 0x8007000d. The data is invalid."
wusa /uninstall /KB:5003638 - "Installer encountered an error: 0x8007000d. The data is invalid."
wusa /uninstall /KB:5005563 - "Installer encountered an error: 0x8007000d. The data is invalid."
wusa /uninstall /KB:5005573 - "Installer encountered an error: 0x8007000d. The data is invalid."
wusa /uninstall /KB:5006669 - "Installer encountered an error: 0x8007000d. The data is invalid."
wusa /uninstall /KB:5008207 - "Installer encountered an error: 0x8007000d. The data is invalid."

All error messages were displayed within a few seconds of entering the commands.
 
Hi,

Please try to uninstall the following two updates again with Process Monitor running.
Code: 
wusa /uninstall /KB:4586830
wusa /uninstall /KB:5003197

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try to remove the updates above using WUSA.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



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 the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
6. Attach also a new copy of the CBS logs.
 
Files are attached. I managed to catch the server early this morning when it wasn't in direct use, so the LogFile.PML file was relatively small. Apparently ProcMon had been run on this server previously, as it had a backing file defined. I reset the ProcMon options to defaults prior to running the commands, but if you feel there are other settings I should check, please let me know.
 

Attachments

It seems because of the delay, not everything was logged yet. Could you please run ProcMon a bit longer, e.g. 2 minutes. Attach also a new copy of the CBS log for the time stamps.
 
Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Open the startmenu and type the command cmd.
  • After you find the Command Prompt, right click on it and select Run as Administrator.
  • Copy and paste the following into the Command Prompt and press enter.
Code: 
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
Right-click on the file FRST64.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Registry button.
Code: 
KB4586830
  • When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
  • Post the logfile SearchReg.txt as attachment in your next reply.
 
Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Great please run the following DISM command again and attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 
1. Start the
55d04c7d453ca-Command_prompt_icon_%28windows%29.png
Command Prompt as administrator.
  • Open the startmenu and type the command cmd.
  • After you find the Command Prompt, right click on it and select Run as Administrator.
  • Copy and paste the following into the Command Prompt and press enter.
Code: 
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
2.Right-click on the file
577bf0efb8088-FRST.png
FRST.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Registry button.
Code: 
KB5006669
  • When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
  • Post the logfile SearchReg.txt as attachment in your next reply.
 
Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

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