QuickBooks Installation Error
How to Fix QuickBooks Error 1935
QuickBooks installer displays: "Error 1935: This setup requires .NET Framework" or "An error occurred during the installation of the assembly" while installing QuickBooks Desktop.
Error 1935 is a Windows installation error, not a QB-specific error. At QuickFix Bookkeeping, it appears when the .NET Framework — a required Windows component — is either missing, corrupted, or in use by another process during QB installation. It affects QB Desktop, .NET Framework installation itself, and other Windows applications like Norton, AutoCAD, and Microsoft Office.
The QuickFix Bookkeeping Distinction — The .NET Toggle Fix
Error 1935 has three causes that look identical on screen. The fastest fix — the .NET Framework toggle — resolves the majority of cases in 5 minutes without any reinstallation.
Cause 1 — .NET Misconfigured
.NET is installed but internally inconsistent. Fix: toggle it off and back on via Windows Features. Takes 5 minutes. Resolves most 1935 cases.
Cause 2 — Antivirus Blocking
Antivirus or security software blocks the installer from writing .NET assembly files. Fix: disable antivirus temporarily during installation, then re-enable.
Cause 3 — Third-Party Conflict
.NET is being used by another installation or background process. Fix: install QB in Selective Startup mode so no other apps are running during installation.
The .NET toggle — why it works: Windows stores .NET Framework as a Windows Feature that can be enabled/disabled. When disabled and then re-enabled, Windows runs a repair pass on the .NET installation — clearing corrupted registry entries, replacing missing assembly files, and rebuilding the component manifest. This is faster and less disruptive than a full .NET uninstall/reinstall, and it resolves the "assembly registration" failures that produce Error 1935 in most cases.
What Causes QuickBooks Error 1935?
Corrupted or Misconfigured .NET Framework
Primary cause — .NET Framework is installed but internally inconsistent. Assembly manifest files, registry keys, or component hashes are damaged. The QB installer attempts to register .NET assemblies during installation, encounters the corruption, and fails with Error 1935. The .NET toggle fix resolves this in most cases.
Antivirus Blocking Assembly Registration
Behaviour-based antivirus programs flag QB's installer writing .NET assembly files into the Windows Global Assembly Cache (GAC) as suspicious. The antivirus quarantines or blocks the write — QB's installer fails mid-assembly and reports 1935. Temporarily disabling antivirus during installation allows QB to complete the assembly registration uninterrupted.
Another Installation Using .NET
If Windows Update, another application installer, or a Windows component is simultaneously using .NET Framework files, QB's installer cannot get exclusive access to the assemblies it needs to install. This produces the "another installation is in progress" variant of Error 1935. Rebooting (to clear all pending installations) and installing in Selective Startup mode resolves this.
.NET Framework Not Installed or Outdated
On some Windows 11 configurations, .NET Framework 3.5 is disabled by default (it is built-in but not active). QB Desktop requires it to be enabled. Enabling .NET 3.5 via Windows Features resolves this immediately. Outdated .NET versions missing updates required by QB also produce Error 1935.
Outdated Windows OS
Windows updates deliver patches to the .NET Framework, Windows Installer service, and core component libraries. Without these updates, the underlying infrastructure QB's installer relies on may be outdated, causing 1935. Ensuring Windows is fully updated before attempting QB installation resolves this variant.
Corrupted Windows Registry
Corrupted registry entries related to .NET Framework or the Windows Installer cause the installation framework itself to fail during QB's setup. The Install Diagnostic Tool scans and repairs registry entries related to the components QB needs for installation.
How to Fix QuickBooks Error 1935
Start with Method 1 — restart and retry first (clears pending installations), then toggle .NET Framework. These two steps resolve most Error 1935 cases.
METHOD 1
Restart and Toggle the .NET Framework
Do this first — resolves most 1935 cases
1
Restart your computer first. This clears any pending Windows Updates, active installations, and locked .NET files from memory — resolving the "another installation in progress" variant.
2
Press Windows + R → type appwiz.cpl → Enter. In Programs and Features → click Turn Windows features on or off (left panel). Find Microsoft .NET Framework 3.5 (includes .NET 2.0 and 3.0). If checked → uncheck it → OK → restart. Then return and re-check it → OK → restart. This forces Windows to repair the .NET installation.
3
After restarting, retry the QB installation. In most cases Error 1935 is resolved after the toggle. If the box was already unchecked (as on some Windows 11 machines) — simply check it → OK → restart → retry QB installation. This enables the .NET 3.5 component QB requires.
METHOD 2
Disable Antivirus Temporarily During Installation
Antivirus blocking assembly registration
1
Temporarily disable your antivirus: right-click the antivirus system tray icon → Disable/Pause protection (choose "Until I restart" or a specific time period if available). Do not uninstall — just suspend real-time protection. Immediately retry the QB Desktop installation. Once QB installs successfully, re-enable antivirus protection. If antivirus was the cause, the installation completes without Error 1935. Add the QB installation folder (C:\Program Files\Intuit\QuickBooks [Year]) to your antivirus exclusion list to prevent future installation interference.
METHOD 3
Install QB in Selective Startup Mode
Third-party app or .NET conflict during installation
1
Press Windows + R → type msconfig → Enter. General tab: select Selective startup → check Load system services → uncheck Load startup items. Services tab: check Hide all Microsoft services → click Disable all → then check the Windows Installer checkbox. Click OK → Restart.
2
In Selective Startup mode, retry the QB Desktop installation. Only Windows components are running — no third-party apps that could interfere with .NET assembly registration. After QB installs successfully: msconfig → General → Normal startup → OK → Restart to return to normal mode.
METHOD 4
Run QB Install Diagnostic Tool
Automated repair of .NET and installer components
1
Open QuickBooks Tool Hub → Installation Issues tab → QuickBooks Install Diagnostic Tool. Close all other running programs. Let it run — up to 20 minutes. It automatically diagnoses and repairs .NET Framework, MSXML, and C++ Redistributable components. Restart when complete. Retry QB installation. The Install Diagnostic Tool addresses all three .NET error causes (misconfiguration, corruption, registry damage) in a single automated pass — making it ideal when the .NET toggle alone didn't resolve Error 1935.
METHOD 5
Update Windows + Repair/Reinstall .NET Framework
Outdated Windows or damaged .NET
1
Update Windows: Start → Settings → Windows Update → Check for updates → install all pending updates → restart. Repair .NET (if toggle failed): Programs and Features → find Microsoft .NET Framework [version] → Uninstall/Change → Repair → follow prompts → restart. Reinstall .NET (if repair fails): visit Microsoft's official .NET download page → download the installer for the required .NET version → install → restart. Also try the Microsoft .NET Framework Repair Tool (free download from Microsoft) — it specifically diagnoses and fixes .NET installation problems without requiring a full uninstall.
Quick Reference
| Your situation |
Likely cause |
Start with |
| First-time QB installation attempt |
.NET misconfigured or disabled |
Method 1 — restart + toggle .NET |
| Have antivirus or security suite installed |
Antivirus blocking assembly write |
Method 2 — disable antivirus during install |
| Windows was recently updated or other apps installing simultaneously |
.NET in use by another process |
Method 3 — Selective Startup install |
| All above tried — still getting 1935 |
Damaged .NET or Windows components |
Methods 4 + 5 — Install Diagnostic + .NET repair |
Frequently Asked Questions
Is Error 1935 a QuickBooks bug or a Windows problem?
Error 1935 is fundamentally a Windows component error, not a QB-specific bug. The error code 1935 is a Windows Installer error that occurs across many applications — not just QuickBooks. Norton antivirus, Alchemy Catalyst, Pinnacle Studio, AutoCAD, and various Microsoft Office products all produce Error 1935 under the same conditions (corrupted .NET Framework, antivirus interference, or concurrent installations). QuickBooks reports it because QB's installer relies on Windows Installer to register .NET assemblies, and Windows Installer encountered a failure in that process. The fix is always at the Windows component level, not QB-specific.
Why does toggling .NET Framework off and back on fix Error 1935?
When you disable .NET Framework via Windows Features, Windows marks all .NET component files as not-in-use and removes their Windows Features registration. When you re-enable it, Windows performs a fresh feature installation pass — re-copying component files from the Windows image (SxS cache), rebuilding the assembly manifest, clearing corrupted registry entries, and recalculating file hashes. This is essentially a targeted repair of the .NET Framework without needing to find and download an installer. It's effective because most Error 1935 cases are caused by minor corruption in the .NET component manifest or assembly cache — exactly what the toggle-repair fixes.
Can I install QB on Windows 11 if .NET Framework 3.5 is disabled?
Yes, but you need to enable .NET 3.5 first. On Windows 11, .NET Framework 3.5 (which includes .NET 2.0 and 3.0) is built into Windows but disabled by default. QB Desktop requires .NET 3.5 for specific components. To enable it: Windows + R → appwiz.cpl → Turn Windows features on or off → check the .NET Framework 3.5 box → OK. Windows may need your installation media or internet connection to download the required files. After enabling and restarting, QB installation proceeds without Error 1935. Note: .NET 3.5 and .NET 4.x (which handles most modern apps) can coexist on Windows — enabling 3.5 does not affect other applications.
Related QuickBooks Installation Errors
Still Getting Error 1935 After .NET Toggle and Install Diagnostic?
Let QuickFix Bookkeeping Get QB Installed.
Certified Intuit ProAdvisors — Installation Specialists
Persistent Error 1935 after .NET toggle, Install Diagnostic Tool, and Selective Startup install typically indicates deeper Windows component damage — corrupted SxS cache, damaged Windows image, or a group policy restricting assembly registration. Our ProAdvisors get QB installed in a single session.
Book a Free 30-Minute Consultation
No obligation. Same-day response. QB installed fast.
