Comprehensive Guide to Resolving QuickBooks Error 1935
QuickBooks Error 1935 is a Windows Installer error that occurs during the installation or repair of QuickBooks Desktop, typically related to Microsoft .NET Framework installation issues. The error manifests with messages such as:
"Error 1935: An error occurred during the installation of assembly""Error 1935: This setup requires .NET Framework""Error 1935: Assembly Microsoft.VC90.ATL, version='9.0.30729.xxxxx'"
This error is not exclusive to QuickBooks but affects various Windows applications, including Norton antivirus, AutoCAD, Pinnacle Studio, and even Microsoft's own applications. It indicates a failure in installing or registering critical Microsoft components required for QuickBooks to function properly.
Critical Impact:
Prevents QuickBooks installation or repair
Blocks access to accounting features
Disrupts business accounting operations
May affect other Windows applications
For immediate expert assistance with QuickBooks Error 1935, contact our certified specialists at +1.888.381.4670.
Root Causes of QuickBooks Error 1935
Understanding the underlying causes is essential for effective troubleshooting:
Primary Technical Causes:
.NET Framework Installation Issues:
Corrupted .NET Framework installation
Incomplete .NET Framework updates
Version conflicts between .NET Framework versions
Registry corruption affecting .NET components
Windows Installer Service Problems:
Windows Installer service not running properly
Corrupted Windows Installer cache
Insufficient permissions for Windows Installer
Security Software Interference:
Antivirus/antimalware blocking installation
Firewall preventing component registration
Real-time scanning interfering with file operations
System File Corruption:
Damaged system files affecting installation
Disk errors preventing proper file writing
Corrupted Windows update components
Conflicting Applications:
Other applications using .NET Framework during installation
Background processes interfering with installation
Previous QuickBooks installations leaving residual files
Permission and Account Issues:
Insufficient administrator privileges
User Account Control (UAC) restrictions
Folder permission conflicts
Common Scenarios Triggering Error 1935:
During fresh QuickBooks installation
When repairing QuickBooks installation
After Windows updates
During .NET Framework updates
When multiple applications are being installed simultaneously
Pre-Troubleshooting Preparation
Before attempting any fixes, complete these essential steps:
1. System Assessment:
Verify Windows version and edition
Check available disk space (minimum 2GB free)
Note exact error message and code
Document recent system changes
2. Basic Verification Steps:
Step A: Restart Your Computer
1. Save all work and close all applications2. Perform a complete restart (not shutdown/sleep)3. Attempt installation again after restart
Step B: Check Windows Updates
1. Settings → Update & Security → Windows Update2. Check for updates → Install all available updates3. Restart if updates are installed
Step C: Microsoft .NET Framework Repair Tool
Download: Microsoft .NET Framework Repair Tool from Microsoft
Run as Administrator: Execute the tool with admin rights
Follow Automated Repair: Allow tool to detect and fix issues
Restart Computer: Complete the repair process
3. Create System Restore Point:
1. Press Windows + R, type "sysdm.cpl"2. System Protection tab → Create3. Name: "Pre-QuickBooks Error 1935 Fix"4. Click Create → OK
Comprehensive Solutions for QuickBooks Error 1935
Solution 1: Selective Startup Mode Activation
When to use: When background applications interfere with installation
Detailed Implementation:
Step A: Access System Configuration
Open Run Dialog:
Press
Windows + Rkeys simultaneouslyType
msconfigin the text boxPress
Enteror clickOK
Configure General Settings:
Select the General tab
Choose Selective startup
Check Load system services
Uncheck Load startup items
Step B: Service Configuration
Navigate to the Services tab
Check Hide all Microsoft services (important)
Click Disable all
Uncheck Hide all Microsoft services
Scroll to find Windows Installer
Ensure Windows Installer is checked (enabled)
Click Apply → OK
Step C: Restart and Install
Click Restart when prompted
After restart, log in as Administrator
Attempt QuickBooks installation
Note if error persists
Solution 2: Restore Normal Startup Mode
After successful installation, return to normal operation:
Procedure:
Open System Configuration:
Windows + R→msconfig→Enter
Restore Normal Settings:
General tab → Normal startup
Click Apply → OK
Restart Computer:
Click Restart when prompted
Verify all services and applications load normally
Solution 3: Antivirus and Security Software Management
When security software blocks installation:
Temporary Disable Method:
For Windows Defender:
1. Windows Security → Virus & threat protection2. Manage settings → Real-time protection → Off3. Attempt installation4. Re-enable immediately after installation
For Third-Party Antivirus:
System Tray Method:
Right-click antivirus icon in system tray
Select "Disable," "Turn off," or similar
Choose time period (15-30 minutes)
Application Interface Method:
Open antivirus application
Navigate to settings/protection
Disable real-time scanning
Add QuickBooks to exclusion list
Permanent Exclusion Method (Recommended):
Add to Exclusion List:- C:\Program Files (x86)\Intuit\- C:\ProgramData\Intuit\- C:\Windows\Installer\ (temporary during installation)- QuickBooks installation .exe file
Solution 4: QuickBooks Install Diagnostic Tool
When .NET Framework or component issues are suspected:
Comprehensive Tool Execution:
Step A: QuickBooks Tool Hub Installation
Download Latest Version:
Visit Intuit's official QuickBooks support site
Search for "QuickBooks Tool Hub"
Download version 1.6.0.3 or newer
Installation Process:
Close all QuickBooks processes
Run
QuickBooksToolHub.exeas AdministratorAccept license agreement
Complete installation wizard
Step B: Diagnostic Tool Execution
Launch Tool Hub as Administrator
Navigate to: Installation Issues tab
Select: "QuickBooks Install Diagnostic Tool"
Tool Actions:
Phase 1: Component Analysis- .NET Framework health check- MSXML component verification- Visual C++ redistributable validationPhase 2: Windows Services Check - Windows Installer service verification - Background process analysis - Permission audit Phase 3: Automated Repair - Component registration repair - Cache clearing- Registry fix applicationDuration: 15-30 minutes
Restart Required: Always restart after completion
Step C: Post-Repair Verification
Test Installation: Attempt QuickBooks installation
Monitor Logs: Check Tool Hub logs for details
Verify .NET Framework: Ensure proper installation
Solution 5: Advanced .NET Framework Repair
When standard repairs fail:
Manual .NET Framework Reinstallation:
Step A: Complete .NET Framework Removal
1. Control Panel → Programs → Programs and Features2. Turn Windows features on or off3. Uncheck all .NET Framework versions4. Restart computer5. Repeat Step 3, re-enable .NET Framework6. Restart again
Step B: Clean .NET Framework Installation
Download .NET Framework Cleanup Tool (from Microsoft)
Run as Administrator: Remove all .NET Framework versions
Restart Computer
Install .NET Framework 3.5 and 4.8 (from Microsoft website)
Restart Computer
Command Line Repair:
Command Prompt (Admin):1. net stop wuauserv2. net stop cryptSvc3. net stop bits4. net stop msiserver5. ren C:\Windows\SoftwareDistribution SoftwareDistribution.old6. ren C:\Windows\System32\catroot2 catroot2.old7. net start wuauserv8. net start cryptSvc9. net start bits10. net start msiserver
Solution 6: Windows Installer Service Repair
When Windows Installer is corrupted:
Service Reset Procedure:
Stop Windows Installer Service:
Command Prompt (Admin):net stop msiserverClear Installer Cache:
Delete folder: C:\Windows\Installer (temporary - backup if needed)Delete files: C:\Windows\%temp%\*Reregister Windows Installer:
Command Prompt (Admin):msiexec /unregistermsiexec /regserverReset Service Permissions:
Command Prompt (Admin):sc.exe sdset msiserver D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;IU)(A;;CCLCSWLOCRRC;;;SU)
Solution 7: Clean Boot with Advanced Configuration
For persistent interference issues:
Advanced Clean Boot Procedure:
Step A: System Configuration Deep Clean
msconfig→ Services tabCheck "Hide all Microsoft services"
Click "Disable all"
Startup tab → Open Task Manager
Disable all startup items
Step B: Service-Specific Management
Services.msc → Windows Installer properties
Set Startup type: Automatic
Recovery tab: Set all failures to "Restart the Service"
Log On tab: Ensure Local System account
Step C: Installation Attempt
Restart in Clean Boot state
Attempt QuickBooks installation
Monitor for error 1935
Advanced Troubleshooting Techniques
Registry Repair (Advanced Users Only):
Critical Registry Keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFrameworkHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\InstallerHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer
Repair Procedure:
Backup Registry First:
regedit → File → ExportPermission Reset:
Command Prompt (Admin):secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verboseComponent Registration:
Command Prompt (Admin):regsvr32 /s msxml3.dllregsvr32 /s msxml6.dll
Disk and File System Repair:
Comprehensive System Check:
Command Prompt (Admin):1. chkdsk C: /f /r2. sfc /scannow3. DISM /Online /Cleanup-Image /RestoreHealth4. Restart after each command completes
Group Policy and Security Settings:
For Domain/Enterprise Environments:
Check Software Restriction Policies
Verify AppLocker settings
Review Windows Defender Application Control
Test with local administrator account
Preventive Measures and Best Practices
Regular Maintenance Schedule:
Before Installation:
Disk Cleanup: Remove temporary files
Update Windows: Install all critical updates
Antivirus Scan: Ensure system is clean
Backup Creation: System and data backup
During Installation:
Close All Applications: Especially resource-intensive ones
Disable Non-Essential Services: Temporarily
Monitor Installation: Don't run other installations simultaneously
After Installation:
Create System Restore Point
Test QuickBooks Functionality
Re-enable Security Software
Update QuickBooks to Latest Release
Configuration Best Practices:
User Account Control:
Set to appropriate level (not too restrictive)
Use administrator account for installation
Document permission requirements
Windows Services Configuration:
Ensure Windows Installer service is enabled
Configure proper service recovery options
Monitor service health regularly
.NET Framework Management:
Keep .NET Framework updated
Regular health checks
Clean installation practices
Documentation and Planning:
Installation Logs:
Maintain installation logs
Document error patterns
Create troubleshooting guides
Recovery Planning:
Regular system image backups
QuickBooks data backup schedule
Disaster recovery procedures
When to Seek Professional Assistance
Contact +1.888.381.4670 immediately if:
Critical Indicators:
Multiple solution attempts fail
Business operations are disrupted
Data integrity concerns exist
Complex network environment
Time-sensitive requirements
Our Expert Services Include:
Remote Diagnostics: Advanced system analysis
Component Recovery: Complex .NET Framework issues
Installation Optimization: Enterprise deployment
Performance Tuning: System optimization
Preventive Planning: Custom maintenance protocols
Frequently Asked Questions (Expanded)
Q: What exactly is QuickBooks Error 1935?
Windows Installer cannot register assemblies
.NET Framework installation is corrupted
System permissions prevent component registration
Conflicting applications interfere with installation
Q: What are common instances triggering Error 1935?
A: Detailed Scenario Analysis:
Installation Scenarios:
Fresh QuickBooks Installation:
Missing .NET Framework prerequisites
Corrupted installation media
Insufficient system permissions
QuickBooks Repair/Update:
Damaged existing installation
Version conflicts
Registry corruption
System Changes:
Windows updates affecting .NET Framework
Antivirus software updates
System restore operations
Component-Specific Issues:
Microsoft.VC90.ATL assembly failures
.NET Framework 3.5/4.8 installation issues
Windows Installer service disruptions
Q: How can I prevent Error 1935?
A: Comprehensive Prevention Strategy:
Technical Measures:
Regular System Maintenance:
Monthly disk cleanup
Quarterly .NET Framework verification
Biannual system optimization
Update Management:
Stagger Windows updates
Test QuickBooks updates in staging
Monitor compatibility reports
Procedural Measures:
Installation Protocols:
Standardized installation procedures
Pre-installation checklists
Post-installation verification
Training and Documentation:
IT staff training on QuickBooks installation
User education on system maintenance
Emergency procedure documentation
Q: Can Error 1935 affect other applications?
A: Cross-Application Impact Analysis:
Yes, Error 1935 affects any application requiring .NET Framework
Commonly affected: Microsoft Office, Adobe applications, development tools
Prevention: System-wide .NET Framework health maintenance
Q: What logging should I enable for troubleshooting?
A: Comprehensive Logging Strategy:
Windows Event Logs:
Event Viewer → Windows Logs → ApplicationFilter for: Source = "MsiInstaller", Event ID 1935
QuickBooks Installation Logs:
%temp% folder → QuickBooks installation logsC:\ProgramData\Intuit\QuickBooks\log
Windows Installer Logging:
Registry: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\InstallerValue: Logging → Voicewarmup (verbose logging)
Quick Reference: Solution Selection Matrix
| Symptom Pattern | First Solution | Secondary Solution | Expert Solution |
|---|---|---|---|
| Fresh installation fails | Selective Startup | .NET Framework repair | Clean system rebuild |
| After Windows update | Windows Update rollback | System restore | Component reinstallation |
| Antivirus interference | Temporary disable | Exclusion configuration | Security software audit |
| Multiple .NET errors | Install Diagnostic Tool | Manual .NET reinstall | System refresh |
| Enterprise environment | Group policy check | Local admin test | Professional deployment |
Emergency Response Protocol
If critical accounting functions are blocked:
Immediate Actions:
Communicate: Notify affected users immediately
Document: Record exact error details and timing
Workaround: Use alternative accounting methods if available
Escalate: Contact support within first hour of failure
Priority Restoration:
Critical Functions First: Payroll, invoicing, tax compliance
Data Access: Company file backup verification
Full Restoration: Complete functionality verification
Communication Plan:
Hourly updates to stakeholders
Clear timeline expectations
Alternative workflow instructions
Important: Never bypass installation errors or use unauthorized workarounds that could compromise system stability or data integrity.
Post-Resolution Verification Protocol
After successful error resolution:
Immediate Testing (24 Hours):
1. Installation Verification:- QuickBooks launch (multiple attempts)- Company file opening- Feature accessibility testing2. System Stability: - Windows Event Log monitoring - .NET Framework health checks - Application compatibility testing 3. Performance Benchmarking: - Installation time measurements - Application launch times- System resource monitoring
Extended Monitoring (7 Days):
Daily QuickBooks launch testing
Error log review
User feedback collection
System performance tracking
Preventive Implementation:
Schedule regular maintenance
Implement monitoring tools
Update installation documentation
Train staff on error recognition

No comments:
Post a Comment