Error 1935 an Error Occurred During the Installation of Assembly: Assembly Installation Blocked? Try These 5 Solutions

If you’ve ever hit error 1935—an error occurred during the installation of assembly on Windows 10/11, it’s usually one of five common fixes—and I’ve resolved this exact issue countless times.

The error typically appears during Office Suite or .NET-dependent software installs, leaving you staring at a screen that refuses to proceed past 99%.

The root causes are almost always the same: corrupted MSI files, a broken .NET Framework installation, missing permissions, or overzealous antivirus interference. I’ve seen this error freeze installations midway through critical updates, and the worst part?

Microsoft’s generic troubleshooting steps rarely cut it. The solutions I’m about to share cut straight to what actually works—no fluff, just fixes.

You’ll walk away with a working installation in under 30 minutes, even if you’ve tried every “recommended” fix already. We’ll start with the quickest wins—like running the installer as admin or disabling Real-Time Protection—and move to deeper fixes like repairing .NET Framework or using msiexec commands.

No tech degree required, just step-by-step instructions that have worked for everyone from IT admins to home users.

Fair warning: if you’ve already tried the usual “repair .NET” advice, skip ahead to the msiexec reset command—it’s the one that finally worked for my coworker after three failed attempts. The solutions here are ordered by how often they resolve the issue, so you won’t waste time on placeholders.

Why it happens

When Error 1935 interrupts your software installation, it’s usually a sign that Windows is struggling to register or deploy a required assembly—a critical component written in .NET or another framework.

Below are the most common culprits behind this frustrating error, explained in technical detail so you can pinpoint the root cause.

🔧 Corrupted or Missing .NET Framework Files

The .NET Framework is the backbone of many Windows applications, and if its files are damaged or incomplete, installations will fail. This error often occurs when:

• Key DLLs (e.g., mscoree.dll, fusion.dll) are corrupted—these handle assembly registration and dependencies.
• A partial or failed .NET update left the framework in an unstable state.
• Antivirus or third-party tools quarantine or delete critical system files during scans.

Why it matters: The Windows Installer relies on msiexec.exe to register assemblies via the Windows Installer Service. If the .NET runtime can’t load properly, the installer throws Error 1935 during the "Installing Assembly" phase.

🛡️ Permission Issues or UAC Restrictions

Windows User Account Control (UAC) or insufficient permissions can block the installer from writing to protected system directories, such as:

• C:\Windows\assembly\ (where .NET assemblies are stored).
• C:\Program Files\ or C:\Program Files (x86)\ (common install paths).

Scenarios that trigger this:

• Running the installer as a standard user (not Administrator).
• A group policy or third-party security tool (e.g., Bitdefender, Norton) restricts write access.
• The Windows Installer Service is disabled or running under a limited account.

Actionable insight: The installer needs full administrative privileges to modify the Global Assembly Cache (GAC). If UAC prompts appear but aren’t honored, the installation silently fails.

🔗 Broken Registry Entries for Assemblies

The Windows Registry tracks installed assemblies, and if entries are missing or corrupted, the installer can’t verify or deploy them. Common triggers include:

• Manual registry edits gone wrong (e.g., deleting .NET-related keys).
• Malware or cleanup tools removing legitimate assembly references.
• Failed updates leaving orphaned registry entries for old assemblies.

Key registry paths affected:

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion (assembly binding info).
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide (SxS manifest cache).

Technical note: The Assembly Binding Log Viewer (Fusion Log) (via fuslogvw.exe) can reveal if the installer is failing to locate or load an assembly due to registry mismatches.

📦 Conflicting or Outdated Software Dependencies

Some applications require specific versions of libraries (e.g., Microsoft.VC++ Redistributable, DirectX, or older .NET versions). If these are:

• Missing entirely—the installer can’t resolve dependencies.
• Outdated—newer apps may reject older versions.
• Corrupted—e.g., a broken vcredist_x64.exe install.

Example: A game or app built with Visual C++ 2010 Redistributable may fail on a system with only the 2015 version installed. The installer’s dependency walker (via depends.exe) can expose these gaps.

💾 Disk or Storage-Related Issues

Physical or logical disk problems can prevent the installer from writing files to:

• The Global Assembly Cache (GAC) (C:\Windows\assembly\).
• The installation directory (e.g., C:\Program Files\AppName\).

Common culprits:

• Low disk space (Windows requires temporary space for installations).
• File system errors (e.g., chkdsk finds bad sectors).
• Read-only or locked drives (e.g., a C: drive marked as read-only).
• Antivirus sandboxing (e.g., Windows Defender isolating the installer).

Pro tip: Run chkdsk C: /f in an elevated Command Prompt to scan for and repair disk errors before retrying the install.

Quick fixes for installation errors

When Error 1935 strikes during an assembly installation, panic isn’t your best move—action is! Below are targeted fixes, organized by the most common causes, to get your software up and running. Each solution is designed to be straightforward, with clear steps and pro tips to avoid future headaches.

🔥 Corrupted or Incomplete Download

If the installer files are damaged or didn’t download fully, the installation will fail before it even starts. Here’s how to reset:

1. 🔄 Redownload the installer
   • Delete the current installer file from your downloads or desktop.
   • Visit the official software website and download a fresh copy.
   • Pro tip: Use a direct download link (not third-party sites) to avoid malware or corrupted files. 🌐
2. 🛡️ Verify file integrity
   • If the installer is an EXE or MSI, check for checksums or SHA-256 hashes on the official site.
   • Use tools like 7-Zip to extract and inspect files before running.

👨‍💻 Permission or Admin Issues

Windows often blocks installations when your user account lacks sufficient permissions. Try these steps:

1. 🔑 Run as Administrator
   • Right-click the installer and select Run as administrator.
   • If prompted by UAC, click Yes.
   • Pro tip: If you’re on a work/school PC, contact IT—they may have locked down installation permissions. 🏢
2. 🔒 Disable User Account Control (UAC) temporarily
   • Press Win + S, type UAC, and select Change User Account Control settings.
   • Drag the slider to Never notify and restart your PC.
   • Warning: Re-enable UAC after installation for security! 🔒

🔧 Missing .NET Framework or Visual C++ Redistributable

Many programs rely on Microsoft’s frameworks. If they’re missing or outdated, Error 1935 will appear. Fix it with these steps:

1. 🔧 Install the latest .NET Framework
   • Download the newest version from Microsoft’s site.
   • Run the installer and restart your PC.
2. 🛠️ Repair or reinstall Visual C++ Redistributable
   • Open Control Panel > Programs > Programs and Features.
   • Find Microsoft Visual C++ Redistributable, right-click, and select Repair.
   • If that fails, uninstall it, restart, and reinstall from Microsoft’s site.
   • Pro tip: Install both x86 and x64 versions if unsure. 💡

🗑️ Conflicting Antivirus or Firewall

Security software can mistakenly flag installers as threats, blocking them entirely. Try these adjustments:

1. 🛡️ Temporarily disable antivirus
   • Right-click your antivirus icon in the system tray and select Disable (usually for 15–30 minutes).
   • Attempt the installation again.
   • Pro tip: Add the software’s installer to your antivirus’s exclusion list to prevent future blocks. ✨
2. 🔥 Adjust Windows Firewall settings
   • Go to Control Panel > Windows Defender Firewall > Allow an app through firewall.
   • Ensure Windows Installer and User Account Control are checked.

🧹 Clean Up Leftover Installation Files

Sometimes, remnants of a failed install cause conflicts. A quick cleanup can resolve Error 1935:

1. 🧹 Use Windows Installer CleanUp Utility
   • Download the Microsoft Fix It tool.
   • Run it, select the problematic software, and choose Repair or Remove.
2. 🗑️ Manually delete registry entries (advanced)
   • Warning: Only attempt this if comfortable with the registry editor!
   • Press Win + R, type regedit, and hit Enter.
   • Navigate to HKEYLOCALMACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.
   • Delete any keys related to the failing software.
   • Pro tip: Back up the registry before making changes! 💾