How to Fix Error 1935 (Windows Installer)
Quick Answer
Error 1935 indicates an issue with the Windows Installer attempting to install a specific assembly component, often due to conflicts with other programs, system file corruption, or insufficient permissions. The fastest fix often involves temporarily disabling antivirus software or running the installer as an administrator.
What Causes This Error
- Conflicting software, particularly antivirus or security programs, interfering with the installation process.
- Corrupted or missing system files, specifically those related to the .NET Framework or Windows Installer.
- Insufficient user permissions to write to necessary system directories or registry keys.
- Issues with the Microsoft .NET Framework installation itself, which is required by many applications.
- Problems with the Windows Modules Installer service or its associated components.
- A previous failed installation or uninstallation leaving behind corrupted registry entries or files.
Step-by-Step Fixes
1Run Installer as Administrator
- Locate the installer executable file for the application you are trying to install.
- Right-click on the installer executable file.
- Select 'Run as administrator' from the context menu.
- Proceed with the installation process and observe if Error 1935 reoccurs.
2Temporarily Disable Antivirus Software
- Locate your antivirus software icon in the system tray (usually near the clock on the taskbar).
- Right-click on the antivirus icon and look for options like 'Disable protection', 'Pause protection', or 'Exit'.
- Select the option to temporarily disable or pause real-time protection. Note that the exact steps vary by antivirus program.
- Attempt to run the application installer again.
- After the installation is complete, remember to re-enable your antivirus software immediately to maintain system security.
3Repair or Reinstall Microsoft .NET Framework
- Open 'Control Panel' by searching for it in the Windows search bar.
- Navigate to 'Programs' > 'Programs and Features' or 'Uninstall a program'.
- Locate all installed versions of Microsoft .NET Framework in the list.
- For each .NET Framework entry, select it and choose 'Change' or 'Repair' if available, then follow the on-screen prompts.
- If repair is not an option or does not resolve the issue, consider uninstalling and then reinstalling the specific .NET Framework version required by the application, or use the Microsoft .NET Framework Repair Tool.
4Check and Repair System Files (SFC Scan)
- Open Command Prompt as an administrator: Search for 'cmd' in the Windows search bar, right-click 'Command Prompt', and select 'Run as administrator'.
- In the Command Prompt window, type 'sfc /scannow' and press Enter.
- Allow the System File Checker to complete its scan. This process may take some time.
- Review the scan results. If corrupted files were found and repaired, restart your computer.
- Attempt the installation again after the system restart.
Advanced Fixes
Reset Windows Installer Service
- Open the Services management console: Press 'Windows key + R', type 'services.msc', and press Enter.
- Scroll down and locate the 'Windows Installer' service.
- Right-click on 'Windows Installer' and select 'Restart'. If 'Restart' is greyed out, select 'Stop' first, then 'Start'.
- Ensure the 'Startup type' for 'Windows Installer' is set to 'Manual'. If not, double-click the service, change the 'Startup type' to 'Manual', click 'Apply', then 'OK'.
- Attempt the application installation again.
Perform a Clean Boot
- Open the System Configuration utility: Press 'Windows key + R', type 'msconfig', and press Enter.
- Go to the 'Services' tab. Check the box 'Hide all Microsoft services'.
- Click 'Disable all'.
- Go to the 'Startup' tab and click 'Open Task Manager'.
- In Task Manager, disable all startup items individually.
- Close Task Manager, click 'OK' in System Configuration, and restart your computer.
- Attempt the application installation. If successful, re-enable services and startup items incrementally to identify the conflict.
- After troubleshooting, remember to return your system to a normal startup by reversing these steps in System Configuration.
Frequently Asked Questions
What does 'HRESULT: 0x80070005' mean in Error 1935?
The 'HRESULT: 0x80070005' part of Error 1935 specifically indicates 'Access is denied'. This typically means the installer lacks the necessary permissions to write to a file, folder, or registry key during the installation process.
Is Error 1935 specific to certain applications?
Error 1935 is not specific to a single application. It is a general Windows Installer error that can occur when installing various software, especially those that rely heavily on the Microsoft .NET Framework or interact with core system components.
Can Windows Update cause Error 1935?
Yes, sometimes an incomplete or corrupted Windows Update, particularly one that affects .NET Framework components or system files, can lead to Error 1935 during subsequent software installations. Ensuring all Windows Updates are successfully installed can sometimes resolve underlying issues.
What is an 'assembly component' in the context of Error 1935?
An 'assembly component' refers to a fundamental building block of an application, often a DLL (Dynamic Link Library) or EXE (Executable) file, particularly within the Microsoft .NET Framework environment. Error 1935 indicates a failure to properly install or register one of these essential components.