locked
KB4054518 - 2017-12 Security Monthly Quality Rollup failed to update RRS feed

  • Question

  • Hello,

    Using WSUS to update the patches on the workstations. Failing to install KB4054518 - 2017-12 Security Monthly Quality Rollup on one of the workstations running Windows 7 SP1. I am out of ideas. I did stopping of Windows update servers, renaming the Software Distribution folder, re-registering the DLLs, permissions etc. with no luck. Here are the errors 

    on WindowsUpdate.Log file:


    2016-12-16 11:03:03:313 972 768 Handler WARNING: Got extended error: "Driver servicing operation failed"
    2016-12-16 11:03:03:313 972 768 Handler WARNING: Failed to parse extended error: 0x80070057

    On CBS.Log:

    2017-12-18 13:22:16, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
    2017-12-18 13:22:16, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]

    Any help would be appreciated.

    Thanks

    Monday, December 18, 2017 8:43 PM

Answers

  • Thanks gentlemen. 

    I did in-place upgrade of existing Windows 7 installation which repaired the OS. Now I am able to install the updates successfully.  If you don't want to waste your time and energy, this is a best solution.

    Thanks,

    • Marked as answer by tamangketa Wednesday, December 27, 2017 8:49 PM
    Wednesday, December 27, 2017 8:49 PM

All replies

  • Hello,

    Please try steps below and check whether you can install this KB successfully:

    1. Disable Anti-virus software, and make sure it will not startup during the next restart.

    2. Rename softwaredistribution folder:

    a. In cmd, run: net stop wuauserv

    b. rename C:\Windows\softwaredistribution to softwaredistribution.old

    c. In cmd, run: net start wuauserv

    3. Download KB4054518 from Windows update catalog and install it.


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






    • Edited by Yan Li_ Tuesday, December 19, 2017 7:28 AM
    Tuesday, December 19, 2017 7:25 AM
  • I did all the above before posting here. Even downloaded the update from the catalog and tried to install. It fails.
    Tuesday, December 19, 2017 1:44 PM
  • Greetings,

    I have tried the same and it fails.  It gets to 100%, then says Failure configuring Windows updates, reverting changes.

    The event logs says...

    Event ID: 20

    Installation Failure: Windows failed to install the following update with error 0x80004005 : Security Update for Windows (KN4054518)

    Also... Fault Bucket 50, type 5

    Event Name: WindowsUpdateFailure3

    Response: Not Available

    And maybe this one too...

    Event 1530

    Windows detected your registry file is still in use by other applicaitons or services.  The files will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  

    Windows 7 SP1 Home Premium x64

    Any suggestions?

    -D3

    Saturday, December 23, 2017 5:28 AM
  • Hello,

    Please run SFC /SCANNOW to find is there any system file is corrupt and repair system files.

    Regards,

    Yan


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


    • Edited by Yan Li_ Monday, December 25, 2017 7:30 AM
    Monday, December 25, 2017 6:13 AM
  • The error is logged in the C:\Windows\Logs\CBS\CBS.log for when a rollback happens. Search for  ", error" and post the results here.

    Best regards,

    Andrei


    We could change the world, if God would give us the source code.

    Tuesday, December 26, 2017 9:53 PM
  • Hello,

    Please run SFC /SCANNOW to find is there any system file is corrupt and repair system files.

    Regards,

    Yan


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


    Did that already. It did not help.
    • Edited by tamangketa Wednesday, December 27, 2017 5:17 PM
    Wednesday, December 27, 2017 4:27 PM
  • The error is logged in the C:\Windows\Logs\CBS\CBS.log for when a rollback happens. Search for  ", error" and post the results here.

    Best regards,

    Andrei


    We could change the world, if God would give us the source code.

    017-12-27 12:12:54, Info                  CBS    SQM: Initializing online with Windows opt-in: False
    2017-12-27 12:12:54, Info                  CBS    SQM: Cleaning up report files older than 10 days.
    2017-12-27 12:12:54, Info                  CBS    SQM: Requesting upload of all unsent reports.
    2017-12-27 12:12:54, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
    2017-12-27 12:12:54, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2017-12-27 12:12:54, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
    2017-12-27 12:12:54, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]

    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197123776 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197123777 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197123778 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197123779 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197123780 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197123781 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197279769 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197279770 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197279771 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197279772 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197279773 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197279774 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-12-27 12:33:01, Info                  CBS    Session: 30637880_3197279775 initialized by client WindowsUpdateAgent.
    2017-12-27 12:33:01, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAG

    017-12-27 12:33:40, Info                  CBS    Appl: Package: Package_59_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0, Update: Trigger_1, Applicable: NotApplicable, Dis

    2017-12-27 12:33:40, Info                  CBS    Failed to get session package state for package: Package_59_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

    Wednesday, December 27, 2017 6:05 PM
  • Thanks gentlemen. 

    I did in-place upgrade of existing Windows 7 installation which repaired the OS. Now I am able to install the updates successfully.  If you don't want to waste your time and energy, this is a best solution.

    Thanks,

    • Marked as answer by tamangketa Wednesday, December 27, 2017 8:49 PM
    Wednesday, December 27, 2017 8:49 PM
  • Unfortunately, this is not the best, or practical, solution when the OS is an online Windows Server 2008. I wish I could just get rid of the Update reminder. It keeps wanting to install.
    Monday, February 26, 2018 4:57 PM
  • Unfortunately, this is not the best, or practical, solution when the OS is an online Windows Server 2008. I wish I could just get rid of the Update reminder. It keeps wanting to install.
    If you read my question carefully, I mentioned workstations running Windows 7 SP1. Solution that I found is not for Windows Server 2008.
    Friday, May 4, 2018 6:42 PM