Error 1935 an Error Occurred During the Installation of Assembly: Assembly Conflict Resolution in 3 Steps

by

Troubleshooting

Error 1935 an Error Occurred During the Installation of Assembly: Assembly Conflict Resolution in 3 Steps

"An error occurred during the installation of assembly"—Error 1935 has haunted me through three Windows updates and a .NET Framework disaster. 💻 The good news? It’s fixable—and I’ve cracked the pattern after 12 failed installations.

Most people blame antivirus or permissions, but the real culprit is often a corrupted registry entry or conflicting assembly version.

The root causes are sneaky: a half-failed update, a leftover registry key from an old install, or your security software flagging the installer as suspicious. I’ve seen this error freeze installations for hours, only to resolve with a single registry tweak or a forced .NET repair.

The key is isolating whether it’s a permissions issue, a file corruption, or an antivirus block.

You’ll need about 20 minutes for the full fix, but the real payoff is a clean installation without the dreaded "assembly conflict" pop-up. We’ll start with the safest steps—like running Windows Update Troubleshooter—and escalate only if needed.

No registry edits unless absolutely necessary, and I’ll warn you before any risky moves.

This works for Windows 10/11 updates, .NET Framework installs, and even third-party software that triggers the error. The same steps saved my coworker’s development machine after a botched Visual Studio update. Let’s get this resolved—permanently.

Root Causes of Installation Failures

When Error 1935 disrupts your software installation, it’s almost always a sign of deeper conflicts beneath the surface. The error occurs when Windows struggles to register or install a required assembly (a compiled code library) during setup.

Below, we break down the most common culprits—each with a clear explanation of why they trigger this frustrating roadblock.

###

🔧 Corrupted or Missing .NET Framework Components

The .NET Framework is the backbone of many Windows applications, acting as a runtime environment for assemblies. If its components are damaged or incomplete, installations fail with Error 1935. Here’s why:

  • Partial updates or failed repairs: Windows Update or manual repairs may leave critical .NET files in a broken state. For example, mscoree.dll or fusion.dll (part of the Windows Fusion assembly binding system) might be corrupted, preventing the installer from validating dependencies.
  • Version mismatches: An app requiring .NET 4.8 may install on a system with only .NET 4.7.2 partially configured. The installer expects specific registry entries and DLL files that don’t exist, causing the failure.
  • Antivirus interference: Security software scanning %WinDir%\Microsoft.NET\Framework during installation can trigger false positives or prematurely delete temporary files needed for registration.

Pro tip: Use the official .NET repair tool to restore missing components before retrying the install. 💡

###

🧩 Assembly Binding Failures in Windows Fusion

Windows uses a system called Assembly Binding (managed by fusion.dll) to locate and load assemblies at runtime. Error 1935 often surfaces when this process breaks down:

  • Incorrect registry entries: The installer checks the HKEYLOCALMACHINE\SOFTWARE\Microsoft\Fusion registry key for assembly bindings. If a previous install left malformed entries (e.g., pointing to a deleted file), Windows throws a 0x800736B3 error (which translates to Error 1935).
  • Side-by-side (SxS) conflicts: Some apps rely on shared assemblies (e.g., System.Windows.Forms.dll) stored in C:\Windows\assembly\. If another app modified or deleted these files, the installer can’t bind to them, triggering the failure.
  • Digital signature validation errors: If an assembly’s signature is invalid or revoked, Windows blocks its installation. This happens frequently with third-party or older software.

Pro tip: Run fuslogvw.exe (from the %WinDir%\Microsoft.NET\Framework\ folder) to log binding failures and identify which assembly is misbehaving. ✨

###

🛡️ Permissions and User Account Control (UAC) Issues

Even if the assembly exists, Windows may block its installation due to permission restrictions. Here’s how:

  • Insufficient admin rights: Installers often require SYSTEM or Administrators privileges to write to C:\Windows\assembly\ or modify registry keys. Running the installer as a standard user triggers Error 1935.
  • UAC virtualization conflicts: If UAC redirects writes to a virtual store (e.g., %LocalAppData%\VirtualStore\), the installer may fail to register the assembly globally. This is common with 32-bit apps on 64-bit systems.
  • Antivirus sandboxing: Some security tools run installers in a restricted environment, preventing writes to protected folders like Program Files.

Pro tip: Always run installers as Administrator and temporarily disable third-party antivirus tools during setup. 🔒

###

🗑️ Leftover Files from Previous Installs

Failed or incomplete installations can leave behind orphaned files or registry keys, confusing the new installer:

  • Dangling assembly references: If a prior install added entries to HKEY_CLASSES_ROOT\Installer\Assemblies but didn’t clean up, the new installer may inherit conflicts.
  • Partial GAC (Global Assembly Cache) entries: The C:\Windows\assembly\ folder might contain broken links or half-installed assemblies, causing binding redirects to fail.
  • MSI repair corruption: If a previous repair operation interrupted, it may leave the MSIHap registry keys in a inconsistent state.

Pro tip: Use msiexec /fva (for MSI-based installers) to force a repair, or manually clean the assembly folder via Assembly Binding Log Viewer. 🧹

Each of these causes disrupts the assembly registration pipeline, where Windows verifies, loads, and installs dependencies. The good news? Most can be resolved with targeted fixes—we’ll cover those in the next steps. Stay tuned! 🚀

How to solve it

Encountering an installation error like Error 1935 can be frustrating, but don’t worry—most fixes are straightforward if you tackle them systematically. Below, we’ve mapped common causes to their solutions, ensuring you can resolve the issue without unnecessary hassle.

Follow these steps, and you’ll be back to smooth software installations in no time!

🔥 Cause 1: Missing or Corrupt .NET Framework Components

If your system lacks the correct version of the .NET Framework or it’s corrupted, installations will fail with this error. This is especially common when upgrading or installing newer software.

  • 🍳 Fix: Reinstall or repair the .NET Framework.
    1. Open Control Panel > Programs and Features.
    2. Click Turn Windows features on or off.
    3. Ensure .NET Framework 3.5 (includes .NET 2.0 and 3.0) and .NET Framework 4.8 are checked. If not, enable them and restart.
    4. If already enabled, download the latest .NET Framework installer from Microsoft and run it.
  • 💡 Prevention Tip: Keep your .NET Framework updated via Windows Update. Enable automatic updates to avoid compatibility issues.

👨‍🍳 Cause 2: Conflicting or Incomplete Previous Installations

Leftover files or partially installed assemblies from a failed attempt can trigger Error 1935. This often happens when an installation is interrupted or when multiple versions of the same software are present.

  • 🥘 Fix: Clean up and reinstall.
    1. Use Microsoft’s Windows Installer CleanUp Utility (if available) to remove residual components. Alternatively, manually delete the installation folder (e.g., C:\Program Files\YourSoftware).
    2. Run System File Checker to repair corrupted system files:
      1. Open Command Prompt as Administrator.
      2. Type sfc /scannow and press Enter.
      3. Wait for the scan to complete and restart your PC.
    3. Reinstall the software using the latest installer from the official source.
  • ✨ Prevention Tip: Always uninstall old software before installing a new version. Use Revo Uninstaller or CCleaner for thorough cleanup.

🔪 Cause 3: Permissions or Registry Issues

If your user account lacks sufficient permissions or the Windows Registry has incorrect entries, installations may fail midway. This is common in shared or restricted environments (e.g., work PCs).

  • 👑 Fix: Adjust permissions and repair the registry.
    1. Run as Administrator:
      1. Right-click the installer and select Run as Administrator.
      2. If prompted by UAC, confirm with Yes.
    2. Repair Registry Permissions:
      1. Open Command Prompt as Administrator.
      2. Type secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose and press Enter.
      3. Restart your PC.
  • 🎯 Prevention Tip: Avoid installing software as a standard user. Create a dedicated admin account for installations or use Windows Installer (msiexec) with elevated privileges.

⏰ Cause 4: Antivirus or Firewall Blocking Installation

Overzealous security software can flag installation files as threats, causing interruptions. This is especially true for third-party antivirus programs.

  • 🛡️ Fix: Temporarily disable security software.
    1. Pause or disable your antivirus/firewall (e.g., Windows Defender, McAfee, Norton).
    2. Attempt the installation again.
    3. After installation, update your antivirus definitions and re-enable it.
  • 💡 Prevention Tip: Add the installer’s folder to your antivirus’s exclusion list before running it. Use trusted sources for downloads to avoid false positives.

Stuck on a specific step? Double-check the error logs in Event Viewer (eventvwr.msc) under Windows Logs > Application for detailed clues. Most Error 1935 issues resolve with one of these fixes—so pick the one that matches your scenario and get back to smooth sailing!

Frequently asked questions

1

Why does Error 1935 appear during software installations?

This error occurs when Windows fails to register or install a required assembly (code library) during setup. Common triggers include corrupted .NET Framework components, permission issues, or conflicts from previous incomplete installations. The system can't properly validate or load the assembly needed for the software to run.

2

Can I fix Error 1935 without advanced technical skills?

Most solutions involve basic troubleshooting like repairing the .NET Framework, running the installer as Administrator, or temporarily disabling antivirus software. The step-by-step fixes in our guide are designed for all skill levels—just follow the instructions carefully.

3

Will disabling my antivirus permanently affect my security?

No, you should only disable it temporarily during installation. After the software installs successfully, remember to re-enable your antivirus and update its definitions. Many security programs offer a "pause protection" feature that's safer than full disablement.

4

What should I do if none of the fixes work?

Check the Windows Event Viewer (eventvwr.msc) for detailed error logs under "Windows Logs > Application." Look for entries around the time of the failed installation—they often reveal specific assembly names causing conflicts. This helps identify whether it's a registry issue or missing system files.

5

Is Error 1935 dangerous for my computer?

The error itself isn't harmful, but the underlying causes (like corrupted system files or registry issues) could potentially affect system stability. That's why fixing it promptly is important. Always back up important data before making registry changes or running system repairs.

★★★★★4.8(5 reviews)
Categories Troubleshooting