none
Win7 SP1 x64 - code 80073701 (SXS_ASSEMBLY_MISSING) on update KB4499164 - Package_17_for_KB4489878 flagged RRS feed

  • Question

  • I've run sfc /scannow and CheckSur MULTIPLE times without issues detected.  I have even copied, from another GOOD system, the:

     amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24387_none_bbb104391f54aec8

    package (had to change ownership of winsxs from Trusted Installer to Administrator - NOT RECOMMENDED - and give Administrator Full Control.

    Also, made sure that the .MUM and .CAT files for:

    Package_17_for_KB4489878~31bf3856ad364e35~amd64~~6.1.1.9

    were present in C:\windows\servicing\Packages subdirectory (another Trusted Installer to Administrator ownership change - NOT RECOMMENDED)

    A reference to the above Package_17 is present in the Registry at:

    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_cpu.inf_31bf3856ad364e35_0.0.0.0_none_dd42ebcfefe8cd1f 

    Value: Package_17_for_KB4489878~31bf3856ad364e35~amd64~~6.1.1.9.4489878-20_neutral_LDR

    Type: REG_SZ   

    Data: 6.1.7601.24387@4

    Processor is an Intel Core 2 Duo E8400 64-bit processor with 4 GBytes of Main Memory.

    CBS.log pertinent text (Time Date - CBS/CSI - Error/Info tags removed):

    Resolving Update: 4489878-19_neutral_LDR,  Package: Package_17_for_KB4489878~31bf3856ad364e35~amd64~~6.1.1.9, PinDeployment: amd64_input.inf_31bf3856ad364e35_6.1.7601.24386_none_7ed5431750122599
    Exec: Resolving Package: Package_17_for_KB4489878~31bf3856ad364e35~amd64~~6.1.1.9, Update: 4489878-20_neutral_LDR
    Exec: Resolving Package: Package_17_for_KB4489878~31bf3856ad364e35~amd64~~6.1.1.9, Update: 4489878-20_neutral_LDR, PinDeployment: amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24387_none_bbb104391f54aec8
    00000011@2019/6/2:17:55:17.354 (F) d:\w7rtm\base\wcp\componentstore\csd_locking.cpp(324): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
    [gle=0x80004005]
    00000012 (F) STATUS_SXS_ASSEMBLY_MISSING #337014# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
    00000013 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #336899# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = cpu.inf, Version = 6.1.7601.24387, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral, cb = (null), s = (null), rid = [79]"Package_17_for_KB4489878~31bf3856ad364e35~amd64~~6.1.1.9.4489878-20_neutral_LDR", rah = [1]"4", manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]

    We all know that Windows 10 Pro will be needed to maintain Microsoft support as Windows 7 support is terminating in January, 2020.  (This system already has a Digital Entitlement for Windows 10 Pro).   I would like to LEARN from this situation and would like to install KB4499164 successfully at some point SOON due to the special fix inside it regarding a serious virus threat.   I will continue to look at systems that have successfully applied KB4489878 and then KB4499164 for answers, especially in the Registry of the Good system. 

    It is interesting to note that a Win/7 Pro SP1 x64 system that had NOT been updated since 2/2017 took 10 updates this past week with KB4499164, BUT DID NOT EVEN INSTALL KB4489878!  That system is all up to date now.  This essentially tells me that KB4499164 JUST MIGHT Completely overlay KB4489878's update.  I need to "force" KB4499164 by some method, of course by ignoring SXS_ASSEMBLY_MISSING errors pointing to KB4489878, if indeed KB4499164 completely replaces it and more.  (There are just two MORE .MUM and .CAT files from KB4499164 (394) over the number in KB4489878 (392)!)

    Help with the "fix" and learning experience is GREATLY Appreciated!

    Monday, June 10, 2019 3:39 PM

All replies

  • Hi, 

    Thank you for posting in Microsoft TechNet Forum.

    Error 0x80073701 is ERROR_SXS_ASSEMBLY_MISSING, it means there are some system files are missing, which caused the update installation failure.

    1. Examine the language packs installed on the system. Uninstall the unnecessary language packs.

    2. Uninstall the patches which were missing assemblies and reboot the windows. 

    Meanwhile, I also found an article which reported some similar issues, it should still be waiting to be fixed.

    Best regards,

    Hurry


    Please remember to mark the reply as an answer if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com



    Tuesday, June 11, 2019 9:30 AM
  • Hurry,

      You will not be surprised to hear that today's KB4503292 (June 11, 2019 Patch Tuesday) will also NOT apply.  Same ERROR_SXS_ASSEMBLY_MISSING on Package_17_for_KB4489878....Hurry, it would likely be PERFECT if I could UNINSTALL KB4489878 and then reinstall.  I see KB4493472 did install back in April along with the Servicing Stack update KB4490628 (early April - but likely belongs to March) and KB4474419 (March 16, 2019).  I do not even see KB4489878 in my Programs and Features - > Installed Update list. Hmmmmmm.  KB4489878 clearly is listed in the View Update History list on March 16, 2019.  I have updated the other 4 household systems and my work PC to today's patches.  I have many Windows 7 Pro SP1 x64 PC to check against.  I guess I'll get to WORK!   Thanks for your reply!  It IS appreciated.  Too bad I "blitzed" my System Restore points.  FIRST Time I've done that in YEARS.  My timing couldn't be more awful!

    Wednesday, June 12, 2019 2:00 AM
  • Hi,

    Thank you for your feedback.

    I'm sorry for the inconvenience.

    Try to reset windows update component and check.

    After January 14, 2020, Microsoft will no longer provide security updates or support for PCs running Windows 7. You had better upgrade your windows to the latest version.

    Best regards,

    Hurry


    Please remember to mark the reply as an answer if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    Thursday, June 13, 2019 7:20 AM
  • This past July 6-7, 2019 weekend, the system in question has been PAINFULLY updated to Windows/10 Pro x64.  As it has a Digital Entitlement, the system activated without issues and no Product Keys were needed or used.  I had to use the Windows/10 Pro x64 Feature 1903 ISO file to build a single-layer DVD.  This was used to apply Windows/10 Pro at Feature 1903 with KEPT personal files but NOT Applications.  As the system has Intel QST for fan controls, the system needed the old Intel AMT driver package, which after must searching on the Lenovo support site, was eventually located.  It actually installed on Windows/10 Pro x64 (was for a Windows/7 x64 system initially).  After that install, the Fan Control software was uninstalled and the system restarted.  Then the Fan Control software was reinstalled and this time, Intel QST version 1.x was recognized and the CPU Fan was listed and controllable.   Display issues for the ATI HD6450 card using an LG Flatron 1920x1080P DVI-D attached display and a SONY KDL-V34XBR970 television via 1920x1080i HDMI connection were resolved.  Windows Defender Firewall was opened for ICMP IPv4 Ping and File and Printer Sharing and Microsoft Remote Desktop.  The Intel AMT Vulnerability involving the LMS service was resolved by DISABLING that service (was not used by me).  (Some may also want to rename the LMS.exe executable.)

    Note that a nearly IDENTICAL Lenovo PC running Feature 1903 of Windows/10 Pro x64 with the Intel Q45/Q43 Express chipset for the Display Adapter NO LONGER works with Microsoft Remote Desktop, yielding a BLACK Screen as reported on other Forum postings.  This was NOT an issue with Feature 1809 as it did not have the RDP changes added to Feature 1903, making that Intel display driver inoperative for RDP.

    I made many other changes to suit Windows/10 Pro.  Here's an example of a Desktop Icon target to have Microsoft Edge (whether the Default Browser or not), now a SYSTEM APP, to open and go to a specific web page:

    C:\Windows\explorer.exe microsoft-edge:https://www.fcc.gov

    You'll need to change the ICON picture to one that matches the web site, of course, and name the desktop icon as appropriate.

    This matter is CLOSED and UNANSWERED, unless one considers moving to Windows 10/Pro x64 and an "answer".

    It will be an interesting Summer, 2019 at my company as we move users to Windows/10 Pro on VMWare VDI and Terminal Server users on Windows/Server 2008 R2 to Windows/Server 2016 or 2019!

    ChevIT Guy

    Monday, July 8, 2019 4:19 PM
  • Well youre missing the default fix in Sfc.....When you run,  Sfc /Scannow  & the utility ends,one must type: CHKDISK C: / F  agree,type: EXIT  the repair(s) get done on pc restart...

    Also,download from catalog.http://catalog.update.microsoft.com/v7/site/Search.aspx?q=4499164

    Win 7 update since 2017??? The OS is misconfigured to defaults..To fix,open add/remove/Windows Components/Services/allow .NET edit others,exit,restart pc.In desktop,download & run kb890830  from catalog,once done,open control panel/Defender/HELP tab/check & run updates.After above,download: windowsupdateagent-7.6-x86  get that from Microsoft...

    Wednesday, July 10, 2019 2:41 AM