QuickBooks Error 1935 Caused by .NET Framework

Let’s Dive in to see…

How to fix QuickBooks Error=1935

Caused by .NET Framework

QuickBooks Installation Error · 1935 · .NET Framework

How to Fix QuickBooks Error 1935 Caused by .NET Framework

QuickBooks displays: "Error 1935: An error occurred during the installation of assembly component..." — specifically referencing a .NET or Microsoft Visual C++ assembly during QB installation.

Error 1935 during QB installation occurs when the Windows Installer can't register a required assembly component. At QuickFix Bookkeeping, when 1935 references a .NET Framework assembly (the error message names a component like Microsoft.VC80.ATL or a .NET namespace), the fix targets .NET Framework — distinct from 1935 caused by corrupted Windows Installer or Visual C++ Redistributable issues.

Reading the Error 1935 Message — Assembly Name Tells You the Fix

The full assembly name in the error message is the diagnostic key:
• Assembly name starts with Microsoft.VC (e.g., Microsoft.VC80.ATL, Microsoft.VC90.CRT) → Visual C++ Redistributable issue → repair/reinstall Visual C++ Redistributable.
• Assembly name contains .NET or a namespace like System. → .NET Framework issue → this page's fixes.
• Error references MSXML → XML component issue → QB Install Diagnostic Tool repairs MSXML.
• No assembly name shown → Windows Installer itself is damaged → re-register Windows Installer service.

What Causes Error 1935 (.NET variant)?

Corrupted .NET Framework Installation

Primary .NET 1935 cause — the .NET Framework installation on the system is damaged. When QB's installer tries to register a .NET assembly, the .NET runtime fails to complete the registration. Repairing .NET Framework via Control Panel or running the .NET Repair Tool resolves this.

Wrong .NET Framework Version

QB requires specific .NET Framework versions (typically 4.x or later). If the required version isn't installed or is an incompatible version, the assembly registration fails with 1935. Windows Update installs .NET updates — running Windows Update before QB installation resolves missing .NET versions.

Antivirus Blocking Assembly Registration

AV real-time scanning intercepts and blocks the .NET Global Assembly Cache (GAC) write during installation. The assembly can't be registered in the GAC and 1935 appears. Disabling AV during QB installation and re-enabling after resolves this.

Windows Installer Service Conflict

A background application is using Windows Installer simultaneously with QB's installation, causing assembly registration conflicts. Installing in Selective Startup (msconfig) eliminates background processes competing with Windows Installer.

Corrupted Windows Registry (.NET keys)

Corrupted registry entries for .NET Framework prevent assembly registration from completing. Running the QB Install Diagnostic Tool (which repairs .NET components including registry keys) or a clean .NET reinstall rebuilds the correct registry structure.

Pending Windows Updates Blocking Installation

Pending Windows Updates (particularly .NET updates) that haven't been installed yet create a conflict when QB tries to install its .NET components — Windows Installer is in a partially-updated state. Completing all Windows Updates and restarting before QB installation eliminates this.

How to Fix Error 1935 (.NET Framework)

METHOD 1Run QB Install Diagnostic + Windows Update + Disable AVResolves most .NET 1935 cases

Run Install Diagnostic Tool first: Tool Hub → Installation Issues → QuickBooks Install Diagnostic Tool → run → restart. This repairs .NET Framework, MSXML, and Visual C++ Redistributable components that QB requires — the most targeted fix for 1935.

Windows Update + disable AV: Windows Settings → Update & Security → install all pending updates → restart. Temporarily disable AV real-time scanning → right-click QB installer → Run as Administrator → install. Re-enable AV after installation completes.

METHOD 2Repair .NET Framework via Control PanelCorrupted .NET installation

Control Panel → Programs → find all Microsoft .NET Framework entries → for each: click → Repair (if available) or Uninstall/Change → Repair. Restart after each repair. Alternatively: download the Microsoft .NET Framework Repair Tool from Microsoft's website → run as Administrator → it automatically detects and repairs the correct .NET issues → restart → retry QB installation.

METHOD 3Install in Selective Startup + Clean Install QBBackground conflict or persistent 1935

Start → msconfig → General → Selective Startup → uncheck "Load startup items" → Services → Hide all Microsoft services → Disable All → Apply → restart. Install QB as Administrator with AV off. After successful install: msconfig → Normal startup → restart. If 1935 still appears: QB Clean Install Tool → uninstall QB → restart → reinstall from a fresh download as Administrator in Selective Startup.

Related QuickBooks Errors

Error 1935 (main) Error 1904 Error 1603 All QB Errors

Error 1935 Persisting After .NET Repair and Selective Startup Install?

Let QuickFix Bookkeeping Complete Your QB Installation.

Persistent 1935 after .NET repair and Selective Startup usually means a specific .NET version is corrupted beyond the Repair Tool's reach — we identify the exact assembly failing and target the specific .NET version that needs a clean reinstall.

Book a Free 30-Minute Consultation

No obligation. Same-day response.