none
Error 1935.An error occurred during the installation of assembly 'Microsoft.VC90.ATL or 'Microsoft.VC80.ATL'

    Question

  • The OS is Windows Server 2008 R2

    I can't install any programs (like backup agents) that require these components: 

    Microsoft Visual C++ 2005 SP1 Redistributable Package (x64) or the
    Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)
    I've tried unregistering the Windows Installer and reregistering it, starting from a clean boot scenario,
    This is the error message:

    Product: Microsoft Visual C++ 2005 Redistributable (x64) -- Error 1935.An error occurred during the installation of assembly 'Microsoft.VC80.ATL,type="win32",version="8.0.50727.762",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64"'. Please refer to Help and Support for more information. HRESULT: 0x80070BC9. assembly interface: IAssemblyCacheItem, function: Commit, component: {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E}

    Seems like there are thousands of entries when you google this error but not too many solutions.

    The only microsoft support KB entry that deals with this error only is for Windows 7, so the Fix It tool can't be run:

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

    Monday, December 13, 2010 7:52 PM

Answers

  • Martin, you are no longer getting an Redistributable install error message, which means that most of the suggestions in these postings won't work for you. From the messages you are getting, I'm guessing SQL won't install because it still has leftover components from the last time you installed it. See this posting for Tao-Min Tan's fix for that:

    http://social.msdn.microsoft.com/Forums/en/sqlsetupandupgrade/thread/62f0cd6b-bf78-46e0-b513-1556c0866241

    On the 1935 error I've been receiving:

    I would not recommend using the .NET framework removal tool on Windows 2008 R2, although that is not a step I tried. Depending on what kind of server it is, you might have components that won't work correctly after the removal and reinstall. (SharePoint and SQL are two that come to mind).

    If you are getting this 1935 error, and the simple fixes mentioned in earlier postings don't work, I recommend reinstalling Windows from scratch on that server. I found out the hard way it isn't worth troubleshooting. I hate to advocate a reinstall rather than getting to the root of the problem, but if you want the C++ redistributable on there and you don't want to mess up your programs or Windows, this seems to be the way to go. The error stems from missing files in the WinSXS folder--although who knows how that happens--I have two identical servers and it happened on only one of them.

    Once Windows is installed with any updates available, install the Microsoft Visual C++ 2005 SP1 Redistributable Package (x64) and the Microsoft Visual C++ 2008 SP1 Redistributable Package (x64) right away. Then do whatever you have to do to get your software/services running again.

    Microsoft walked me through finding what files were missing from the WinSXS folder and tried installing those files on the machine with the issue. That didn't work (and consisted of a lot of finding GUIDS, and copying and pasting files..painful). Then they said let's try an inplace upgrade of windows (said it wouldn't affect SharePoint or IIS) and it killed SharePoint--and Windows had poor performance. I rolled back any changes. So, I don't have time to troubleshoot it anymore, I'm building a new server (and I don't want a server that's had the in place upgrade run on it anyway, even if I could get IIS and SharePoint to work). This error has been around since 2001 from what I can see in the forums. And, I have no idea how items were missing in the WinSXS folder as these are two identical servers, installed the same way and with the same software, and only one has the issue. Check out this blog from 2004: http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx The steps are too old to help newer systems, but it does explain the error well.

    • Marked as answer by Donia Strand Wednesday, September 12, 2012 4:07 PM
    Wednesday, December 29, 2010 5:15 PM

All replies

  • if the fix-it tool does not work, try it manually. As stated in the above KB article, go to
    HKEY_LOCAL_MACHINE\COMPONENTS and remove PendingXmlIdentifier, NextQueueEntryIndex, AdvancedInstallersNeedResolving.
    be sure to make a backup before you delete the keys. A step by step guide can be found in the mentioned article.
    hth
    Gregor Stefka
    Monday, December 13, 2010 9:33 PM
  • No can do. This is Server 2008 R2, not Windows 7. Those keys don't exist, otherwise the fix it tool would work. A Symantec Backup agent KB article suggests this:

    http://www.symantec.com/business/support/index?page=content&id=TECH125274&key=15047&actp=LIST

    I've tried option 1:

    Solution 1:
     
    1. Start > All Programs > Accessories > Right-click on Command Prompt and select "Run as Administrator" > Click "Allow" for the elevation prompt
     
    2. Execute the following command:
     
    fsutil resource setautoreset true C:\
     
    The command above assumes C: is the system volume. If the Operating System is installed on an alternate partition ( e.g. D: ), edit the command accordingly.
     
    3. Reboot the system

    and that didn't work. Option 2 suggests reinstalling the windows installer, but there is no redistributable Windows 5.0 installer and that's what Windows Server 2008 R2 uses.

    Monday, December 13, 2010 9:40 PM
  • Hi,

     

    As this issue is related to Visual C++ installation, I suggest discussing it in our Visual C++ forum. They are the best resource to troubleshoot this issue.

     

    http://social.msdn.microsoft.com/Forums/en/vcgeneral/threads

     

    Meanwhile, I would like to share you with the following link:

     

    http://social.msdn.microsoft.com/Forums/en/vcgeneral/thread/7074decf-d077-4697-8a8b-4e04d9cb8e67

     

    Tim Quan

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.  

    Tuesday, December 14, 2010 3:32 AM
    Moderator
  • HI Tim:

    Thanks for your response. The link you shared did not help the user who posted a similar problem to mine. Nor did the link within that post help the other users who posted. This really isn't a developer issue at all--it seems to be a .NET 3.5 and windows installer issue. Any installers (like Symantec backup exec) that require that assembly fail. The Microsoft Visual C++ 2005 and 2008 Redistributable Packages install runtime components of Visual C++ Libraries required to run applications developed with Visual C++ on computers that do not have Visual C++  installed.

    Tuesday, December 14, 2010 5:35 AM
  • Hi,

     

    I did not say this is a developer issue. Since it is a Visual C++ related installation issue, I suggest discussing it in Visual C++ General forum. They deal with Visual C++ Setup issues.

     

    If you feel it is related to corrupt Windows Installer, I suggest trying to install Office or Windows Live Messenger to test the result. If they can be installed successfully, we can infer Windows Installer is working properly.

     

    If you feel it is related to corrupt .Net Framework, I suggest removing .NET Framework using the removal tool:

     

    1. Please download the tool from the following link:

    http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog_Tools/dotnetfx_cleanup_tool.zip

     

    Please Note: The third-party product discussed here is manufactured by a company that is independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's performance or reliability.

     

    2. Please save the zip file (dotnetfx_cleanup_tool.zip) from the above link to the local Desktop and extract it.

    3. Double click cleanup_tool.exe to run the tool.

    4. Please follow the instructions given.

    In the "Product to cleanup:" box, please select ".NET Framework - All versions".

    5. Click "Cleanup Now" button.

     

    Then reinstall all .Net Framework components.

     

    Tim Quan

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.  

    Wednesday, December 15, 2010 3:43 AM
    Moderator
  • Any update?
    Friday, December 17, 2010 9:54 AM
    Moderator
  • I'm working with Microsoft on this issue and will post once resolved. Thanks!
    Monday, December 20, 2010 6:29 PM
  • Also having the same issue. Not only with the vc++ install, but also with Sql Server 2008 r2.

    This is ridiculous. It's taking days of my time now and the issue still stands.

     

    Steps I've done so far:

    Enabled .net framework 3.5 - didn't work

    Uninstalled prev version of SQL Server - didn't work.

    Installed a ____ load of vc++ redistributable package - didn't work,  of course stuck on the 2005 SP1 x64. The other ones installed just fine.

    Also tried the registry edit, suggested above - didn't work.

    Tried to install .net 2.0 - didn't work, wouldn't even let me.

     

     

     

    Does anybody know how to change the registry/env variable so that it points to an earlier .net framework, whenever possible?

    Thursday, December 23, 2010 10:12 AM
  • Hey St.clouds2, I feel your pain. I'll make sure to post with my results, still working with Microsoft.

    Here's what we did so far (hasn't worked for me, but may be worth a try for others):

    1) Try running sfc from the windows server 2008 r2 (or whatever OS you have) CD in offline mode. The command line is this:

    sfc /scannow /offbootdir=c:\  /offwindir=c:\windows

     

    2) Run the System Readiness Tool as it may be able to fix some of the missing files.

    http://www.microsoft.com/downloads/en/details.aspx?FamilyId=c4b0f52c-d0e4-4c18-aa4b-93a477456336&displaylang=enand then check the errors in the C:\Windows\Logs\CBS\CheckSUR.log You'll probably see a lot of missing manifests and components like this:

    Component Store
    (f) CSI Payload File Missing 0x00000000 msvcr80.dll amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_c905be8887838ff2 
    (f) CSI Store Directory Missing 0x00000002 winsxs\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_c905be8887838ff2\ amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_c905be8887838ff2 
    (fix) CSI Store Directory Missing CSI Store Directory Created C:\Windows\winsxs\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_c905be8887838ff2\
    (f) CSI Payload File Missing 0x00000000 msvcp80.dll amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_c905be8887838ff

     

    A bunch of files are missing from the side by side folder in these cases (winsxs folder).

     

    Repairing the framework is not really an option on a production server if it is possible at all with windows server 2008 r2 x64.

     

    The funny thing is, in my environment, is there are two absolutely identical Web Front Ends, installed on same environment, exactly the same way, at exactly the same time, with exactly the same software. (Not imaged, either). One front end has the issue, the other doesn't.

    Thursday, December 23, 2010 4:45 PM
  • Hi All

     

    I have the Same_D_n_Problem.... However, I WAS able to download and install the VC++ 2005 Redist x_64 after removing the one that was there.... Didn't help :(

    Tried removing, then installing using a CleanBoot - no luck

    REinstalled VC++2005 Redist. No problem but cannot install SQL 2008 R2

    Soooo... have traced the SQL Installer log file - and one can get to the entry by searching for 1935 - then looked back for what I think is the begining of the problem - I have marked this with ********************* here is the LogFile excerpt:

    ---------------

    2010-12-29 22:08:59 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\Services\SSIS Server - OK.
    2010-12-29 22:08:59 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\SqlUA - OK.
    2010-12-29 22:08:59 Slp: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\SqlUA\CurrentVersion - OK.
    2010-12-29 22:08:59 Slp: ------------------------------------------------------------
    2010-12-29 22:08:59 Slp: D:\SQLInstal\x64\FixSqlRegistryKey_x86.exe exit code: 0
    2010-12-29 22:08:59 Slp: Completed Action: FixSqlRegistryKey, returned True
    2010-12-29 22:08:59 Slp: ----------------------------------------------------------------------
    2010-12-29 22:08:59 Slp: Running Action: PostMsiTimingConfigAction
    2010-12-29 22:08:59 Slp: The object state property 'workflow' is null/empty. *********************
    2010-12-29 22:08:59 Slp: Error: Action "PostMsiTimingConfigAction" failed during execution.
    2010-12-29 22:08:59 Slp: Completed Action: PostMsiTimingConfigAction, returned False
    2010-12-29 22:08:59 Slp: Completed Action: ExecuteStandardTimingsWorkflow, returned True
    2010-12-29 22:08:59 Slp: ----------------------------------------------------------------------
    2010-12-29 22:08:59 Slp: Running Action: ExecuteCloseWorkflow
    2010-12-29 22:08:59 Slp: Workflow to execute: 'CLOSE'
    2010-12-29 22:08:59 Slp: ----------------------------------------------------------------------
    2010-12-29 22:08:59 Slp: Skipping Action: ProduceStatusLogs
    2010-12-29 22:08:59 Slp: Action is being skipped due to the following restrictions:
    2010-12-29 22:08:59 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/AreProductFeaturesSupported set" did not pass as it returned false and true was expected.
    2010-12-29 22:08:59 Slp: ----------------------------------------------------------------------
    2010-12-29 22:08:59 Slp: Running Action: FinalizeProgressStatus
    2010-12-29 22:08:59 Slp: Completed Action: FinalizeProgressStatus, returned True
    2010-12-29 22:08:59 Slp: ----------------------------------------------------------------------
    2010-12-29 22:08:59 Slp: Running Action: RebootMessageAction
    2010-12-29 22:08:59 Slp: Completed Action: RebootMessageAction, returned True
    2010-12-29 22:08:59 Slp: ----------------------------------------------------------------------
    2010-12-29 22:08:59 Slp: Skipping Action: FinishPage
    2010-12-29 22:08:59 Slp: Action is being skipped due to the following restrictions:
    2010-12-29 22:08:59 Slp: Condition "Is the user's scenario set to EditionUpgrade" did not pass as it returned false and true was expected.
    2010-12-29 22:08:59 Slp: ----------------------------------------------------------------------
    2010-12-29 22:08:59 Slp: Skipping property RequireMode of class: StopAction
    2010-12-29 22:08:59 Slp: Input of property will not be set due to the following failed restriction(s):
    2010-12-29 22:08:59 Slp: Condition "Is the user's scenario set to ComponentUpdate" did not pass as it returned true and false was expected.
    2010-12-29 22:08:59 Slp: ----------------------------------------------------------------------
    2010-12-29 22:08:59 Slp: Running Action: CloseUI
    2010-12-29 22:08:59 Slp: Stop Action
    2010-12-29 22:08:59 Slp: Completed Action: CloseUI, returned True
    2010-12-29 22:08:59 Slp: Completed Action: ExecuteCloseWorkflow, returned True
    2010-12-29 22:08:59 Slp: ----------------------------------------------------------------------
    2010-12-29 22:08:59 Slp: Running Action: PassPidBackFromComponentUpdate
    2010-12-29 22:08:59 Slp: Pass the flag CuPidDisplayed to the main setup
    2010-12-29 22:08:59 Slp: ENU value specified, trying to pass the value to main setup
    2010-12-29 22:08:59 Slp: PID value specified, trying to pass the value to main setup
    2010-12-29 22:08:59 Slp: SQMREPORTING value is specified in CU workflow, trying to pass the value to main setup
    2010-12-29 22:08:59 Slp: Completed Action: PassPidBackFromComponentUpdate, returned True
    2010-12-29 22:08:59 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2010-12-29 22:08:59 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
    2010-12-29 22:08:59 Slp: Sco: Attempting to get registry value CustomerFeedback
    2010-12-29 22:09:00 Slp:
    2010-12-29 22:09:00 Slp:
    2010-12-29 22:09:00 Slp: ----------------------------------------------------------------------
    2010-12-29 22:09:00 Slp:
    2010-12-29 22:09:00 Slp: Error result: -2068052081
    2010-12-29 22:09:00 Slp: Result facility code: 1212
    2010-12-29 22:09:00 Slp: Result error code: 1935
    2010-12-29 22:09:00 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2010-12-29 22:09:00 Slp: Sco: Attempting to open registry subkey
    2010-12-29 22:09:00 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
    2010-12-29 22:09:00 Slp: Sco: Attempting to get registry value DW0201
    2010-12-29 22:09:22 Slp: Submitted 1 of 1 failures to the Watson data repository
    2010-12-29 22:09:22 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2010-12-29 22:09:22 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
    2010-12-29 22:09:22 Slp: Sco: Attempting to get registry value CustomerFeedback

     

     

    Would be great to hear others' thoughts on this

     

    Cheers

     

    Martin

     

    Wednesday, December 29, 2010 12:41 PM
  • Martin, you are no longer getting an Redistributable install error message, which means that most of the suggestions in these postings won't work for you. From the messages you are getting, I'm guessing SQL won't install because it still has leftover components from the last time you installed it. See this posting for Tao-Min Tan's fix for that:

    http://social.msdn.microsoft.com/Forums/en/sqlsetupandupgrade/thread/62f0cd6b-bf78-46e0-b513-1556c0866241

    On the 1935 error I've been receiving:

    I would not recommend using the .NET framework removal tool on Windows 2008 R2, although that is not a step I tried. Depending on what kind of server it is, you might have components that won't work correctly after the removal and reinstall. (SharePoint and SQL are two that come to mind).

    If you are getting this 1935 error, and the simple fixes mentioned in earlier postings don't work, I recommend reinstalling Windows from scratch on that server. I found out the hard way it isn't worth troubleshooting. I hate to advocate a reinstall rather than getting to the root of the problem, but if you want the C++ redistributable on there and you don't want to mess up your programs or Windows, this seems to be the way to go. The error stems from missing files in the WinSXS folder--although who knows how that happens--I have two identical servers and it happened on only one of them.

    Once Windows is installed with any updates available, install the Microsoft Visual C++ 2005 SP1 Redistributable Package (x64) and the Microsoft Visual C++ 2008 SP1 Redistributable Package (x64) right away. Then do whatever you have to do to get your software/services running again.

    Microsoft walked me through finding what files were missing from the WinSXS folder and tried installing those files on the machine with the issue. That didn't work (and consisted of a lot of finding GUIDS, and copying and pasting files..painful). Then they said let's try an inplace upgrade of windows (said it wouldn't affect SharePoint or IIS) and it killed SharePoint--and Windows had poor performance. I rolled back any changes. So, I don't have time to troubleshoot it anymore, I'm building a new server (and I don't want a server that's had the in place upgrade run on it anyway, even if I could get IIS and SharePoint to work). This error has been around since 2001 from what I can see in the forums. And, I have no idea how items were missing in the WinSXS folder as these are two identical servers, installed the same way and with the same software, and only one has the issue. Check out this blog from 2004: http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx The steps are too old to help newer systems, but it does explain the error well.

    • Marked as answer by Donia Strand Wednesday, September 12, 2012 4:07 PM
    Wednesday, December 29, 2010 5:15 PM
  • Hi Donia

    Thanks for your reply....

    The log seems to give a different error message to the installer

    Still get this message from the Installer


    TITLE: Microsoft SQL Server 2008 R2 Setup
    ------------------------------

    The following error has occurred:

    An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80070003.

    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1&EvtType=0xDF039760%25401201%25401

    ------------------------------

    I also have images of my disk as well as backup tapes of C drive - can restore C:\Windows directory and C:\ but think this is a shotgun approach...

    or try Tao-Min Tan's approach...

     

    Or simply live with SQL 2008 and wait for an alternative solution (not a huge problem for me, I guess)


    Your thoughts?

    Thanks

    Martin

     

    Wednesday, December 29, 2010 10:36 PM
  • Hi Martin:

    Ah, you are still getting the VC80 error, gotcha, and you are upgrading from SQL Server 2008.

    I don't think restoring your C: will help because if the 1935 error stems from problems with .NET or missing WinSXS files, you'd have the same problem again.

    When I've had issues upgrading SQL in the past (although I didn't get the 1935 error then), one way around it was to install SQL from the command line with the upgrade switch (might be worth a try for you), here's how:

    http://msdn.microsoft.com/en-us/library/ms144259.aspx#Upgrade

    Is this a production server? Could it be rebuilt quickly if a troubleshooting step went awry? If so, you may want to have a  look at this post about turning .NET 3.51 on and off (install and reinstall through features)
    http://social.answers.microsoft.com/Forums/en-US/w7programs/thread/046b7c56-af58-4076-bf05-3417a0960fa6

    It did sound like that didn't help StCloud, though, as he had said in his post that he'd tried enabling .NET 3.5.

    This definitely wouldn't be recommended in a critical production server.

    Did you get a chance to try the offline SFC scan and running the System Readiness tool (from my previous post)? I'd try that too.

    Wednesday, December 29, 2010 11:17 PM
  • Thanks Donia for your reply.....

     

    Didnt do the offine scan because of reports that it creates inconsistencies with updates that have been installed..... Tried Command line prompt - no luck even though it seemed ok: here is the dos stuff:

     

    D:\SQLInstal>Setup.exe /q /ACTION=upgrade /INSTANCENAME=MSSQLSERVER /RSUPGRADEDA
    TABASEACCOUNT="sa" /RSUPGRADEPASSWORD="57vintage" /ISSVCAccount="NT Authority\Ne
    twork Service" /IACCEPTSQLSERVERLICENSETERMS
    Microsoft (R) SQL Server 2008 R2 Setup 10.50.1600.01
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    D:\SQLInstal>dir
     Volume in drive D is New Volume
     Volume Serial Number is D89A-A320
    
    

     


    Thursday, December 30, 2010 12:39 PM
  • Hi Martin:

    The q parameter is only required if you are doing an unattended install--and therefore you also don't need /IACCEPTSQLSERVERLICENSETERMS. You don't want this running in quiet mode--you'll want to see what it fails at.

    /InstanceID is required when you upgrade from SQL Server 2008 and is only optional when you upgrade from SQL Server 2000 and SQL Server 2005 (you are missing this parameter):

    SQL Server Setup Control

    /INSTANCEID

    Required when you upgrade from SQL Server 2008

    Optional when you upgrade from SQL Server 2000 and SQL Server 2005

    Specifies a nondefault value for an InstanceID.

    SQL Server Setup Control
     /INSTANCEID

    Required when you upgrade from SQL Server 2008

    Optional when you upgrade from SQL Server 2000 and SQL Server 2005
     Specifies a nondefault value for an InstanceID.

    Is your /Instance name the default MSSQLServer or is it a named instance?

    I think if you get rid of quiet mode, you'll be able to see what is going on, plus you need the /InstanceID para. Also, you do have Integration and Reporting services? Just checking.

    Thursday, December 30, 2010 11:12 PM
  • Agree with Donia. A lot of people having problems and no real answers - My issue is the same on Win7.

    When installing C++ re-distributable on Win7 x64 Ultimate I have run into major issues, and every subsequent attempt to add or remove a C++ redist now results in a hang (normally when Feature: Ft_VC_Redist_OpenMP_x86 is onscreen) and an error message as listed at the bottom. The installers also hange when attempting to roll back.

    It seems to have stuffed a lot of things up in the process making installing software requiring C++ impossible.

    Whilst most threads advise running "sfc /scannow" I get an error as shown below.
    - sfc /scannow = "Windows Resource Protection could not start the repair service." (Yes I was admin) 

    So I've tried hours of registry fixes, services.msc changes, boots from repair disks, you name it... I have read every thread and fix but nothing works. I don't even know if sfc/scannow is going to fix the problem. Driving me bonkers.

     Attempted fixes so far (the ones I remember I did):

    - Uninstalling various versions of C++ redist (x86 and x64) they hang before completing.

    - Booted with a W7 Repair Disc, which repaired something in the boot file with no noticable difference.  Also with the Repair Disc I ran the command line and ran sfc /scannow with the hope that permissions would be off outside of W7.  This time it stops and tells me that a system repair is pending and to try again after reboot, which doesn't change anything.

    - Services.msc : Windows Modules Installer / Windows installer (both set to 'manual') 

    - Added various things other people have done like HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control Key: RegistrySizeLimit to ffffffff

    - Cleaned registry, turned off antivirus (MSE) etc

     

    Here's the windows logs error messages I extracted:

    2011-05-01 11:40:51, Info                  CBS    Starting TrustedInstaller initialization.

    2011-05-01 11:40:51, Info                  CBS    Loaded Servicing Stack v6.1.7601.17514 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\cbscore.dll

    2011-05-01 11:41:08, Info                  CBS    Failed to load the COMPONENTS hive from 'C:\Windows\System32\config\COMPONENTS' into registry key 'HKLM\COMPONENTS'. [HRESULT = 0x800703f8 - ERROR_REGISTRY_IO_FAILED]

    2011-05-01 11:41:08, Info                  CBS    Failed to load WCP DLL. [HRESULT = 0x800703f8 - ERROR_REGISTRY_IO_FAILED]

    2011-05-01 11:41:08, Info                  CBS    Failed to initialize the Core DLL: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\cbscore.dll [HRESULT = 0x800703f8 - ERROR_REGISTRY_IO_FAILED]

    2011-05-01 11:41:08, Info                  CBS    Failed to initialize CBS Core. [HRESULT = 0x800703f8 - ERROR_REGISTRY_IO_FAILED]

    2011-05-01 11:41:08, Info                  CBS    Ending TrustedInstaller initialization.

    2011-05-01 11:41:08, Info                  CBS    Failed to initialize Trusted Installer. [HRESULT = 0x800703f8 - ERROR_REGISTRY_IO_FAILED]

    2011-05-01 11:41:08, Info                  CBS    Starting TrustedInstaller finalization.

    2011-05-01 11:41:08, Info                  CBS    Trusted Installer core was not initialized.

    2011-05-01 11:41:08, Info                  CBS    Ending TrustedInstaller finalization.

    Error When installing C++ 2008 redist:

    Error 1935. An error occurred during the installation of assembly 'Microsoft.VC90.ATL,version="9.0.30729.4148",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecure="x86",type"win32" Please refer to Help and Support for more information. HRESULT: 0x800736FD

     Here's the extra issue for me - I can't do an in place upgrade because I have Windows on an SSD and my program files and user folders on another drive. So it won't let me.

    Looks like a fresh install is my only option which is a serious pain in the neck having to set up all the symlinks for using an SSD.

     

    Microsoft - PLEASE FIND A FIX!

    Sunday, May 01, 2011 10:47 AM
  • WOW!!!

     

    I have been fighting the same problem for the last several days while trying to install Sony Vegas Movie Studio. it uses C++ 2005 Redist. and C++ 2008 redistributable....UNFORTUNATELY...LOL...it needed to insatll the updated versions of those programs and they WOULD NOT...gave me the same 1935 error and "policy.8.0.Microsoft.VC80.CRT........"

    I think i have found the culprit!!!!

    Unfortunately I cant REMOVE the culprit!!  OI-VEY!!!

    I found a registry key that is almost verbatim of the error...and strangely it can't be removed...tried Registry Assassin, safe mode, logged in as both administrator and regular user...tried changing the name..NOPE...tried changing permisssions...NOPE...it WON'T BUDGE!!!  and I can't even find a way to alter it!!!!!  Anyone help with that???? Took me days to track this lil bastage down and now I can get rid of it!! I've invested probably 30 hours or more into this.

    I also tried reganul or whatever it was...this thing, so far is BULLETPROOF!   Anyone have armor piercing bullets for this turkey?? PLEASE let me know. LOL

    Anyway the dirty, rotten, no good, unmovable, undelete-able, registry key/file address is:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.0.0_none_801f9b67bc08bc01

     

    AND it's a real stinker...LOL Sorry just about hairless now...from pulling it out.

     

     

    Tuesday, May 03, 2011 4:11 AM
  • Also remove:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_policy.8.0.microsoft.vc80 & vc90 entries…

    [HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.8.0.microsoft.vc80 & vc90 entries

    [HKEY_LOCAL_MACHINE\COMPONENTS\WINNER\Components\x86_policy.8.0.microsoft.vc80 & vc90 entries.

    Then run services.msc and set "Windows Module Installer" to auto and restart it. Reboot.

    This worked for us - original issue where we received error was failed VC Redist++ install as dependency for SAS on W7 Enterprise. Hope this helps others.

    • Proposed as answer by TANKtr0n Thursday, December 01, 2011 11:06 PM
    Thursday, December 01, 2011 11:04 PM
  • Anyone have a solution for this problem.  I've tried everything here and also working with Microsoft to try and figure this out.

     

    Product: Microsoft Visual C++ 2005 Redistributable -- Error 1935.An error occurred during the installation of assembly 'Microsoft.VC80.ATL,type="win32",version="8.0.50727.762",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"'. Please refer to Help and Support for more information. HRESULT: 0x80070057. assembly interface: IAssemblyCacheItem, function: Commit, component: {97F81AF1-0E47-DC99-A01F-C8B3B9A1E18E}

     

     

     
    Bradley
    Thursday, December 29, 2011 6:53 AM
  • Is there finally a fix for this from Microsoft?

     

    Thanks,

    Mark

    Wednesday, January 18, 2012 3:29 PM
  • Just had to reinstall Windows 7 because of Vista and Win7 problem that made some processes taking 100% of a core and unkillable. Microsoft still has no fix that after all the years. It eventually completely broke my win7. And now i'm having this problem when im trying to install OpenOffice.org. Great that M$ doesnt give a **** about this either.


    • Edited by bhasic Monday, February 13, 2012 2:11 AM
    Monday, February 13, 2012 2:05 AM
  • All u need to do is just start some of the service u might have stop or never start... it's work for me... i m not sure which one either but i started around 10 services which i suspected..

    cheers

    • Proposed as answer by inertias_dream Thursday, August 30, 2012 11:49 PM
    • Unproposed as answer by Donia Strand Friday, August 31, 2012 5:30 AM
    Thursday, May 31, 2012 12:23 AM
  • This worked for me as well.  Went through and started some services that sounded like they shouldn't be stopped and I stopped getting errors. I was getting the 1935 error while attempting to install Visual C++ 2008 Redistributable SP1 x64. 
    Thursday, August 30, 2012 11:51 PM
  • Glad that starting some of the services worked for you--but for the majority of these kind of issues, rebooting and restarting services do not work, so I must unpropose this answer. Additionally, as this original post is from 2010--I'd recommend perhaps creating a new post on this issue.

    :)

    Friday, August 31, 2012 5:33 AM
  • I have to say - I had this error while installing the C++ 2005 Redistributable, but I was also in the middle of Windows Updates on my newly stood up Windows Server 2008.  The 2 things it had on it prior to this:  Windows Installer 4.5 and .NET Framework 3.5 SP1.  I had also already rebooted from the first round of updates, this was when it was on its 2nd.  I didn't want to wait for C++ to come down on its own, if it was going to, since it is a SQL Server pre-req't.  But so when the current round completed, I rebooted, and tried C++ again - all went well.  I know this will not likely be the common case, but it should show that it probably has some contention for the Windows system files that are affected by updates, as the root cause, at least that was it, in my case.
    Sunday, November 25, 2012 3:21 AM
  • I fixed this by running services.msc and set "Windows Module Installer" to enabling and starting it. 
    • Proposed as answer by KeBodin Wednesday, August 14, 2013 9:41 PM
    Friday, July 19, 2013 11:06 PM
  • Thanks - after removing all other Visual C++ redistributables, restart of the server and then starting the Windows Module Installer, I was able to install the Visual C++ 2005 redistributables and then managed to install SQL.
    Tuesday, September 10, 2013 8:44 PM