Error 1935 an Error Occurred During the Installation of Assembly: Assembly Installation Error Resolved in Minutes

When "error 1935: an error occurred during the installation of assembly" strikes—especially mid-update or software install—it can feel like hitting a brick wall. ⚡ I’ve seen this block users for hours, but the fixes are often simpler than they seem.

The root causes usually boil down to permission issues, corrupted system files, or overzealous antivirus software stepping in at the wrong time.

The good news? Most solutions take under 10 minutes and don’t require advanced tech skills. We’ll start with the quickest fixes—running the installer as administrator, repairing the .NET Framework, or temporarily disabling your antivirus—before diving into deeper tools like DISM or SFC if needed.

I’ve tested these steps on Windows 10 and 11 across different software installs, and they work reliably.

By the end, you’ll have your assembly installed without the error, and you’ll know exactly what went wrong so you can prevent it next time. No more guessing or wasted time—just a smooth, working system. Let’s get this resolved step by step.

If you’re still stuck after the basic fixes, we’ll cover advanced troubleshooting like manual registry checks or using the Windows Module Installer service. Every solution here is backed by real-world fixes from users and Microsoft’s official documentation, so you’re not flying blind.

Root Causes of Installation Failures

When you encounter Error 1935 during an assembly installation, it’s usually a sign that Windows can’t properly register or validate a required component. Below are the most common reasons why this error occurs, explained in technical detail so you can pinpoint the issue quickly.

🔧 Corrupted or Missing .NET Framework Components

The .NET Framework is a core dependency for many Windows applications, and if its components are damaged or incomplete, installations will fail. This error often surfaces when:

• Critical DLL files (e.g., mscoree.dll, fusion.dll) are missing or corrupted.
• The Windows Installer service (msiexec.exe) fails to interact with .NET assemblies due to registry inconsistencies.
• A partial or failed update left the framework in a broken state.

💡 Why it matters: The .NET Framework relies on the Windows Registry to map assembly dependencies. If entries are missing or misconfigured, Windows Installer throws Error 1935 when it can’t locate the required files during setup.

🔗 Broken Registry Entries for Assemblies

The Windows Registry stores metadata about installed assemblies, including their locations and dependencies. If these entries are:

• Corrupted (e.g., due to abrupt system shutdowns or malware).
• Missing (e.g., after a failed uninstall or manual deletion).
• Pointing to incorrect paths (e.g., after a system restore or disk cleanup).

The installer cannot resolve the assembly’s location, triggering Error 1935. This is especially common with:

• Third-party software that modifies registry keys (e.g., HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion).
• Custom applications built with ClickOnce or WiX Toolset, which rely on precise registry mappings.

🔥 Key detail: The error often includes a HRESULT like 0x800736B3, which translates to "The assembly is not registered correctly in the Windows Registry."

🛡️ Antivirus or Firewall Blocking Installer Processes

Security software can interfere with installations by:

• Quarantining or deleting temporary installer files (e.g., .msi, .exe, or *.dll in %TEMP%).
• Blocking permissions for msiexec.exe or dllhost.exe (used for .NET assembly loading).
• Scanning assemblies in real-time, causing timeouts or incomplete installations.

🛡️ How it happens: If your antivirus flags an assembly as "suspicious" during the GAC (Global Assembly Cache) verification step, the installer aborts with Error 1935. This is common with:

• Overly aggressive real-time protection (e.g., McAfee, Norton).
• Third-party security suites that hook into Windows Installer (e.g., MsiAdvertiseProduct calls).

🖥️ Insufficient Permissions or UAC Restrictions

Windows Installer requires elevated privileges to:

• Write to the Global Assembly Cache (GAC) (C:\Windows\assembly).
• Modify registry keys under HKLM (local machine hive).
• Access protected system folders (e.g., C:\Program Files).

If the installer runs under a standard user account or UAC is blocking it, the following can occur:

• The installer fails to register assemblies in the GAC, leading to Error 1935.
• Registry writes are redirected to HKCU (current user hive) instead of HKLM, breaking system-wide dependencies.

✨ Pro tip: Always run installers as Administrator, even if the prompt doesn’t explicitly ask. Some applications silently fail permission checks and only show Error 1935 later.

🔄 Conflicting or Outdated Windows Updates

Windows Updates can introduce or fix issues related to:

• Windows Installer service (msiexec) (e.g., KB updates for Windows Installer 5.0).
• .NET Framework patches (e.g., cumulative updates for .NET 4.x).
• Assembly binding redirects (changes in machine.config or app.config).

If your system is missing critical updates or has conflicting patches, the installer may fail to:

• Resolve assembly dependencies correctly.
• Communicate with the Windows Module Installer (TiWorker.exe).
• Validate digital signatures for assemblies.

📊 Example: Installing an app that requires .NET 4.8 on a system with only .NET 4.7.2 installed can trigger Error 1935 because the installer expects a higher version of clr.dll.

🗑️ Disk Errors or Corrupted System Files

Physical or logical disk issues can disrupt the installation process by:

• Preventing file writes to the installation directory or GAC.
• Corrupting system files like msi.dll or fusion.dll.
• Causing read errors when accessing assembly manifests or dependencies.

Common triggers include:

• Bad sectors on your system drive.
• Fragmented files in the Windows or Program Files directory.
• Filesystem corruption (e.g., NTFS errors not yet repaired).

🔪 Red flag: If you see Error 1935 after a disk cleanup or defrag, the issue may stem from lost or misplaced assembly references.

Quick Fixes for Installation Errors

When Error 1935 strikes during assembly installation, panic isn’t your best move—solutions are! Below, we break down the most common causes and their fixes, step by step. Whether it’s a corrupted file, missing permissions, or a stubborn .NET Framework hiccup, we’ve got you covered with practical, no-nonsense troubleshooting.

🔥 Corrupted or Incomplete Download

If the assembly file itself is damaged, installation will fail before it even starts. Here’s how to reset it:

• 🔄 Redownload the installer: Grab the latest version from the official source (e.g., Microsoft’s site for .NET updates). Avoid third-party mirrors—they’re riskier.
• 📂 Verify file integrity: Check the file’s hash (MD5/SHA-1) against the publisher’s provided values. Tools like HashTab can help.
• 🗑️ Clear temp files: Press Win + R, type %temp%, and delete everything in the folder. Reboot before retrying.

💡 Pro Tip: If the file is large, pause downloads midway and resume—corruption often sneaks in during partial transfers.

👨‍💻 Missing or Broken .NET Framework

Error 1935 often crops up when the .NET Framework isn’t up to date or is misconfigured. Try these steps:

• 🔧 Repair .NET Framework:
  1. Open Control Panel > Programs > Turn Windows features on or off.
  2. Uncheck .NET Framework, click OK, and wait for changes.
  3. Recheck the box and restart your PC.
• 🔄 Update manually: Download the latest .NET Framework version from Microsoft’s site.
• 🛠️ Use DISM: Open Command Prompt as Admin and run:

  DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:"C:\path\to\sources\sxs"

  (Replace the path with your Windows installation media if needed.)

⚠️ Warning: If you’re on Windows 10/11, avoid manually installing older .NET versions—Windows Update handles this automatically.

🔒 Permission or Admin Issues

If your user account lacks sufficient privileges, Windows will block the installation. Here’s how to fix it:

• 🛡️ Run as Administrator: Right-click the installer, select Run as administrator, and enter your admin credentials.
• 🔐 Take Ownership (Advanced):
  1. Right-click the installer file > Properties > Security.
  2. Click Advanced > Change and enter your admin username.
  3. Check Replace owner on subcontainers and apply.
• 🔒 Disable User Account Control (UAC) temporarily:
  1. Search for Change User Account Control settings in the Start menu.
  2. Drag the slider to Never notify and restart.

  ⚠️ Warning: Only do this if you’re comfortable with security risks. Re-enable UAC afterward!

🧹 Conflicting Software or Antivirus

Overzealous security software can flag installers as threats and block them. Try these steps:

• 🛡️ Temporarily disable antivirus: Pause real-time protection in your AV software (e.g., Windows Defender, McAfee) and retry the install.
• 🔄 Add an exception: Whitelist the installer file in your antivirus settings.
• 🚫 Disable conflicting programs: Close background apps like OneDrive, Steam, or cloud sync tools—they sometimes interfere with file operations.

💡 Pro Tip: If using Windows Defender, run a full scan afterward to ensure no malware snuck in during the install.

🔧 Registry or System File Corruption

Deep system issues can trigger Error 1935. Use these nuclear options (backup first!):

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

     sfc /scannow

  2. Wait for the scan to complete and restart.
• 🛠️ Reset Windows Components:
  1. Open Command Prompt as Admin and run:

     DISM /Online /Cleanup-Image /RestoreHealth

  2. Follow with:

     sfc /scannow

• 🔄 Repair Install Windows: Use the Media Creation Tool to refresh Windows without losing data.

⚠️ Warning: Registry edits or deep system repairs can brick your OS. Backup your data before proceeding!

🛡️ Prevention Tips for Future Installs

Once you’ve resolved Error 1935, keep it from returning with these habits:

• 📥 Download from trusted sources: Always use official websites or verified mirrors.
• 🔄 Update regularly: Keep Windows and .NET Framework updated via Settings > Windows Update.
• 🛡️ Use admin tools sparingly: Avoid running installers as admin unless absolutely necessary.
• 🗑️ Clean up regularly: Delete temp files and old installers to free up space and reduce conflicts.
• 🔒 Scan for malware: Run Windows Defender Offline Scan monthly to catch hidden threats.

Frequently asked questions