Quick Fix for QuickBooks Error 1935 — Under 10 Minutes
QuickBooks error 1935 appears during installation with the message “An error occurred during the installation of assembly” — and it stops the installer completely. This error almost always points to a Microsoft .NET Framework problem on your Windows PC, not a fault with QuickBooks itself. The fix is straightforward and in most cases takes under 10 minutes to complete.
Cause: Microsoft .NET Framework files are corrupted or the wrong version is installed, blocking QuickBooks from registering its assembly components during setup.
Fix: Repair .NET Framework using the Microsoft repair tool, then rerun the QuickBooks installer.
What Causes QuickBooks Error 1935?
QuickBooks error 1935 is a Windows Installer error that occurs when a required assembly — a package of code that QuickBooks needs — cannot be registered during installation. The most common causes are:
- Corrupted .NET Framework: QuickBooks requires specific versions of Microsoft .NET Framework. If any version is damaged, the installer cannot register assemblies and fails with error 1935.
- Antivirus blocking assembly registration: Real-time antivirus tools can flag and block the file registration steps QuickBooks performs during installation, causing the 1935 error mid-install.
- Windows Update running in the background: If Windows is downloading or applying updates while you install QuickBooks, the two processes can conflict — particularly around .NET components being updated simultaneously.
- Corrupted Windows registry entries: Leftover registry entries from a previous QuickBooks uninstall can conflict with the new installation’s assembly registration steps.
- Insufficient permissions: Running the installer without full administrator rights can prevent assembly registration from completing.
Quick Fix for QuickBooks Error 1935 — Step by Step
Fix 1: Disable antivirus temporarily (fastest fix — try this first)
Right-click your antivirus icon in the system tray → Pause protection for 15 minutes → run the QuickBooks installer again. If installation succeeds, add QuickBooks to your antivirus exclusion list before re-enabling real-time protection. This resolves error 1935 in a large number of cases because antivirus tools frequently block the COM assembly registration QuickBooks performs during setup.
Fix 2: Run QuickBooks Install Diagnostic Tool
Download QuickBooks Tool Hub from Intuit’s support site, open it, and go to Installation Issues → QuickBooks Install Diagnostic Tool. This free tool automatically checks and repairs your .NET Framework, Windows Installer, and Microsoft Visual C++ components. After it completes, restart your computer and try the QuickBooks installation again. This is the most comprehensive automated fix for error 1935.
Fix 3: Repair .NET Framework manually
Go to Control Panel → Programs and Features. Find each version of Microsoft .NET Framework listed (there may be several — 3.5, 4.0, 4.8). Right-click each one and select Repair. Wait for each repair to fully complete before starting the next. After repairing all versions, restart your computer and run the QuickBooks installer again. This directly fixes the corrupted .NET files that trigger error 1935.
Fix 4: Install .NET Framework 3.5 (if missing)
Some Windows 10 and 11 installations do not have .NET 3.5 enabled by default, which QuickBooks requires. Press Windows + R, type optionalfeatures, and press Enter. In the Windows Features dialog, check .NET Framework 3.5 (includes .NET 2.0 and 3.0) → click OK. Windows will download and install it. Restart your computer and retry the QuickBooks install.
Fix 5: Run installer as administrator
Right-click the QuickBooks installer file → select Run as administrator. Even if you are logged in as an admin, explicitly running as administrator grants the installer elevated permissions that are sometimes required for assembly registration. This is a quick one-step check before moving to more involved fixes.
Fix 6: Clean install using QuickBooks Clean Install Tool
If all previous fixes fail, use the QuickBooks Clean Install Tool (available inside QuickBooks Tool Hub under Installation Issues) to completely remove all QuickBooks files, folders, and registry entries. Restart your computer. Then run the QuickBooks installer fresh — a clean environment eliminates any conflicting leftover files that were causing error 1935.
Still Getting Error 1935?
If error 1935 persists after all six fixes, run Windows’ built-in system file checker. Open Command Prompt as administrator (search “cmd” → right-click → Run as administrator) and type: sfc /scannow then press Enter. This scans and repairs corrupted Windows system files that may be preventing .NET from functioning correctly. After the scan completes (takes 10–15 minutes), restart and try the QuickBooks install once more.
Prevent QuickBooks Error 1935 in the Future
- Keep Windows Update current. .NET Framework updates are delivered through Windows Update. A fully updated Windows system is far less likely to develop the file corruption that causes error 1935.
- Pause Windows Update before installing QuickBooks. Go to Settings → Windows Update → Pause updates for 1 week before running a major QuickBooks install or update. This prevents .NET conflicts during installation.
- Add QuickBooks to your antivirus exclusion list. Exclude the QuickBooks installation folder (C:\Program Files\Intuit\QuickBooks) and the installer executable from real-time scanning to prevent interference both during install and daily use.
QuickBooks error 1935 is one of the most common installation errors but also one of the most consistently fixable — disabling antivirus and repairing .NET Framework resolve it in the vast majority of cases. For a similar installation error that shares the same root cause, see our guide on QuickBooks error 1603. If you are seeing errors during QuickBooks updates rather than fresh installs, our QuickBooks installation error guide covers update-specific fixes in detail.
Frequently Asked Questions
What does QuickBooks error 1935 mean?
Error 1935 means the QuickBooks installer failed to register an assembly — a package of required code — during installation. The Windows Installer encountered an error (specifically a COM component registration failure) that stopped the install from completing. The root cause is almost always a corrupted or missing .NET Framework component on your PC, not a problem with the QuickBooks download.
Does error 1935 only happen with QuickBooks?
No. Error 1935 is a Windows Installer error code that can appear when installing any software that relies on .NET Framework or COM components — including Microsoft Office, Adobe products, and many other applications. QuickBooks is simply one of the more common triggers because it has specific .NET Framework version requirements.
How long does fixing error 1935 take?
If disabling antivirus does the trick, under 5 minutes. Running the QuickBooks Install Diagnostic Tool takes about 10–15 minutes including the restart. Repairing .NET Framework manually takes 15–20 minutes. A clean install takes 30–45 minutes total. In most cases the first or second fix resolves the error — you rarely need to go through all six steps.
Can I fix error 1935 without reinstalling Windows?
Yes — in almost every case. The six-step process above resolves error 1935 without touching Windows itself. Only in extreme cases of deep system corruption would a Windows reinstall be considered, and even then the sfc /scannow command usually handles it first.
Frequently Asked Questions
What Causes QuickBooks Error 1935?
QuickBooks error 1935 is a Windows Installer error that occurs when a required assembly — a package of code that QuickBooks needs — cannot be registered during installation. The most common causes are:
Quick Fix for QuickBooks Error 1935 — Step by Step?
Fix 1: Disable antivirus temporarily (fastest fix — try this first)
Still Getting Error 1935?
If error 1935 persists after all six fixes, run Windows’ built-in system file checker. Open Command Prompt as administrator (search “cmd” → right-click → Run as administrator) and type: sfc /scannow then press Enter. This scans and repairs corrupted Windows system files that may be



