Error 1935
An error occurred during the installation of assembly component
The installer tried to register a .NET or side-by-side assembly and Windows refused. Almost always the .NET Framework itself is damaged, not the program you are installing.
What it actually means
Assembly installation goes through the Windows side-by-side store. When that store or the .NET Framework underneath it is inconsistent, every installer that registers assemblies fails the same way, which is why this error follows people across different programs.
How to fix it, in order
Ordered by how often each one is the answer, not by how clever it sounds.
- 01Install any pending Windows Updates and restart. .NET is serviced through Windows Update and a half-applied update produces exactly this.
- 02Repair the .NET Framework with Microsoft's .NET Framework Repair Tool, which is the supported fix and handles the common cases automatically.
- 03Temporarily disable antivirus during the install. Real-time scanning interfering with assembly registration is a documented cause of 1935.
- 04Run "sfc /scannow" and then DISM, since a damaged component store prevents assemblies from registering at all.
- 05Check the Windows Modules Installer service is running: it is called TrustedInstaller and assembly registration depends on it.
Common questions
- What causes error 1935 during installation?
- A damaged .NET Framework or Windows side-by-side assembly store, rather than a problem with the program being installed. Run Windows Update, then Microsoft's .NET Framework Repair Tool.
Before you retry the installer
If the package came from anywhere other than the publisher, confirm it is the file they actually shipped. Check its SHA-256 against our index, which settles in seconds whether you are debugging an installer or a damaged download.