Quick answer

QuickBooks error 1935 means Windows could not install or register a .NET assembly that setup needs. The usual culprits are a damaged Microsoft .NET Framework, a broken Visual C++ runtime, MSXML registration problems, or another program locking Windows Installer. Repair those Windows components with Microsoft's own tools, update Windows, then run the QuickBooks installer as administrator.

What QuickBooks error 1935 means

Error 1935 appears during installation, update, or repair, and it always points at the same layer: the Windows Installer engine failed while registering a .NET assembly. You will see one of two messages.

  • "Error 1935: An error occurred during the installation of assembly component" followed by a component name, version, and an HRESULT code.
  • "Error 1935: This setup requires .NET Framework" when setup cannot find a usable runtime on the computer.

The assembly name in the first message is the real clue. Entries such as Microsoft.VC90.ATL or Microsoft.VC80.CRT point at the Microsoft Visual C++ runtime, not at QuickBooks. An HRESULT of 0x80070005 means access denied: the installer could not write where it needed to.

QuickBooks Desktop setup depends on Microsoft components that either ship with Windows or arrive with the installer. When one of those components is half-installed, locked, or damaged, setup rolls back near the end and reports 1935.

Symptoms that come with error 1935

  • The installer reaches the final registration stage, shows "rolling back changes," and removes QuickBooks.
  • The error repeats on every retry and is sometimes followed by a second failure such as error 1603.
  • QuickBooks may appear in Settings → Apps → Installed apps but will not open or update.
  • Windows Update history shows a failed .NET Framework update around the same time.

Common causes, ranked by how often they appear

  1. Damaged or partially installed .NET Framework. An assembly manifest exists, but the Global Assembly Cache entry behind it is broken, so registration fails.
  2. A pending or concurrent installation. A restart is pending, Windows Update is mid-install, or a second MSI is running. Windows Installer allows only one installation at a time.
  3. Antivirus or endpoint security blocking setup. Intuit lists antivirus and anti-spyware as a cause of error 1935 because security filters can block writes to the assembly store and temp folders.
  4. A missing or damaged Visual C++ runtime. Assemblies named Microsoft.VC80.* map to the Visual C++ 2005 runtime, and Microsoft.VC90.* maps to Visual C++ 2008.
  5. MSXML registration problems. MSXML 6.0 ships with Windows, but its registration can be broken by cleanup tools or failed updates.
  6. Windows component or servicing corruption. A damaged servicing stack or component store prevents Windows Installer from registering assemblies correctly.
  7. Permissions. The installer is not elevated, or the account cannot write to the program or temp folders, which produces the classic 0x80070005 result.

Back up first. Copy your company file folder, including the .QBW, .TLG, and .ND files, to an external drive before any repair or reinstall. Component repairs never touch company data, but a failed clean install can leave you unable to open it if something goes wrong.

Before you begin

  • Sign in with a Windows administrator account for every step below.
  • Current QuickBooks releases need a supported 64-bit Windows version and roughly 2.5 GB of free space before setup starts. Confirm the QuickBooks installation requirements if you are unsure.
  • Write down your license and product numbers. You need them after a clean install.
  • Budget 30 to 60 minutes. The .NET repair tool and the Windows component scans are the slow parts.

How to fix QuickBooks error 1935

1

Restart, then run setup as administrator

Close every program and restart Windows. After the restart, open Task Manager with Ctrl + Shift + Esc and check the Details tab for msiexec.exe and any running setup process. Finish one installation before starting another, because a pending restart blocks Windows Installer.

Then right-click the QuickBooks installer and choose Run as administrator. This single step clears the most common permission-related 1935 failures.

2

Run the QuickBooks Install Diagnostic Tool

Install the current QuickBooks Tool Hub, open it, select Installation Issues, then select QuickBooks Install Diagnostic Tool. Let it finish. Intuit notes it can take up to 20 minutes, and it repairs .NET Framework, MSXML, and Visual C++ problems in one pass. Restart the computer when it completes.

If you have never used the tool, follow the dedicated Install Diagnostic Tool walkthrough first.

3

Install every Windows update

Open Settings → Windows Update, select Check for updates, and install everything offered. Then open Advanced options → Optional updates and install the .NET-related entries. Restart and retry the QuickBooks installer.

.NET Framework fixes arrive through Windows Update, so a machine that has not updated in months is the most likely to fail assembly registration.

4

Repair .NET Framework with Microsoft's tool

Download the Microsoft .NET Framework Repair Tool (NetFxRepairTool.exe) from the Microsoft Download Center and run it as administrator. The wizard detects setup issues, applies fixes with your consent, and repairs installed .NET versions from 3.5 SP1 through 4.8. Restart, then retry QuickBooks setup.

If setup still fails, follow Microsoft's Repair an installation of .NET Framework procedure (KB306160), which runs msiexec against the original runtime package with REINSTALL=ALL. Do not use third-party .NET cleanup utilities. They remove assemblies that Windows and QuickBooks still need.

5

Check Windows features and repair the Visual C++ runtimes

Open Control Panel → Programs and Features and select Turn Windows features on or off. Confirm .NET Framework 3.5 (includes .NET 2.0 and 3.0) and .NET Framework 4.8 Advanced Services are selected. If one is already selected but misbehaving, clear it, restart, then select it again. That off-and-on cycle is the sequence Intuit documents for manually fixing .NET Framework errors.

Next, open Settings → Apps → Installed apps, find each Microsoft Visual C++ Redistributable entry, select Modify, then Repair. Repair both the x86 and x64 packages. If a package is missing, install the current supported redistributables from Microsoft.

6

Re-register MSXML

Open Command Prompt as administrator and run regsvr32 /s msxml6.dll, then regsvr32 /s msxml3.dll. MSXML 6.0 is part of Windows 10 and Windows 11, so the goal is to restore registration, not to download a new copy. Avoid third-party sites that offer MSXML installers.

7

Repair Windows component health

If updates fail or the installer keeps rolling back, repair the component store. Open an elevated Command Prompt and run DISM /Online /Cleanup-Image /RestoreHealth, then run sfc /scannow. Restart when the scan finishes and retry setup.

These commands repair the servicing stack and system files that Windows Installer relies on when it writes assemblies. Skipping this step is why some 1935 errors survive every .NET reinstall.

8

Rule out antivirus and third-party blockers

Pause your antivirus protection using the vendor's documented method, and add exclusions for C:\Program Files\Intuit, C:\ProgramData\Intuit, and the folder that contains the installer. Turn protection back on as soon as setup finishes.

If the installer is still blocked, install QuickBooks in Selective Startup, which is Intuit's supported way to isolate third-party interference. Press Windows + R, type msconfig, choose Selective startup with Load system services, select Hide all Microsoft services, select Disable all, re-check Windows Installer, and restart. Return to Normal startup when you are done.

A clean install removes settings, not company data — but still back up. Uninstalling QuickBooks deletes program files and preferences. Your company files live elsewhere, yet you should copy them to an external drive and verify the copy opens before you continue.

9

Perform a clean install

Uninstall QuickBooks from Settings → Apps → Installed apps, or from Programs and Features in Control Panel. Restart, then run the freshly downloaded installer as administrator. For stubborn cases, Intuit's Reinstall QuickBooks Desktop article adds a deeper option: after removing the program, rename the leftover folders by appending "old" to C:\ProgramData\Intuit\QuickBooks (year), C:\Users\<user>\AppData\Local\Intuit\QuickBooks (year), and C:\Program Files\Intuit\QuickBooks (year) or C:\Program Files (x86)\Intuit\QuickBooks (year), then reinstall so QuickBooks rebuilds them. If the program will not uninstall cleanly, see the QuickBooks Clean Install Tool guide, and use the QuickBooks Desktop installation guide for the full walkthrough.

Verify the installation

  1. Setup finishes without a rollback message and QuickBooks opens to the activation or sign-in screen.
  2. Press F2 to open the Product Information window and confirm the product and version.
  3. Open your company file and run File → Utilities → Verify Data. A healthy file reports no problems.
  4. If you work in multi-user mode, confirm a second computer can open the company file over the network.

If error 1935 comes back

Look at the assembly named in the message before you retry anything. A repeated failure on the same Microsoft.VCxx assembly means that specific Visual C++ runtime family is still damaged. Repair the matching redistributable: VC80 for the 2005 runtime, VC90 for 2008, VC100 for 2010, and so on.

If Windows itself is failing updates, repairing system files, or throwing errors in other installers, the problem sits above QuickBooks. Intuit's guidance at that point is a qualified IT professional or Microsoft, because the operating system needs repair, not the accounting program. A practical test is to install QuickBooks on a different, fully updated Windows PC. If setup succeeds there, your company file is fine and the original machine needs OS-level attention, such as a repair install or reset if an IT professional recommends it.

Prevention

  • Keep Windows Update enabled and install .NET updates promptly. Most 1935 errors trace back to a missing or failed runtime update.
  • Never run registry cleaners or "system optimizer" tools on a machine that runs QuickBooks. They delete assembly and runtime registrations that setup depends on.
  • Install QuickBooks from local storage with administrator rights, and pause security software using the vendor's documented method.
  • Keep your installer file, license number, and product number together so a future reinstall takes minutes instead of an afternoon.
  • Before any QuickBooks upgrade, back up the company file so troubleshooting steps like the error 1603 fixes never put data at risk.

Frequently asked questions

Will fixing error 1935 delete my company data?

No. Error 1935 happens while Windows registers program components, long before QuickBooks touches a company file. Your .QBW file is untouched by .NET repairs and reinstalls. Keep a backup anyway, because a failed install can leave the program unusable until it is reinstalled properly.

Do I need to uninstall QuickBooks before repairing .NET Framework?

No. Repair .NET first and run the installer over the top. Uninstalling QuickBooks before the runtime is healthy only adds a second failure point. Uninstall QuickBooks only when you have decided to do a clean reinstall.

Which .NET version does QuickBooks Desktop need?

Current releases include Microsoft .NET Framework 4.8 Runtime, about 60 MB, with the installation files, and Windows 10 and Windows 11 include .NET 4.8 or later. Older QuickBooks versions used earlier runtimes. The repair workflow stays the same regardless of version.

What does Microsoft.VC90.ATL mean in the error?

It is a Visual C++ assembly. VC90 identifies the Visual C++ 2008 runtime, and VC80 identifies the Visual C++ 2005 runtime. Repair or install the matching x86 and x64 redistributable packages, and do not delete files from the assembly store.

Can antivirus software cause error 1935?

Yes. Intuit lists antivirus and anti-spyware software as a cause of error 1935 because security products can block installer writes. Pause protection using the vendor's method, add exclusions for the Intuit and QuickBooks folders, install, then turn protection back on.

Sources & further reading