Referenced Assembly Not Installed on Windows 10?

If Windows 10 says “The referenced assembly is not installed on your system,” an application or Windows component is trying to use a software component that Windows cannot find or load. The message does not identify one universal missing file; the safest fix depends on which program triggered it, so start with Windows Update and the program’s own repair options before attempting advanced system repairs.

What the error means

In Windows, an assembly is a managed software component: a collection of code and related information that an application can use. Applications built with Microsoft .NET may depend on assemblies provided by Windows, the .NET Framework, or the application itself. Windows also uses component packages to install and maintain operating-system features and updates. These related uses can produce similar-looking errors, but they do not all point to the same cause.

The message can appear when installing or opening a program, installing a Windows update, enabling a Windows feature, or running a system maintenance task. A damaged component store, an incomplete update, a missing application dependency, or an application that expects a different version can all be possibilities. The wording alone cannot tell you which one is responsible.

In particular, do not assume that a file with a name such as assembly.dll is necessarily missing, or download a replacement DLL from an unfamiliar website. The error usually needs to be diagnosed by identifying the failing program or Windows operation, not by guessing at a filename.

Start with the program or task that failed

Note when the error occurs and what you were doing. If it appears only when opening one application, focus first on that application. If it appears during Windows Update or while changing a Windows feature, use the Windows repair steps below. If it began after a recent change, such as an update or software installation, record that detail; it can help narrow down the cause.

Restart the computer. A restart can finish a pending update or release files that were in use. Try the failed task again once Windows has loaded.
Check Windows Update. Open Settings > Update & Security > Windows Update, select Check for updates, and install applicable updates. Restart if prompted. Windows 10 support and update availability depend on the device and its servicing status, so follow the options shown on your PC.
Repair or reinstall the affected application. In Settings > Apps > Apps & features, select the program and look for Modify or Repair, if offered. Not every desktop application provides these buttons. Otherwise, use the program’s own installer to repair or reinstall it, and get the installer from its publisher or your organization’s approved source.
Check the application’s requirements. Confirm that it supports your Windows edition and that any required runtime or component is installed. Do not install several similar-looking packages at random; use the application’s documented requirements or the instructions from your IT administrator.

Repair Windows component files

If the error affects Windows itself, happens with several programs, or persists after a failed update, Windows’ built-in servicing commands may help. They check and repair system files and the Windows component store. Use an administrator account and run the commands in the order below.

Right-click Start and choose Windows PowerShell (Admin) or Command Prompt (Admin), depending on what appears. Approve the User Account Control prompt.
Enter DISM.exe /Online /Cleanup-Image /RestoreHealth and press Enter. Wait for it to finish; it may take a while. DISM repairs the Windows image used as a source for system-file repair. It can use Windows Update to obtain needed files, so a working connection may be required.
Then enter sfc /scannow and press Enter. System File Checker scans protected Windows files and attempts to replace damaged copies.
When both operations finish, restart Windows and repeat the task that produced the error.

Run the commands exactly as written, including spaces. Do not close the window just because progress appears to pause. If DISM reports that it could not find source files, or SFC says it could not repair some files, note the result rather than repeatedly running random repair commands. A managed computer may need an administrator or IT team to provide the correct repair source.

When an update or Windows feature is involved

If the error appears specifically during an update, first restart and retry Windows Update. Check that the computer has enough free storage for the update and that its date and time are set correctly. If an update repeatedly fails, record its name or identifier from View update history in Windows Update settings. That information is more useful for targeted troubleshooting than the assembly message by itself.

For a Windows feature, open Control Panel > Programs > Programs and Features and select Turn Windows features on or off. Change only the feature implicated by the failing program, and follow the program’s requirements. Some features require a restart. Avoid turning off unrelated Windows components as a trial-and-error fix; doing so may cause other software to stop working.

If the computer belongs to a workplace or school, check with its administrator before changing optional features, removing updates, or using installation media. Organizations can manage which Windows components and repair sources are available.

Common mistakes and unsafe fixes

Downloading individual DLL files. A DLL from an unverified site may be the wrong version, incomplete, or unsafe. Windows and application installers should supply their own required files.
Editing the registry without a specific diagnosis. The message does not identify a registry entry that needs changing. Uninformed edits can create additional problems.
Running commands from unclear instructions. Use commands from reliable Windows documentation or a qualified administrator. Do not run scripts you do not understand, especially with administrator privileges.
Removing updates or system components immediately. First establish which update or feature is involved. Removing the wrong item can weaken compatibility or undo a needed fix.

A system restore or Windows reinstallation may be considered only after simpler repairs fail and important files are backed up. These are broader changes, and the available recovery options vary by device. If the computer is unstable, encrypted, or managed by an organization, get appropriate help before proceeding.

When to seek more help

Contact the software publisher if one application consistently triggers the message after its repair or reinstall. Provide the exact wording, the action that causes it, the application name and version, and whether other applications are affected. For a Windows update or feature failure, share the relevant update history and the final DISM or SFC message with a support professional.

Seek help from your organization’s IT administrator for a managed computer. If the error occurs in multiple Windows tasks, returns after repairs, or is accompanied by other system failures, a technician can inspect servicing logs and determine whether the component store, update source, or installation needs further attention.

Frequently Asked Questions

What does “the referenced assembly is not installed” mean?
It means Windows or an application tried to use a software component that it could not locate or load. The message does not, by itself, identify the missing component or prove that a particular DLL needs downloading.

Can I fix this error by downloading a DLL?
That is not a safe general fix. A DLL may be the wrong version or come from an untrustworthy source. Repair the affected application or Windows components using trusted installers and built-in tools instead.

Should I run DISM or SFC first?
For a suspected Windows component-store problem, run DISM with /RestoreHealth first, then run sfc /scannow. Restart afterward and check whether the original problem remains.

Why does the error happen in only one program?
The program may have a missing, damaged, or incompatible dependency, while Windows itself is otherwise working. Repairing or reinstalling that program and checking its documented prerequisites is a sensible first approach.

What if DISM or SFC cannot repair the files?
Keep the exact completion message and seek targeted support. A repair source, update problem, or deeper Windows issue may need attention; the error alone is not enough to choose a safe next command.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →