[SOLVED] Windows Server 2016 Build 1493.5989 cannot add feature defender with assembly error 0x80073701

Here's the next fix.

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.

Afterwards try to install the Windows Defender feature again. If it fails attach a new copy of the CBS log.
 

Attachments

Maxstar,

that helped. I was able to install WD on my test server.
Thank you so far.

No it is time to repeat all the steps with your fixlist files on my production server?

Best regards

Arno
 

Attachments

Hi,

You're welcome, glad the problem on the testing environment is solved.

You could simplify the same steps on the production server:

1. Run the following commands:
Code: 
wusa /uninstall /KB:4565511
wusa /uninstall /KB:4577015
wusa /uninstall /KB:5003638

2. With the following steps you can create one Regsearch.txt file for the three updates which are partially installed.

Open a elevated command prompt and run the following command (to be sure that the COMPONENTS hive is loaded).
Code: 
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
Open FRST64.exe as administrator and perform a registry search for:
Code: 
KB4565511;KB4577015;KB5003638

Then I can provide just one fixlist to the remove all the remnants with a single fix?
 
Thats fine,
I'm doing a backup right now, that will take about another half hour.
Will you be online for so long?
 
On the test server, scf /scannow now reports corrupted files. Is this due to the registry cleanup and do I need to fix this?
 
I just started scanhealth (finished) and restorehealth, thats not finished.
 

Attachments

This issue has nothing to do with the removed updates, but it is a common (hash mismatch) issue on server systems.

Step 1. Download
56f31e53c97da-SFCFix.PNG
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.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

restorehealth reported error. I think I need to bring the test server online and repeat restorehealth?
 
Yes, I would run the fix above on the test server and then run DISM with the restorhealth parameter again, and afterwards SFC /Scannow, just to be sure there are no remaining issues.
 
The fix completed succesfully, so I don't expect any more errors after running DISM and SFC / Scannow.
 
You were right.
The test server is ok.
Now it goes to the production server.
 
Great, let me know when you're ready and I will provide a new fixlist to remove the three partially installed updates at once.
 
Here's the fixlist for the 3 KB's, including the following warning because no one else should use this fix.

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

Attachments

Hi Maxstar,

here ist the fixlog. I was able to install WD.
Can I use the SFC Fix from the Testserver or would recommend to repeat the steps?
 

Attachments

Let's run SFC /Scannow and DISM with the RestoreHealth parameter first, afterwards attach the CBS log if it fails. Then I can take a look if the same issue appeared.
 
Exactly the same issue is reported, so I would perform the steps in post #28 on the production server as well.
 
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