none
Windows Update Fails RRS feed

  • Question

  • Hi

    Windows Update fails with the error below. I have tried the commands below without success.

    Regards,

    Michael

    net stop wuauserv
    reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f
    reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientIDValidation /f
    rd %WINDIR%\SoftwareDistribution
    net start wuauserv
    wuauclt.exe /resetauthorization /detectnow

    2015-10-29 09:28:09:272  380 1124 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 2633; does use network; is at background priority
    2015-10-29 09:28:09:459  380 1124 WS WARNING: Nws Failure: errorCode=0x803d0013
    2015-10-29 09:28:09:459  380 1124 WS WARNING: The body of the received message contained a fault.
    2015-10-29 09:28:09:459  380 1124 WS WARNING: Soap fault info:
    2015-10-29 09:28:09:459  380 1124 WS WARNING: reason: Fault occurred
    2015-10-29 09:28:09:459  380 1124 WS WARNING: code: Client
    2015-10-29 09:28:09:459  380 1124 WS WARNING: detail: <detail><ErrorCode>InvalidParameters</ErrorCode><Message>parameters.OtherCachedUpdateIDs</Message><ID>0377b0ea-e8ea-41e0-a0d0-6ed693cacc47</ID><Method>"</detail">http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"</Method></detail>
    2015-10-29 09:28:09:459  380 1124 WS WARNING: Soap fault detail: errorCode='InvalidParameters', message='parameters.OtherCachedUpdateIDs', id='0377b0ea-e8ea-41e0-a0d0-6ed693cacc47', method='"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"'
    2015-10-29 09:28:09:459  380 1124 WS FATAL: OnCallFailure failed with hr=0X80244007
    2015-10-29 09:28:09:459  380 1124 PT WARNING: PTError: 0x80244007
    2015-10-29 09:28:09:459  380 1124 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80244007
    2015-10-29 09:28:09:459  380 1124 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 2633) stopped; does use network; is at background priority
    2015-10-29 09:28:09:459  380 1124 PT   + SyncUpdates round trips: 54
    2015-10-29 09:28:09:459  380 1124 PT WARNING: Sync of Updates: 0x80244007
    2015-10-29 09:28:09:459  380 1124 PT WARNING: SyncServerUpdatesInternal failed: 0x80244007
    2015-10-29 09:28:09:459  380 1124 Agent   * WARNING: Failed to synchronize, error = 0x80244007
    2015-10-29 09:28:09:459  380 1124 Agent   * WARNING: Exit code = 0x80244007
    2015-10-29 09:28:09:459  380 1124 Agent *********
    2015-10-29 09:28:09:459  380 1124 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 37]
    2015-10-29 09:28:09:459  380 1124 Agent *************
    2015-10-29 09:28:09:459  380 1124 Agent WARNING: WU client failed Searching for update with error 0x80244007
    2015-10-29 09:28:09:459  380 1124 IdleTmr WU operation (CSearchCall::Init ID 37, operation # 2541) stopped; does use network; is not at background priority
    2015-10-29 09:28:09:459  380 1124 IdleTmr Decremented idle timer priority operation counter to 1
    2015-10-29 09:28:09:459  380 19c0 AU >>##  RESUMED  ## AU: Search for updates [CallId = {C4B313BC-9EA2-414C-BD7D-508D8D1AC643} ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}]
    2015-10-29 09:28:09:459  380 19c0 AU   # WARNING: Search callback failed, result = 0x80244007
    2015-10-29 09:28:09:459  380 19c0 AU #########
    2015-10-29 09:28:09:459  380 19c0 AU ##  END  ##  AU: Search for updates  [CallId = {C4B313BC-9EA2-414C-BD7D-508D8D1AC643} ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}]
    2015-10-29 09:28:09:459  380 19c0 AU #############
    2015-10-29 09:28:09:459  380 19c0 AU All AU searches complete.
    2015-10-29 09:28:09:459  380 19c0 AU   # WARNING: Failed to find updates with error code 80244007
    2015-10-29 09:28:09:459  380 19c0 AU AU setting next detection timeout to 2015-10-29 13:28:09
    2015-10-29 09:28:09:459  380 19c0 AU Adding timer:
    2015-10-29 09:28:09:459  380 19c0 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-10-29 13:28:09, not idle-only, not network-only
    2015-10-29 09:28:09:459  380 19c0 AU   # Publishing WNF Per user update count event Count: 29 SID {S-1-5-21-1377393817-2111133311-1600358205-500} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
    2015-10-29 09:28:09:459  380 19c0 AU   # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-1377393817-2111133311-1600358205-1004} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
    2015-10-29 09:28:09:459  380 19c0 AU Currently AUX is enabled - so not show any WU Upgrade notifications.

    Thursday, October 29, 2015 11:35 AM

Answers

  • Hi,

    Thank you for your reply.

    Since SFC found the corrupt file but cannot fix, you need to fix it manually. Please check the SFC log by typing the command below in Command Prompt.

    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log  >sfcdetails.txt

    You will see the corrupt file in the log and you can copy the file from another computer and replace the corrupted one. Pay attention to that you would better find a PC with the same operating system.

    Wish you have a nice day.

    Best Regards

    Simon


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

    Friday, November 13, 2015 1:40 AM
    Moderator

All replies

  • Open Start and search for Action Center and open it and under Troubleshoot, click on Windows Update troubleshooter.
    Thursday, October 29, 2015 3:06 PM
  • I ran "Fix problems with Windows Update" and it reported the following:

    Windows Update components must be repaired Fixed

    I then restarted the computer and ran "Check for updates", but it fails with the same error as above.

    Friday, October 30, 2015 7:38 AM
  • Hello,

    i have had update issues with windows 8.1 using the auto update programs and troubleshooting crap... what i found that solved my issue was downloading the update file directly from microsoft (KBwatevernumberyourupdateis) download the appropriate version for your OS and install it thru the kb .exe file ..

    you can also try loading up in safe mode and trying to install updates or run the wizards

    Coroner

    Friday, October 30, 2015 8:57 AM
  • Hi

    How can I see if the error is related to a specific KBnumber?

    Regards,

    Michael

    Friday, October 30, 2015 11:20 AM
  • if you goto

    C:\windows\logs

    you should see a directory called CBS if you open the log file and read the latest date and time entries straight after trying to install the updates it should show you the KB number of the update

    example

    2015-10-30 14:00:58, Info                  CBS    Appl: detect Parent, Package: Package_for_KB3105210~31bf3856ad364e35~amd64~~10.0.1.3, Parent: Microsoft-Windows-CoreCountrySpecificEdition~31bf3856ad364e35~amd64~~10.0.10240.16384, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present

    you can also goto administrator tools from control panel... and then goto event viewer.. and read thru the logs in there

    admin tools > event viewer > applications and services > microsoft > windows> windows updates > operations

    Coroner




    Friday, October 30, 2015 1:22 PM
  • Thanks for helping with this issue.

    This is the contents of the CBS.log. As far as I can see there is no reference to a KBnumber:

    2015-10-30 13:35:15, Info                  CBS    TI: --- Initializing Trusted Installer ---
    2015-10-30 13:35:15, Info                  CBS    TI: Last boot time: 2015-10-30 08:26:09.767
    2015-10-30 13:35:15, Info                  CBS    Starting TrustedInstaller initialization.
    2015-10-30 13:35:15, Info                  CBS    Ending TrustedInstaller initialization.
    2015-10-30 13:35:15, Info                  CBS    Starting the TrustedInstaller main loop.
    2015-10-30 13:35:15, Info                  CBS    TrustedInstaller service starts successfully.
    2015-10-30 13:35:15, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
    2015-10-30 13:35:15, Info                  CBS    Startup processing thread terminated normally
    2015-10-30 13:35:15, Info                  CBS    Starting TiWorker initialization.
    2015-10-30 13:35:15, Info                  CBS    Ending TiWorker initialization.
    2015-10-30 13:35:15, Info                  CBS    Starting the TiWorker main loop.
    2015-10-30 13:35:15, Info                  CBS    TiWorker starts successfully.
    2015-10-30 13:35:15, Info                  CBS    Universal Time is: 2015-10-30 12:35:15.389
    2015-10-30 13:35:15, Info                  CBS    Loaded Servicing Stack v6.3.9600.17709 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17709_none_fa7932f59afc2e40\cbscore.dll
    2015-10-30 13:35:15, Info                  CSI    00000001@2015/10/30:12:35:15.389 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fff04247f19 @0x7fff0e084984 @0x7fff0e0841bb @0x7ff7518ad69a @0x7ff7518adf4f @0x7fff1c782053)
    2015-10-30 13:35:15, Info                  CBS    SQM: Initializing online with Windows opt-in: False
    2015-10-30 13:35:15, Info                  CBS    SQM: Cleaning up report files older than 10 days.
    2015-10-30 13:35:15, Info                  CBS    SQM: Requesting upload of all unsent reports.
    2015-10-30 13:35:15, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
    2015-10-30 13:35:15, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2015-10-30 13:35:15, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
    2015-10-30 13:35:15, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
    2015-10-30 13:35:15, Info                  CBS    NonStart: Set pending store consistency check.
    2015-10-30 13:35:15, Info                  CBS    Session: 30479119_1838473957 initialized by client WindowsUpdateAgent.
    2015-10-30 13:35:28, Info                  CBS    Session: 30479119_1967226026 initialized by client WindowsUpdateAgent.
    2015-10-30 13:35:28, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2015-10-30 13:35:28, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    2015-10-30 13:35:28, Info                  CBS    Session: 30479119_1967379356 initialized by client WindowsUpdateAgent.
    2015-10-30 13:35:28, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2015-10-30 13:35:28, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    2015-10-30 13:37:28, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
    2015-10-30 13:37:28, Info                  CBS    TiWorker signaled for shutdown, going to exit.
    2015-10-30 13:37:28, Info                  CBS    Ending the TiWorker main loop.
    2015-10-30 13:37:28, Info                  CBS    Starting TiWorker finalization.
    2015-10-30 13:37:28, Info                  CBS    Ending the TrustedInstaller main loop.
    2015-10-30 13:37:28, Info                  CBS    Starting TrustedInstaller finalization.
    2015-10-30 13:37:28, Info                  CBS    Ending TrustedInstaller finalization.
    2015-10-30 13:37:28, Info                  CBS    Ending TiWorker finalization.

    Friday, October 30, 2015 2:46 PM
  • KB2919355  - this is a common update that fails alot..

    download here - https://www.microsoft.com/en-au/download/details.aspx?id=42327 foir single update...

    however i recommend this download link instead as it has all the update kb files that is used to get everything up and running

    https://www.microsoft.com/en-us/download/details.aspx?id=42335

    Coroner



    Friday, October 30, 2015 3:48 PM
  • Another step u could take.. scanning the windows files for corruption

    click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, enter the password, or click Allow.

    1. Open a command prompt with administrator privileges.

    2. Copy and Paste > SFC /scannow & hit > Enter.

    Friday, October 30, 2015 4:07 PM
  • Hi

    All the updates were already installed.

    Regards,

    Michael

    Monday, November 2, 2015 7:38 AM
  • Hi

    Running the scan did not fix the problem.

    Regards,

    Michael

    Monday, November 2, 2015 7:39 AM
  • Hi,

    We have found a workaround to solve the error 80244007. You can first follow the steps in the link below to fix it.   

    http://www.mssccm.com/uncategorized/software-updates-colde-80244007-windows-update-ean-into-a-problem/

    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    If it doesn’t work, you can try to reset Windows Updates components to check the issue.

    https://support.microsoft.com/en-us/kb/971058

    Also, for help you better, you can upload your WindowsUpdate.log to us which under the path “C:\Windows”.

    Please kindly tell us if it works.

    Best Regards

    Simon


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

    Tuesday, November 3, 2015 1:55 AM
    Moderator
  • Hi

    The first link does not seem to apply to Windows 8.1. The file %windir%\SysWOW64\CCM\SMSCFGRC.cpl does not exist.

    I have already tried the second link, and it does still not solve the problem.

    The error from the WindowsUpdate.log is shown at the start of this thread.

    Regards,

    Michael

    Wednesday, November 4, 2015 6:40 PM
  • Hi,

    Thank you for your reply.

    Some steps in the first link also applied to Windows 8.1, such as DISM “DISM.exe /Online /Cleanup-image /Restorehealth” command, have you tried this?

    If you use WSUS to get updates, you would better to confirm whether the client connects to the server correctly.

    For another possibility, some anti-virus software or security software will block Windows Update, you can try to disable your Windows firewall and uninstall anti-virus temporarily. Then start the Windows in clean boot mode. After that, check for updates again.

    https://support.microsoft.com/en-us/kb/929135

    Good luck with you.

    Best Regards

    Simon


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

    Thursday, November 5, 2015 1:53 AM
    Moderator
  • Hi

    I have run

    SFC /scannow

    DISM.exe /Online /Cleanup-image /Restorehealth

    The problem is still present. I do not have a WSUS. The computer is a Windows 8.1 MSDN image hosted in Windows Azure. As far as I can see from the WindowsUpdate.log it does connect, but receives some invalid message from the Microsoft server.

    Regards,

    Michael

    2015-10-29 09:28:09:272  380 1124 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 2633; does use network; is at background priority
    2015-10-29 09:28:09:459  380 1124 WS WARNING: Nws Failure: errorCode=0x803d0013
    2015-10-29 09:28:09:459  380 1124 WS WARNING: The body of the received message contained a fault.
    2015-10-29 09:28:09:459  380 1124 WS WARNING: Soap fault info:
    2015-10-29 09:28:09:459  380 1124 WS WARNING: reason: Fault occurred
    2015-10-29 09:28:09:459  380 1124 WS WARNING: code: Client
    2015-10-29 09:28:09:459  380 1124 WS WARNING: detail: <detail><ErrorCode>InvalidParameters</ErrorCode><Message>parameters.OtherCachedUpdateIDs</Message><ID>0377b0ea-e8ea-41e0-a0d0-6ed693cacc47</ID><Method>"</detail">http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"</Method></detail>
    2015-10-29 09:28:09:459  380 1124 WS WARNING: Soap fault detail: errorCode='InvalidParameters', message='parameters.OtherCachedUpdateIDs', id='0377b0ea-e8ea-41e0-a0d0-6ed693cacc47', method='"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"'
    2015-10-29 09:28:09:459  380 1124 WS FATAL: OnCallFailure failed with hr=0X80244007

    Thursday, November 5, 2015 8:35 AM
  • Hi,

    Thank you for your reply.

    However, have you tried my suggestion to uninstall your anti-virus software temporarily and start the Windows in clean boot mode to test the issue?

    If it doesn't work, you can try system restore if you have a point before the issue.

    Wish you have a nice day.

    Best Regards

    Simon


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

    Friday, November 6, 2015 1:19 AM
    Moderator
  • Hi

    I have tried to run Windows Update with Firewall and anti-virus (System Center Protection) turned off, but I get the same error.

    System Restore is not turned on in the Windows 8.1 MSDN image.

    I'm not sure starting in clean boot mode is supported in Windows Azure. I might end up not being able to connect to the VM.

    Regards,

    Michael

    Friday, November 6, 2015 7:31 AM
  • Hi,

    Thank you for your reply.

    Clean boot mode is just disable the 3rd party software, it will not affect your basic use.

    In addition to that, I would like to know if there is any error appeared and cannot be fixed when you run SFC tool. Also, due to you are in the Windows Azure environment, you would better to contact your local administrator to know if any policy or script to prevent Microsoft Store updating.

    Wish you have a nice day.

    Best Regards

    Simon


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

    Tuesday, November 10, 2015 4:46 AM
    Moderator
  • Hi

    I got the following output from SFC /scannow:

    Beginning system scan.  This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.

    However, the word "corrupt" is not present in the CBS.log which is 1.057 KB and ends with:

    2015-11-12 10:57:32, Info                  CSI    00000941 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
    2015-11-12 10:59:39, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
    2015-11-12 10:59:39, Info                  CBS    TiWorker signaled for shutdown, going to exit.
    2015-11-12 10:59:39, Info                  CBS    Ending the TiWorker main loop.
    2015-11-12 10:59:39, Info                  CBS    Starting TiWorker finalization.
    2015-11-12 10:59:39, Info                  CBS    Ending the TrustedInstaller main loop.
    2015-11-12 10:59:39, Info                  CBS    Starting TrustedInstaller finalization.
    2015-11-12 10:59:39, Info                  CBS    Ending TrustedInstaller finalization.
    2015-11-12 10:59:39, Info                  CBS    Ending TiWorker finalization.

    Thursday, November 12, 2015 10:07 AM
  • Hi,

    Thank you for your reply.

    Since SFC found the corrupt file but cannot fix, you need to fix it manually. Please check the SFC log by typing the command below in Command Prompt.

    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log  >sfcdetails.txt

    You will see the corrupt file in the log and you can copy the file from another computer and replace the corrupted one. Pay attention to that you would better find a PC with the same operating system.

    Wish you have a nice day.

    Best Regards

    Simon


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

    Friday, November 13, 2015 1:40 AM
    Moderator