An error occurred during the installation of assembly microsoft vc80 atl type win32

Hello,  I am asking this question because none of the answers I’ve read here have solved my problem. 

I use an HP Pavilion 64 bit computer with a Windows 7 operating system.  I recently purchased some video-editing software, which produced the following error message when I tried to install it: Error 1935 … microsoft.vc80.atl,type=»win32″,version=»8.50727.42″,publicKeyToken=»1fc8b3b9a1e18e3b»,processorArchitecture=»x86″

At the point when this happened, the installer was trying to access Microsoft Visual C++ 2005 Redistributable Package, which isn’t installed on my computer.  I tried to download and install the redistributable package.  But when I did, I received
the following error message:

Error 1935.An error occurred during the installation of assembly ‘Microsoft.VC80.ATL,type=»win32″,version=»8.0.50727.42″,publicKeyToken=»1fc8b3b9a1e18e3b»,processorArchitecture=»x86″‘. Please refer to Help and Support for more information.

Looking at the log-files, I see HRESULT: 0x80070002.

I have attempted to resolve this problem by:

1) rebooting, repeatedly;

2) running chkdsk for system errors;

3) uninstalling software that may possibly be blocking the installation;

4) temporarily disabling antivirus and anti-spyware software, and attempting installation;

5) and more steps which I can barely remember by now.

I’ve had this problem for over a week now, and every attempted solution either has no effect or simply discloses a further problem.  Can anyone help me understand what is causing this, and how I can solve it?

Kind regards,

Richard

Symptom:

While installing various Wasp software products on Windows 7 or Windows 8, during the installation of component Microsoft Visual C++ 2005 Redistributable, this error message appears, and the component will not install:

Error 1935. An error occurred during the installation of assembly (followed by something similar to the following)

* ‘Microsoft.VC80.ATL,type=»win32″,version=»8.0.50727.42″,publicKeyToken=»1fc8b3b9a1e18e3b»,processor Architecture=»x86″.

* ‘Microsoft.MSXML2,publicKeyToken=»6bd6b9abf345378f»,version=»4.20.9818.0″,type=»win3 2″,processor Architecture=»x86″.

Please refer to help and support for more information.

Cause:

The Microsoft component «Windows Modules Installer» service (TrustedInstaller.exe) is disabled. Note: This is not the only cause of this error.

Resolution:

Open Control Panel, Administrative Tools, Services.

Find and double-click Windows Modules Installer.

Change the Startup type to Manual.

OK.

The component should now install without error.

Additional Information:

* If this procedure does not solve the problem, it will be necessary to do a web search for other potential solutions. The error is due to a conflict among the Windows OS and the Microsoft Visual C++ component, and possibly other Windows components.

* When trying to start the Windows Trusted Installer service, if it gives error «Windows could not start the Windows Modules Installer service on Local Computer. Error 126: The specified module could not be found.», follow the steps in Microsoft KB article:

Error message when you start the Windows Modules Installer service (TrustedInstaller): «System Error 126: The specific module could not be found»

X

I am trying to install SQL server 2014 Express on a windows 7 PC for 2 days now. I re-installed then installed SQL Server 2014 several times but I keep getting the same window installer error message
I keep getting the following errors here’s the full log:

SQL Server Setup has encountered an error when running a Windows Installer file.

Windows Installer error message: An error occurred during the installation of assembly ‘Microsoft.VC80.ATL,version=»8.0.50727.6229″,publicKeyToken=»1fc8b3b9a1e18e3b»,processorArchitecture=»x86″,type=»win32″‘. Please refer to Help and Support for more information. HRESULT: 0x8007054F. Windows Installer file: C:UsersRecenoAppDataLocalTempSQL Server 2012Setup1033_ENU_LPx64setupsqlsupport_msiSqlSupport.msi Windows Installer log file: C:Program FilesMicrosoft SQL Server110Setup BootstrapLog20150109_213740SqlSupport_Cpu64_1_ComponentUpdate_1.log

Click ‘Retry’ to retry the failed action, or click ‘Cancel’ to cancel this action and continue setup.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xDC80C325

SYMPTOMS

After installing Genie Timeline (GTL) or Genie Backup Manager (GBM), you receive the following error in the Event Viewer:

“Error 1935. An error occurred during the installation of assembly ‘Microsoft.VC80.ATL, type=”win32″, version=”8.0.50727.4053″, publicKeyToken=”1fc8b3b9a1e18e3b”, processorArchitecture=”x86″‘. Please refer to Help and Support for more information”

Definition

A 1935 error is one of the most common problems that can prevent a user from being able to install any application that uses the Microsoft Windows Installer MSIAssembly and MSIAssemblyName tables to install assemblies. In general, this error means that Microsoft Windows Installer encountered an error while trying to install assemblies to the Global Assembly Cache (GAC) or the Win32 GAC (WinSxS). This error is considered fatal and causes setup to fail and initiate rollback.

The error can be caused by a variety of reasons:

• Another application deletes the file while our application tries to open this file.
• Some driver in the file system stack intercepts a CreateFile/ReadFile etc and translates the error code to “file not found” etc.

Solution

Solution 1: Clear the transaction log

If you receive a 1935 error, the Windows file system transaction log has become corrupted. The transaction log is used by the Windows file system to recover when a file error occurs. To correct this install error, you need to clear the log as follows:

1. From the Start menu, type cmd and you will see Command Prompt listed as the main result. Right-click that result and choose Run as administrator.
2. In the command prompt, type the following command and hit Enter:

   fsutil resource setautoreset true C:

   This assumes that C: is the drive in which Windows is installed. If it is installed on another drive like D:, please change the drive letter appropriately.

3. Restart your computer.
4. Install GTL or GBM again.

Solution 2: Disable antispyware and antivirus software or remove adware or spyware from your computer and then install GTL or GBM

1. Disable the following applications or types of applications, following any instructions provided by such software:
   • Disable Lavasoft Ad-Watch, Ad-Aware, or similar detection software before installation.
   • Disable WebRoot Spy Sweeper.
2. Install GBM or GTL again.

Solution 3: Remove adware and then install GBM or GTL

Error 1935 can be caused by a certain type of adware running on the system.

1. Start the Task Manager. (Alt + Ctrl + Delete)
2. Look for a process named wtoolsa.exe. If this process is running, then you will need to remove this adware.
3. Install GBM or GTL again.

Solution 4: Perform an installation repair of Windows

Your system might have some corruption that has gone undetected.

1. Re-install or repair your Windows.
2. Install GTL or GBM again.

Applies to: All GBM and GTL versions.

I got this gem of an error tonight while installing SQL Server 2014 Express (just trying to get the management studio mind you but having to install the whole package):

Error installing SQL Server Setup Support Files
An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80070BC9.
Error code: 1935

This error can occur for multiple reasons. One has an easy fix, one has more detailed fix.

Solution 1:

The first (and easiest to fix) is if you have a pending Windows Update reboot (one that auto-installed but hasn’t rebooted yet).  This is the easy fix, reboot and let Windows Update finish updating.  After the reboot you should be able to continue your install. I assume something in the Windows Update conflicted with the SQL Server install.

Solution 2:

This can also apparantly occur if the Microsoft.VC80.ATL file becomes corrupted. If this is the case you’ll have to repair the installation
Follow the steps in this blog over at MSDN:

• http://blogs.msdn.com/b/sqlserverfaq/archive/2010/04/23/sql-server-2005-setup-fails-on-windows-2008-due-to-corrupt-vc-component.aspx

For posterity, here are the steps.

1. Go to Start, Run and type in INSTALLER ad press Enter (this should pull up the installer folder).
2. Arrange the window in Details view.
3. Right click the header and click add columns.
4. Check the checkbox for Comments column.
5. In the comments column, look for Microsoft Visual C++ 2005 redistributable RTL.
6. Right click the msi and click Repair the VC++ 2005 redistributable.
7. The repair process will look for vcredist.msi in the temp folder and most probably it will not find it there and prompt to provide location for the same file.
8. Downloaded the VC++ 2005 redistributable from: http://www.microsoft.com/downloads/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee&displaylang=en
9. We need to extracted the exe using the following commands at command prompt:

C:vcredist_x86.exe /C
C:"VCREDI~1.EXE" /C

1. After running the above steps, we get the vcredist.msi extracted.
2. Provide the location for vcredist.msi for prompt in Step7.
3. Once the repair is complete, start the SQL Setup and this should help installing SQL Server successfully

Problem

How do you resolve the Windows install error 1935?

Resolving The Problem

• Restart your computer.

  -or-

• Stop, then restart the Windows Installer (msiservice) and try the installation again.

To stop Windows Installer, follow these steps:
1. Open Control Panel.
2. Double-click Administrative Tools.
3. Double-click Services.
4. Right-click the Windows Installer service.
5. Click Stop.
6. Click Start.

If you are still unable to resolve the 1935 error after either of the above two methods, gather the following documents and contact IBM Support for further assistance:

1. Microsoft Support Diagnostic Tool (

http://support.microsoft.com/kb/926079

)
2. MSI Verbose logging (

http://support.microsoft.com/kb/223300

)
3. Process Monitor Logs (

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

)

The following is a list of possible HRESULT values and their meanings.