locked
KB4467107 failing to install on Windows 7 machines RRS feed

  • Question

  • Hi,

    KB4467107 nearly completes then reverts on all tested Windows 7 Pro x64 machines.

    On reference machines I have tried the following:

    • sfc /scannow
    • chkdsk /R
    • System update readiness tool
    • removed softdist catroot2 folders
    • Removed AV (ESET)
    • Tried on different vendors machines (dell/lenovo)

    Any idea what the next troubleshooting steps could be?

    Thursday, November 15, 2018 9:07 PM

All replies

  • Try downloading & installing from Win update catalog.

    http://catalog.update.microsoft.com/v7/site/Search.aspx?q=4467107

    Also,the cmdyou entered is wrong,use: CHKDSK C: /F  or /R  the cmd /R really isn't needed,/F is usually enough,the R (repair) takes 1-2 hrs.Also,windows will not update w/o kb890830 being ran,& .NET must be enabled in windows components/Add Remove.Also,after the above,download: windowsupdateagent-7.6-x86   another is available,its:  windowsupdateagent 20-x86  but requires some user editing to function.890830 can be had thru update catalog...

    Friday, November 16, 2018 2:27 AM
  • Hi jibberfrl,

    Thanks for your posting here.

    1. install this update manually or automatically?

    2. please turn off the third party antivirus software.

    3.After run “sfc /scannow” and checksur (also named as system update readiness tool), reboot the machine to take effect.

    4. Use Fix it tool to reset the Windows Update Components.
      -----------------------------------------------------------------
     https://support.microsoft.com/en-us/help/971058/how-do-i-reset-windows-update-components 

    5. Ensure that you have installed the latest servicing stack update, please refer to the KB4467107 article.

    6.perform a clean boot to install the patch again.

    7. If the patch still cannot be installed, please check the system event log and setup log in the event viewer to see if there is any error message during the installation of the patch. Also, upload the CBS log(C:\Windows\logs\CBS) to OneDrive and share the link.

    Hope can help you.

    Best regards,


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


    Friday, November 16, 2018 5:15 AM
  • Hi cora,

    Tried steps 1-7. Still no luck. I can't post links as my account is not 'verified'

    I believe these are the relevant parts of CBS.log

    2018-11-16 09:56:00, Info                  CSI    00000070 Begin executing advanced installer phase 24 (0x00000018) index 42 (0x000000000000002a) (sequence 67)
        Old component: [ml:348{174},l:346{173}]"Microsoft-Windows-PowerShell-Gac-Installation-8IP, Culture=neutral, Version=7.3.7601.23846, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
        New component: [ml:348{174},l:346{173}]"Microsoft-Windows-PowerShell-Gac-Installation-8IP, Culture=neutral, Version=7.3.7601.24278, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
        Install mode: uninstall
        Installer ID: {c145fd5d-1b9b-4738-9961-64034a3da28f}
        Installer name: [27]"Generic Command (uninstall)"
    2018-11-16 09:56:00, Info                  CSI    00000071 Performing 1 operations; 1 are not lock/unlock and follow:
      LockComponentPath (10): flags: 0 comp: {l:16 b:0a8b2194927dd4010f00000054013404} pathid: {l:16 b:0a8b2194927dd4011000000054013404} path: [l:204{102}]"\SystemRoot\WinSxS\amd64_powershell-gac-tool_exe_31bf3856ad364e35_7.3.7601.16384_none_98a9bac53345fd0c" pid: 154 starttime: 131868357537176355 (0x01d47d92901e1b23)
    2018-11-16 09:56:00, Info                  CSI    00000072 Calling generic command executable (sequence 42 (0x0000002a)): [128]"C:\Windows\WinSxS\amd64_powershell-gac-tool_exe_31bf3856ad364e35_7.3.7601.16384_none_98a9bac53345fd0c\PSCustomSetupInstaller.exe"
        CmdLine: [218]""C:\Windows\WinSxS\amd64_powershell-gac-tool_exe_31bf3856ad364e35_7.3.7601.16384_none_98a9bac53345fd0c\PSCustomSetupInstaller.exe" /uninstall System.Management.Automation,Version=3.0.0.0,PublicKeyToken=31bf3856ad364e35"
    2018-11-16 09:56:00, Info                  CSI    00000073 Performing 1 operations; 1 are not lock/unlock and follow:
      LockComponentPath (10): flags: 0 comp: {l:16 b:8b102b94927dd4011100000054013404} pathid: {l:16 b:8b102b94927dd4011200000054013404} path: [l:234{117}]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_6.1.7600.16385_none_3868158f24725705" pid: 154 starttime: 131868357537176355 (0x01d47d92901e1b23)
    2018-11-16 09:56:00, Info                  CSI    00000074 Creating NT transaction (seq 1), objectname [6]"(null)"
    2018-11-16 09:56:00, Info                  CSI    00000075 Created NT transaction (seq 1) result 0x00000000, handle @0x284
    2018-11-16 09:56:00, Info                  CSI    00000076@2018/11/16:09:56:00.529 CSI perf trace:
    CSIPERF:TXCOMMIT;22380
    2018-11-16 09:56:00, Error                 CSI    00000077 (F) Done with generic command 42 (0x0000002a); CreateProcess returned 0, CPAW returned S_OK
        Process exit code 4294967286 (0xfffffff6) resulted in success? FALSE
        Process output: [l:0 ][gle=0x80004005]
    

    and

    2018-11-16 09:56:01, Info                  CSI    000000aa@2018/11/16:09:56:01.964 CSI Advanced installer perf trace:
    CSIPERF:AIDONE;{c145fd5d-1b9b-4738-9961-64034a3da28f};Microsoft-Windows-PowerShell-Gac-Installation-8IP, Version = 7.3.7601.24278, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;2058745
    2018-11-16 09:56:01, Error      [0x018008] CSI    000000ab (F) Failed execution of queue item Installer: Generic Command (uninstall) ({c145fd5d-1b9b-4738-9961-64034a3da28f}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]
    2018-11-16 09:56:02, Info                  CSI    000000ac End executing advanced installer (sequence 67)
        Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED) 
    

    Friday, November 16, 2018 11:22 AM
  • I've also tried KB4467106, the security only update and this fails as well.
    Friday, November 16, 2018 2:02 PM
  • Hi Andrew,

    • Latest KB890830 is installed.
    • .NET 3.5.1 and 4.7.2 are installed and patched.
    • Windows Update Agent 7.6 is installed.

    Friday, November 16, 2018 2:17 PM
  • Also seeing this issue across multiple Windows 7 Pro (SP1) and Server 2008 R2 systems. Same error, same troubleshooting, no resolution. Also verified that latest servicing stack update is installed KB3177467.

    Error code: 80004005

    • Edited by catsla Monday, November 19, 2018 4:19 PM
    Monday, November 19, 2018 7:18 AM
  • Hi jibberfrl,

    Thanks for your replying.

    1. You can reply this thread to verify your account.

    https://social.technet.microsoft.com/Forums/en-US/dc4002e4-e3de-4b1e-9a97-3702387886cc/verify-account-42?forum=reportabug

    2. from the cbs log you provided, I cannot see much information about KB4467107, it seems the component installation went wrong.  Once you have verified your account successfully, Would you please upload the upload the CBS log(C:\Windows\logs\CBS) to OneDrive and share the link.

    Best regards,


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

    Tuesday, November 20, 2018 7:55 AM
  • Just chiming in with "us too", Win7 Pro x64 systems, similar troubleshooting steps.  The update always shows that it has succeeded and needs a reboot, then when you reboot it starts configuring, gets to 93%, then fails and reverts.
    Tuesday, November 20, 2018 3:16 PM
  • "Us too" :)

    I'm hoping someone has a fix for this. Or maybe by December's updates, they will fix it in the next rollup and the November updates will be superseded. I've been following this issue on a couple of different Sysnative.com posts and so far, no luck.

    Wednesday, November 21, 2018 3:39 PM
  • Anybody else using PDQ Inventory Agent?

    If we uninstall the Agent then the KB installs fine. Disabling the service is not enough.

    • Proposed as answer by jasonj_jnosaj Wednesday, November 21, 2018 7:35 PM
    Wednesday, November 21, 2018 6:09 PM
  • Had same issue on dozens of workstations today.  Remove PDQ agent and update installed without issue.
    Wednesday, November 21, 2018 7:35 PM
  • Yes, it was PDQ in our case as well, actually having PDQ Deploy installed prevents the update from installing.  So looks like having either PDQ Agent or PDQ Deploy is a blocker for the November updates. Hoping to reinstall fine after the update, we'll see in a few minutes.
    Wednesday, November 21, 2018 10:07 PM
  • Yep, uninstalling PDQ Inventory Agent allowed KB4467106 to install for me also. Curious thing though.. I have the remote deploy/inventory consoles, and the agent installed on my PC and didn't have any issues with these updates. Wonder what the trick is... and how'd ya find that it might'be been PDQ causing it?
    Wednesday, November 21, 2018 10:47 PM
  • Hi jibberfrl,

    Thanks for sharing the solution.

    If you have any other questions, please feel free to post.

    Best regards,


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

    Thursday, November 22, 2018 4:54 AM
  • I eventually ended up simply removing installed applications then re-trying the update after each one.

    If you contact PDQ support they will be able to supply a customer build that fixes the issue.

    Monday, November 26, 2018 2:34 PM