[SOLVED] Server 2016 – DISM Error 1734 (CBS Catalog Missing KB4580346)

C

CarlFromOhio

Member
Joined
Jul 3, 2025
Posts
5
Hi,

I have a server that's working correctly, but I am afraid to reboot it because it's failing in our disaster recovery test environment. I believe the issue started after the most recent KB5058383 Windows 2025-05 Cumulative Update for Windows Server 2016 for x64-based Systems. KB5058383 was installed successfully on June 29, 2025.

Our disaster recovery test restores have failed since this update was installed.

Windows Boot Manager Error.webp

File: \windows\system32\winload.exe
Status: 0xc000007b
Info: The application or operating system couldn't be loaded because a required file is missing or contains errors.


I'm attempting to repair this issue with the SFC and DISM tools. I’m encountering DISM and CBS corruption on a fully patched Windows Server 2016 Standard system. CBS repeatedly logs missing entries tied to KB4580346, and DISM fails with:

Error: 1734
The array bounds are invalid.

This happens even though the system is fully updated and sfc /scannow passes.


System:
  • Windows Server 2016 Standard
  • Build: 14393.8062 (May 1, 2025)
  • DISM version: 10.0.14393.4169
  • Image version: 10.0.14393.7426

Symptoms:

  • DISM /Online /Cleanup-Image /RestoreHealth fails with 0x800f081f / 1734
  • CBS.log shows repeated:

    CBS Catalog Missing: Package_*_for_KB4580346~31bf3856ad364e35~amd64~~10.0.1.6


  • sfc /scannow completes successfully (no integrity violations)
Note:
I ran sfc /scannow, DISM, and SFCFix before I found your posting instructions. All logs are current.


Attachments:

  • CBS.zip (entire CBS folder)
  • ComponentScanner.txt
  • SFCFix.txt
  • DISM.zip

Thanks in advance for your time and help.
 

Attachments

Hi @CarlFromOhio,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Hello and welcome,

Remove Update Manually
  1. Right-Click the Start button and click Command Prompt (Admin) on the list.
  2. When command prompt opens, copy and paste the following command into it, then press enter.
    wusa /uninstall /KB:4580346
  3. Let me know if it says it was successful or if there are any errors.
 
FRST Registry Search
  1. Click the Start button and in the search box, type CMD
  2. When you see cmd.exe on the list, right-click on it and select Run as administrator.
  3. When command prompt opens, copy and paste the following command into it, press enter afterwards.
    Code: 
    REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS

    Note: This loads your components hive which is what we want. Please keep the command prompt window open while you perform the remaining steps. You can minimize it if you wish but keep it open.
  4. Download the Farbar Recovery Scan Tool and save it to your Desktop:
    64-bit: Downloading Farbar Recovery Scan Tool
    Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  5. Right-click on the file FRST64.exe and choose Run as administrator.
  6. Copy and paste KB4580346 into the Search box and click the Search Registry button.
  7. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
  8. You may close any remaining open windows now.
 
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 

Attachments

Great. Thank you for the donation.

Follow the instructions below to cleanup the tools and logfiles used in this thread.
Rename the file FRST64.exe to uninstall.exe and run it. This will remove all files and folders created by FRST and the tool itself.
Reboot the machine to complete.
You may remove all other tools and log files.

Take care.
 
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