locked
SP1 setup fails "ERROR_SXS_ASSEMBLY_MISSING(0x80073701)" - Win7 x64

    Question

  • This is 100% repro.  The System Update Readiness tool and a few reboots did not resolve the issue.

    Here is what looks like the most relevant part of CBS.LOG:

     

    2010-07-14 19:24:47, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, Update: INF_rawsilo
    2010-07-14 19:24:47, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, Update: INF_rawsilo, PinDeployment: amd64_rawsilo.inf_31bf3856ad364e35_6.1.7600.16385_none_72e15d77b1af67e1
    2010-07-14 19:24:47, Info                  CBS    Resolving Update: INF_rawsilo,  Package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, PinDeployment: amd64_rawsilo.inf_31bf3856ad364e35_6.1.7600.16385_none_72e15d77b1af67e1
    2010-07-14 19:24:47, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, Update: INF_usbcir
    2010-07-14 19:24:47, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, Update: INF_usbcir, PinDeployment: amd64_usbcir.inf_31bf3856ad364e35_6.1.7600.16385_none_fa3c88e716331440
    2010-07-14 19:24:47, Info                  CBS    Resolving Update: INF_usbcir,  Package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, PinDeployment: amd64_usbcir.inf_31bf3856ad364e35_6.1.7600.16385_none_fa3c88e716331440
    2010-07-14 19:24:47, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, Update: INF_circlass
    2010-07-14 19:24:47, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, Update: INF_circlass, PinDeployment: amd64_circlass.inf_31bf3856ad364e35_6.1.7600.16385_none_fd65696e44277672
    2010-07-14 19:24:47, Info                  CBS    Resolving Update: INF_circlass,  Package: Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, PinDeployment: amd64_circlass.inf_31bf3856ad364e35_6.1.7600.16385_none_fd65696e44277672
    2010-07-14 19:24:47, Info                  CBS    Exec: Resolving Package: Package_2_for_KB972270~31bf3856ad364e35~amd64~~6.1.1.0, Update: 972270-3_neutral_LDR
    2010-07-14 19:24:47, Info                  CBS    Exec: Resolving Package: Package_2_for_KB972270~31bf3856ad364e35~amd64~~6.1.1.0, Update: 972270-3_neutral_LDR, PinDeployment: amd64_94bf1a1bb6ea2b9c00cf9d5d9319e6a4_31bf3856ad364e35_6.1.7600.20553_none_9f149ece13582b37
    2010-07-14 19:24:47, Info                  CBS    Exec: Resolving Package: Package_2_for_KB972270~31bf3856ad364e35~amd64~~6.1.1.0, Update: 972270-4_neutral_LDR
    2010-07-14 19:24:47, Info                  CBS    Exec: Resolving Package: Package_2_for_KB972270~31bf3856ad364e35~amd64~~6.1.1.0, Update: 972270-4_neutral_LDR, PinDeployment: amd64_94bf1a1bb6ea2b9c00cf9d5d9319e6a4_31bf3856ad364e35_6.1.7600.20553_none_9f149ece13582b37
    2010-07-14 19:24:47, Info                  CBS    Exec: Resolving Package: Package_3_for_KB972270~31bf3856ad364e35~amd64~~6.1.1.0, Update: 972270-6_neutral_LDR
    2010-07-14 19:24:47, Info                  CBS    Exec: Resolving Package: Package_3_for_KB972270~31bf3856ad364e35~amd64~~6.1.1.0, Update: 972270-6_neutral_LDR, PinDeployment: amd64_c0573f2ae4a12fe59bf91b63dda50f14_31bf3856ad364e35_6.1.7600.20553_none_a2c40020faaa0281
    2010-07-14 19:24:47, Error                 CSI    0000000c@2010/7/15:02:24:47.392 (F) d:\w7rtm\base\wcp\componentstore\csd_locking.cpp(321): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
    [gle=0x80004005]
    2010-07-14 19:24:47, Error                 CSI    0000000d (F) STATUS_SXS_ASSEMBLY_MISSING #273344# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
    2010-07-14 19:24:47, Error                 CSI    0000000e (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #273229# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = c0573f2ae4a12fe59bf91b63dda50f14, Version = 6.1.7600.20553, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, cb = (null), s = (null), rid = [75]"Package_3_for_KB972270~31bf3856ad364e35~amd64~~6.1.1.0.972270-6_neutral_LDR", rah = [1]"3", manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
    2010-07-14 19:24:47, Info                  CBS    Failed to pin deployment while resolving Update: 972270-6_neutral_LDR from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2010-07-14 19:24:47, Info                  CBS    Failed to resolve item[0] in Package: Package_3_for_KB972270~31bf3856ad364e35~amd64~~6.1.1.0, Update: 972270-6_neutral_LDR [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2010-07-14 19:24:47, Info                  CBS    Failed to resolve execution update. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2010-07-14 19:24:47, Error                 CBS    Failed to resolve execution package: Package_3_for_KB972270~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2010-07-14 19:24:47, Info                  CSI    0000000f@2010/7/15:02:24:47.579 CSI Transaction @0x246d240 destroyed
    2010-07-14 19:24:47, Info                  CBS    Perf: Resolve chain complete.
    2010-07-14 19:24:47, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2010-07-14 19:24:47, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2010-07-14 19:24:47, Info                  CBS    WER: Generating failure report for package: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.0.16562, status: 0x80073701, failure source: Resolve, start state: Partially Installed, target state: Installed, client id: SP Coordinater Engine
    2010-07-14 19:24:47, Info                  CBS    Failed to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2010-07-14 19:24:47, Info                  CBS    Failed to add %windir%\winsxs\pending.xml to WER report because it is missing.  Continuing without it...
    2010-07-14 19:24:47, Info                  CBS    Failed to add %windir%\winsxs\pending.xml.bad to WER report because it is missing.  Continuing without it...
    2010-07-14 19:24:47, Info                  CBS    Reboot mark refs: 0
    2010-07-14 19:24:47, Info                  CBS    SQM: Reporting package change for package: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.0.16562, current: Partially Installed, pending: Default, start: Partially Installed, applicable: Installed, target: Installed, limit: Installed, hotpatch status: StillGoing, status: 0x0, failure source: Resolve, reboot required: False, client id: SP Coordinater Engine, initiated offline: False, execution sequence: 182, first merged sequence: 182
    2010-07-14 19:24:48, Info                  CBS    SQM: Upload requested for report: PackageChangeBegin_Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.0.16562, session id: 142859, sample type: Always
    2010-07-14 19:24:48, Info                  CBS    SQM: Warning: Failed to get machine name. The data won't be available. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2010-07-14 19:24:48, Info                  CBS    SQM: Warning: Failed to get domain name. The data won't be available. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

    Thursday, July 15, 2010 3:03 AM

Answers

  • How do I launch an In-place upgrade?

    those 4 errors from the checkSUR.log cause the rollback. But the tool doesn't have the data to repair it. I which that MSFT creates on online version of the tool (like the Symbol Server to get the required PDB files), which downloads the missing and corrupted files, instead of downloading a new version every 2 months which includes the files.

    Run the In-Place Upgrade:

    Start your Windows, put the DVD in it and run the setup.exe from the DVD. In the setup select Upgrade. This starts the In-Place upgrade and repairs your Windows:

    http://www.howtogeek.com/howto/3075/how-to-upgrade-the-windows-7-rc-to-rtm/


    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, July 16, 2010 10:02 PM

All replies

  • Is this the WU version or the standalone ISO. 

     

    It could have actually been a corrupt download. 

    Thursday, July 15, 2010 9:23 AM
  • Hi Berry,

    it looks like you're missing some files of the Update KB972270.

    Please run the System Update Readiness Tool for Windows 7 [1]. When the tool finished its work, start the Explorer and go to the folder C:\Windows\logs\CBS and look for a file called checkSUR.log. Open it and look if there are still broken/damaged/missing files. If everything is now ok, try to install the Sp1 again.


    @rmelv7

    no, the message menas a file in the WinSxS folder is missing and has nothing to do with the download.


    best regards
    André

    [1] http://support.microsoft.com/kb/947821/en-us


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, July 15, 2010 11:28 AM
  • Have you remove anything on your WinSXS folder? If so, that may be the root cause. To resolve the issue, you may need to run In-place Upgrade to repair the system.
    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. ”
    Friday, July 16, 2010 9:20 AM
    Moderator
  • As I said in line 1 of my post, I ran the System Update Readiness Tool and it did not fix the problem.  Here is my checkSUR.log file.


    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7600.20667
    Package Version 8.0
    2010-07-14 17:22

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store
    (f) CSI Missing Deployment Key 0x00000000 151f6702e79..4d0f8a2899d_31bf3856ad364e35_6.1.7600.20633_2672a2bdd1cb747d HKLM\Components\CanonicalData\Deployments 
    (f) CSI Missing Deployment Key 0x00000000 94bf1a1bb6e..d5d9319e6a4_31bf3856ad364e35_6.1.7600.20553_9f149ece13582b37 HKLM\Components\CanonicalData\Deployments 
    (f) CSI C Mark Deployment Missing 0x00000000 c!f54d0b27dbc..c05bfc0676d_31bf3856ad364e35_6.1.7600.20633_7a044546b57655e1 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7600.20633_en-us_840957ccfc10f6c6 
    (f) CSI C Mark Deployment Missing 0x00000000 c!c0573f2ae4a..b63dda50f14_31bf3856ad364e35_6.1.7600.20553_a2c40020faaa0281 amd64_microsoft-windows-font-embedding_31bf3856ad364e35_6.1.7600.20553_none_125d22cf51abe51a 

    Summary:
    Seconds executed: 384
     Found 4 errors
      CSI Missing Deployment Key Total count: 2
      CSI C Mark Deployment Missing Total count: 2

     

    Friday, July 16, 2010 1:22 PM
  • No, I have never removed anything from my WinSXS folder.  How do I launch an In-place upgrade?

    It may be relevant:  KB972270 is mentioned in CBS.LOG as the cause of the failure.  I am unable to uninstall that particular hotfix - the uninstall simply fails.  I am unable to install it again, as the installer reports that it is already present.

     

    Barry

    Friday, July 16, 2010 1:24 PM
  • Standalone EXE.   I have used the same EXE to install on multiple computers.  Only one computer fails with the message.  comp.exe reports no diffs between the failing computer's copy and other computers' copies.

    562,976,752 windows6.1-KB976932-X64-INTL.exe

     

    Friday, July 16, 2010 1:26 PM
  • How do I launch an In-place upgrade?

    those 4 errors from the checkSUR.log cause the rollback. But the tool doesn't have the data to repair it. I which that MSFT creates on online version of the tool (like the Symbol Server to get the required PDB files), which downloads the missing and corrupted files, instead of downloading a new version every 2 months which includes the files.

    Run the In-Place Upgrade:

    Start your Windows, put the DVD in it and run the setup.exe from the DVD. In the setup select Upgrade. This starts the In-Place upgrade and repairs your Windows:

    http://www.howtogeek.com/howto/3075/how-to-upgrade-the-windows-7-rc-to-rtm/


    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, July 16, 2010 10:02 PM