[SOLVED] Server 2016 DISM/CBS missing manifest issues

I

i_am_root

Member
Joined
May 18, 2025
Posts
7
Hi, I was reading the forums and saw a number of posts from Maxstar helping people with DISM/CBS manifest issues. I tried to post to the "Windows Update Fixes and tutorials" forum (where the posts I referenced were located), but it says I have insufficient privileges to do that, so I thought I'd try posting here.

I am trying to change an old 2016 Server running the Eval version to a Server Standard version with a proper license key (long story, but can give details if needed), and when I do so I am getting an error. I've think I've tracked the issue down to a missing manifest for a superseded package.

After getting an error with the DISM command to change to the ServerStandard edition, I dug around in the logs and ran the "DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH" command and got an "Error 1734 - The array bounds are invalid" message. Some more digging around in the CBS log and I see the following:
Mark store corruption flag because of package: Package_7395_for_KB4550947~31bf3856ad364e35~amd64~~10.0.1.8. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

It seems that KB4550947 was superseded by other packages but the command is still looking for it. I tried downloading and installing that KB, but it gives me an error that "the update is not applicable to your computer" even though I got it from the MS update site.

In the other posting I saw Maxstar had asked for various log files and provided some data files to run with a tool he referenced, but they were specific to that particular issue so I'm not exactly sure what they were trying to fix.

At any rate, I'm not sure how to proceed at this point since I can't get the original KB to install and I don't know how to get into the guts of the system to remove the dependence on that KB or update it to the packages that superseded it or anything.

Any assistance with this would be really appreciated, thanks!
 
Hi @i_am_root,

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,

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.
 
Thanks for getting back to me. I've attached the CBS log in .zip format as requested. The first part of the log contains the info from the DISM command I gave in the original post with the reference to missing manifests from KB4550947. The rest of the log is from the SFC /scannow that I did after just to see what would happen. Please let me know if you need any further information, thanks!
 

Attachments

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:4550947
  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 KB4550947 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

The Fixlog.txt (zipped) is attached. SFC /scannow said it did not find any integrity violations after restarting the system.

What should my next steps be? Thanks!
 

Attachments

Run the command Dism /Online /Cleanup-Image /RestoreHealth 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.
 
I did so and it reported that the command completed successfully. Also did the /ScanHealth and /CheckHealth versions and they also both reported no issues. I guess the only thing left is to try the DISM commands to apply the valid license key and see how that goes. Will report back here if it works or not. Thank you for all the help! I'll be making a donation to the site, either through myself or the company, to help support the site and the valuable help you have provided so far...and maybe again depending on how the next steps go...heh.
 
Go ahead indeed. Try the upgrade again and report the result.
Thank you for the donation.(y)
 
Everything worked smoothly, thanks so much for your help!

Just out of curiosity, do you have programs or scripts that parse the CBS logs and spit out the registry fixes that the FRST64.exe uses, or do you have to go through them manually to see what the issues are and generate the fixlist?

Again, your help was really appreciate and saved me a lot of time and effort, thanks!
 
Yes, we use tools to parse log files but manual searching is still needed with all the different operating systems and errors that can occur.

Follow the instructions below to cleanup the tool 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.

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