[SOLVED] The referenced assembly could not be found.

swstrath

Member
Joined
Nov 24, 2022
Posts
9
When attempting to install a feature on Server 2016 I am presented with the error "The Referenced assembly could not be found. Error: 0x80073701"

When running dism, the following 1015 event is logged in the even viewer "0 of 18 instances of system store corruption have been repaired. Unrepaired corruptions may lead to failures in future system servicing."

I have tried using dism with a different sources but its not fixed it.

Can anyone help fix this issue?
 

Attachments

Hi and welcome to Sysnative,

Follow these instructions to remove an update.
  • Open the Start menu of Windows and type the command CMD
  • When you see Command Prompt on the list, right-click on it and select Run as administrator.
  • When command prompt opens, copy and paste the following command into it, then press enter.
Code:
wusa /uninstall /KB:4507459
  • Let me know if it says it was successful or you get the message: The update KB4507459 is not installed on this computer.
 
Hi Maxstar,

When I run the provided command I get the message "The update KB4507459 is not installed on this computer."

1695802869369.png
 
Hi,

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Open the startmenu and type the command cmd.
  • After you find the Command Prompt, right click on it and select Run as Administrator.
  • Copy and paste the following into the Command Prompt and press enter.
Code:
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
Right-click on the file FRST64.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Registry button.
Code:
KB4507459
  • When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
  • Post the logfile SearchReg.txt as attachment in your next reply.
 
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.
 

Attachments

Great, here's the next fix.

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.
650c22f99662d-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

I have attached requested logs but I retried the Install and its now Successful so looks like my initial problem has been solved. I did receive an error when running dism so not sure if that still indicates a corruption somewhere, its not really hindering me though at this point.
 

Attachments

  • CBS (2).zip
    CBS (2).zip
    11.2 MB · Views: 1
  • SFCFix.txt
    SFCFix.txt
    18 KB · Views: 2
  • Screenshot 2023-09-27 135109.png
    Screenshot 2023-09-27 135109.png
    93 KB · Views: 4
  • Screenshot 2023-09-27 135040.png
    Screenshot 2023-09-27 135040.png
    44.6 KB · Views: 4
Glad the installation of the feature succeeded without any issues. Can you please reboot the server and then run DISM again.
 
Hi Maxstar, That restart seems to have done it. Thanks for your time and help, I really appreciate it.
 

Attachments

  • Screenshot 2023-09-27 151113.png
    Screenshot 2023-09-27 151113.png
    26.4 KB · Views: 5

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top