QuickBooks Error 1935 -- .NET Framework Conflict During Install

QuickBooks Error 1935 stops installation when .NET Framework assemblies fail to register; our engineers walk through resolving the conflict so setup completes cleanly.

QuickBooks Error 1935 appears mid-installation when the Windows Installer cannot assemble a required .NET Framework component. The installation halts, sometimes after the progress bar has moved well past halfway, leaving QuickBooks in a partially configured state. Our engineers have resolved this error across every supported QuickBooks Desktop version, and in nearly every case the root cause is a .NET Framework installation that is damaged, disabled, or locked by another process.

What the Error Message Says

The message typically reads:

"Error 1935. An error occurred during the installation of assembly component {hex-identifier}. HRESULT: 0x800736FD."

The hex identifier in the braces varies depending on which assembly the installer was trying to register when it failed. The HRESULT may also differ — common variants include 0x80070003, 0x80070422, and 0x80073712 — but they all point to the same class of problem: Windows could not install or register a .NET component that QuickBooks depends on.

What the Code Means

Error 1935 is a Windows Installer code, not a QuickBooks-specific one. It signals that the transaction the installer used to put a .NET assembly into the Global Assembly Cache was rolled back. Think of it as the installer beginning to place a component, encountering a conflict or permission barrier, and then undoing the partial write. QuickBooks surfaces this because its setup routine calls Windows Installer to lay down .NET components before it configures its own application files.

What Triggers It

The most common triggers, in the order our engineers see them:

1. A corrupted or incomplete .NET Framework installation — prior Windows updates, manual uninstalls, or registry cleaners have left .NET in an inconsistent state.
2. Antivirus or endpoint security software locking files — real-time scanning intercepts the assembly registration and blocks write access to the GAC.
3. Insufficient Windows account privileges — the user running the installer lacks local administrator rights.
4. Windows Update service stopped or disabled — the installer depends on background Windows services that, if disabled, cause assembly registration to fail.
5. Conflicting background installations — a pending Windows update or another MSI-based install is holding a lock.

How to Fix It

Scenario 1: Corrupted .NET Framework (most common)

1. Close QuickBooks and all running applications.
2. Open Control Panel → Programs and Features → Turn Windows features on or off.
3. Uncheck every .NET Framework entry (3.5 and 4.x), click OK, and restart the computer.
4. Return to the same dialog, re-check all .NET Framework entries, click OK, and restart again.
5. Download the QuickBooks Install Diagnostic Tool from the PerpetualBooks tools page, run it, and allow it to complete.
6. Relaunch the QuickBooks installer.

Scenario 2: Antivirus interference

1. Temporarily disable real-time scanning in your endpoint security product.
2. Re-run the QuickBooks installer.
3. Once installation completes, re-enable real-time scanning and add the QuickBooks installation directory to any exclusions your security product recommends.

Scenario 3: Insufficient privileges

1. Verify the Windows user account is a member of the local Administrators group.
2. Right-click the QuickBooks installer executable and select Run as administrator.
3. Complete the installation.

Scenario 4: Windows Update services disabled

1. Press Win+R, type services.msc, and press Enter.
2. Locate Windows Update (or Update Orchestrator Service on newer builds). If the status is Disabled, right-click, select Properties, set Startup type to Manual, and click Start.
3. Repeat for Background Intelligent Transfer Service and Cryptographic Services.
4. Restart the computer and re-run the installer.

Scenario 5: Pending or stuck installation lock

1. Restart the computer — do not shut down and power back on; choose Restart explicitly.
2. Before opening any other application, run the QuickBooks installer.

How to Prevent It Recurring

Before any future QuickBooks installation or upgrade, confirm that .NET Framework 3.5 and 4.x are both fully enabled in Windows Features, that no pending Windows updates are staged, and that endpoint security software is temporarily disabled for the duration of setup. Running the QuickBooks Install Diagnostic Tool proactively — before launching the main installer — clears residual registration conflicts in most cases. If the 1935 error persists after all scenarios above have been exhausted, the Windows component store itself may need repair via DISM, which our engineers can guide you through.