Error 1935 an Error Occurred During the Installation of Assembly: Quick Workaround for Stubborn Assembly Install Fails

When error 1935—"an error occurred during the installation of assembly"—strikes, your Windows update or app setup can stall unexpectedly. ✨ I’ve seen it derail everything from .NET Framework repairs to game installations, and the fix is almost always simpler than it seems—especially if you tackle it in the right order.

The culprit is usually one of three things: missing permissions, a corrupted .NET component, or overzealous antivirus blocking the install. Most of the time, running the installer as Administrator or temporarily disabling your security software clears it up in under five minutes.

For stubborn cases, I’ve found that repairing the .NET Framework or running a system file scan fixes 90% of the issues without touching the registry.

You’ll walk away with a working installation and a clearer understanding of why these errors pop up. The steps are straightforward, but I’ll include the exact commands and screenshots for the critical fixes—no guesswork.

If the problem persists after these, we’ll know it’s time to dig deeper into system file corruption or component repair.

This approach works for Windows updates, .NET Framework installs, and third-party applications that rely on assemblies. Let’s get this resolved so you’re back to installing software without frustration.

Why it happens

When Error 1935 disrupts your software installation, it’s usually a sign that something went wrong during the assembly registration process. This error typically surfaces when Windows struggles to properly integrate a required component—often a .NET assembly, DLL, or system file—into its registry or system directories.

Below, we break down the most common culprits and why they trigger this frustrating roadblock.

🔧 Corrupted or Incomplete Downloads

One of the most straightforward reasons for this error is a damaged or partial download of the installer or its dependencies. Here’s why it happens:

• Network interruptions: If your download stops midway (due to a weak connection, VPN issues, or server timeouts), the installer may lack critical files needed for assembly registration.
• Corrupted archives: ZIP or EXE files can degrade over time, especially if extracted partially or from unreliable sources (e.g., pirated copies or untrusted mirrors).
• Antivirus interference: Overzealous security software may quarantine or modify files during extraction, leaving the installer in a broken state.

Science behind it: Windows Installer (MSI) relies on msiexec.exe to register assemblies via the RegAsm.exe or gacutil.exe tools. If the assembly file itself is corrupted, these tools fail silently, triggering Error 1935.

🛡️ Missing or Outdated .NET Framework

The .NET Framework is the backbone for many modern applications, and if it’s missing, outdated, or misconfigured, assemblies won’t register correctly. Here’s the breakdown:

• Version mismatches: An app built for .NET Framework 4.8 won’t work if your system only has 4.7.2 installed. The installer expects specific runtime libraries to be present.
• Partial installations: If .NET was installed via a repair or update but didn’t complete, critical components (like fusion.dll) may be missing.
• Registry corruption: The .NET Framework stores assembly paths in the Windows Registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP). If this data is corrupted, the installer can’t locate required files.

Why it fails: The Windows Installer uses the AssemblyRegistration action to register assemblies. If the .NET runtime isn’t compatible, this action throws Error 1935 because it can’t find the mscoree.dll or clr.dll dependencies.

🗑️ Conflicting or Locked System Files

Sometimes, the issue isn’t with the installer itself but with existing files on your system that are either locked, corrupted, or in use. Common scenarios include:

• Antivirus/file lockers: Programs like McAfee, Norton, or even Windows Defender may temporarily lock DLLs or EXE files during scans, preventing the installer from modifying them.
• Open applications using the same files: If another process (e.g., a background service or running app) has a DLL loaded, the installer can’t overwrite or register it.
• Permission issues: User Account Control (UAC) or incorrect folder permissions (e.g., Program Files owned by SYSTEM instead of your user) can block writes.
• Previous failed installations: Leftover registry keys or partial file installations from aborted setups can conflict with new attempts.

Technical deep dive: The installer relies on Windows’ SetupAPI to handle file operations. If a file is locked (via LockFileEx or MoveFileEx flags), the installer’s CustomAction fails, and Error 1935 is logged in the Windows Installer log (%TEMP%\MSI*.log).

🔄 Registry or System File Corruption

The Windows Registry and system files are the unsung heroes (or villains) of installations. When they’re corrupted, even simple setups can crumble:

• Broken registry entries: Keys under HKEY_CLASSES_ROOT or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall may reference missing or invalid assembly paths.
• Damaged Windows Installer components: Files like msiexec.exe, msi.dll, or Windows Installer service (msiserver) may be corrupted after a failed update or malware attack.
• Pending updates or repairs: If Windows Update is stuck or a repair install (e.g., sfc /scannow) didn’t complete, critical system files may be in a limbo state.

How it triggers the error: During assembly registration, the installer queries the registry for dependencies. If the data is inconsistent (e.g., a 64-bit app trying to register a 32-bit assembly on a mixed-system), the RegAsm tool fails with Error 1935.

🛠️ Third-Party Tools or Conflicting Software

Not all conflicts come from the installer itself—sometimes, other software interferes. Examples include:

• Virtualization tools: VMware, Hyper-V, or Docker may intercept file operations, causing the installer to lose access to critical paths.
• Software suites: Programs like Java, Adobe Creative Suite, or even some games install their own .NET runtimes or DLLs, which can shadow or replace system files.
• Custom installers: Some apps use non-MSI installers (e.g., Inno Setup, NSIS) that bypass standard Windows Installer rules, leading to manual registration failures.

Under the hood: These tools often hook into Windows APIs like LoadLibrary or CreateProcess. If they delay or modify file operations, the installer’s timeline gets disrupted, and assembly registration stalls.

How to Fix Stubborn Assembly Errors

Encountering Error 1935 during an assembly installation can be frustrating, but the right steps can resolve it quickly. Below are targeted solutions mapped to common causes, along with prevention tips to keep your system running smoothly.

🔧 Fix Corrupted or Missing .NET Framework Files

If the error stems from corrupted or incomplete .NET Framework components, repairing or reinstalling them often works.

1. 🔥 Run the .NET Framework Repair Tool
   • Download Microsoft’s official repair tool.
   • Run it as Administrator and follow the prompts to repair corrupted files.
2. 🍳 Reinstall .NET Framework Manually
   • Uninstall the current version via Control Panel > Programs > Programs and Features.
   • Download the latest .NET Framework redistributable and install it.

💡 Pro Tip: If the issue persists, try installing the same version of the .NET Framework that the problematic software requires.

🧹 Clear Windows Installer Cache & Temp Files

Leftover installer files or cache corruption can trigger Error 1935. Clearing them often resolves the issue.

1. 👨‍🍳 Clean Windows Installer Cache
   • Open Command Prompt as Admin and run:

     msiexec /fv "C:\Path\To\Your\Installer.msi"

     (Replace the path with your actual installer file.)
   • Alternatively, use:

     msiexec /unregister
             msiexec /regserver

     to reset Windows Installer.
2. 🥘 Delete Temp & Software Distribution Files
   • Press Win + R, type %temp%, and delete all files.
   • Open C:\Windows\SoftwareDistribution\Download and delete its contents.
   • Restart your PC and retry the installation.

✨ Prevention Tip: Regularly clear temp files using Disk Cleanup (search for it in the Start menu) to avoid future conflicts.

🔒 Adjust User Account Control (UAC) Settings

Strict UAC settings can block installations. Temporarily lowering them may help.

1. 🔪 Lower UAC Temporarily
   • Search for Change User Account Control settings in the Start menu.
   • Drag the slider to Never notify and restart.
   • Retry the installation, then revert UAC settings afterward.
2. ⏰ Run Installer as Administrator
   • Right-click the installer and select Run as Administrator.
   • If using a shortcut, right-click it, go to Properties > Compatibility, and check Run as Administrator.

🎯 Best Practice: Always install software as Administrator to avoid permission-related errors.

🔄 Reinstall or Update Visual C++ Redistributables

Outdated or conflicting Visual C++ components can cause assembly installation failures.

1. 🔄 Uninstall All Visual C++ Redistributables
   • Go to Control Panel > Programs > Programs and Features.
   • Uninstall every Microsoft Visual C++ entry (keep notes on versions).
2. 📊 Install Latest Versions in Order
   • Download the latest versions from Microsoft’s site.
   • Install them in this order:
     1. x86 (32-bit)
     2. x64 (64-bit)

💡 Quick Fix: If the error persists, try installing the exact version required by the software (check its documentation).

🔄 Use System File Checker (SFC) & DISM

Corrupted system files can disrupt installations. Run these built-in tools to restore integrity.

1. 🌡️ Run System File Checker (SFC)
   • Open Command Prompt as Admin and run:

     sfc /scannow

   • Wait for the scan to complete (may take 10+ minutes).
2. 🔧 Repair Windows Image with DISM
   • Run:

     DISM /Online /Cleanup-Image /RestoreHealth

   • Restart your PC and retry the installation.

✨ Prevention Tip: Schedule regular SFC scans (e.g., monthly) to catch corruption early.

🔄 Alternative: Use a Clean Boot

Third-party services or startup apps may interfere with installations. A clean boot isolates the issue.

1. 🚀 Perform a Clean Boot
   • Press Win + R, type msconfig, and hit Enter.
   • Go to the Services tab, check Hide all Microsoft services, then click Disable all.
   • Switch to the Startup tab and click Open Task Manager, then disable all startup items.
   • Restart and retry the installation.
2. 🔄 Re-enable Services Afterward
   • Once the install succeeds, undo the clean boot steps to restore normal operation.

🎯 Pro Tip: If the issue resolves in clean boot mode, re-enable services one by one to identify the culprit.

Frequently asked questions