Windows update error ID3 2147957505 on 2016 server 1607 14393.5989

[bfanack]

Hello, I have a 2016 server in production that no longer wants to perform Windows updates.
Right-clicking on properties no longer works either.
I can't reinstall it.
SFC is in error, and so is DISM.
SFCFix is in error 0xc015004.
I scanned with ComponentsScanner.
I'm attaching the files.
Can you help me?
Thank you, kind regards.

 

[Maxstar]

Hi and welcome to Sysnative,

WOW! This does not look good at all, but let's see what we can do....

- Do you have backups of this system and or similar 2016 servers in your network?

Here's the first fix.

Step 1. Download

SFCFix and save it to your desktop.

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

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[bfanack]

Hi,
Thanks for your answer.
I tried drag and drop, app crashed



Yes i have some backups but all recents one are with this OS corrupted
I have one backup maked in 2019, i hope it is a clean install
Kings Regards
Bruno

 

[Maxstar]

Hi,

Please try to run the following command with an backup or other server specified as source:

DISM /Online /Cleanup-Image /RestoreHealth /Source:\\ServerName\C$\Windows\WinSxS\ /LimitAccess

DISM /Online /Cleanup-Image /RestoreHealth /Source:X:\Backup-source /LimitAccess

 

[bfanack]

With the 2019 backup and this CMD
C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth /Source:H:\Windows\WinSxS\ /LimitAccess

Bruno
Regards

 

[Maxstar]

Hi,

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[bfanack]

hi,

thanks
sfcfix.exe still crashed




Is there another way to apply fix ?

 

[Maxstar]

Hi,

1. Please unzip SFCFix.zip to a new folder e.g. C:\Tempfiles
2. Run DISM again with that path as source:

DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\Tempfiles /LimitAccess

 

[bfanack]

same issue

 

[Maxstar]

Yes, we'll need to replace a large number of files, and the CBS log shows only a shortened result with the corruptions so please provide the latest CBS logs.

 

[bfanack]

i forgot new logs, sorry

 

[Maxstar]

Please do the same with the attached ZIP file.

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

 

[bfanack]

do i need to clean old files in temp folder? or put new fix with the old files?

 

[Maxstar]

Just extract the new files into the WinSxS folder to have a complete set of replacement files to backup later.

 

[bfanack]

 

[Maxstar]

Please do the same with the next batch of replacement files.

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

 

[bfanack]

still same error

 

[Maxstar]

Please do the same with the next batch of replacement files.

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

 

[bfanack]

thanks
still in error
regards

 

[Maxstar]

Please do the same with the next batch of replacement files.

P.s. no need to attach the DISM log, this file is not helpful at all.

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