[SOLVED] Win2K16 Server DISM/SFC / Start menu issues

F

fuzzsoth

Member
Joined
May 3, 2025
Posts
8
Hello,
I have a similar issue with a Windows Server 2016 server which others have reported previously.
Specifically, the Windows Start button and Menu have spontaneously stopped working, as of about two weeks ago. This server is a DC and RDS, and the issue doesn't seem to affect all users - only some.

I've attempted the usual fixes... DISM, SFC. Both fail with various errors - DISM is a 1734 Array out of bounds, and SFC detects problems but can't repair because the component store is corrupt.

Attaching my CBS and DISM files in the hope that the expertise here can assist.

Thanks.
 

Attachments

Hi @fuzzsoth,

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,

Follow the instructions below please.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download
    myjIXnC.png
    SFCFix and move the executable to your desktop.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Attach that file to your next reply.
 

Attachments

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.
 
Hello Peter,
Attached as requested. Looks like just a few issues at the end?

Thanks.
 

Attachments

Looks like just a few issues at the end?
Click to expand...
Yes, I included them in my previous fix but it failed because the files are in use.
Lets try again.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

Looks good this time.

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.
 
DISM has failed with the same 1734 Array out of bounds.
Just before it failed, its memory use spiked to about 6GB.
Which files do you need?
 
The file C:\Windows\Logs\CBS\cbs.log please.
 
Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the
    myjIXnC.png
    SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in 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

Hello! Happy to report that the issue is now resolved. You guys are legends!

Donation incoming 👍
 
Great and your welcome.
You may remove the tool SFCFix.exe and its logfiles to clean up.

Take care and thank you for the donation.
 
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