Windows Update Error: 80073AA2

Have you tried?

This guide is specific for for the error code 80073AA2 however, even in some cases this guide does not help. Please make sure you’ve read Windows Update is causing Problems first and tried those steps.

[symple_button url=”” color=”grey” size=”default” border_radius=”3px” target=”self” rel=”” icon_left=”” icon_right=””]Read it here[/symple_button]

Resolving the error.

[symple_box color=”red” fade_in=”false” float=”center” text_align=”left” width=””] To resolve this problem adjustments have to be made to the Windows Registry, make sure you have a restore point or any other recovery method before executing these steps.
[/symple_box] [symple_box color=”yellow” fade_in=”false” float=”center” text_align=”left” width=””] DISCLAIMER: This method has been tried and tested on a Virtual Machine and worked without any major effects upon the stability of the system. However removing Windows keys from the registry is never without a risk. Please read our Disclaimer and Terms and Conditions

1. Press the Windows + R key at the same time, now type regedit in the Run window and hit OK.

Run: Regedit
Run: Regedit

2. Now Unfold HKEY_LOCAL_MACHINE, then unfold SOFTWARE, then unfold Microsoft, then Windows, then CurrentVersion, then right-click WINEVT

WINEVT: Delete
WINEVT: Delete

3. Then choose Delete and confirm your action by clicking on YES.

4. Reboot your device and try to run Windows Update again.

About the Author

2014, 2015, 2016, 2017 and 2018 Microsoft Most Valuable Professional Windows
Yuri specializes in troubleshooting (crash analysis and devices), system resource utilisation and system performance. He is also very interested in Customer Security. Yuri can be found as Windows Community Moderator and Wiki Author on Microsoft Answers and is active on different communities all across the web.


  1. This not only fixed the issues with Windows Update but an issue I was having with the task scheduler as well. Keep up the good work!

  2. I have to say I’m impressed – I never would have thought of deleting components of the Windows Event Log would solve Windows Update errors. I delete the regkey with some trepidation after making a backup of it, and then asked the user I was supporting to report back if the Update kept reverting back during reboots.

    It wasn’t anymore! I was actually shocked this worked, but I’ll definitely keep this bookmarked for the next time I run into 80073aa2.

  3. Thank you so much, I had tried all the other solutions it it was yours that finally worked for me. You have no idea how much I appreciate your solution.

  4. -Running Windows 8.0 (9200) on HP dv1325ea-
    This also solved the error in question on my old laptop (for update KB3000061), also I found that Resetting IE also somehow solved some other WU Error Codes I was getting (possibly 800F0992). As an extra safety step, instead of deleting WINEVT, I renamed it to 1WINEVT1 so it would be easily restorable if needed by renaming it back. Those that don’t want to leave duff registry entrys laying around, regedit.exe has an Export option to backup a specified reg entry to a desired location. Then you can delete the actual entry. It can then be restored by double clicking the file that you exported which will merge it back into the registry and it shouldn’t harm any subsequent entrys that may have been added automatically in the mean time. (ie. if WINEVT has recreated itself, it shouldn’t be a problem, they will merge. It may not even need to be restored but the safety net can be there anyhow).

    If I may leave you with a couple of other possible repair methods (I’ve not had a chance to check if they are covered else where on the site). Load a Command Prompt (with Admin rights) to execute the maintenance tasks below:

    DISM.exe /Online /Cleanup-image /Restorehealth
    sfc /scannow

  5. I have implemented your solution to solve update errors and it seems to work. Many thanks. One question, though, what facilities, if any, have I lost by deleting this item?

    1. Hello Crowther

      You should see no impact from this if you restored it from the Virus Vault. 🙂 Thank you for your feedback always nice to hear if people’s problem are solved

Leave a Reply

Your email address will not be published. Required fields are marked *