QuickBooks Payroll Setup Files Are Corrupted: Causes, Fixes & Prevention Guide (2025)
Fix QuickBooks Error 1935 fast — learn causes, step-by-step fixes (Tool Hub, .NET repair, selective startup) and FAQs to get back to work.
Image title: QuickBooks Error 1935 Fix
Image alt: Computer screen showing QuickBooks Error 1935 with .NET Framework icon
If QuickBooks throws Error 1935 during installation or updates, it usually means Windows components (most often the Microsoft .NET Framework) are missing, damaged, or blocked by another program. The quickest reliable fixes: run the QuickBooks Install Diagnostic Tool from the Tool Hub, update Windows, temporarily disable antivirus, and if needed repair or reinstall .NET and MSXML. Official Intuit guidance and Microsoft troubleshooting steps are the safest route. (Sources: QuickBooks Tool Hub & .NET repair docs)
Error 1935 is a Windows installer error that appears when Windows can’t install or configure a required assembly (a packaged component) — typically during the installation of applications that depend on the .NET Framework. For QuickBooks, Error 1935 commonly appears with messages such as “This setup requires .NET Framework” or “An error occurred during the installation of the assembly.” The root causes include damaged .NET files, Windows updates pending, or third-party software blocking the install.
Important: Back up your data and close other programs before you start. If you’re on a company-managed PC, check with IT before disabling security software or making system changes.
This tool automates common fixes (including .NET repair) and is Intuit’s recommended first step.
Run Windows Update: install all pending updates, reboot, then retry. Many .NET problems are resolved by Windows updates. Make sure Windows Modules Installer is enabled (services.msc → Windows Modules Installer).
Temporarily turn off real-time protection or third-party antivirus (disconnect when doing so). Re-run the installer. If it works, re-enable protection immediately after installation. (Do not leave antivirus off permanently.)
Use Microsoft’s .NET Repair Tool or Windows Features (Turn Windows features on or off) to enable/repair .NET 3.5 and .NET 4.x as required. If automatic repair fails, manually uninstall and reinstall the .NET Framework versions needed by your QuickBooks version.
QuickBooks also uses MSXML. Use Programs & Features → Turn Windows features on/off or download MSXML fixes from Microsoft and repair/reinstall. Intuit lists MSXML repair as a manual step if diagnostic tools don’t help.
Use msconfig → Selective Startup (uncheck Load startup items, keep Windows services) and disable non-Microsoft services temporarily. Reboot and install QuickBooks. After a successful install, revert to normal startup. This removes third-party interference during install.
If nothing works, uninstall QuickBooks, clean remaining QuickBooks folders/registry entries (careful: back up!), repair or reinstall .NET, then reinstall QuickBooks. If you're not comfortable editing the registry, get IT or Microsoft support help.
sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth
A: No — it’s an installer issue affecting program files or components, not usually your QuickBooks company data. Still, back up company files before troubleshooting to be safe.
A: No. Installing or repairing .NET and QuickBooks requires administrative privileges.
A: Running diagnostic tools may take 10–30 minutes; manual .NET repairs and Windows updates can take longer depending on downloads and restarts.
A: If you’re not comfortable repairing .NET, editing system services, or using msconfig/registry, ask IT or Microsoft support. These fixes touch core Windows components.
A: No—if you back up your company file first. Reinstallation affects program files, not your saved company data — but always create backups before major changes.
QuickBooks Error 1935 is annoying, but it's usually fixable with methodical steps: run the QuickBooks Install Diagnostic Tool, update Windows, temporarily disable antivirus, and repair or reinstall the Microsoft .NET Framework or MSXML when necessary. Start with the Tool Hub — it often solves the problem quickly — and move to manual repairs only if needed. If you’re unsure about registry or .NET changes, involve IT or Microsoft support; that avoids accidental system damage.
If you want, I can convert these steps into a printable checklist or a short script of commands to run (for Windows admin), but before that tell me whether you’re on Windows 10 or 11 and whether you have admin access — I’ll tailor the exact commands.
Comments
Post a Comment