system.runtime.remoting.dll Missing: Repair .NET Framework on Windows

system.runtime.remoting.dll is a genuine Microsoft .NET Framework assembly, not a DirectX, Visual C++, graphics-driver, or ordinary Windows system DLL. If Windows says system.runtime.remoting.dll is missing or cannot be loaded, repair or reinstall the .NET Framework version required by the affected program instead of downloading a replacement DLL.

The correct fix depends on whether one application fails, several .NET applications fail, the program requires .NET Framework 3.5, or the error is actually an assembly-binding or dependency problem.

As an Amazon Associate I earn from qualifying purchases.

What this file actually does

System.Runtime.Remoting.dll belongs to the legacy .NET Framework Remoting infrastructure. .NET Framework applications used remoting for communication between objects, application domains, processes, and machines through proxies, channels, and related services.

Microsoft documents remoting types such as RemotingService in the System.Runtime.Remoting.dll assembly. Some related remoting types are implemented in mscorlib.dll, so the namespace, assembly name, and physical file do not always correspond one-to-one.

The file may appear in file information as Microsoft .NET Runtime Object Remoting and is published as part of Microsoft .NET Framework.

.NET Framework versus modern .NET

This file belongs to .NET Framework, not modern .NET.

.NET Framework is the Windows-focused runtime family used by many older desktop applications. Depending on the Windows release, parts of .NET Framework are included with Windows or available as optional components.

Modern .NET versions, including .NET 6 and later, do not support .NET Remoting. Installing a standalone copy of System.Runtime.Remoting.dll does not add the missing remoting infrastructure to a modern .NET application. If a developer has ported an application from .NET Framework to modern .NET, the application must use a supported replacement for remoting or continue running on its compatible .NET Framework build.

Microsoft maintains an overview of .NET Framework installation and documents technologies unavailable on .NET 6 and later.

Where the file normally lives

System.Runtime.Remoting.dll is a managed MSIL assembly. It is normally resolved through the .NET Framework installation, the Global Assembly Cache, application probing paths, and assembly-binding policy.

For .NET Framework 4 and later, the GAC is commonly located below:

%windir%\Microsoft.NET\assembly

A loaded-assembly report may show a path resembling:

C:\Windows\Microsoft.Net\assembly\GAC_MSIL\
System.Runtime.Remoting\v4.0_4.0.0.0__b77a5c561934e089\
System.Runtime.Remoting.dll

The exact directory varies with Windows, the installed Framework generation, servicing updates, and process architecture. Microsoft explains the Global Assembly Cache and how the runtime locates assemblies.

Do not assume that the file should be in C:\Windows\System32 or C:\Windows\SysWOW64. Those directories are primarily associated with Windows and native system components. Copying a managed Framework assembly into either directory does not repair the Framework installation.

Does it have separate 32-bit and 64-bit copies

Not in the same way as a native DLL.

System.Runtime.Remoting.dll is managed MSIL code rather than a normal x86 or x64 native runtime library. A 32-bit or 64-bit .NET Framework process can load the appropriate managed Framework assembly when the required Framework components and dependencies are installed.

A program may still have architecture-related problems if another dependency is native, if the wrong application build is installed, or if a different DLL is actually causing the failure. Do not move files between System32 and SysWOW64 to solve this message.

Cause-by-symptom guide

What you see	Most likely explanation	Correct first action
Several .NET applications fail	Damaged or incomplete .NET Framework installation	Run the .NET Framework Repair Tool, then repair or install the required Framework runtime
One program fails after an update or reinstall	Incomplete application installation or a private application dependency	Repair or reinstall that application from its original vendor
An old program requests .NET 2.0, 3.0, or 3.5	The separate .NET Framework 3.5 feature is disabled or missing	Enable .NET Framework 3.5 (includes .NET 2.0 and 3.0)
The message includes Version=4.0.0.0	The application is requesting a .NET Framework assembly identity	Repair the .NET Framework 4.x installation and check assembly binding
The message says “one of its dependencies”	The named assembly may exist, but another dependency cannot be resolved	Capture the complete error and repair the application or Framework
The message says “not designed to run on Windows” or shows a bad-image code	A file or dependency may be corrupt or incompatible	Run DISM, SFC, and the appropriate Framework repair
Windows Security lists the file in Protection history	Antivirus quarantine or a false positive may have removed it	Verify the path and detection before restoring; otherwise repair .NET Framework
Only a game fails and its launcher offers Verify or Repair	The game installation is incomplete	Use the launcher’s repair or file-verification function
The application is built for .NET 6 or later	.NET Remoting is not supported by modern .NET	Install the vendor’s .NET Framework build or contact the developer
The error names msvcp140.dll, d3dx9_43.dll, or another file	The problem is not System.Runtime.Remoting.dll	Install or repair the package belonging to the named file

A missing-file popup does not always prove that the named file is absent. The loader may have failed to resolve the requested assembly identity, a binding redirect may be wrong, or another dependency may have failed first.

Fix 1: Identify the application and exact error

Before changing Windows components, record the full message.

Look for these details:

• The exact filename and capitalization.
• Whether the message says “missing,” “not found,” “could not load file or assembly,” or “not designed to run on Windows.”
• Any requested assembly version, such as Version=4.0.0.0.
• The application or launcher displaying the message.
• The full path shown in the error.
• Any error code, such as 0xc000012f or 0xc000007b.
• Whether one program fails or several programs fail.
• Whether the issue began after Windows Update, antivirus activity, a cleanup utility, an application update, or an interrupted installation.

These distinctions determine whether the repair belongs to Windows, .NET Framework, or the application itself.

For example, this message usually indicates an assembly-loading problem:

Could not load file or assembly
'System.Runtime.Remoting, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089' or one of its dependencies.
The system cannot find the file specified.

The phrase “or one of its dependencies” is important. It does not necessarily mean that System.Runtime.Remoting.dll itself is absent.

Fix 2: Repair the affected application first when only one program fails

If every other .NET application works and only one game or program displays the error, repair that application before changing Windows.

Use Windows application repair

On Windows 11:

1. Open Start.
2. Select Settings.
3. Select Apps.
4. Select Installed apps.
5. Find the affected program.
6. Select the three-dot menu beside it.
7. Choose Advanced options, if available.
8. Select Repair.
9. Start the program again.

On Windows 10:

1. Open Start.
2. Select Settings.
3. Select Apps.
4. Select Apps & features.
5. Select the affected program.
6. Select Advanced options, if available.
7. Choose Repair.

The Repair option may not be available for every desktop application.

Reinstall from the original source

If Windows does not offer Repair:

1. Close the application and its launcher.
2. Uninstall the program from Settings > Apps.
3. Restart Windows.
4. Download or reinstall the application using its original vendor, launcher, or installation media.
5. Run the program again.

For a game, use the launcher’s Verify, Repair, or Verify integrity of game files command where available.

If the application installer places a private copy of System.Runtime.Remoting.dll beside the executable, do not overwrite that copy with a file from another computer. It may be tied to the application’s deployment, configuration, or assembly identity.

If reinstalling the program fixes the error, the original installation was incomplete or damaged. If the program still fails while other .NET applications work, collect the complete error and contact the application publisher.

Fix 3: Repair Microsoft .NET Framework automatically

The official .NET Framework Repair Tool is appropriate when Framework files, registration data, or installation state are damaged.

1. Open Microsoft’s .NET Framework Repair Tool page.
2. Download the tool from Microsoft.
3. Run the downloaded installer.
4. Accept the license terms.
5. Allow the tool to inspect the Framework installation.
6. Apply the recommended repair.
7. Restart Windows.
8. Retry the affected application.

The tool is designed to repair the Framework installation. It does not repair a broken application’s private files, obsolete configuration, or missing non-Framework dependency.

If the tool reports that it cannot complete the repair, continue with the appropriate Framework installation below. If several applications remain broken, also run the Windows component repair commands in Fix 7.

When the repair involves repeatedly running system commands and checking whether Windows changed anything, Outbyte PC Repair can provide a scan that identifies repair issues; its full repair functions require the full version, and it is optional rather than required for this fix.

Fix 4: Install or repair the .NET Framework 4.x Runtime

Use this fix when the application targets .NET Framework 4.x, the error requests an assembly such as version 4.0.0.0, or the application documentation specifies .NET Framework 4.

The assembly version and file version are different. A .NET Framework 4 assembly can retain an assembly identity such as 4.0.0.0 while Microsoft changes the file version through servicing updates.

Check whether .NET Framework 4.x is installed

Open PowerShell:

1. Open Start.
2. Search for PowerShell.
3. Right-click Windows PowerShell.
4. Select Run as administrator.
5. Run:

Get-ItemPropertyValue `
  -LiteralPath 'HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' `
  -Name Release

The value is stored under:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full

Microsoft documents these release-key thresholds:

• 528040 indicates .NET Framework 4.8.
• 533320 indicates .NET Framework 4.8.1.

The release value tells you which Framework 4.x generation is installed. It does not prove that every file is healthy.

Install the current supported Framework 4.x Runtime

1. Open the official .NET Framework 4.8.1 download page.
2. Choose Runtime.
3. Do not choose Developer Pack unless you are compiling software.
4. Download the installer.
5. Close running programs.
6. Run the installer as an administrator.
7. Allow setup to complete.
8. Restart Windows.
9. Start the affected program again.

If the computer or application does not support 4.8.1, use the official .NET Framework 4.8 Runtime instead.

Prefer the offline installer when the web installer fails or the computer has unreliable internet access. A newer .NET Framework 4.x release is generally an in-place update, but installing it does not automatically enable the separate .NET Framework 3.5 feature.

How to tell whether this worked

The repair succeeded if:

• The installer completes without an error.
• Windows restarts normally.
• The application opens without the System.Runtime.Remoting.dll message.
• Other affected .NET applications also start.

If the same error remains, check whether the application requires .NET Framework 3.5 rather than 4.x. If only that application remains broken, repair or reinstall the application.

Fix 5: Enable .NET Framework 3.5 for older applications

.NET Framework 3.5 includes .NET Framework 2.0 and 3.0 components. Many older applications require this separate feature even when .NET Framework 4.8 or 4.8.1 is installed.

Installing .NET Framework 4.x does not automatically satisfy every application built for .NET Framework 1.1 through 3.5.

Enable it through Windows Features

On Windows 10 or Windows 11:

1. Open Start.
2. Search for Windows Features.
3. Select Turn Windows features on or off.
4. Select the checkbox beside .NET Framework 3.5 (includes .NET 2.0 and 3.0).
5. Select OK.
6. If Windows asks to download files, allow it.
7. Restart Windows if prompted.
8. Start the application again.

If the checkbox is already selected, clear it, restart Windows, select it again, and restart once more. Do this only when the feature state appears inconsistent.

Enable it from an elevated Command Prompt

1. Open Start.
2. Search for Command Prompt.
3. Right-click it.
4. Select Run as administrator.
5. Run:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All

1. Wait for DISM to finish.
2. Restart Windows.
3. Retry the application.

Use matching installation media when Windows cannot find source files

If DISM reports that the source files cannot be found, use installation media that matches the installed Windows version.

For media mounted as drive D:, run:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /Source:D:\sources\sxs /LimitAccess

Replace D: with the actual drive letter.

The installation media must match the installed Windows version. Media from a different Windows release can create a mismatched or unserviceable Framework installation.

On newer Windows 11 releases where .NET Framework 3.5 is delivered as a standalone installer rather than the traditional optional feature, use Microsoft’s version-specific instructions on the .NET Framework 3.5 installation page.

How to tell whether .NET 3.5 fixed the problem

The fix worked if the older application starts and no longer asks for the remoting assembly. If the message changes to another missing file, install or repair the component named in the new message rather than copying the original DLL.

If the feature installs successfully but the program still fails, repair or reinstall the application. The program may require a private dependency or an older configuration file.

Fix 6: Install Windows updates

.NET Framework is serviced through Microsoft’s Windows and Framework servicing channels. An incomplete update can leave Framework components in an inconsistent state.

1. Open Start.
2. Select Settings.
3. On Windows 11, select Windows Update.
4. On Windows 10, select Update & Security, then Windows Update.
5. Select Check for updates.
6. Install available updates.
7. Restart Windows.
8. Check for updates again after the restart.
9. Retry the application.

Use Microsoft’s instructions for installing Windows updates.

If Windows Update repeatedly fails, record the displayed error code. Do not repeatedly interrupt the update process. Continue with DISM and SFC if the Framework or Windows component store appears damaged.

Fix 7: Repair Windows components with DISM and SFC

Use these commands when the Framework installer fails, Windows reports a bad image, multiple system components are damaged, or the file may have been removed from a protected Windows component.

Microsoft recommends running DISM before SFC.

Run DISM

1. Open Start.
2. Search for Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for the operation to complete.
2. Restart Windows if DISM reports that a restart is required.

DISM checks and repairs the Windows component store. It can take time and may appear to pause at a percentage. Allow it to finish.

Run SFC after DISM

In the same elevated Command Prompt, run:

sfc /scannow

Wait until verification reaches 100 percent.

Possible results include:

• Windows Resource Protection did not find any integrity violations: SFC found no protected-file corruption.
• Windows Resource Protection found corrupt files and successfully repaired them: restart Windows and retry the application.
• Windows Resource Protection found corrupt files but was unable to fix some of them: run DISM again, restart, and run SFC again. If it still cannot repair the system, use matching installation media or Windows recovery options.

If DISM cannot obtain repair files from Windows Update, Microsoft documents using a matching repair source with /Source and /LimitAccess.

When the manual DISM and SFC process becomes difficult to track, Outbyte PC Repair can scan for repair issues and show what needs attention; the full version performs its repair functions, but Microsoft’s DISM and SFC remain the built-in path.

Do not use a DLL downloaded from an unknown source as a substitute for component-store repair.

Fix 8: Check Windows Security quarantine

Antivirus software can quarantine a legitimate Framework file, although a missing-file message alone does not prove that antivirus software removed it.

1. Open Start.
2. Search for Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent detections.
7. Check whether the detection identifies System.Runtime.Remoting.dll.
8. Verify the path and detection details before taking action.

Restore the file only if you can verify that it is the genuine Microsoft-supplied file and the detection is a false positive. Microsoft warns that restoring a real threat can expose the device.

If the file was removed rather than quarantined, repair .NET Framework instead of searching for a replacement download. Afterward, update Defender security intelligence and run a full scan.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 9: Check assembly binding and application configuration

A managed application can report that it cannot load System.Runtime.Remoting.dll even when a file with that name exists somewhere on the computer.

The .NET Framework loader considers:

• The requested assembly identity.
• Binding policy.
• The Global Assembly Cache.
• Application probing paths.
• Codebase settings.
• Binding redirects.
• The application’s private dependencies.

Check the complete exception for:

Version=
Culture=
PublicKeyToken=

If the application includes a configuration file beside its executable, do not randomly edit it. Look for incorrect probing paths, obsolete binding redirects, or a <codeBase> entry only when you understand what the application expects.

The safest repair order is:

1. Confirm whether the application targets .NET Framework.
2. Repair or reinstall the required Framework generation.
3. Repair or reinstall the application.
4. Contact the vendor if the complete assembly identity still cannot be resolved.

A standalone DLL copied into the application folder may satisfy one lookup while creating a strong-name, assembly-version, or servicing mismatch elsewhere.

Fix 10: Treat bad-image and architecture errors separately

Messages such as these require additional care:

The application was unable to start correctly (0xc000007b).

The program cannot start because the file is either not designed
to run on Windows or it contains an error.

BadImageFormatException

These messages may indicate a corrupt file, an incompatible .NET generation, or a 32-bit/64-bit mismatch in another dependency. They do not prove that System.Runtime.Remoting.dll is the bad component.

Use this sequence:

1. Capture the full error and the named module.
2. Run DISM and SFC.
3. Repair the required .NET Framework generation.
4. Repair or reinstall the affected application.
5. Check native dependencies separately.
6. Use the application’s correct x86 or x64 build if the vendor provides separate versions.

Do not attempt to make the problem fit a 32-bit or 64-bit DLL-copying solution. This assembly is managed MSIL, while a different native dependency may be responsible for the architecture error.

Why regsvr32 does not fix this file

Do not run:

regsvr32 System.Runtime.Remoting.dll

regsvr32 is intended for native DLLs that expose COM registration entry points such as DllRegisterServer. System.Runtime.Remoting.dll is a managed .NET Framework assembly and is not a self-registering COM server.

The command will usually produce an error such as a missing entry point or an invalid registration message. Even if a command appears to complete, it does not repair .NET Framework assembly loading.

regasm is also not a general repair command. It registers selected .NET Framework assemblies for COM clients and does not repair an ordinary application that cannot load its Framework dependencies.

Why Visual C++, DirectX, and drivers are usually unrelated

Visual C++ Redistributables install Microsoft C and C++ runtime libraries. DirectX packages install DirectX components. Neither package installs .NET Framework Remoting.

Install those packages only when the complete error names a file belonging to that technology, such as:

msvcp140.dll
vcruntime140.dll
d3dx9_43.dll
xinput1_3.dll

Similarly, there is no evidence that System.Runtime.Remoting.dll belongs to a graphics, chipset, audio, storage, or other hardware-driver package.

If the actual error names a driver DLL or the application’s failure is independently proven to be driver-related, check drivers separately:

1. Open Start.
2. Search for Device Manager.
3. Open it.
4. Expand the device category named by the error or related hardware.
5. Right-click the device.
6. Select Properties.
7. Open the Driver tab.
8. Record the provider, date, and version.
9. Use Update Driver or obtain the correct package from the hardware or computer manufacturer.
10. Restart Windows and retest.

Do not reinstall a display or chipset driver as a response to a Framework-only error.

If checking dozens of device versions manually is the main obstacle, Outbyte Driver Updater can scan for outdated drivers and identify updates; driver installation through its full version is optional, and a driver update is not the definitive fix when the error specifically names System.Runtime.Remoting.dll.

Why random DLL downloads are unsafe

Do not download System.Runtime.Remoting.dll from a random DLL website and copy it into System32, SysWOW64, or the application folder.

That approach can fail because:

• The file may be modified or malicious.
• The version may not match the application’s requested assembly identity.
• The file may belong to a different .NET Framework servicing level.
• A managed assembly may require related files and registration state.
• The copy may bypass normal Framework servicing.
• The application may actually be missing another dependency.
• A file copied into the wrong directory can make later troubleshooting harder.

Use Microsoft’s .NET Framework Runtime, Windows Features, the .NET Framework Repair Tool, Windows Update, DISM, and SFC. If a specific application supplies a private assembly, reinstall that application from its original publisher.

Manual replacement is defensible only as a controlled recovery procedure after identifying a damaged protected file and obtaining a verified same-version file from the same Windows installation source. It is not a reason to use an unknown DLL download.

Last-resort recovery options

If several Windows components remain damaged after DISM and SFC, and the .NET Framework installer still fails, consider recovery options in this order:

1. Repair or reinstall the affected application.
2. Run System Restore if a suitable restore point exists.
3. Perform an in-place Windows repair.
4. Use Windows recovery options after backing up important personal data.

To start System Restore:

1. Press Win + R.
2. Enter:

rstrui.exe

1. Press Enter.
2. Choose an appropriate restore point.
3. Review the affected programs.
4. Complete the restore.
5. Restart Windows and test the application.

You can also open Control Panel > Recovery > Open System Restore.

System Restore rolls back system files, registry settings, and installed programs while preserving personal files. It does not guarantee that an application’s private files or modern application data will be restored.

Frequently asked questions

Is System.Runtime.Remoting.dll a real Windows file

Yes. It is a genuine Microsoft .NET Framework assembly used by the legacy .NET Remoting infrastructure.

It is supplied through .NET Framework rather than being a normal standalone native Windows DLL.

Does it ship with Windows

The answer depends on the Windows release and the installed .NET Framework components. Some Framework components are included with Windows, while others are optional or require installation.

A missing file should be repaired through the appropriate Microsoft Framework component rather than copied from another computer.

Is it part of .NET 6, 7, 8, 9, or 10

No. .NET Remoting is a .NET Framework technology and is not supported by .NET 6 or later.

If a modern .NET application requests this assembly, verify that you installed the correct vendor build. The developer may need to provide a .NET Framework version or replace the remoting dependency.

Should I copy it into System32 or SysWOW64

No. It is a managed MSIL assembly and is normally resolved through .NET Framework and the GAC. Copying it into either native Windows directory is not a normal repair method.

Should I run regsvr32

No. regsvr32 is for DLLs that expose COM registration entry points. System.Runtime.Remoting.dll is not an ordinary self-registering COM DLL.

Will Visual C++ Redistributable fix it

No. Visual C++ Redistributables install C and C++ runtime libraries. They do not install .NET Framework Remoting.

Will DirectX fix it

No. DirectX repairs are relevant when the error names a DirectX file. They do not install System.Runtime.Remoting.dll.

Does .NET Framework 4.8 replace .NET Framework 3.5

Not necessarily. .NET Framework 3.5 is a separate Windows feature and includes components used by applications targeting .NET Framework 2.0 and 3.0.

Enable .NET Framework 3.5 when an older application requires it.

Why does the error say “one of its dependencies”

The .NET loader may have found the requested assembly but failed to load another dependency, resolve the requested version, or apply the correct binding policy.

Capture the entire exception before assuming that the named file is absent.

Does the file need a separate x86 and x64 copy

It is not a normal native x86/x64 runtime DLL. A 32-bit or 64-bit managed process can use the appropriate Framework installation, while another native dependency may still have an architecture requirement.

Do not copy files between System32 and SysWOW64.

What information should I give the application vendor

Provide:

• The exact error text.
• The error code.
• The application name and version.
• The Windows version.
• Whether the application is 32-bit or 64-bit, if known.
• The requested assembly version and public key token.
• The full path shown in the error.
• Whether .NET Framework 3.5 is enabled.
• The installed .NET Framework 4.x release value.
• Whether one application or several applications fail.
• What changed immediately before the problem began.
• Whether repairing .NET Framework and reinstalling the application changed the message.

This information lets the vendor distinguish a Framework installation problem from an application-specific dependency or configuration error.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.