QuickBooks Error 1935 on Windows 11 — Step-by-Step Fix

QuickBooks Error 1935 stops the installation with the message “Error 1935: An error occurred during the installation of assembly component.” It’s one of the most frustrating QuickBooks setup errors because it happens before the software even finishes installing — and it’s become increasingly common on Windows 11. The cause is almost always a conflict with Microsoft .NET Framework or Visual C++ components, and the fix is straightforward once you know where to look.

What Causes QuickBooks Error 1935 on Windows 11?

Error 1935 is a Windows Installer assembly error. “Assembly” refers to the .NET Framework and Visual C++ components that QuickBooks needs to install. When Windows can’t write these components correctly to the system, it throws Error 1935. The most common causes on Windows 11 are:

• Corrupted .NET Framework. Windows 11 ships with .NET Framework 4.8 and includes .NET 3.5 as an optional feature. If either version has corrupted files — often after a failed Windows update or interrupted upgrade — the QuickBooks installer can’t install the assembly components it needs.
• Windows Update service interference. If Windows Update is actively running or stuck in the background while you install QuickBooks, the two processes compete for access to system assemblies. This conflict almost always produces Error 1935.
• Antivirus blocking assembly writes. Aggressive antivirus software — particularly real-time protection features — sometimes blocks the QuickBooks installer from writing .NET assembly files, triggering 1935 mid-install.
• Outdated Visual C++ Redistributables. QuickBooks requires specific versions of Microsoft Visual C++ Redistributable packages. If these are outdated or corrupted on Windows 11, the assembly installation fails.
• Windows 11 side-by-side assembly cache corruption. Windows 11 maintains a “WinSxS” folder that stores assembly components. If this folder has corrupted entries, new assembly writes fail with Error 1935.

How to Fix QuickBooks Error 1935 on Windows 11: Step-by-Step

Fix 1 — Disable Antivirus and Stop Windows Update Before Installing

This combination resolves the majority of Error 1935 cases on Windows 11.

1. Open your antivirus software and temporarily disable real-time protection.
2. Press Windows + R, type services.msc, and press Enter.
3. Scroll to Windows Update in the list, right-click it, and select Stop.
4. Also stop the Background Intelligent Transfer Service (BITS) the same way.
5. Now run the QuickBooks installer immediately.
6. Once QuickBooks finishes installing, re-enable antivirus and restart Windows Update (right-click → Start).

Fix 2 — Repair .NET Framework Using the Repair Tool

1. Search for “Microsoft .NET Framework Repair Tool” on Microsoft’s website and download it (it’s a free official tool).
2. Right-click the downloaded file and select Run as administrator.
3. Follow the prompts — the tool detects and repairs corrupted .NET Framework components automatically.
4. Restart your computer after the repair finishes.
5. Try the QuickBooks installation again.

Fix 3 — Enable .NET Framework 3.5 in Windows Features

QuickBooks requires .NET Framework 3.5, which is disabled by default on Windows 11. If it’s not enabled, Error 1935 will occur during installation.

1. Press Windows + R, type optionalfeatures, and press Enter.
2. In the Windows Features window, find .NET Framework 3.5 (includes .NET 2.0 and 3.0).
3. Check the box next to it and click OK.
4. Windows will download and install the feature — this may take a few minutes and requires an internet connection.
5. Restart your computer and run the QuickBooks installer.

Fix 4 — Run System File Checker and DISM

If the Windows 11 system file cache is corrupted, these two commands repair it.

1. Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin).
2. Run this command and wait for it to complete (takes 5–10 minutes):

   DISM /Online /Cleanup-Image /RestoreHealth

3. Once DISM finishes, run:

   sfc /scannow

4. Restart your computer after both commands complete.
5. Try installing QuickBooks again.

Fix 5 — Update or Reinstall Visual C++ Redistributables

1. Open Settings → Apps → Installed Apps.
2. Search for “Microsoft Visual C++” — you’ll see multiple entries for different years (2013, 2015, 2017, 2019, 2022).
3. For each entry, click the three dots and select Modify → Repair.
4. If repair doesn’t help, uninstall the older versions (2013 and 2015) and reinstall them fresh from Microsoft’s website.
5. Restart and try QuickBooks again.

Fix 6 — Install QuickBooks in Clean Boot Mode

A clean boot starts Windows 11 with only essential services, eliminating third-party software conflicts.

1. Press Windows + R, type msconfig, and press Enter.
2. Click the Services tab, check Hide all Microsoft services, then click Disable all.
3. Click the Startup tab → Open Task Manager → disable all startup items.
4. Click OK, restart your computer.
5. After restart, run the QuickBooks installer.
6. Once QuickBooks is installed successfully, re-enable services via msconfig and restart again.

Still Not Working?

• Use QuickBooks Tool Hub. Download QuickBooks Tool Hub from Intuit, open it, go to Installation Issues → QuickBooks Install Diagnostic Tool. Run it — it automatically repairs .NET Framework, MSXML, and Visual C++ components that cause Error 1935.
• Check Windows 11 is fully updated. Go to Settings → Windows Update and install all pending updates including optional ones. Some Windows 11 builds have known assembly bugs that were patched in later updates.
• Try installing as a different Windows user. Create a new local administrator account (Settings → Accounts → Family & other users → Add account), log in as that user, and try installing QuickBooks. If it works, your original user profile may have corrupted assembly permissions.

If you’re also seeing other installation failures, see our guide on QuickBooks installation errors on Windows 10 and 11 — it covers the full range of setup failures that often appear alongside Error 1935.

Prevent QuickBooks Error 1935 on Windows 11 in the Future

• Always pause Windows Update before installing QuickBooks. Go to Settings → Windows Update → Pause updates for 1 week before any QuickBooks installation or major update. Resume after the install completes.
• Keep .NET Framework components healthy. Run the .NET Framework Repair Tool once a year or any time Windows Update reports a .NET-related failure. Catching corruption early prevents it from blocking future QuickBooks installs.
• Use QuickBooks Tool Hub for all installs. Running the Install Diagnostic Tool before installing QuickBooks pre-repairs common Windows component issues and prevents Error 1935 from occurring in the first place.

Frequently Asked Questions

Why is QuickBooks Error 1935 more common on Windows 11?

Windows 11 has stricter assembly write policies and handles .NET Framework differently from Windows 10. The WinSxS assembly cache in Windows 11 is more sensitive to corruption, and Windows 11’s more aggressive background update activity frequently conflicts with third-party installers. This combination makes Error 1935 more common on Windows 11 than on previous Windows versions.

Is my company data safe when Error 1935 occurs?

Yes. Error 1935 only occurs during installation — it cannot affect company files that are already saved on your computer. Your existing QuickBooks data (.QBW files) are completely unaffected by installation errors. The error only prevents the new installation from completing.

Do I need to uninstall the old QuickBooks version before fixing Error 1935?

Not necessarily. Error 1935 is a Windows component issue, not a conflict between QuickBooks versions. Try the .NET Framework repair and antivirus/Windows Update fixes first. If those don’t work, then do a clean uninstall of any previous QuickBooks version before attempting a fresh install.

How long does it take to fix Error 1935?

Fix 1 (disabling antivirus and stopping Windows Update) takes about 5 minutes and resolves most cases. Fix 4 (DISM and SFC scans) takes 15–20 minutes. The QuickBooks Install Diagnostic Tool takes 15–20 minutes. In total, most users resolve Error 1935 within 30 minutes using the steps above.