[SOLVED] DISM 1734 Array Bounds Are Invalid Error

[Maxstar]

This looks good, so please reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs and the Setupapi.dev.log.

 

[itguy540]

Thank you. I will try the restart this evening and let you know the result.

 

[Maxstar]

Great. I moved your other question a new thread: Issue with Server 2012R2

 

[itguy540]

Unfortunately, this Server (2016) rolled back the updates as well. Attached is the new round of logs. Thank you!

 

[Maxstar]

Hi,

Here's the next fix.

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download PsExec from Microsoft Sysinternals to your desktop.
• Unzip PsTools.zip to its own directory on the system drive, for example: C:\Tools\PsTools
• Navigate in an elevated command prompt to the PsTools directory: cd C:\Tools\PsTools.
• Now copy and paste the following command into the command prompt and press enter. Click on the Agree button when the licence agreement of PsExec appears.
• Note: Ensure that both FRST64.exe and the Fixlist.txt file are on your desktop! Otherwise you'll need to ammend the command to the right location.
  

  psexec -i -d -s "%userprofile%\desktop\FRST64.exe"

• FRST will make a new backup of the registry first, please wait until this process is completed.
• Ensure the provided Fixlist.txt is in the same location as FRST64.exe and then 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.

 

[itguy540]

Sorry, this server reverted updates again too. Attached are the new set of logs.

 

[Maxstar]

And the next fix.

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download PsExec from Microsoft Sysinternals to your desktop.
• Unzip PsTools.zip to its own directory on the system drive, for example: C:\Tools\PsTools
• Navigate in an elevated command prompt to the PsTools directory: cd C:\Tools\PsTools.
• Now copy and paste the following command into the command prompt and press enter. Click on the Agree button when the licence agreement of PsExec appears.
• Note: Ensure that both FRST64.exe and the Fixlist.txt file are on your desktop! Otherwise you'll need to ammend the command to the right location.
  

  psexec -i -d -s "%userprofile%\desktop\FRST64.exe"

• FRST will make a new backup of the registry first, please wait until this process is completed.
• Ensure the provided Fixlist.txt is in the same location as FRST64.exe and then 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.

 

[itguy540]

Thank you. Fixlog.txt is attached.

 

[itguy540]

This Server 2016 is installing updates now. Thank you so very much for your help!

Is this something that could possibly be built into the SFCFix tool to check the atapi, pciide, and intelide keys? I just ask because I thought I saw some other people having trouble with the same keys too.

 

[Maxstar]

Hi,

You're welcome.

Is this something that could possibly be built into the SFCFix tool to check the atapi, pciide, and intelide keys?

Then you'll need to create a complete routine for each key under services. Because this issue may also occur with other keys.