Can't install KB4343900. "The referenced assembly could not be found."

KB4343900 keeps failing when I try to install it. Downloading the MSU and installing doesn't help.


Windows Event Viewer shows this error each time I try:

Code:

Windows update "Security Update for Windows (KB4343900)" could not be installed because of error 2147956481 "The referenced assembly could not be found." (Command line: ""C:\Windows\system32\wusa.exe" "C:\Users\{**}\Downloads\windows6.1-kb4343900-x64_8acbe17ab3a57e50df6c84a4940f2933fa790468.msu"        ")

In my CBS.log, this is where things start to go wrong:

Code:

2018-08-18 15:57:00, Info                  CSI    000001c8@2018/8/18:19:57:00.617 CSI Transaction @0x148e61e0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [86]"TI1.30684973_2490558992:2/Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24214.1.5"

2018-08-18 15:57:00, Info                  CBS    Exec: Resolving Package: Package_3_for_KB4284826~31bf3856ad364e35~amd64~~6.1.1.4, Update: 4284826-3_neutral_LDR
2018-08-18 15:57:00, Info                  CBS    Exec: Resolving Package: Package_3_for_KB4284826~31bf3856ad364e35~amd64~~6.1.1.4, Update: 4284826-3_neutral_LDR, PinDeployment: amd64_58ad1c3a2d30797c1aead73a258c6859_31bf3856ad364e35_6.1.7601.23933_none_5f927fe311434516
2018-08-18 15:57:00, Error                 CSI    000001c9@2018/8/18:19:57:00.619 (F) d:\w7rtm\base\wcp\componentstore\csd_locking.cpp(324): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
[gle=0x80004005]
2018-08-18 15:57:01, Error                 CSI    000001ca (F) STATUS_SXS_ASSEMBLY_MISSING #3060861# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2018-08-18 15:57:01, Error                 CSI    000001cb (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #3060746# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = 58ad1c3a2d30797c1aead73a258c6859, Version = 6.1.7601.23933, 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 = [77]"Package_3_for_KB4284826~31bf3856ad364e35~amd64~~6.1.1.4.4284826-3_neutral_LDR", rah = [1]"5", manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2018-08-18 15:57:01, Info                  CBS    Failed to pin deployment while resolving Update: 4284826-3_neutral_LDR from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2018-08-18 15:57:01, Info                  CBS    Failed to resolve item[0] in Package: Package_3_for_KB4284826~31bf3856ad364e35~amd64~~6.1.1.4, Update: 4284826-3_neutral_LDR [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2018-08-18 15:57:01, Info                  CBS    Failed to resolve execution update. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2018-08-18 15:57:01, Error                 CBS    Failed to resolve execution package: Package_3_for_KB4284826~31bf3856ad364e35~amd64~~6.1.1.4 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2018-08-18 15:57:01, Info                  CSI    000001cc@2018/8/18:19:57:01.329 CSI Transaction @0x148e61e0 destroyed
2018-08-18 15:57:01, Info                  CBS    Perf: Resolve chain complete.
2018-08-18 15:57:01, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2018-08-18 15:57:01, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2018-08-18 15:57:01, Info                  CBS    WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24214.1.5, status: 0x80073701, failure source: Resolve, start state: Resolved, target state: Installed, client id: WindowsUpdateAgent

I tried installing KB4284826 manually, but it says that the update is not applicable to my computer. But I found the Package_3_for_KB4284826 file, and it references these assemblies:

Code:

        <installerAssembly name="Microsoft-Windows-ServicingStack" version="6.0.0.0" language="neutral" processorArchitecture="amd64" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35"/>
        <update name="4284826-3_neutral_LDR">
            <applicable disposition="staged">
                <updateComponent elevate="distribution">
                    <assemblyIdentity name="usb.inf.Resources" version="6.1.7601.23933" processorArchitecture="amd64" language="en-US" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS"/>
                    <assemblyIdentity name="usbport.inf.Resources" version="6.1.7601.23933" processorArchitecture="amd64" language="en-US" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS"/>
                </updateComponent>
            </applicable>
            <component>
                <assemblyIdentity name="58ad1c3a2d30797c1aead73a258c6859" version="6.1.7601.23933" processorArchitecture="amd64" language="neutral" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS"/>
            </component>
        </update>

I had been having trouble with USB drivers on this machine for awhile. When I first set it up years ago, installing one set of chipset drivers completely disabled my USB ports, but I was able to remote desktop in to continue installing the rest, and after that my USB ports worked, but not in 3.0 mode. Somewhat recently, I tried installing the Gigabyte App Center and letting it search and update my various drivers, and after that my USB ports worked fine in 3.0 mode. I don't know if that's related to the difficulty I'm having right now. But it does look to me like this update is searching for a USB driver that I don't have.

I flushed the logs, followed your instructions, then tried to reinstall the package (and failed again). I've attached the logs after doing all that, in that order. The sfc /scannow command reported corruption that it could not fix.


The CbsPersist logs were too big to attach, so I split them up manually and attached them separately in two additional parts.

I was hoping to avoid that. I had a lot of trouble getting Windows 7 to install in the first place. The setup didn't recognize my hard drive (a Samsung 950 Pro NVMe) or work with my USB ports. I don't remember exactly how I got it to work in the first place, but IIRC it had something to do with slipstreaming drivers.


I could probably locate the files myself. For instance, when I saw this:
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_1002_for_KB4103713~31bf3856ad364e35~amd64~~6.1.1.9.mum



I tried downloading and installing KB4103713, and it refused saying that the update wasn't applicable to my PC. I'd noticed that even though I can't install it, that if I browse the MSU files using 7zip, it does contain a large number of mum files and corresponding cat files.


There's only about 25 distinct KB's referenced in the entire SURT log. I could download them all without too much trouble, and I could write a script that would automatically extract the mum and corresponding cat files listed as missing in the log.


If I do that, where would I put them? Or is there a problem with this approach that I'm not seeing?


I am running MSE as my sole AV and malware protection. So far I have not had a single infection as far as I can tell.

Thanks, I have the problem solved now, with a combination of SFC Fix and Farbar Recovery Scan Tool. The update is installed, CheckSUR no longer returns any errors, and things seem to be working fine now.

Heh, wasn't my doing. I got more help at another forum, and while I think I've got a pretty good grip on how to use SFC Fix (lesson learned - don't manually download multiple MSUs at once, they will get corrupted!) I'll be blessed if I understand what Farbar does.