Windows update ошибка 8024000e

Download Windows Speedup Tool to fix errors and make PC run faster

Windows Update Error 0x8024000E is caused when the Windows Update Agent is not updated or has become corrupted. Basically, the update.xml file of a few drivers contains information that cannot be read unless you have updated the Windows Update Agent.

WU_E_XML_INVALID: Windows Update Agent found invalid information in the update’s XML data

0x8024000E

The problem is that while the Windows Update Agent could be updated manually for versions of Windows till Windows 8.1, the same is not true for Windows 11/10. The WU Agent updates automatically.

You can try the following suggestions and see if they help you.

1] Update the Windows Update Agent manually

For versions of Windows up to Windows 8.1/8/7, the procedure to update the Windows Update Agent & the download links has been mentioned on microsoft.com. This would surely resolve your problem. Windows 11/10 users don’t need to update the WU Agent manually.

2] Reset Windows Update Agent

Reset Windows Update Agent to default in Windows 10 and see if that helps you.

3] Use the Windows Update Troubleshooter

The Windows Update troubleshooter could fix this problem in Windows 10. The procedure to run the Windows Update troubleshooter is as follows:

Click on Start > Settings > Updates and Security > Troubleshoot. Then select the Windows Update troubleshooter and run it. Restart the system once done.

4] Reset Windows Update components

It is possible that the Windows Update troubleshooter would fail in fixing the Windows Update Agent. In such a case, the only resolution would be resetting all Windows Update components. This would probably fix the problem when nothing else does.

Hope this helps!

Karan is a B.Tech, with several years of experience as an IT Analyst. He is a passionate Windows user who loves troubleshooting problems and writing about Microsoft technologies.

Источник

Обновлению Windows иногда может препятствовать ошибка с кодом 0x8024000e. Причина — сервис обновления не может прочитать информацию с XML-файла по неизвестным причинам.

0x8024000e

Исправлять сбой необходимо следующим образом:

  1. Отключите все антивирусы. Это касается не только ПО от сторонних разработчиков (к примеру, Avast, Eset, Kaspersky), но и антивируса, идущего в стандартной поставке ОС (Защитник Windows). После выключения — пытайтесь установить апдейты.
  2. Используйте Windows Update troubleshooter. Зажмите клавишу Win и введите в строке поиска troubleshooting. Запустите найденную утилиту. Слева нажмите на «Отобразить все», отыщите и клацните на «Центр обновления». Следуйте инструкциям, которые будут отображаться. Также имеет смысл скачать и запустить это приложение от Microsoft. Его используют для решения неполадок именно сервиса обновления, ответственного за ошибку 0x8024000e.
Источник

Follow the steps below:

  1. Type “services.msc” on keyboard in the search panel.
    2. Open “services.msc” when the search results show up.
    3. Now you will see all Windows services on your system.
    4. Search for “Windows Update”
    5. Right-click the “Windows Update” and then click Stop.

Clean the Windows Update temporary cache folder:

  1. Press Windows + R to launch the Run Command Box.
  2. Type “%windir%\SoftwareDistribution\DataStore” in Run Command Box and click OK.
  3. This will open Windows Explorer on the correct location.
  4. Delete all contents of this folder.

Restart the Windows Update Service again:

  1. Switch back to the windows Services.
  2. Locate Windows Update.
  3. Right-click on it and choose Start.

If the problem still persists, you can run the System File Checker (SFC) utility. This tool will check your filesystem.

  1. Search “cmd” in the search panel.
  2. Open Cmd by right-clicking it and selecting Run as administrator.
  3. Provide the password if prompted.
  4. A black window opens up.
  5. Type sfc/scannow and press Enter.

Come back to the black window after some time and check if the process is finished.
As soon as the SFC process is finished, restart your computer. After the restart, search for Updates again.

Loading…

By Dr. Joseph H Volker

|

On August 8, 2018

   

Источник
  • Remove From My Forums

  • Question

  • Hello, please help me with fixing Windows update on my test servers!

    It all started a week ago, my WS 2008 R2 stopped receiving and searching for updates. I tried many fixes including:

    • WU fixit
    • manually registering dll’s
    • cleaning software distribution etc.
    • sfc /scannow
    • changing Ethernet options (since it’s a VM)

    After all I have decided to reinstall the affected machine. I tried once, no luck (it was in place reinstall with changing windows to windows.old etc.)

    After that I have decided to reinstall it on the new datastore thus, new vhdd. The same, no luck

    Windows is installed from geniue DVD, and activated. 

    Below, log from affected machine:

    2014-05-05	13:28:46:664	 824	90c	AU	## START ##  AU: Search for updates
2014-05-05	13:28:46:664	 824	90c	AU	#########
2014-05-05	13:28:46:680	 824	90c	AU	<<## SUBMITTED ## AU: Search for updates [CallId = {EF20BA31-3F1F-41DD-A056-026F70EDDC93}]
2014-05-05	13:28:46:680	 824	938	Agent	*************
2014-05-05	13:28:46:680	 824	938	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2014-05-05	13:28:46:680	 824	938	Agent	*********
2014-05-05	13:28:46:680	 824	938	Agent	  * Online = Yes; Ignore download priority = No
2014-05-05	13:28:46:680	 824	938	Agent	  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-05-05	13:28:46:680	 824	938	Agent	  * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2014-05-05	13:28:46:680	 824	938	Agent	  * Search Scope = {Machine}
2014-05-05	13:28:46:680	 824	938	Setup	Checking for agent SelfUpdate
2014-05-05	13:28:46:680	 824	938	Setup	Client version: Core: 7.6.7600.256  Aux: 7.3.7600.16385
2014-05-05	13:28:46:711	 824	938	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:
2014-05-05	13:28:46:820	 824	938	Misc	 Microsoft signed: Yes
2014-05-05	13:29:00:845	 824	938	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:
2014-05-05	13:29:00:860	 824	938	Misc	 Microsoft signed: Yes
2014-05-05	13:29:00:860	 824	938	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-05-05	13:29:00:876	 824	938	Misc	 Microsoft signed: Yes
2014-05-05	13:29:03:746	 824	938	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-05-05	13:29:03:746	 824	938	Misc	 Microsoft signed: Yes
2014-05-05	13:29:03:762	 824	938	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-05-05	13:29:03:778	 824	938	Misc	 Microsoft signed: Yes
2014-05-05	13:29:03:793	 824	938	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-05-05	13:29:03:809	 824	938	Misc	 Microsoft signed: Yes
2014-05-05	13:29:03:918	 824	938	Setup	Determining whether a new setup handler needs to be downloaded
2014-05-05	13:29:03:918	 824	938	Setup	SelfUpdate handler is not found.  It will be downloaded
2014-05-05	13:29:03:934	 824	938	Setup	Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-05-05	13:29:03:980	 824	938	Setup	Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-05-05	13:29:03:980	 824	938	Setup	Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-05-05	13:29:04:043	 824	938	Setup	Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is applicable but is already staged; it will not be downloaded.
2014-05-05	13:29:04:043	 824	938	Setup	Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-05-05	13:29:04:121	 824	938	Setup	Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-05-05	13:29:04:121	 824	938	Setup	SelfUpdate check completed.  SelfUpdate is required.
2014-05-05	13:29:04:121	 824	938	Setup	Downloading binaries required for SelfUpdate
2014-05-05	13:29:04:121	 824	938	Setup	Downloading SelfUpdate handler WuSetupHandler.cab from http://download.windowsupdate.com/v9/1/windowsupdate/b/selfupdate/WSUS3/x64/Vista
2014-05-05	13:29:04:121	 824	938	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupHandler.cab:
2014-05-05	13:29:04:152	 824	938	Misc	 Microsoft signed: Yes
2014-05-05	13:29:04:152	 824	938	Setup	Successfully downloaded SelfUpdate handler
2014-05-05	13:29:04:152	 824	938	Setup	Download of SelfUpdate binaries succeeded
2014-05-05	13:29:04:152	 824	938	Setup	Starting agent SelfUpdate
2014-05-05	13:29:04:152	 824	938	Setup	Skipping installation because no critical packages are ready to install.
2014-05-05	13:29:04:402	 824	938	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:
2014-05-05	13:29:04:417	 824	938	Misc	 Microsoft signed: Yes
2014-05-05	13:29:04:433	 824	938	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:
2014-05-05	13:29:04:433	 824	938	Misc	 Microsoft signed: Yes
2014-05-05	13:29:04:433	 824	938	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
2014-05-05	13:29:04:433	 824	938	PT	  + ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL = https://update.microsoft.com/v6/ClientWebService/client.asmx
2014-05-05	13:29:06:757	 824	938	PT	WARNING: Cached cookie has expired or new PID is available
2014-05-05	13:29:06:835	 824	938	PT	WARNING: PTWarn: Anonymous plug-in skipped for WU
2014-05-05	13:29:57:551	 824	938	PT	WARNING: PopulateDataStore failed: 0x8024000e
2014-05-05	13:29:57:551	 824	938	PT	WARNING: Sync of Updates: 0x8024000e
2014-05-05	13:29:57:551	 824	938	PT	WARNING: SyncServerUpdatesInternal failed: 0x8024000e
2014-05-05	13:29:57:551	 824	938	Agent	  * WARNING: Failed to synchronize, error = 0x8024000E
2014-05-05	13:29:57:551	 824	938	Agent	  * WARNING: Exit code = 0x8024000E
2014-05-05	13:29:57:551	 824	938	Agent	*********
2014-05-05	13:29:57:551	 824	938	Agent	**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2014-05-05	13:29:57:551	 824	938	Agent	*************
2014-05-05	13:29:57:551	 824	938	Agent	WARNING: WU client failed Searching for update with error 0x8024000e
2014-05-05	13:29:57:707	 824	254	AU	>>##  RESUMED  ## AU: Search for updates [CallId = {EF20BA31-3F1F-41DD-A056-026F70EDDC93}]
2014-05-05	13:29:57:707	 824	254	AU	  # WARNING: Search callback failed, result = 0x8024000E
2014-05-05	13:29:57:707	 824	254	AU	  # WARNING: Failed to find updates with error code 8024000E
2014-05-05	13:29:57:707	 824	254	AU	#########
2014-05-05	13:29:57:707	 824	254	AU	##  END  ##  AU: Search for updates [CallId = {EF20BA31-3F1F-41DD-A056-026F70EDDC93}]
2014-05-05	13:29:57:707	 824	254	AU	#############
2014-05-05	13:29:57:707	 824	254	AU	Successfully wrote event for AU health state:0
2014-05-05	13:29:57:707	 824	254	AU	AU setting next detection timeout to 2014-05-05 16:29:57
2014-05-05	13:29:57:707	 824	254	AU	Setting AU scheduled install time to 2014-05-06 01:00:00
2014-05-05	13:29:57:707	 824	254	AU	Successfully wrote event for AU health state:0
2014-05-05	13:29:57:707	 824	254	AU	Successfully wrote event for AU health state:0
2014-05-05	13:29:57:722	 824	938	Report	REPORT EVENT: {F9FA331A-4B13-41A9-8A0F-8CB00FD746BE}	2014-05-05 13:29:04:152+0200	1	162	101	{61CA813A-7585-442E-A66B-B0D15CE6BDC0}	1	0	SelfUpdate	Success	Content Download	Download succeeded.
2014-05-05	13:29:57:722	 824	938	Report	CWERReporter finishing event handling. (00000000)
2014-05-05	13:30:02:558	 824	938	Report	REPORT EVENT: {C660EC65-02E6-4EDD-A123-3701C380D966}	2014-05-05 13:29:57:551+0200	1	148	101	{00000000-0000-0000-0000-000000000000}	0	8024000e	AutomaticUpdates	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x8024000e.
2014-05-05	13:30:02:636	 824	938	Report	CWERReporter::HandleEvents - WER report upload completed with status 0x8
2014-05-05	13:30:02:636	 824	938	Report	WER Report sent: 7.6.7600.256 0x8024000e 00000000-0000-0000-0000-000000000000 Scan 101 Unmanaged
2014-05-05	13:30:02:636	 824	938	Report	CWERReporter finishing event handling. (00000000)

    I also downloaded and installed Windows Update rediness tool Feb 2014 and WSUS Client updated itself but after restart those updates aren’t visible in history anymore. 

    • Edited by

      Monday, May 5, 2014 1:03 PM

Answers

  • Ok I have figured it out!

    It was one of the hdd that was failing. This, in combination with disabling IPv6 on the host gave that strange errors.

    After moving affected VMs to other storage and enabling IPv6 all problems are gone. ALL versions of Windows update themselves without any problems. 

    Now, I will rebuild a test WSUS and check if its operating normally.

    Thank you for your efforts and help!

    Regards,

    Milosz Engel

    • Marked as answer by
      Milosz Engel
      Wednesday, May 14, 2014 3:02 PM

Источник

In this tutorial, we have outlined the prime reasons that may cause the update error 0x8024000E on a Windows 10 PC along with ways to counter them. So, if you are getting this bug while upgrading your operating system to its next available version, read this post in detail. 

The error 0x8024000E usually occurs because of Windows Image becoming corrupted, missing DLL files, or due to partially/fully filled update folders.

If you are getting this error on Windows 8/8.1, you may get the following additional information – 

WU_E_XML_INVALID: Windows Update Agent found invalid information in the update’s XML data

To fix this, all you require is to manually download and update the Windows Update Agent.

Since the Windows Update Agent upgrades automatically on Windows 10, what you can really do is try out the below workarounds – 

  • Run Windows Update Troubleshooter
  • Reset Winsock
  • Clear Windows Update Download path
  • Reset Windows Update components

Here’s how to get rid of the error code 0x8024000E while upgrading Windows 10 to its next available build version –

1] Run Windows Update Troubleshooter

This is by far the best way to find the exact cause that might have prevented you from updating your operating system. To use this in-built tool, follow the below guideline –

  • First of all, press Win + I to enter the Settings app.
  • Select Update & Security > Troubleshoot.
  • Jump to the right side and click “Additional troubleshooters“.
  • On the next screen, click to expand the Windows Update section and hit Run the troubleshooter. 

Windows Update Troubleshooter

  • This tool will then start scanning the entire PC for possible bugs/errors. In case of finding the main culprit, there appears a detailed description of fixing the issue at hand. 

However, if this doesn’t reveal any anomaly, try out the next set of solutions discussed below –

2] Reset Winsock to Fix Update Error Code 0x8024000E

In case this error is a result of some missing DLL files, you may solve it by simply resetting Winsock. To do so, use these steps –

  • Launch Command Prompt as an Administrator.
  • Copy/paste the below code and press Enter –

netsh winsock reset

  • If you want to generate a log file of all recent changes to the computer, run this command –

netsh winsock reset c:\winsocklog.txt

  • Let the Command Prompt reset your operating system. When it does, restart your PC to incorporate the above changes. 

3] Clear Windows Update Download path

Clearing the Windows Update download path may also provide you an edge over solving the update error 0x8024000E. Here’s how to proceed –

Imp: As this solution involves the registry editor, make sure that you have already created a backup image of your entire registry. 

  • Press the Windows key and R altogether.

  • Type “regedit”, and hit OK.
  • Using the left-side navigation, reach out to the location – 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

  • On the right pane, look for the following keys – WUServer and WIStatusServer. 

Quick Note: If they are not listed here, skip this solution and try out the last workaround. 

  • Right-click on each one of these entries and select the delete option.

  • Lastly, restart your computer so that changes made come into effect. 

4] Reset Windows Update components

Windows 10 gets a security update every second Tuesday of a month. Apart from this, there come several other cumulative patches that you may or may not install on your computer as they are optional in nature. Each time you upgrade your operating system, Windows 10 downloads and saves a copy in its cache folder. 

Since you are no longer able to update your PC normally, there is a possibility that the update folders have become corrupted. You may fix this by simply renaming these folders to “FolderName.old“. Before proceeding to actually renaming the cache folders, make sure that you have stopped the essential services that are required for a smooth Windows 10 update. Here’s how to perform this task –

  • Open Services window – Press Win + R, type “services.msc“, and press Enter.
  • The services that require stopping are – Windows Update, BITS, Wuauserv, and Cryptographic services. 

Update Error 0x8024000E

Now, that you have stopped these services, reach out to the below location, and rename the cache folders.

  • C:/Windows – SoftwareDistribution
  • C:/Windows/system32 – Catroot2

After successfully renaming the above two folders, go back to the services window, and restart the services that you stopped earlier. 

In certain cases, you may require to fix the missing DLL files on your device. Here’s how to re-register BITS or Windows Update DLL files using Command Prompt.

Источник

Понравилась статья? Поделить с друзьями:
  • Windows xp ошибка часов гугл хром как убрать
  • Windows update ошибка 666
  • Windows выдает ошибку при включении
  • Windows update выдает ошибку
  • Windows xp система восстановлена после серьезной ошибки