CheckSUR riddled with errors, DISM gives up.

[FrozenHaxor]

Here you go: COMPONENTS.zip

 

[PeterJ]

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.
  
  
• 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.

 

[FrozenHaxor]

Log:

 

[PeterJ]

The remaining missing files are for a Windows 7 SP1 Polish installation only which I currently don't have.
Do you have access to a similar machine to retrieve the missing files?

 

[FrozenHaxor]

I could prepare a clean installation of such OS on a spare machine. What would I need to do next?

 

[PeterJ]

Just report back when the installation of Windows 7 SP1 is ready. We 'll go from there.

 

[FrozenHaxor]

Good to go, got that install ready.

 

[PeterJ]

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 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.
   
   
2. Download the attachment fixlist.txt and save it to your desktop.
3. Right-click on FRST64.exe and select "Run as administrator".
4. Press the Fix button.
5. The tool will now process fixlist.txt.
6. 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.
7. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
8. Post the logfile Fixlog.txt as attachment in your next reply.

 

[FrozenHaxor]

Here is the log from donor system:

 

[PeterJ]

Do the following on the donor machine.

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
  
  SFCFix and move the executable to your desktop.
• Download the attachment SFCFixScript.txt and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFixScript.txt 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.
• Attach that file to your next reply.
• Also attach the file log.zip which is on your desktop.

 

[FrozenHaxor]

Here you go:

 

[PeterJ]

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
  
  SFCFix.exe executable and release it.
  
  
• 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.

Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log to your next reply.

 

[FrozenHaxor]

Logs:

 

[PeterJ]

Do the following on the donor machine.

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 and <date>_<time>.zip will appear in the same directory the tool is run from.
7. Post both files as attachment in your next reply.

 

[FrozenHaxor]

I apologize for the delayed response, had a slight setback. Here are the files:

 

[PeterJ]

No need to apologize. We're not in a race.

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
  
  SFCFix.exe executable and release it.
  
  
• 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.

Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log to your next reply.

 

[FrozenHaxor]

Looks like you've managed to fix all of the errors! Thanks so much!

Here's the logs:

 

[PeterJ]

Great. Any remaining issues on this machine ?

 

[FrozenHaxor]

Well, honestly not sure if this is suitable for this forum, but basically there is an issue with Office 2016 that had a sudden onset and for totally unknown reason. I believe it happened after Office did some automatic self update. Everything works fine, except when I try to save to a network share drive on a windows server machine, Word or Excel or PowerPoint simply crashes and disappears without any message whatsoever. All other computers work fine and are able to save and read from the network share, but they are Windows 10 machines so perhaps that's the difference. It is also impossible to open any Office file directly from the share, Office loading logo will show briefly then disappear without any information, a silent crash. I have to first drag the file out of the share using file explorer, then open it from a local drive. Same goes for saving, I have to save locally and then drag the file onto the server. Any other program (notepad etc) can save and read directly from the share no problem. Only Office fails at this.

I tried to run extensive online repair of the Office, I even removed it completely and installed again - nothing has worked.

The server did not have any interruptions or updates during the time this problem came up. I'm kinda at a loss with it.

Other than this the machine runs great and even installed new updates that would fail before.

 

[PeterJ]

Everything works fine, except when I try to save to a network share drive on a windows server machine, Word or Excel or PowerPoint simply crashes and disappears without any message whatsoever.

Remove the network share and reboot the machine.
Recreate the share and try again. Report the result.