Error 1935 during a QuickBooks Desktop install: the fix that works

Error 1935 is one of those QuickBooks Desktop problems that shows up at the worst possible moment. The installer runs partway, Windows throws the code, and setup ends without a working program. The accepted resolution is settled by now: run the Install Diagnostic Tool from the QuickBooks Tool Hub, bring Windows up to date, and try the installation again.

What does error 1935 look like?

The code appears in two situations. Some users hit it while installing QuickBooks Desktop, when setup stops partway and Windows reports the failure. Others see it when opening the program for the first time after an install that seemed to finish cleanly.

In most cases the code points at Windows components rather than at QuickBooks itself. Desktop relies on Microsoft .NET Framework and MSXML as it installs. When one of those pieces fails to register properly, Windows reports error 1935 and setup cannot continue.

Users describe the same pattern each time: setup reaches a late stage, the screen reports the Windows code, and the installer exits. Because the message names a Windows component rather than a QuickBooks module, it is easy to assume a damaged download or an account problem is to blame. The accepted answer does not treat either as the cause; it treats the Windows components as the target.

That placement explains why a plain retry seldom clears it. Running the installer again does nothing for the components underneath, so the same code tends to reappear. The accepted fix goes after those components first, and it uses a dedicated tool to do the work.

The accepted fix: the Install Diagnostic Tool

The accepted answer starts with the QuickBooks Tool Hub, a repair utility that bundles fixes for common Desktop errors. The guidance cites version 1.4.0.0 as current. If the hub is already on your machine, you can confirm your copy on the Home tab; the version number sits at the bottom right of the window. The guidance also recommends Windows 10, 64-bit for the best experience.

Follow this sequence:

1. Close QuickBooks if it is open.
2. Download the QuickBooks Tool Hub and save the file somewhere easy to find, such as your Downloads folder or the Windows desktop.
3. Open the downloaded QuickBooksToolHub.exe file and follow the on-screen prompts, agreeing to the terms when they appear.
4. When setup finishes, double-click the new desktop icon to open the hub.
5. Select Installation Issues, then QuickBooks Install Diagnostic Tool.
6. Let the tool run. It can take up to 20 minutes, so allow for the wait.
7. Restart your computer when the tool finishes.

If the desktop icon is hard to find, search Windows for QuickBooks Tool Hub and open the program from there. The 20-minute run is the longest step in the sequence, so plan for it before you start.

After the tool runs

Two more steps close out the repair. Run Windows Update and install anything pending, then restart the computer a second time. Neither restart is optional. The accepted steps treat both as part of the fix, not as housekeeping around it.

From there the path splits in two. If QuickBooks was already installed and opened before the error appeared, open the program and your company file as usual. If the installation never completed, run the QuickBooks Desktop installer again. With the Windows components repaired, setup should carry through this time.

The fallback repairs

The accepted sequence has a fallback layer. If the code returns after the tool has run, two manual repairs come next. The first is to repair or reinstall Microsoft .NET Framework. The second is to repair Microsoft MSXML.

Both are the components named earlier, so either one can be the piece that failed to register during setup. The accepted order places them behind the tool because the tool performs the same repairs automatically where it can. After either manual repair, restart and run the installation once more.

Error 1935 looks like a QuickBooks failure, but the repair path runs through Windows. The Tool Hub automates the first pass. The two restarts lock the repairs in place. The manual component fixes cover the stubborn cases. Follow the full sequence in order and the Desktop installation should finish without the code returning.