[SOLVED] Server 2016: DISM Error 1734 Array bounds are invalid - KB5011495

[marcoi]

Hi Support,

I been trying to clear out issues with my WS2016 essentials server. Seems like corruption with KB5011495 and MS removed that package from their catalog. I been trying to clear out the reg manually but its super slow process. Any help would be appreciated.
If the reg cleanup i been attempting causing issues, I have a snapshot I can revert back too which was before i started the manually deletes.

 

[Windows Update Bot]

Hi @marcoi,

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

 

[marcoi]

ran some of the other tools.
not finding issues but dism failing so not sure they would.

 

[PeterJ]

Hello and welcome,

Remove Update Manually

1. Click on the Start button and in the search box, type Command Prompt.
2. When you see Command Prompt 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, then press enter.
   wusa /uninstall /KB:5011495
   
4. Let me know if it says it was successful or if there are any errors.

 

[marcoi]

@PeterJ I tried that early and just again, both times I get the following

 

[PeterJ]

Ok. I just wanted a confirmation of that command to start with.

FRST Registry Search

1. Open an elevated command window again.
2. Copy and paste the following command into it, press enter afterwards.
   
   

   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.
3. 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.
4. Right-click on the file FRST64.exe and choose Run as administrator.
5. Copy and paste KB5011495 into the Search box and click the Search Registry button.
6. 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.
7. You may close any remaining open windows now.

 

[marcoi]

here is the results from fbst

 

[PeterJ]

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.

 

[marcoi]

Thanks @PeterJ - the file fixed the issue with my system- Donation sent!

Sfc scan came back clean.
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.

DISM came back clean as well.

PS C:\WINDOWS\system32> DISM /ONLINE /CLEANUP-IMAGE /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.7426

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32> DISM /ONLINE /CLEANUP-IMAGE /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.7426

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\WINDOWS\system32>

 

[PeterJ]

the file fixed the issue with my system- Donation sent!

Great and thanks 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.