QuickBooks Error 1935: Fixing Assembly Component Installation Errors

August 16, 2026 13 min read

QuickBooks Error 1935 occurs during the installation or updating of QuickBooks Desktop when the Windows Installer fails to register a required assembly component. The error prompt typically reads: “Error 1935: An error occurred during the installation of assembly component,” often citing an alphanumeric GUID along with HRESULT: 0x80070005 or 0x80070003.

This failure occurs when the Microsoft .NET Framework runtime is damaged, when Microsoft Visual C++ redistributable packages cannot commit to the system registry, or when active antivirus software locks system files. Repairing .NET components, updating Visual C++ libraries, and running installation diagnostics will resolve the error.

Fast-Fix: The 45-Second Solution

To resolve Error 1935, restart your computer in Selective Startup (Safe Mode with Networking) to prevent background programs from locking system files. Download and run the QuickBooks Install Diagnostic Tool from the QuickBooks Tool Hub to repair damaged Microsoft .NET Framework and C++ runtimes automatically. Once the tool finishes, restart your computer and run the QuickBooks installation again as Administrator.

Quick Status & Triage Snapshot

  • Data Risk Tier: Zero. Error 1935 is an operating system component installation error. It prevents QuickBooks from installing or updating, but it does not touch or damage existing .QBW company files.
  • Multi-User Impact: Isolated to the workstation or server where the installation is being run. Other workstations on the network can continue accessing the company file normally.
  • Common Trigger: Installing a new version of QuickBooks Desktop, applying a major release patch, or running Windows updates that leave .NET Framework assembly registrations incomplete.
  • Estimated Fix Time: 10–15 minutes.

Diagnostic Flowchart: Error 1935 Decision Path

[Start: Error 1935 Halts Installation]
       |
       v
Did the error appear during the .NET Framework install stage?
  |
  |-- YES --> Microsoft .NET Framework is corrupted or turned off in Windows Features.
  |           Action: Run QuickBooks Install Diagnostic Tool & repair .NET Framework.
  |
  \-- NO ---> Error occurred during C++ runtime or file registration stage.
              |
              v
       Is real-time antivirus or endpoint security actively scanning?
         |-- YES --> Security software is locking the Global Assembly Cache (GAC).
         |           Action: Temporarily disable antivirus; install via Clean Boot.
         |
         \-- NO ---> Windows Component Store or Visual C++ libraries damaged.
                     Action: Repair Visual C++ runtimes & run system file check.

Technical Anatomy: Why Error 1935 Breaks the Installation

During setup, the QuickBooks installer (an MSI package) unpacks core program files and configures shared system libraries. Error 1935 represents a failure in the Global Assembly Cache (GAC) or the Windows Side-by-Side (WinSxS) subsystem.

  1. Assembly Registration: QuickBooks relies heavily on managed code built on Microsoft .NET. When the installer registers an assembly (a compiled code library such as a .dll), it makes system calls to write entries into the GAC (C:\Windows\Microsoft.NET\assembly).
  2. The Lockout: If another process (such as a pending Windows Update or real-time antivirus scanner) holds an open lock on the registry keys under HKLM\Software\Microsoft\Fusion or files inside WinSxS, the installer receives an access-denied signal (0x80070005).
  3. The Rollback: Because the assembly registration is marked as critical in the MSI manifest, the installer cannot ignore the failure. It triggers a rollback sequence, removing copied files and leaving QuickBooks uninstalled.

Step-by-Step Repair Guide

Step 1: Run the QuickBooks Install Diagnostic Tool

Intuit provides an automated repair tool inside the QuickBooks Tool Hub that scans and repairs broken .NET Framework and C++ runtime dependencies.

  1. Close any open applications and your web browser.
  2. Download the latest version of the QuickBooks Tool Hub from Intuit’s official download page.
  3. Open the downloaded file (QuickBooksToolHub.exe) and follow the on-screen prompts to install it.
  4. Launch the QuickBooks Tool Hub from your desktop shortcut.
  5. In the left-hand menu, select Installation Issues.
  6. Click QuickBooks Install Diagnostic Tool.
  7. Allow the tool to run. This scan can take 15 to 20 minutes to audit and repair Windows system components.
  8. Once the process completes, restart your computer and attempt to install QuickBooks again.

For more details on resolving stubborn installation failures, see Clean Install Tool: Using the QuickBooks Tool Hub to Fix Corrupt Installs.

Step 2: Manually Repair Microsoft .NET Framework

If the automated tool does not clear Error 1935, toggle the Microsoft .NET components directly in Windows to force a rebuild of the assembly cache.

  1. Press Windows Key + R, type optionalfeatures.exe, and press Enter.
  2. In the Windows Features dialog box, locate .NET Framework 3.5 (includes .NET 2.0 and 3.0) and .NET Framework 4.8 Advanced Services (or 4.7/4.6, depending on your Windows version).
  3. If the boxes are checked:
    • Uncheck both .NET Framework entries.
    • Click OK and let Windows apply the changes.
    • Restart your computer.
  4. After restarting, press Windows Key + R, run optionalfeatures.exe again, and re-check both .NET Framework options.
  5. Click OK. Windows will download fresh component binaries from Windows Update.
  6. Restart your computer once more.

For a full breakdown of repairing underlying framework services, review .NET Framework: Repairing Windows Components for QuickBooks Stability.

Step 3: Reinstall Microsoft Visual C++ Redistributables

QuickBooks requires functioning 32-bit and 64-bit Visual C++ runtimes to register assemblies.

  1. Press Windows Key + R, type appwiz.cpl, and press Enter to open Programs and Features.
  2. Scroll down to find the Microsoft Visual C++ Redistributable packages.
  3. Note the versions installed (typically 2012, 2013, 2015–2022).
  4. Right-click each package, select Change, and then click Repair.
  5. If the repair option is unavailable or fails:
    • Uninstall the packages.
    • Download fresh installers directly from Microsoft’s official support site (download both the x86 and x64 versions of the Visual C++ 2015–2022 redistributable).
    • Install both packages and reboot the computer.

Step 4: Perform the Installation in Selective Startup (Clean Boot)

Third-party services, security software, and backup utilities can lock the Global Assembly Cache during installation. Running a clean boot eliminates these interferences.

  1. Press Windows Key + R, type msconfig, and press Enter.
  2. On the General tab, select Selective startup.
  3. Uncheck Load startup items, but make sure Load system services remains checked.
  4. Go to the Services tab:
    • Check the box at the bottom labeled Hide all Microsoft services.
    • Click Disable all.
  5. Click Apply, then OK, and restart your computer.
  6. Run the QuickBooks Desktop installer again.
  7. Once installed, return to msconfig, select Normal startup, click OK, and restart Windows to re-enable your background apps.

Hard Stop: When to Escalate to Windows System Repairs

If Error 1935 continues to appear across clean boots and .NET repairs, the underlying Windows Component Store (WinSxS) has suffered deeper system corruption.

Before escalating to OS-level reinstallation:

  1. Open Command Prompt as Administrator (cmd).
  2. Run sfc /scannow to scan and repair protected system files.
  3. If SFC finds files it cannot fix, run:
    DISM /Online /Cleanup-Image /RestoreHealth
  4. This command uses Windows Update to replace damaged assembly manifests in the Component Store. Once finished, re-attempt the installation.

Closing the Books

Error 1935 is an environmental installation barrier caused by locked registry keys or damaged Windows system libraries, not a problem with your accounting data. Rebuilding your .NET Framework assemblies, repairing the Visual C++ redistributable runtimes, and running the setup in Selective Startup clears the assembly cache roadblocks and allows QuickBooks Desktop to install properly.

QuickBooks Error 1935 typically occurs during the installation or updating of QuickBooks Desktop, signaling that the setup process was abruptly halted while trying to install essential assembly components. This system-level installation failure generally stems from damaged Microsoft .NET Framework components, corrupted C++ redistributable packages, or aggressive third-party security software actively blocking background system modifications.

Fast-Fix: The 45-Second Solution

To resolve this error immediately, close all active applications, use the QuickBooks Install Diagnostic Tool from the QuickBooks Tool Hub to patch the installer files, and ensure your Windows system updates are completely caught up. Fixing this installation block ensures your system can register the software files cleanly and completes the installation without sudden rollbacks.

Quick Status & Triage Snapshot

  • Data Risk Tier: None (This error blocks the installation or update of the QuickBooks program itself; your company data files sit safely elsewhere on your drive).
  • Multi-User Impact: Single Workstation (The issue only affects the individual computer where the installer is failing).
  • Common Trigger: An outdated Microsoft .NET installation, background antivirus apps locking system registries mid-install, or installing a major QuickBooks version upgrade.
  • Estimated Fix Time: 15 to 25 minutes.

Diagnostic Flowchart: Installation Block Path

[Start Setup] -> Run the QuickBooks Installer -> Does Error 1935 appear?
                     |
                     +--> Yes -> Close the installer window completely.
                                  |
                                  +--> Run the QuickBooks Install Diagnostic Tool from the Tool Hub.
                                       |
                                       +--> Does the installation still fail?
                                            |
                                            +--> Yes -> Navigate to Windows Features -> Toggle .NET states off and back on.
                                            +--> No  -> Installation complete.

Is Your Data at Risk?

Because Error 1935 hits during the application software setup process, your actual transaction data, customer profiles, and balance sheets are completely unaffected. The program file installation system is completely separate from your active database directories.

Critical Safety Rule: If this error interrupts an automated update inside an existing QuickBooks setup, do not immediately attempt to manually uninstall your current version of QuickBooks without verifying that you have your original installation license numbers and product codes documented safely nearby.

Technical Anatomy: The Missing Foundation Blocks

Think of installing QuickBooks Desktop like building a heavy factory machine on a concrete foundation. QuickBooks relies on pre-made foundation pieces provided by Windows, specifically Microsoft runtime components and assembly packages, to support its heavy data operations.

Error 1935 occurs when the factory machine goes to snap its custom components into the base blocks, only to find the pre-made foundation hooks are warped, cracked, or completely missing from the host computer. When the installer gets rejected by the operating system’s registry, it panics, stops the build, and rolls back the setup files to prevent half-finished programs from leaving loose debris across your hard drive.

Root Cause Analysis: Why the Assembly Fails

  • Most Likely (70%): A broken or unoptimized Microsoft assembly component on the Windows operating system is rejecting new software code updates.
  • Possible (20%): A running security program or real-time backup application has locked down the Windows Registry to protect it, inadvertently blocking the QuickBooks utility from writing its startup entries.
  • Rare (10%): The installation setup file itself is partially corrupted due to a broken or incomplete digital download stream.

Risk Escalation & Severity Factors

The difficulty of clearing an assembly component block depends on the condition of your operating system. If you are performing a fresh installation on a computer running a new upgrade of Windows 11, background file permission rules can sometimes conflict with older legacy assembly layers. If the underlying system files are deeply corrupted, standard repair utilities will fail, requiring a more thorough manual cleanup.

The Cost of Delay: Today vs. End of Week

  • Today: Complete installation block. You cannot launch the accounting interface on this computer, delaying invoice preparation, cash flow recording, and routine data entries.
  • End of Week: Backlogged paperwork blocks your business operations, causing unrecorded financial movements and preventing the processing of critical employee payroll deadlines.

Differential Diagnosis: Don’t Confuse This With…

Ensure you distinguish an engine installation block from general system requirement errors:

Step-by-Step Repair Guide

Step 1: Deploy the Automated Install Diagnostic Tool

Using the automated cleanup suite resets the baseline installation keys without requiring deep manual edits. For information on clearing out corrupt installation files, see our tool guide: Clean Install Tool: Using the QuickBooks Tool Hub to Fix Corrupt Installs.

  1. Close the blocked QuickBooks installation screen.
  2. Open your web browser and download the official QuickBooks Tool Hub file. Save it directly to your Windows desktop.
  3. Open the downloaded QuickBooksToolHub.exe installer file and follow the clear configuration instructions to install the program.
  4. Launch the Tool Hub using the new shortcut icon on your desktop screen.
  5. Choose the Installation Issues category tab located on the left side menu panel.
  6. Click the green QuickBooks Install Diagnostic Tool button. The application will open a command console window and scan your core Windows setup components.
  7. Let the utility run through its automated scripts completely (this can take up to 20 minutes depending on your hard drive speed). Once the repair process finishes, restart your computer.

Step 2: Manually Refresh the Windows Assembly Components

If the automated diagnostic tool doesn’t clear the error, you must force Windows to reload its underlying component sub-layers.

  1. Press the Windows Key + R on your keyboard to open the manual Run command box.
  2. Type optionalfeatures inside the box text entry area and hit Enter.
  3. Look at the very top of the list for the Microsoft component entries (often labeled as .NET Advanced Services).
  4. If the check box next to the component is unchecked, check it immediately to turn the option on, then click OK.
  5. If the box is already filled with a check mark or solid block:
    • Uncheck the box completely, click OK, and let Windows disable the component files temporarily.
    • Restart your computer, return to this exact same Windows Features menu, recheck the box to turn the component back on, and click OK. This forces Windows to completely rewrite the baseline application hooks.

Step 3: Clear and Enable the Windows Modules Installer Service

Ensure the background Windows setup engine has the clearance it needs to edit system files.

  1. Press Windows Key + R, type services.msc, and press Enter.
  2. Scroll through the background tool management list to find Windows Modules Installer.
  3. Right-click the service name entry and choose Properties.
  4. Change the Startup type option selection from Manual to Automatic.
  5. Look at the current status line. If the service is stopped, click the Start button immediately. Click Apply and then click OK.
  6. Temporarily pause your local third-party antivirus program shield through its taskbar shortcut menu, right-click your QuickBooks installation setup file, and select Run as Administrator.

Hard Stop: When to Call an Expert

You should stop troubleshooting and contact a professional technician if:

  • The installation script continues to drop Error 1935 immediately after you have toggled the Windows subcomponent features and run the automated tool diagnostics.
  • Your operating system returns a “Fatal System Registry Write Error” notification, indicating deep operating system issues that go beyond standard software configurations.

Professional Intervention: What a ProAdvisor Will Do

An IT deployment professional or certified ProAdvisor will dive directly into your Windows registry trees using administrative command utilities. They will manually rebuild corrupted component logs, remove conflicting system sub-layers from older legacy software builds, verify file system integrity metrics, and clean up background folder permissions to ensure the installer has clear access to your storage drives.

Estimated Professional Repair Costs

  • Standard Component Optimization: $125 – $225 (Covers automated diagnostic tool deployment, runtime component correction, and verification).
  • Deep Operating System Restoration: $275 – $450 (Required if your computer has deep registry failures, system security conflicts, or requires an operating system reset).

If you clear the initial assembly installation blocks but your software still encounters permission walls during the final activation process, your licensing verification files may be broken. To make sure your software rights match your machine identity perfectly, look through our specialized validation guide: License Validation: Updating EntitlementDataStore.ecml for QuickBooks.

Closing the Books

Fixing QuickBooks Error 1935 is a systematic task that focuses on cleaning up your computer’s baseline files. By using the automated Install Diagnostic tool to patch missing runtime parameters and ensuring your Windows subcomponents are active and responsive, you can easily bypass installation blocks. Keeping these foundation layers updated and clean keeps your accounting system stable so you can run your business smoothly.

QuickBooks Error 1722: Troubleshooting Windows Installer Package Problems

August 17, 2026

QuickBooks Error 1603: Repairing Fatal MSI Installation & Update Errors

July 2, 2026

How to Fix QuickBooks Error 1903: Resolving System Requirement & Component Failures

July 2, 2026