Share via

Error 8007000e windows update.

Anonymous
2016-10-29T13:27:17+00:00

I have tried every option posted in here. this is the latest error log, win 7 pro new install after windows update agent I get this error log is posted below

2016-10-29          07:29:46:804       996        70c         PT             + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx

2016-10-29          07:30:09:954       996        70c         PT           WARNING: PopulateDataStore failed: 0x8007000e

2016-10-29          07:30:09:954       996        70c         PT           WARNING: Sync of Updates: 0x8007000e

2016-10-29          07:30:09:954       996        70c         PT           WARNING: SyncServerUpdatesInternal failed: 0x8007000e

2016-10-29          07:30:09:954       996        70c         Agent      * WARNING: Failed to synchronize, error = 0x8007000E

2016-10-29          07:30:09:954       996        70c         Agent      * WARNING: Exit code = 0x8007000E

2016-10-29          07:30:09:954       996        70c         Agent    *********

2016-10-29          07:30:09:954       996        70c         Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]

2016-10-29          07:30:09:954       996        70c         Agent    *************

2016-10-29          07:30:09:954       996        70c         Agent    WARNING: WU client failed Searching for update with error 0x8007000e

2016-10-29          07:30:10:095       996        644         AU          >>##  RESUMED 

AU: Search for updates [CallId = {49710D9D-A631-4E9F-9B67-9D614AC951E5}]

2016-10-29          07:30:10:095       996        644         AU            # WARNING: Search callback failed, result = 0x8007000E

2016-10-29          07:30:10:095       996        644         AU            # WARNING: Failed to find updates with error code 8007000E

2016-10-29          07:30:10:095       996        644         AU          #########

2016-10-29          07:30:10:095       996        644         AU          ##  END  ##  AU: Search for updates [CallId = {49710D9D-A631-4E9F-9B67-9D614AC951E5}]

2016-10-29          07:30:10:095       996        644         AU          #############

2016-10-29          07:30:10:095       996        644         AU          Successfully wrote event for AU health state:0

2016-10-29          07:30:10:110       996        644         AU          AU setting next detection timeout to 2016-10-29 17:30:10

2016-10-29          07:30:10:110       996        644         AU          Setting AU scheduled install time to 2016-10-30 08:00:00

2016-10-29          07:30:10:110       996        644         AU          Successfully wrote event for AU health state:0

2016-10-29          07:30:10:110       996        644         AU          Successfully wrote event for AU health state:0

2016-10-29          07:30:10:110       996        70c         Report  CWERReporter finishing event handling. (00000000)

2016-10-29          07:30:14:962       996        70c         Report  REPORT EVENT: {117038AC-1B0E-435E-A4F0-FC609D66B878}                2016-10-29 07:30:09:954-0500     1              148         101         {00000000-0000-0000-0000-000000000000}           0                8007000e             AutomaticUpdates          Failure  Software Synchronization            Windows Update Client failed to detect with error 0x8007000e.

2016-10-29          07:30:14:978       996        70c         Report  CWERReporter::HandleEvents - WER report upload completed with status 0x8

2016-10-29          07:30:14:978       996        70c         Report  WER Report sent: 7.6.7600.320 0x8007000e 00000000-0000-0000-0000-000000000000 Scan 101 Unmanaged

2016-10-29          07:30:14:978       996        70c         Report  CWERReporter finishing event handling. (00000000)

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2016-10-29T21:04:00+00:00

    Please provide more information to enable your problem to be diagnosed.

    Please restart your computer and allow 20 minutes for the system to run before uploading information. When examining Event Viewer log files many, not all, problems show in the period immediately after the computer has been booted.

    Please provide a copy of your System Information file. Type System Information in the Search Box above the start Button and press the ENTER key (alternative is Select Start, All Programs, Accessories, System Tools, System Information). Select File, Export and give the file a name noting where it is located. Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload the file to your OneDrive, share with everyone and post a link here. If the report is in a language other than English, please state the language.

    Please upload and share with everyone a fresh copy of your System log from your Event Viewer to your One Drive and post a link here. It helps to avoid confusion if you remove any earlier copies of the log files from your OneDrive.

    To access the System log select Start, Control Panel, Administrative Tools, Event Viewer, from the list in the left side of the window expand Windows Logs and select System. Place the cursor on System, select Action from the Menu and Save All Events as (the default evtx file type) and give the file a name. Do not provide filtered files. Do not place the cursor in the list of reports before selecting Action from the menu. Do not clear logs whilst you have a continuing problem.

    For help with OneDrive see paragraph 9.3:

    http://www.gerryscomputertips.co.uk/MicrosoftCommunity1.htm

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments