---Advertisement---

Error 1935 An Error Occurred During The Installation Of Assembly Component FIX

Published On: September 8, 2025
Error 1935 An Error Occurred During The Installation Of Assembly Component FIX
---Advertisement---

If you encounter the error message “Error 1935: An error occurred during the installation of assembly component” while installing software via an .msi package, don’t worry — you’re not alone. This error often stems from issues with system files, the .NET Framework, or Windows installation services. Here’s how to fix it step-by-step.

Error 1935

Why This Error Happens

Error 1935 occurs due to multiple possible causes:

  • Corrupt or missing .NET Framework components
  • Windows Installer (msiexec) conflicts or disabled services
  • Resource/log file corruption in the Windows file system
  • Outdated or missing Visual C++ redistributables
  • Interference from registry conflicts or orphaned entries

Fix #1: Run System Repair Tools (SFC & DISM)

Start with system file integrity checks:

  1. Open Command Prompt as an administrator.
  2. Run: sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth
  3. Reboot your system and retry the installation.
Run System Repair Tools

Fix #2: Repair Visual C++ Redistributables

Issues with the Visual C++ runtime often trigger this error. Fix them as follows:

  1. Navigate to Settings → Apps → Installed Applications.
  2. Find all Microsoft Visual C++ Redistributable entries.
  3. Select each, choose Modify, then click Repair.

Fix #3: Enable the Windows Modules Installer Service

This service (TrustedInstaller) is vital for assembly installations:

  1. Press Win + R, type services.msc, and press Enter.
  2. Find Windows Modules Installer, right-click → Properties.
  3. Set Startup Type to Manual, and click Start.
  4. Try the install again.

Fix #4: Clear the File System Transaction Log

The file system transaction log can become corrupted and block assembly installs:

  1. Run Command Prompt as Administrator.
  2. Execute: fsutil resource setautoreset true C:
  3. Restart your PC and retry installation.

Fix #5: Repair or Reinstall .NET Framework

A damaged .NET Framework often causes assembly errors:

  1. Open Control Panel → Programs and Features → Turn Windows features on or off.
  2. Disable and re-enable .NET Framework 3.5, then restart.
  3. If unavailable, use the .NET Framework Repair Tool or do a clean reinstallation.

Fix #6: Run Installer as Administrator in Compatibility Mode

Permission or compatibility issues can block installation:

  1. Right-click the installer → select Properties.
  2. Go to the Compatibility tab.
  3. Enable Run this program in compatibility mode (e.g., Windows 10).
  4. Check Run as administrator.
  5. Try installing again.

Fix #7: Delete the APPMODEL Registry Key (Office-Specific)

If installing Microsoft Office and facing this error:

  1. Open Registry Editor (regedit).
  2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\APPMODEL
  3. Right-click and delete the key. Confirm and restart your computer.
  4. Retry the installation.

Final Thoughts

Error 1935 can be resolved effectively with the right steps. Start with system file fixes (SFC/DISM), then move to runtime repairs and permissions. For Office, try the registry clean-up. If issues persist, consider clean-booting your system, temporarily disabling antivirus, or seeking support from the software publisher.

---Advertisement---

Related Post

Enable New Windows 11 25H2 Features After December Update (KB5070311)
Enable/Disable Steam Networking IP Sharing – Step-by-Step Guide
Valorant Stuck on Loading Screen? Fix It Now!
Tips

Valorant Stuck on Loading Screen? Fix It Now!

By Tech Gitter
|
December 31, 2025
How to Increase or Decrease Font Size in Google Chrome
Solutions

How to Increase or Decrease Font Size in Google Chrome

By Tech Gitter
|
December 29, 2025

Leave a Comment

Join WhatsApp Join Telegram