DISM restore health error 1734

[hantraxhat]

Hi guys,
we tried to convert a Win Server 2016 STD to DC edition with DISM, but the process always stuck at same point.
So we run a DISM /online /cleanup-image /restorehealth
and the check failed with error 1734

In the CBS log attached we found some erorrs, could you help us solve that issue?
Unfortunately we can't run other tools than Microsoft provided (like ComponentScanner) by sec policy, so we can investigate only with that.

Thanks

 

[Windows Update Bot]

Hi @hantraxhat,

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

 

[PeterJ]

Hello and welcome,

Unfortunately we can't run other tools than Microsoft provided (like ComponentScanner) by sec policy

If you mean ComponentsScanner, that tool is not provided by Microsoft.

Start with these instructions:
Remove Update Manually

1. Right-Click the Start button and click Command Prompt (Admin) on the list.
2. When command prompt opens, copy and paste the following command into it, then press enter.
   wusa /uninstall /KB:4561616
3. Let me know if it says it was successful or if there are any errors.

 

[hantraxhat]

Hi Peter,
it seems that the KB is not installed:



Thanks

 

[PeterJ]

Ok. KB4561616 is probably partially installed. We need to remove the remnants.
Please do following:

FRST Registry Search

1. Click the Start button and in the search box, type CMD
2. When you see cmd.exe on the list, right-click on it and select Run as administrator.
3. When command prompt opens, copy and paste the following command into it, press enter afterwards.
   
   

   REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS

   
   Note: This loads your components hive which is what we want. Please keep the command prompt window open while you perform the remaining steps. You can minimize it if you wish but keep it open.
4. 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.
5. Right-click on the file FRST64.exe and choose Run as administrator.
6. Copy and paste KB4561616 into the Search box and click the Search Registry button.
7. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
8. You may close any remaining open windows now.

 

[hantraxhat]

Hi Peter,
attached the export of Farbar

Thanks

 

[PeterJ]

Please don't edit the log files.

Step 1:
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 will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to 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.