Accounting Professionals

Accounting Professionals
Accounting Troubleshooting

Tuesday, October 21, 2025

Getting QuickBooks Error 1935

Comprehensive Guide to Resolving QuickBooks Error 1935


Understanding 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:

  1. .NET Framework Installation Issues:

    • Corrupted .NET Framework installation

    • Incomplete .NET Framework updates

    • Version conflicts between .NET Framework versions

    • Registry corruption affecting .NET components

  2. Windows Installer Service Problems:

    • Windows Installer service not running properly

    • Corrupted Windows Installer cache

    • Insufficient permissions for Windows Installer

  3. Security Software Interference:

    • Antivirus/antimalware blocking installation

    • Firewall preventing component registration

    • Real-time scanning interfering with file operations

  4. System File Corruption:

    • Damaged system files affecting installation

    • Disk errors preventing proper file writing

    • Corrupted Windows update components

  5. Conflicting Applications:

    • Other applications using .NET Framework during installation

    • Background processes interfering with installation

    • Previous QuickBooks installations leaving residual files

  6. 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

text
1. Save all work and close all applications
2. Perform a complete restart (not shutdown/sleep)
3. Attempt installation again after restart

Step B: Check Windows Updates

text
1. Settings → Update & Security → Windows Update
2. Check for updates → Install all available updates
3. Restart if updates are installed

Step C: Microsoft .NET Framework Repair Tool

  1. Download: Microsoft .NET Framework Repair Tool from Microsoft

  2. Run as Administrator: Execute the tool with admin rights

  3. Follow Automated Repair: Allow tool to detect and fix issues

  4. Restart Computer: Complete the repair process

3. Create System Restore Point:

text
1. Press Windows + R, type "sysdm.cpl"
2. System Protection tab → Create
3. 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

  1. Open Run Dialog:

    • Press Windows + R keys simultaneously

    • Type msconfig in the text box

    • Press Enter or click OK

  2. Configure General Settings:

    • Select the General tab

    • Choose Selective startup

    • Check Load system services

    • Uncheck Load startup items

Step B: Service Configuration

  1. Navigate to the Services tab

  2. Check Hide all Microsoft services (important)

  3. Click Disable all

  4. Uncheck Hide all Microsoft services

  5. Scroll to find Windows Installer

  6. Ensure Windows Installer is checked (enabled)

  7. Click Apply → OK

Step C: Restart and Install

  1. Click Restart when prompted

  2. After restart, log in as Administrator

  3. Attempt QuickBooks installation

  4. Note if error persists

Solution 2: Restore Normal Startup Mode

After successful installation, return to normal operation:

Procedure:

  1. Open System Configuration:

    • Windows + R → msconfig → Enter

  2. Restore Normal Settings:

    • General tab → Normal startup

    • Click Apply → OK

  3. 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:

text
1. Windows Security → Virus & threat protection
2. Manage settings → Real-time protection → Off
3. Attempt installation
4. Re-enable immediately after installation

For Third-Party Antivirus:

  1. System Tray Method:

    • Right-click antivirus icon in system tray

    • Select "Disable," "Turn off," or similar

    • Choose time period (15-30 minutes)

  2. Application Interface Method:

    • Open antivirus application

    • Navigate to settings/protection

    • Disable real-time scanning

    • Add QuickBooks to exclusion list

Permanent Exclusion Method (Recommended):

text
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

  1. Download Latest Version:

    • Visit Intuit's official QuickBooks support site

    • Search for "QuickBooks Tool Hub"

    • Download version 1.6.0.3 or newer

  2. Installation Process:

    • Close all QuickBooks processes

    • Run QuickBooksToolHub.exe as Administrator

    • Accept license agreement

    • Complete installation wizard

Step B: Diagnostic Tool Execution

  1. Launch Tool Hub as Administrator

  2. Navigate to: Installation Issues tab

  3. Select: "QuickBooks Install Diagnostic Tool"

  4. Tool Actions:

    text
    Phase 1: Component Analysis
    - .NET Framework health check
    - MSXML component verification
    - Visual C++ redistributable validation

    Phase 2: Windows Services Check - Windows Installer service verification - Background process analysis - Permission audit Phase 3: Automated Repair - Component registration repair - Cache clearing
    - Registry fix application
  5. Duration: 15-30 minutes

  6. Restart Required: Always restart after completion

Step C: Post-Repair Verification

  1. Test Installation: Attempt QuickBooks installation

  2. Monitor Logs: Check Tool Hub logs for details

  3. 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

text
1. Control Panel → Programs → Programs and Features
2. Turn Windows features on or off
3. Uncheck all .NET Framework versions
4. Restart computer
5. Repeat Step 3, re-enable .NET Framework
6. Restart again

Step B: Clean .NET Framework Installation

  1. Download .NET Framework Cleanup Tool (from Microsoft)

  2. Run as Administrator: Remove all .NET Framework versions

  3. Restart Computer

  4. Install .NET Framework 3.5 and 4.8 (from Microsoft website)

  5. Restart Computer

Command Line Repair:

text
Command Prompt (Admin):
1. net stop wuauserv
2. net stop cryptSvc
3. net stop bits
4. net stop msiserver
5. ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
6. ren C:\Windows\System32\catroot2 catroot2.old
7. net start wuauserv
8. net start cryptSvc
9. net start bits
10. net start msiserver

Solution 6: Windows Installer Service Repair

When Windows Installer is corrupted:

Service Reset Procedure:

  1. Stop Windows Installer Service:

    text
    Command Prompt (Admin):
    net stop msiserver
  2. Clear Installer Cache:

    text
    Delete folder: C:\Windows\Installer (temporary - backup if needed)
    Delete files: C:\Windows\%temp%\*
  3. Reregister Windows Installer:

    text
    Command Prompt (Admin):
    msiexec /unregister
    msiexec /regserver
  4. Reset Service Permissions:

    text
    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

  1. msconfig → Services tab

  2. Check "Hide all Microsoft services"

  3. Click "Disable all"

  4. Startup tab → Open Task Manager

  5. Disable all startup items

Step B: Service-Specific Management

  1. Services.msc → Windows Installer properties

  2. Set Startup type: Automatic

  3. Recovery tab: Set all failures to "Restart the Service"

  4. Log On tab: Ensure Local System account

Step C: Installation Attempt

  1. Restart in Clean Boot state

  2. Attempt QuickBooks installation

  3. Monitor for error 1935


Advanced Troubleshooting Techniques

Registry Repair (Advanced Users Only):

Critical Registry Keys:

text
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer

Repair Procedure:

  1. Backup Registry First: regedit → File → Export

  2. Permission Reset:

    text
    Command Prompt (Admin):
    secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose
  3. Component Registration:

    text
    Command Prompt (Admin):
    regsvr32 /s msxml3.dll
    regsvr32 /s msxml6.dll

Disk and File System Repair:

Comprehensive System Check:

text
Command Prompt (Admin):
1. chkdsk C: /f /r
2. sfc /scannow
3. DISM /Online /Cleanup-Image /RestoreHealth
4. Restart after each command completes

Group Policy and Security Settings:

For Domain/Enterprise Environments:

  1. Check Software Restriction Policies

  2. Verify AppLocker settings

  3. Review Windows Defender Application Control

  4. Test with local administrator account


Preventive Measures and Best Practices

Regular Maintenance Schedule:

Before Installation:

  1. Disk Cleanup: Remove temporary files

  2. Update Windows: Install all critical updates

  3. Antivirus Scan: Ensure system is clean

  4. Backup Creation: System and data backup

During Installation:

  1. Close All Applications: Especially resource-intensive ones

  2. Disable Non-Essential Services: Temporarily

  3. Monitor Installation: Don't run other installations simultaneously

After Installation:

  1. Create System Restore Point

  2. Test QuickBooks Functionality

  3. Re-enable Security Software

  4. Update QuickBooks to Latest Release

Configuration Best Practices:

  1. User Account Control:

    • Set to appropriate level (not too restrictive)

    • Use administrator account for installation

    • Document permission requirements

  2. Windows Services Configuration:

    • Ensure Windows Installer service is enabled

    • Configure proper service recovery options

    • Monitor service health regularly

  3. .NET Framework Management:

    • Keep .NET Framework updated

    • Regular health checks

    • Clean installation practices

Documentation and Planning:

  1. Installation Logs:

    • Maintain installation logs

    • Document error patterns

    • Create troubleshooting guides

  2. 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?

A: Technical Definition:
QuickBooks Error 1935 is a Windows Installer error code indicating failure during assembly installation, particularly Microsoft .NET Framework components. The error occurs when:

  • 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:

  1. Fresh QuickBooks Installation:

    • Missing .NET Framework prerequisites

    • Corrupted installation media

    • Insufficient system permissions

  2. QuickBooks Repair/Update:

    • Damaged existing installation

    • Version conflicts

    • Registry corruption

  3. System Changes:

    • Windows updates affecting .NET Framework

    • Antivirus software updates

    • System restore operations

Component-Specific Issues:

  1. Microsoft.VC90.ATL assembly failures

  2. .NET Framework 3.5/4.8 installation issues

  3. Windows Installer service disruptions

Q: How can I prevent Error 1935?

A: Comprehensive Prevention Strategy:

Technical Measures:

  1. Regular System Maintenance:

    • Monthly disk cleanup

    • Quarterly .NET Framework verification

    • Biannual system optimization

  2. Update Management:

    • Stagger Windows updates

    • Test QuickBooks updates in staging

    • Monitor compatibility reports

Procedural Measures:

  1. Installation Protocols:

    • Standardized installation procedures

    • Pre-installation checklists

    • Post-installation verification

  2. 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:

text
Event Viewer → Windows Logs → Application
Filter for: Source = "MsiInstaller", Event ID 1935

QuickBooks Installation Logs:

text
%temp% folder → QuickBooks installation logs
C:\ProgramData\Intuit\QuickBooks\log

Windows Installer Logging:

text
Registry: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Value: Logging → Voicewarmup (verbose logging)

Quick Reference: Solution Selection Matrix

Symptom PatternFirst SolutionSecondary SolutionExpert Solution
Fresh installation failsSelective Startup.NET Framework repairClean system rebuild
After Windows updateWindows Update rollbackSystem restoreComponent reinstallation
Antivirus interferenceTemporary disableExclusion configurationSecurity software audit
Multiple .NET errorsInstall Diagnostic ToolManual .NET reinstallSystem refresh
Enterprise environmentGroup policy checkLocal admin testProfessional deployment

Emergency Response Protocol

If critical accounting functions are blocked:

Immediate Actions:

  1. Communicate: Notify affected users immediately

  2. Document: Record exact error details and timing

  3. Workaround: Use alternative accounting methods if available

  4. Escalate: Contact support within first hour of failure

Priority Restoration:

  1. Critical Functions First: Payroll, invoicing, tax compliance

  2. Data Access: Company file backup verification

  3. 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):

text
1. Installation Verification:
- QuickBooks launch (multiple attempts)
- Company file opening
- Feature accessibility testing

2. 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

QuickBooks Error 6069

  Guide to Resolving QuickBooks Error 6069 Introduction QuickBooks Error 6069 is a versatile and disruptive issue that can surface unexpecte...