{"id":10686,"date":"2025-03-25T05:00:49","date_gmt":"2025-03-25T05:00:49","guid":{"rendered":"https:\/\/cheapwindowsvps.com\/blog\/how-to-fix-the-the-referenced-assembly-could-not-be-found-error-0x80073701-on-windows\/"},"modified":"2025-03-25T05:00:49","modified_gmt":"2025-03-25T05:00:49","slug":"how-to-fix-the-the-referenced-assembly-could-not-be-found-error-0x80073701-on-windows","status":"publish","type":"post","link":"https:\/\/cheapwindowsvps.com\/blog\/how-to-fix-the-the-referenced-assembly-could-not-be-found-error-0x80073701-on-windows\/","title":{"rendered":"How to Fix the “The Referenced Assembly Could Not Be Found” Error (0x80073701) on Windows"},"content":{"rendered":"

When working with Windows Server or Windows 10\/11, you may encounter the error:<\/p>\n

The referenced assembly could not be found. Error: 0x80073701.<\/code><\/pre>\n
This issue typically arises when adding or removing features or roles. A similar error may also appear when trying to enable optional features via PowerShell, such as the Windows Subsystem for Linux (WSL):<\/p>\n
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux<\/code><\/pre>\n
This error indicates that the necessary source files for the specified component are either missing or corrupt in the Windows installation image.<\/p>\n
To troubleshoot, first check for any updates that may require a reboot by running:<\/p>\n
dism \/online \/get-packages \/format:table | Select-String "Pending"<\/code><\/pre>\n
Reboot the system if updates are pending. If issues persist and certain packages remain in a Pending Reboot state after multiple reboots, you can rename the C:WindowsWinsxsPending.xml<\/code> file to Pending.xml.old<\/code> and restart the server.<\/p>\n
Subsequently, use DISM to check the integrity of the Windows image:<\/p>\n
DISM \/Online \/Cleanup-Image \/CheckHealth<\/code><\/pre>\n
If it indicates that the component store is repairable, proceed with:<\/p>\n
DISM \/Online \/Cleanup-Image \/RestoreHealth<\/code><\/pre>\n
Next, verify the integrity of the system files by running:<\/p>\n
sfc \/scannow<\/code><\/pre>\n
If Windows features are still unserviceable post-repairing system files, consult the %windir%LogsCBSCBS.log<\/code> for errors.<\/p>\n
The CBS log could reveal messages indicating missing files from a specific update, like KB5012170<\/code>. If this is the case, manually download and install the update from the Microsoft Update Catalog. If the update can’t be installed directly, you can extract the contents of the MSU file and manually add the CAB package to the Windows image:<\/p>\n
expand -f:* windows10.0-kb5012170-x64 c:tempDISM.exe \/Online \/Add-Package \/PackagePath:c:TempWindows10.0-KB5012170-x64.cab<\/code><\/pre>\n
If the update is not applicable to your Windows version, you might need to configure Windows to ignore the corrupted package. Note, these steps are risky and should be approached with caution:<\/p>\n
    \n
  1. Navigate to HKLMSOFTWAREMicrosoftWindowsCurrentVersionComponent Based Servicing<\/code> in the registry.<\/li>\n
  2. Change the ownership of this registry key to your account and grant full control.<\/li>\n
  3. Find the listed update package and set the CurrentState<\/strong> value to 0, indicating it is not present.<\/li>\n
  4. Restore original permissions for security and restart your computer.<\/li>\n<\/ol>\n
    Afterwards, check if you can install Windows features without issues. If multiple KB packages show ERROR_SXS_ASSEMBLY_MISSING<\/code>, repeat the process for each.<\/p>\n
    As a last resort, consider performing an in-place upgrade, using an installation ISO compatible with your current build. Execute setup.exe<\/code> from the ISO and choose the option to keep personal files and apps.<\/p>\n
    For further assistance, refer to the following links:<\/p>\n