Fix QuickBooks Desktop Error 1935 During Installation

Resolve QuickBooks Error 1935, an assembly component issue tied to the Windows installer family. Learn how to fix it offline and keep your Desktop version

When installing or updating QuickBooks Desktop, you might suddenly be stopped dead by Error 1935. This is a Windows installation error, not a problem with your accounting data. It means the installation process was interrupted while trying to register an assembly component in the Windows .NET Framework.

If you are maintaining an older, discontinued version of QuickBooks Desktop, installation errors can feel like a dead end since official support is no longer available. Fortunately, because this is a Windows-level issue, you can resolve it entirely on your own without needing an upgrade or outside intervention.

Understanding the 1xxx Installer Family

Error 1935 belongs to the 1xxx family of QuickBooks installation errors. If you are seeing this code—or nearby codes like 1903, 1921, or 1936—the underlying culprit is almost always the same. The Windows installer is failing to execute a command, usually because necessary background services are turned off, Microsoft's core XML and .NET services are damaged, or another program is locking the files QuickBooks needs to write to.

Common Causes of Error 1935

Before running through the fixes, it helps to know what triggers the assembly component halt:

• Disabled Windows services: The .NET Framework and MSXML services need to be running for the installer to work.
• Corrupt .NET Framework: If your Windows operating system's core frameworks are damaged, QuickBooks cannot install its required components.
• Antivirus interference: Security software often misidentifies installer behavior as suspicious and silently blocks it.
• Incomplete previous installations: Leftover registry keys or partial files from an older QuickBooks attempt can block a new install.

How to Fix Error 1935

You can resolve this error using tools already built into Windows, alongside the QuickBooks Tool Hub. Follow these steps in order.

1. Run the QuickBooks Install Diagnostic Tool The fastest way to bypass Error 1935 is to let QuickBooks diagnose its own installation environment.

• Open the QuickBooks Tool Hub (if you don't have it, you can download the Tool Hub installer from an archived source or a secondary PC and move it via a USB drive).
• Select Installation Issues.
• Click QuickBooks Install Diagnostic Tool and let it run. This tool automatically checks for damaged .NET Frameworks and restarts necessary Windows services.

2. Update Your Windows .NET Framework Manually If the diagnostic tool fails, the .NET Framework on your computer is likely badly damaged. Because this is a Windows component, you must repair it at the operating system level.

• Open the Windows Control Panel, go to Programs and Features, and select Turn Windows features on or off.
• Uncheck .NET Framework 4.x, click OK, and restart your computer.
• Return to the same menu, re-check the box, and restart again. This forces Windows to rebuild the framework from scratch.

3. Perform a Clean Installation If the error persists, leftover files from previous attempts are causing a conflict. You will need to uninstall QuickBooks, use the Tool Hub's Clean Install Tool to strip out all residual folders, and then reinstall your QuickBooks Desktop version.

Why Archived Installers Keep You Protected

When you maintain a discontinued version of QuickBooks Desktop, you are largely independent of Intuit's live servers. However, you still depend on the original installation file.

Keepers of archived installers (saved .exe or .zip files on a local drive or USB) are protected against forced updates and server outages. If a Windows update breaks your current QuickBooks installation, having your specific version's installer safely backed up means you can completely uninstall, clean the registry, and reinstall your exact version offline without being forced into an upgrade.

Preventing Future Installation Errors

To keep your legacy QuickBooks Desktop running smoothly:

• Always install as an Administrator: Right-click your installer file and select Run as Administrator to ensure the installer has the necessary permissions to write to the Windows registry.
• Temporarily disable antivirus: Turn off your third-party antivirus software just before clicking "Install" to prevent it from locking assembly files. You can turn it back on the moment the installation finishes.
• Keep your license and installation keys documented: Store your license number, product number, and installation key codes in a text file alongside your archived installer.

When to Suspect Company File Damage

Error 1935 is strictly an installation failure. It does not damage your company file (.qbw). However, if a botched installation attempt forced you to forcefully close QuickBooks while a company file was open, or if you experience sudden data corruption immediately after fixing the installation, the file itself may have sustained damage. In these cases, use the Tool Hub's QuickBooks File Doctor to scan for structural corruption. If the file fails to verify or repair, you may need to repair your damaged QuickBooks company file to recover your accounting history safely.