Error 1935 an Error Occurred During the Installation of Assembly: Registry-Cleaning Workaround for Stubborn Installs

"Error 1935: an error occurred during the installation of assembly—this cryptic message has haunted Windows setups for years, halting everything from Visual Studio to random .NET apps, until the registry-cleaning workaround finally breaks the cycle when nothing else does. ⚡ The problem almost always traces back to corrupted permissions or leftover junk from failed installs.

The registry gets messy when installers fail midway, leaving behind broken entries and permission conflicts. Microsoft’s official fixes—like running the installer as admin or repairing .NET—work for most people, but stubborn cases need deeper surgery.

That’s where the registry cleanup comes in, and it’s not as scary as it sounds if you follow the right steps.

You’ll walk away with a clean slate for your next install, no more phantom dependencies, and a system that finally lets you move past this error. The process takes about 15 minutes and requires zero special tools—just a little patience and the right registry tweaks.

This works for Windows 10 and 11, whether you’re installing enterprise software or just trying to get a stubborn app up and running. Here’s how to make it happen without breaking anything else in the process.

Why it happens

When you encounter Error 1935 during software installation, it’s usually a sign that your system is struggling to process a critical component—specifically, an assembly (a reusable software module in .NET or Windows).

This error typically surfaces when the installer can’t properly register or deploy these components. Below, we break down the most common causes, explained in plain terms with actionable insights.

🔍 Corrupted or Missing .NET Framework Files

The .NET Framework is the backbone for many Windows applications, and if its core files are damaged or incomplete, installations will fail. Error 1935 often appears when:

• Partial updates: If a .NET Framework update was interrupted or installed incorrectly, critical DLLs (like mscoree.dll or fusion.dll) may be corrupted.
• Version conflicts: Mixing incompatible .NET versions (e.g., trying to install a .NET 4.8 app on a system with only .NET 4.5) triggers dependency errors.
• Registry misconfigurations: The Windows Registry stores paths and permissions for .NET assemblies. If these entries are broken, the installer can’t locate or validate the required files.

Why it happens: The installer relies on the Windows Installer (MSI) service to deploy assemblies. If the .NET runtime or its registry keys are missing, the MSI service throws Error 1935 because it can’t resolve the assembly’s dependencies.

🛡️ Insufficient Permissions or Locked Files

Windows installations often require elevated privileges to modify system directories (e.g., C:\Windows\assembly or C:\Program Files). If your user account lacks permissions or files are locked by another process, the installation stalls.

• UAC (User Account Control) interference: Running the installer without admin rights or with UAC blocking critical operations can prevent file writes.
• Antivirus/firewall blocking: Security software may quarantine or lock assembly files during installation, mistaking them for threats.
• Open handles: If another program (e.g., a running service or background process) has a file locked, the installer can’t overwrite it, leading to Error 1935.

Why it happens: The Windows Installer service uses transactional NTFS (TxF) to safely modify files. If permissions are denied or files are locked, the transaction fails, and the error surfaces during the assembly registration phase.

🧹 Registry Corruption or Clutter

The Windows Registry acts as a central database for software configurations, including assembly paths and dependencies. If registry keys related to .NET or the installer are corrupted or overloaded with leftover entries from failed installs, Error 1935 can occur.

• Orphaned entries: Uninstalled software may leave behind registry keys pointing to non-existent assemblies, confusing the installer.
• Malformed paths: If registry values for assembly locations (e.g., HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework) contain typos or broken links, the installer can’t resolve them.
• Permission issues: Registry keys may be locked or inaccessible to the installer due to restrictive permissions.

Why it happens: During installation, the MSI service queries the registry to validate assembly dependencies. If these queries return errors (e.g., "file not found" or "access denied"), the installer aborts with Error 1935.

🔧 Conflicting Software or Services

Some applications and services interfere with the Windows Installer service or .NET runtime, causing installations to fail. Common culprits include:

• Third-party installers: Tools like Inno Setup or _NSIS_ may conflict with MSI-based installers if they modify shared components.
• Antivirus real-time protection: Programs like McAfee or Norton may block the installer from writing to critical directories.
• Running services: Services like Windows Installer (MSIExec) or .NET Runtime Optimization Service (clroptimizationv4.0.30319) may be stuck, preventing new installations.
• Previous failed installs: Aborted installations can leave the system in an unstable state, where subsequent installers inherit the same errors.

Why it happens: The installer relies on a clean environment to deploy assemblies. If another process is hogging resources (CPU, disk I/O, or file locks), the installation transaction times out or fails to complete.

💾 Disk or System Resource Issues

Even if your hardware meets the minimum requirements, temporary glitches can derail installations. Error 1935 may appear if:

• Low disk space: The installer needs temporary space in %TEMP% or C:\Windows\Installer. If these folders are full, the process crashes.
• Fragmented disk: Severe disk fragmentation can slow down file operations, causing timeouts during assembly deployment.
• Memory pressure: If your system is low on RAM, the .NET runtime may fail to load assemblies properly.
• Corrupted system files: sfc /scannow or DISM errors can leave critical files in a broken state.

Why it happens: The Windows Installer service uses Windows Resource Protection (WRP) to ensure system files remain intact. If disk or memory constraints interfere, WRP may block the installation, resulting in Error 1935.

Fixing stubborn assembly errors

Encountering Error 1935 during software installation can be frustrating, but the right fixes can resolve it quickly. Below are targeted solutions mapped to common causes, along with prevention tips to avoid future headaches.

🔧 Corrupted or Missing Registry Entries

If the Windows Registry has broken or incomplete entries for the assembly, the installer may fail to locate required components.

🔥 Step 1: Manually Clean the Registry

Use a trusted registry cleaner to scan and repair corrupted entries. Warning: Always back up your registry before making changes!

1. Download a registry cleaner like CCleaner or WinAbility Registry Cleaner.
2. Run a scan and let it identify issues related to the failing assembly.
3. Export the registry (File > Export) as a backup before fixing.
4. Delete or repair the flagged entries, then restart your PC.

💡 Pro Tip:

If you’re unsure about manual registry editing, use System File Checker (SFC) to restore missing system files:

1. Open Command Prompt as Administrator (Win + X > Terminal (Admin)).
2. Type sfc /scannow and press Enter. Wait for the scan to complete.
3. Restart your computer and retry the installation.

📦 Damaged or Incomplete Installation Files

If the installer files are corrupted or partially downloaded, the assembly won’t install properly.

🍳 Step 1: Re-Download the Installer

Delete the existing installer and download a fresh copy from the official source.

1. Uninstall the problematic software (if partially installed).
2. Delete leftover files in C:\Program Files or C:\Program Files (x86).
3. Download the installer again from the vendor’s website.
4. Run as Administrator (right-click > Run as Administrator).

🔪 Step 2: Use a Clean Boot

A conflicting background service might interfere with the installation.

1. Press Win + R, type msconfig, and hit Enter.
2. Go to the Services tab, check "Hide all Microsoft services", then click Disable all.
3. Switch to the Startup tab and click Open Task Manager to disable startup apps.
4. Restart and retry the installation.

🔐 Permission or UAC Issues

If your user account lacks sufficient permissions, the installer may fail silently.

👨‍🍳 Step 1: Run as Administrator

Always install software with elevated privileges.

1. Right-click the installer and select Run as Administrator.
2. If prompted by UAC, click Yes.

🌡️ Step 2: Adjust User Account Control (UAC) Settings

Temporarily lower UAC to test if it’s the culprit.

1. Go to Control Panel > User Accounts > User Accounts (Classic View).
2. Click Change User Account Control settings.
3. Drag the slider to Never notify and restart.
4. Retry the installation, then revert UAC to default afterward.

🛡️ Antivirus or Firewall Blocking Installation

Security software may flag the installer as a threat or block its execution.

⏰ Step 1: Temporarily Disable Security Software

1. Pause or disable your antivirus (e.g., Windows Defender, McAfee, Norton).
2. Disable the Windows Firewall temporarily (Control Panel > Windows Defender Firewall > Turn Windows Defender Firewall on or off).
3. Retry the installation, then re-enable security measures.

✨ Pro Tip:

Add an exception for the installer in your antivirus software to prevent false positives.

🔄 Prevent Future Errors

Once you’ve resolved the issue, take these steps to avoid Error 1935 in the future:

• Keep Windows updated—Microsoft regularly patches registry and installation issues.
• Use administrative privileges for all installations.
• Regularly clean your registry with trusted tools (but back up first!).
• Avoid abrupt shutdowns during installations—always let them complete.
• Download installers from official sources to prevent corrupted files.

Frequently asked questions