Error 1935 an Error Occurred During the Installation of Assembly: 3-Step Workaround for Stubborn Assembly Installs

"Error 1935 an error occurred during the installation of assembly"—I’ve seen this freeze more Windows updates than I can count. ⚡ The culprit? Corrupted .NET Framework files, permission conflicts, or a service blocking the install. My first fix for this usually works in under 10 minutes, and it’s saved me from reinstalling Windows more times than I’d like to admit.

The root causes are sneaky: Windows Update downloads can get interrupted, registry entries might be corrupted, or a third-party antivirus could be overzealous. I’ve tracked this error to three main spots—the Windows Installer service, the .NET Framework cache, and system permissions.

The good news? Each has a targeted fix that doesn’t require a full OS reset.

You’ll walk away with a clean install path, whether it’s for .NET, a Windows update, or even stubborn software packages. The steps are straightforward: reset the Windows Installer, clear the .NET cache, and verify permissions. No technical degree required—just patience and a few command-line commands.

Works for Windows 10 and 11, though the registry tweaks differ slightly between versions. I’ll walk you through each step with the exact commands and registry paths you’ll need. Let’s get this resolved once and for all.

Why it happens

When you encounter the infamous "Error 1935" during an assembly installation, it’s usually a sign that something went wrong behind the scenes—often involving permissions, corrupted files, or conflicts with your system’s core components.

Below, we break down the most common culprits, explained in plain terms with the technical details you need to understand (and fix) them.

🔒 Corrupted or Incomplete .NET Framework Files

The .NET Framework is the backbone of many Windows applications, and if its files are damaged or partially installed, Error 1935 can rear its head. This happens when:

• Windows Update fails silently: A botched update may leave critical .NET components in a broken state, causing installations to stumble over missing or mismatched files.
• Manual repairs go wrong: Tools like the .NET Framework Repair Tool might not fully restore files, leaving gaps that trigger this error during assembly registration.
• Disk errors or bad sectors: If the system drive (where .NET files reside) has corrupted sectors, Windows may fail to read or write assembly files during installation.

Why it matters: Assemblies rely on the .NET runtime to register and execute. If the runtime is incomplete, the installer throws Error 1935 because it can’t validate the assembly’s dependencies.

🛡️ Permission Issues with System Folders

Windows installations require administrative privileges to modify system folders like C:\Windows\assembly or C:\Program Files. If your user account lacks these permissions—or if User Account Control (UAC) is misconfigured—the installer will fail with Error 1935.

• Standard user accounts: Running the installer as a non-admin user (even if prompted for credentials) can cause partial installs, leaving assemblies in a "broken" state.
• Corrupted UAC settings: If UAC is disabled or configured incorrectly, the installer may not escalate privileges when needed.
• Antivirus/firewall interference: Overzealous security software can block the installer from writing to protected system folders, triggering this error.

Why it matters: The msiexec.exe process (used by many installers) requires SYSTEM-level permissions to modify the Global Assembly Cache (GAC). Without them, the assembly can’t be registered, and the error appears.

🧩 Conflicting or Outdated Visual C++ Redistributables

The Microsoft Visual C++ Redistributable packages provide runtime libraries that many applications depend on. If you have:

• Multiple conflicting versions: Installing both the 2010 and 2015 redistributables (for example) can cause DLL conflicts, making the installer reject assemblies.
• Missing or corrupted VC++ components: Some installers silently fail if critical msvcr*.dll files are absent or damaged.
• 32-bit vs. 64-bit mismatches: A 64-bit application trying to install a 32-bit assembly (or vice versa) can trigger this error if the system lacks the correct redistributable.

Why it matters: Assemblies compiled with Visual C++ rely on these redistributables to run. If the wrong versions are installed—or none at all—the installer can’t verify the assembly’s compatibility, leading to Error 1935.

🗑️ Leftover Residual Files from Previous Installs

If a previous installation of the same (or a similar) application failed, it may have left behind:

• Orphaned registry entries: The Windows Registry may still reference a broken assembly, causing conflicts during new installations.
• Partially installed files in the GAC: The Global Assembly Cache might contain corrupted or half-installed assemblies, blocking new ones from registering.
• Lock files or temporary files: Stale .tmp or .lock files in %TEMP% or C:\Windows\assembly can prevent the installer from writing new files.

Why it matters: The installer checks for existing assemblies before proceeding. If it detects conflicts or corruption, it aborts with Error 1935 to prevent further damage.

🔧 Broken Windows Installer Service

The Windows Installer service (msiexec) is responsible for managing installations and assemblies. If it’s corrupted or not running properly, you’ll see Error 1935 because:

• Service crashes or hangs: A faulty msiexec.exe process can’t complete assembly registration, leaving the install in limbo.
• Pending transactions in the queue: If a previous install was interrupted, the service may be stuck in a "pending" state, blocking new installations.
• Outdated Windows Installer version: Older versions of Windows (or unpatched systems) may lack fixes for assembly registration issues.

Why it matters: The installer relies on msiexec to handle assembly deployment. If the service is compromised, the error occurs as a safety measure to prevent system instability.

Fixing stubborn assembly installation errors

Encountering Error 1935 during an assembly installation can feel like hitting a digital brick wall—but don’t panic! Below are targeted fixes, organized by the most common causes, to get your software up and running smoothly. Each solution includes step-by-step instructions and prevention tips to avoid future headaches.

🔥 Corrupted or Incomplete Downloads: Re-Download the Installer

If the installer file itself is damaged or partially downloaded, Windows will reject it during setup.

1. 🔄 Delete the corrupted installer: Locate the setup file (e.g., .exe or .msi) and permanently delete it.
2. 🌐 Re-download from the official source: Use a direct link from the software vendor’s website—not third-party sites—to ensure a clean file.
3. 🛡️ Verify the file’s integrity: Some installers (like Microsoft’s) include checksum tools. Compare the downloaded file’s hash with the official one.

💡 Prevention Tip: Always download installers via _HTTPS_ and scan them with Malwarebytes before running.

🍳 Missing .NET Framework or Visual C++ Redistributables: Install Dependencies First

Many applications rely on Microsoft’s runtime libraries. If these are missing or outdated, Error 1935 appears during assembly registration.

1. 🔧 Check installed versions:
   • Press Win + R, type appwiz.cpl, and review installed updates under "Microsoft .NET Framework" and "Visual C++ Redistributable."
   • Note the latest versions (e.g., .NET 4.8, VC++ 2019).
2. 📥 Download the latest versions:
   • .NET Framework
   • Visual C++ Redistributable (x64 or x86, depending on your system).
3. 🔄 Restart your PC after installation to finalize updates.

💡 Prevention Tip: Use Windows Update to automatically install critical updates, including runtime dependencies.

👨‍🍳 Permissions Issues: Run as Administrator or Repair Install

If your user account lacks sufficient privileges, Windows blocks assembly registration, triggering Error 1935.

1. 🛡️ Run the installer as Administrator:
   • Right-click the setup file → Run as administrator.
   • If prompted by UAC, confirm with "Yes."
2. 🔄 Repair the .NET Framework (if applicable):
   • Open Command Prompt as Admin and run: dism /online /cleanup-image /restorehealth (wait 10+ minutes).
   • Then repair .NET with: sfc /scannow.

💡 Prevention Tip: Create a dedicated Administrator account for installations to avoid permission conflicts.

🥘 Conflicting Antivirus or Firewall: Temporarily Disable Security Software

Overzealous security tools may block assembly installation, mistaking it for a threat.

1. 🛡️ Pause real-time protection:
   • Temporarily disable Windows Defender or third-party AV (e.g., McAfee, Norton).
   • For Windows Security: Go to Virus & threat protection → Manage settings → Real-time protection → Turn off.
2. 🔄 Add an exception for the installer’s folder (if disabling isn’t an option).
3. 🔄 Retry the installation immediately after disabling security software.

💡 Prevention Tip: Whitelist known installers in your antivirus before running them to avoid future interruptions.

⏰ System File Corruption: Use System Restore or Reset Windows

If the issue persists, deeper system corruption may be at fault.

1. 🔄 Restore to a previous state:
   • Open System Restore via Win + R → rstrui.
   • Select a restore point before the error appeared.
2. 🔄 Reset Windows (last resort):
   • Go to Settings → Update & Security → Recovery → Reset this PC.
   • Choose "Keep my files" to preserve data.

💡 Prevention Tip: Regularly back up your system using Windows Backup or Macrium Reflect to recover quickly from corruption.

🔪 Advanced Fix: Manually Register the Assembly

For developers or power users, manually registering the assembly via command line can bypass the installer’s error.

1. 📂 Locate the assembly file (e.g., MyAssembly.dll) in the installer’s extracted folder.
2. 🖥️ Open Command Prompt as Admin and navigate to the folder using cd path\to\folder.
3. 🔧 Register the assembly with: regasm MyAssembly.dll /codebase (Replace MyAssembly.dll with your file’s name.)

⚠️ Warning: Only attempt this if you’re comfortable with command-line tools. Incorrect registration can cause system instability.

Frequently asked questions