[SOLVED] WS2016 DISM error 1734 the array bounds are invalid

Monarke

Monarke

Member
Joined
Oct 10, 2022
Posts
12
When I click on the Windows Icon from the Admin desktop, it shows a busy-circle for a second or two then nothing else happens. The Windows program menu does not open.

I can trace this back to a mistake I made by installing the Ricoh software package Scan Router Lite version 2.

It was after installing and starting this package that the Windows menu stopped working. I have removed ScanRouter Lite software, but this did not fix the problem.

I ran DISM.exe with /Online /Cleanup-image /Restorehealth settings. After finishing the scan it came back with the error:

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================100.0%==========================]
Error: 1734

The array bounds are invalid.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>

This is the server in my home office, and this would not be a good time at all to re-install WS2016.

I hope you all can help.

Thank You
 
Please provide the CBS logs and we will investigate the error.
The CBS directory contains all the relevant logs for Windows Update, DISM and SFC. Without these files, we cannot help you. Please zip up the folder by following the below instructions so it can be attached to your thread.
  1. Open Windows Explorer and browse to the C:\Windows\Logs folder.
  2. Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  3. Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  4. Click on the Yes button here. A file called CBS.zip will be created on your desktop
 
Attached is the win zipped cbs.log folder.

I forgot to mention, if I right click on the Windows icon in the programs menu from the desktop I can access a basic text like menu, but not all of the selections are there.

I also considered restoring the system drive from a back-up dated several weeks ago. I then saw that it would "format" the drive first before restore. This conjured up a memory of a mishap with a Sun 3/50 server's device file/folder many years ago.

Thank You
 

Attachments

Based on the error showing up in the logs I have prepared the following fix. Please follow the steps below.

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Attach this file into your next post for me to analyse please.

If all looks good you should be able to run the DISM RestoreHealth command successfully.
 

Attachments

Last edited:
I've attached the SFCFix.txt file. I copied the SFCFix.txt file off of the machine. I then rebooted the server and logged back on. There has been no change. The Windows Menu is not yet repaired.


Thanks
 

Attachments

Did you rerun the DISM command as I instructed in post #4?
 
I'm sorry, I misunderstood. I thought you wanted to look at the SFCFix.txt file first before I ran dism.exe again.

I just started dism now.

Thank You
 
C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>


Will reboot again and see what happens.
 
Please run SFC /scannow and then try again. If any errors are reported please post a new set of CBS logs.
 
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc.exe /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\Windows\system32>

I'm waiting for the server to reboot. Attached is the latest CBS logs.
 

Attachments

The Windows menu not opening still persists. There is also a notification appearing in taskbar on the lower right side. Clicking upon the notification shows a momentary "busy" circle, but it does not open. Right clicking on the notification opens the bare bones sub-menu. Selecting "Open Action Center" also shows a momentary "busy" circle but it will not open.
 
I'm sorry this did not work. The log shows the file that was corrected:
2022-10-12 05:19:40, Info CSI 00007735 [SR] Repairing corrupted file \??\C:\Users\Public\Desktop\Windows Server Essentials Dashboard.lnk from store

The DISM and SFC scans have not picked up any other errors.

I will have to do some further research and get back to you.
 
I went through some of that Server 2016 thread, and it is extremely long with various fixes. Seems there are several which were not permanent. Since the bulk of the responses are from 2017 there may have been a Windows Update fix for this problem after 2017 or 2020.

At this point I think it would be best if I purchase another system drive of the same make and model as I have originally installed. Then restore to the new drive from a back up approximately 4 weeks ago. The only foreseeable problem this may create is the new recovered system HDD will have a drive letter other than C:. I'll also make a DVD recovery disk, before beginning the restore process.

I've also considered that if I buy a newer model HDD, the installed driver from the restore might not work, or it's operation will be extremely slowed down (crippled).
 
I agree that not all the fixes are worth trying but some tests might be worth doing such as creating a new admin user and seeing if the start menu works for the new admin account. You might be able to copy all you need over to the new account. If it does not work it implies the problem is deep seated.

Do you know that your System backup is free from the problem? Can you recover the data from the last 4 weeks? These are all questions to consider before you begin with your approach. A clean install on the new drive with the old drive removed will give you a clean system with the right drive letter and boot files.

Now that you have got the DISM and SFC working you might consider starting a new thread in W10 section to seek advice on restoring from the backup and how best to swap to a new drive.
 
I created an additional Admin level user account. When I logged in, the same problem persists. Clicking on the Window menu does not open it. According to the system back-ups I can restore as far back as 2020.

The additional HDD will be here in a few days.
 
I restored the original C: drive from back-up using this method, with a back-up from 9/10/2022.
How to Recover Server 2016 from a System Image Backup if Windows Fails to Boot Normally. (Offline Method)

The online method of restore took almost two hours to tell me that it had failed, and it would not restore EFI System along with the C: Partition. The offline method allowed me to restore the C: partition and the two hidden partitions (EFI System Partition, Recovery Partition)

My Windows 2016 Server menu has returned.

win2016standardmenu.jpg

I only have to allow WS2016 to re-install the back-updates.

With Windows back-up, it doesn't save duplicates, but only one incarnation of a file then places markers where there were changes. In essence, the restoration of the C; drive should be as good as what is found on the installation disk.

I am using Windows 2016 Standard with The Essentials Experience installed. My prior server software experience was Windows Home Server 2011 (Modified Server 2008 R2). It does almost everything automatically.

I spent at least a week, looking up all of the permission requirements and correct settings I needed for Windows Server 2016 Standard. I could have gone with Windows Server Essentials 2016 but it has a limitation of 64GB of RAM. Windows 10's RAM limit is much higher than that.

Windows Server 2016 Standard was a rather steep learning curve, to say the least.
 
Well done! I hope the remainder of the updates work successfully for you and I will leave you to mark this as solved once you are satisfied it is fully restored.
 
After rebooting, WS2016 backed up the machine twice. Health monitor did it's clean-up. It's now downloading the back updates.

One less headache to pull my hair out over.... ;)
 
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