Friday, October 9, 2015

Some clients not updating, reporting 8007000E error in WindowsUpdate.log

At customer location workstations doesn't install any updates anymore. This because of the following error in windowsupdate.log: COMAPI WARNING: ISusInternal::GetUpdateMetadata2 failed, hr=8007000E. For it seems this we be only the case on Windows 7 x86 systems. Installing a new hotfix must do the trick. Let's have a look at that one.
 
The issue is discussed on Microsoft TechNet too:
Some Clients Not Updating. Reporting "Compliant." hr=8007000E Error in WindowsUpdate.log
 
For it seems there is an issue in which the Windows Update Client displays an out-of-memory error during the scan operation (0x8007000E) on systems that have small amounts of physical RAM. Therefore a hotfix is needed.
 
The hotfix (KB3050265) can be download here:
New Windows Update Client for Microsoft Windows 7 Available

After installation (and a required reboot) there was still an error however. Therefore we started the following commands (in an elevated command prompt) to make it functional again:
Net stop wuauserv
Sc config wuauserv type= own
Net start wuauserv

After that everything started to work again! :)

Update 23-11: (by Trevor Jones)
Just FYI, KB3050265 has been superseded by several updates. The latest WU client is http://support.microsoft.com/en-us/kb/3102810 and fixes the same plus additional issues :)
Posted by Henk Hoogendoorn at 4:42 PM
Labels: , , , , , ,

145 comments:

  1. UnknownNovember 19, 2015 at 4:48 AM

    After the reboot how do I start the commands you mentioned?

    ReplyDelete
    Replies
    1. Henk HoogendoornNovember 20, 2015 at 7:47 AM

      Within an elevated command prompt. Thanks for mentioning.

      Delete
  2. Trevor JonesNovember 20, 2015 at 3:13 PM

    Just FYI, KB3050265 has been superseded by several updates. The latest WU client is http://support.microsoft.com/en-us/kb/3102810 and fixes the same plus additional issues :)

    ReplyDelete
    Replies
    1. Henk HoogendoornNovember 23, 2015 at 10:00 PM

      Thanks for mentioning. Will update the blogpost!

      Delete
    2. AnonymousApril 19, 2016 at 4:04 AM

      Thank you, thank you, Trevor Jones.

      Delete
  3. DiegoJanuary 20, 2016 at 2:57 AM

    I test in a client environment and the last KB Works perfect for the Windows 7 X86 machines, thanks for the blog..

    ReplyDelete
  4. UnknownJanuary 28, 2016 at 8:17 PM

    This worked for me! Thk. Felipe (BR)

    ReplyDelete
  5. AnonymousJanuary 28, 2016 at 8:20 PM

    This worked fine. Thank you! Felipe (BRAZIL)

    ReplyDelete
  6. UnknownJanuary 31, 2016 at 1:19 PM

    Thank you, I've been looking all over the place for a solution like this!

    ReplyDelete
  7. Paul H.February 1, 2016 at 1:14 PM

    Thanks, Henk. However, still failing :-( Error message on attempted WU is 8007000E - after about 20 minutes of "Checking for updates...."

    I have manually applied http://support.microsoft.com/en-us/kb/3102810 - and stopped and restarted the WU service - as admin; but still no luck.

    Strangely, the machine worked fine 11 months ago when I built it, and it automatically applied all the necessary, relevant updates at the time...

    The only gremlin last week was that CMOS / BIOS had lost the time after 11 months, and had to be reset - but everything else works OK...

    Perhaps I'm just too optimistic using this hardware configuration?

    Paul H.(W7 Home Premium, SP1, Processor 1.5GHz, 2.00 Gb RAM)

    ReplyDelete
  8. oleredeyeFebruary 1, 2016 at 2:07 PM

    Thanks, Henk. However, still failing :-( Error message on attempted WU is 8007000E - after about 20 minutes of "Checking for updates...."

    I have manually applied http://support.microsoft.com/en-us/kb/3102810 - and stopped and restarted the WU service - as admin; but still no luck.

    Strangely, the machine worked fine 11 months ago when I built it, and it automatically applied all the necessary, relevant updates at the time...

    The only gremlin last week was that CMOS / BIOS had lost the time after 11 months, and had to be reset - but everything else works OK...

    Perhaps I'm just too optimistic using this hardware configuration?

    oleredeye - Paul H.(W7 Home Premium, SP1, Processor 1.5GHz, 2.00 Gb RAM)

    ReplyDelete
  9. AnonymousFebruary 3, 2016 at 8:50 AM

    kb3102810 worked for me as well, thanks!

    ReplyDelete
  10. AnonymousFebruary 11, 2016 at 8:16 PM

    Hey Henk, after several attempts to solve my problem of not be able to have the Windows Update to work, I have finally get it working. Thanks for your very professional article. From Portugal

    ReplyDelete
    Replies
    1. Henk HoogendoornFebruary 17, 2016 at 4:55 PM

      My pleasure and thanks for comment. Glad that it works for you too!

      Delete
  11. UnknownFebruary 18, 2016 at 11:10 AM

    Wow thank you Henk for this usefull info, i was struggling for about a week with updates. nothing seem to work except this post

    ReplyDelete
  12. Gary HalversonFebruary 19, 2016 at 6:32 PM

    Great info! Works! Thx!

    ReplyDelete
  13. UnknownFebruary 24, 2016 at 8:26 PM

    This was super helpful, I had 2 machines with same issue, this solved both of them, thanks!!

    ReplyDelete
  14. UnknownFebruary 25, 2016 at 1:37 PM

    Fantastic! I'd been scratching my head trying to sort this out. Installing the 3102810 fixed it. Many thanks guys.

    ReplyDelete
  15. AnonymousFebruary 25, 2016 at 6:41 PM

    Thanks a lot, it has worked for me too !

    Thx !

    ReplyDelete
  16. AngelFebruary 26, 2016 at 11:15 AM

    Thanks a lot, it has worked for me too! After three days of searching and trying I finally found this solution!!

    ReplyDelete
  17. AnonymousFebruary 26, 2016 at 7:44 PM

    After two days of attempting to correct this problem, finally a solution. Thanks so much!!

    ReplyDelete
  18. UnknownMarch 1, 2016 at 10:51 AM

    Thanks very much for this, seems to have resolved my issues.

    ReplyDelete
  19. UnknownMarch 3, 2016 at 3:59 AM

    Gracias por la documentación, me es de mucha utilidad

    ReplyDelete
  20. AnonymousMarch 5, 2016 at 11:52 AM

    THANK YOUUUUU !! I have win7SP1
    With this problem I tried very much solutions and any work. I tried your The hotfix (KB3050265) and not work, I format the PC and I get the error, I put your The hotfix (KB3050265) and not work.
    I put the Update 23-11: (by Trevor Jones) and WORK FINE THANK YOU VERY MUCH Fabian .C.

    ReplyDelete
  21. AnonymousMarch 7, 2016 at 5:42 PM

    You would think Microsoft Windows Support team would be aware of this problem and it's solution by now. I had their technician on my computer for 4 hors on last Friday, and 3 this morning before elevating to second tier support. While waiting for second tier I installed the hotfix and it is now installing another 192 updates. We will see if windows update continues to function when this is completed. The last tech I spoke to said because it is Win 7 (an old operating system) I would not continue to get updates. She had nothing to say when I told her my other 38 Win7 machines were still updating just fine.

    ReplyDelete
  22. ClareSnyderMarch 7, 2016 at 6:10 PM

    Why do Microsoft Windows Support staff know about this???? I've wasted 2 half days with their support people logged onto my computer trying to fix this very issue

    ReplyDelete
  23. AnonymousMarch 9, 2016 at 4:52 PM

    Why is it my experience that a windows question is most likely to be answered by non-microsoft websites?

    Thanks so much (x3), Henk!
    Tim

    ReplyDelete
  24. AnonymousMarch 11, 2016 at 12:30 AM

    Henk, thanks for the post, it fixed my issue

    ReplyDelete
  25. AnonymousMarch 16, 2016 at 12:37 PM

    Mi PC tardaba mucho tiempo en hacer Windows Update y terminaba con el error 8007000e. Yo hice lo que indica el artículo y ha ido todo bien. Muchas gracias
    Jose M. Carralero

    ReplyDelete
  26. hurikanemanMarch 17, 2016 at 7:20 AM

    Thank you! this worked.

    ReplyDelete
  27. AnonymousMarch 18, 2016 at 2:54 PM

    It worked for me too, after three full reinstallation of Win 7, always stuck with Windows update errors after the first Service Pack update.
    Really many, many thanks, you're very generous to share knowledge like this.

    ReplyDelete
  28. AnonymousMarch 21, 2016 at 7:38 PM

    Thanks. You're a genius. MS should be paying you

    ReplyDelete
  29. Alescito cpMarch 22, 2016 at 9:08 AM

    Thx so much, it worked 4 me!!!! :)

    ReplyDelete
  30. Alescito cpMarch 22, 2016 at 9:09 AM

    Thx, it worked 4 me :)

    ReplyDelete
  31. TommyMarch 23, 2016 at 1:11 AM

    Hi mate, just worked for me and I can now download all the updates. I owe you a pint! Many thanks, Tommy in Ireland

    ReplyDelete
  32. AnonymousMarch 23, 2016 at 3:06 PM

    Hi Henk,

    Was really struggling with this one but your info above helped me as well. Great job, big thanks from Belgium !

    BR//Bart

    ReplyDelete
    Replies
    1. Henk HoogendoornMarch 24, 2016 at 7:01 PM

      Great to hear that! Glad it works for you too.

      /Henk

      Delete
  33. MartinMarch 27, 2016 at 1:24 PM

    Huge huge sigh of relief when this worked for me. Thank you very very much Henk! I was banging my head on a wall for two days over this.

    ReplyDelete
  34. AnonymousMarch 28, 2016 at 2:12 PM

    Hello,

    Thank you so so so much for this.
    Working for me.

    ReplyDelete
  35. UnknownMarch 29, 2016 at 6:26 PM

    Thanks for the info it helped me as well :), when it first was stuck in loop mode when I was trying to get updates.

    ReplyDelete
  36. AnonymousMarch 30, 2016 at 8:32 AM

    Thank you! That worked. I tried to found solution many days. Nothing works but finally this hotfix maked windows update working again.

    ReplyDelete
  37. AnonymousMarch 30, 2016 at 10:07 AM

    Finally! Thanks so much Henk. This has been bothering me for months. All good now. Only problem is I have 269 updates to install now ;)

    ReplyDelete
  38. AnonymousMarch 31, 2016 at 3:36 PM

    Works! Thnx!

    ReplyDelete
  39. UnknownApril 1, 2016 at 7:53 AM

    Thank you Henk, u r a genius...the hotfix and cmd solutions works perfectly for me... cheers.

    ReplyDelete
  40. AnonymousApril 2, 2016 at 11:40 PM

    Hi Henk,
    I just wanted to thank you for this tip. The hotfix and command lines worked perfectly and solved my issue! Thank you for sharing your knowledge!
    Cheers from Brussels (Belgium)

    ReplyDelete
  41. RengowApril 5, 2016 at 3:01 AM

    Thank you so much!!! You save me a lot of hours! :-)
    Cheers from Argentina.

    ReplyDelete
  42. Ken SmelserApril 5, 2016 at 10:08 PM

    Worked Great! Thanks

    ReplyDelete
  43. UnknownApril 10, 2016 at 1:56 AM

    Struggling for weeks on error 8007000E which occurred immediately after a fresh W7 install, SP1 applied and then windows update dowloading an updated windows update client.

    Tried the KB3102810, still no good.

    Then tried Henk's commands.

    Net stop wuauserv
    Sc config wuauserv type= own
    Net start wuauserv

    Finally, now have 228 updates to install.

    Cheers

    ReplyDelete
  44. AnonymousApril 11, 2016 at 2:07 PM

    This worked!!! Thank you! :-)

    ReplyDelete
  45. lodestarApril 12, 2016 at 7:21 PM

    Wooooo！！！it works！！Great!!

    ReplyDelete
  46. Lucas KuhnApril 13, 2016 at 5:15 AM

    Really needed to leave a comment here... I have tinkered with this issue for a while and Microsoft's forums and personnel didn't know jack about it.

    Thank you so much, don't know how this KB isn't mentioned as a fix on ANY of their responses to this issue...

    ReplyDelete
    Replies
    1. Henk HoogendoornApril 14, 2016 at 1:40 PM

      Great to hear that! Glad it works for you too.

      /Henk

      Delete
  47. JAVHApril 17, 2016 at 2:40 AM

    Thanks a lot! I did this problem with 2 PCs, i reinstalled and got the same problem, I did think was my install disc are damaged, With update 3102810 work like a charm.

    Thanks :)

    ReplyDelete
  48. AnonymousApril 17, 2016 at 9:08 PM

    Hi, from Lisbon, Portugal.

    I only resolved the dificulty after install the KB3050265, and has been works fine!! :)
    thanks

    RogerPZ

    ReplyDelete
  49. AnonymousApril 20, 2016 at 6:20 AM

    @Henk, I've tried everything from the above link and steps, still not working for me.

    Thank you,

    ReplyDelete
    Replies
    1. Henk HoogendoornApril 20, 2016 at 9:16 PM

      Did you check this too?

      Net stop wuauserv
      Sc config wuauserv type= own
      Net start wuauserv

      Delete
  50. AnonymousApril 20, 2016 at 10:51 AM

    well done everyone...worked for me too

    ReplyDelete
  51. AnonymousApril 22, 2016 at 9:57 AM

    Thank you Henk from IL, cheers

    ReplyDelete
  52. AnonymousApril 24, 2016 at 1:29 AM

    Thank you, i was facing the same problem and that did the trick for me! ;)

    ReplyDelete
  53. เกษตร5G ผลผลิตดีด้วย ยูนิไลฟ์April 25, 2016 at 7:21 PM

    After installing kb3102810 it can be updated as normal. Thank you very much

    ReplyDelete
  54. UnknownApril 27, 2016 at 9:13 PM

    Hi Henk,

    I have 3 computers that are getting the 8007000E error and they are all windows 7 professional 32 bit with 4GB of memory.

    I tried installing the KB3050265 and the KB3102810. After a reboot I ran these 3 commands in an elevated cmd prompt.

    Net stop wuauserv
    Sc config wuauserv type= own
    Net start wuauserv

    Then I tried running windows update again and still got the 8007000E error.

    Is there anything else I can try or are there any new KB updates I can install to get past this?

    Thanks,

    Jason

    ReplyDelete
    Replies
    1. Henk HoogendoornApril 28, 2016 at 4:49 PM

      Just install KB3102810, Run CMD as administrator, typed net stop wuauserv, sc config wuauserv type= own, net start wuauserv. Exit CMD and start Windows Update again?

      Delete
  55. AnonymousApril 28, 2016 at 5:48 AM

    Thanks so much for this fix. Been fighting with this for days. Updates are pouring in now...

    ReplyDelete
  56. AnonymousApril 28, 2016 at 3:58 PM

    Thank you so much for this! Ive been trying to update for 5 days & tried numerous solutions from the web, and this worked first time.

    I installed KB3102810, ran cmd as administrator, typed net stop wuauserv, then sc config wuauserve type = own, then net start wuauserve. Exited cmd and ran the update, and it came up immediately with 213 important and 44 optional, so a BIG BIG thank you

    ReplyDelete
    Replies
    1. Henk HoogendoornApril 28, 2016 at 4:50 PM

      Great to hear that! Glad it works for you too.

      /Henk

      Delete
  57. Henk HoogendoornApril 28, 2016 at 4:46 PM

    Thanks for comments everyone! Happy that so much people are helped with this solution. Keep the comments going ;)

    ReplyDelete
  58. AnonymousMay 1, 2016 at 1:29 PM

    KB3102810 and the three lines of commands and go back to work!!!
    Thank you very much from Spain.
    Greetings.

    ReplyDelete
  59. 星光May 8, 2016 at 4:05 PM

    Hello Henk, Thank you very much...you really safe my life.Your method was worked for me .

    ReplyDelete
  60. 星光May 8, 2016 at 4:06 PM

    Hello Henk, Your method is really worked for me !!! Thank you very much.

    ReplyDelete
  61. AnonymousMay 11, 2016 at 4:46 PM

    Thank you, it worked for me (fresh 32b pro SP1 install)
    You saved me lot of time !!!!

    ReplyDelete
  62. UnknownMay 12, 2016 at 9:32 AM

    Worked as charm, regards from Serbia. Thank you very much Henk.

    ReplyDelete
  63. RobertoUKMay 14, 2016 at 4:03 AM

    It's 3am have just found your updated fix, hurrah it works - i can go to bed soon!

    ReplyDelete
  64. UnknownMay 17, 2016 at 10:50 PM

    AMAZING
    As simple as
    1..2...3...
    Net stop wuauserv
    Sc config wuauserv type= own
    Net start wuauserv

    ReplyDelete
  65. AnonymousMay 24, 2016 at 6:18 AM

    Hey, I'm trying to follow your steps, but when I'm installing KB3102810, it's failed many times. I'm already reboot my computer many times but still doesn't work. Please help:(

    ReplyDelete
  66. AnonymousMay 24, 2016 at 6:36 AM

    After I reinstalled Windows 7 x86 and updated the initial install I got "unknown error 8007000E". That happened after several updates were installed. I think the error happened after SP1 was installed. I looked for a solution but initially I did not find one. By coincidence after leaving the pc on for several days ( I think it was three) some update installed and fixed the error. However I have several systems to reinstall and I can’t wait several days on each system. My search led me to your post and I used http://support.microsoft.com/en-us/kb/3102810 and that just really solved the problem. I would like to just say thank you to both Mr. Henk Hoogendoorn and Mr. Trevor Jones for taking the time to post the solution. Your post really saved me lots of time and frustration. I just like to add that I do not believe the problem is because the system has small amounts of physical RAM. The P.C. I had this problem with had 4 Gigs of RAM and nothing but Windows installed. Anyhow, Thanks again.

    ReplyDelete
  67. John DoeMay 26, 2016 at 1:58 AM

    And it continues to work. Thxs!

    ReplyDelete
  68. AnonymousJune 2, 2016 at 6:12 PM

    Thank you Henky, this resolved the issue I was having and your blog was the first in the Google search list. Very much appreciated. Thankies.

    Antonio Proudarse

    ReplyDelete
    Replies
    1. Henk HoogendoornJune 2, 2016 at 9:11 PM

      Good to hear that! first in Google search list, whoow :)

      Delete
  69. asia on my mindJune 21, 2016 at 7:28 AM

    Thanks Henk! You saved me a lot of grief and I found your post #1 on google search. The hot patch alone didn't fix, but with your command line steps did. My update download took many hours but now all is well.

    ReplyDelete
    Replies
    1. Henk HoogendoornJune 21, 2016 at 4:33 PM

      Great to hear that! And thanks for the comment.

      Delete
    2. AnonymousJune 22, 2016 at 12:17 PM

      Thanks for the Hotfixe! Work like a charm!I have installed the Convenience Rollup Update (CRU) and after that i had this problem, i though it was the CRU but it wasn't in fact!

      Delete
  70. UnknownJune 26, 2016 at 1:45 PM

    Henk thank you for your blog/ forum about this topic. I really tried everything before i found this page. From adjusting my virtual RAM, to windows fixit, manual update reset and more. But i still have one question: before i never had any problems downloading those updates and i have 4 Gb RAMS at my disposal. Did this happen because of an malfunctioning hotfix? Greetz and lots of thanks. Danny

    ReplyDelete
    Replies
    1. Henk HoogendoornJune 27, 2016 at 11:12 PM

      Yes, it's the only reasonable explanation I guess!

      Delete
  71. AnonymousJuly 1, 2016 at 6:36 PM

    Henk, thank you! Another happy camper here. applied http://support.microsoft.com/en-us/kb/3102810 - and stopped and restarted the WU service; finally Windows Update is checking for updates... =:>)

    ReplyDelete
  72. AnonymousJuly 8, 2016 at 2:59 AM

    Thank you! Been working on this all night and finally I can update!

    ReplyDelete
  73. AnonymousJuly 11, 2016 at 1:58 PM

    Thank you, two days of fruitless efforts and help to your advice! KB3102810 update and it works :-)

    ReplyDelete
  74. AnonymousJuly 16, 2016 at 6:44 AM

    Thank you for taking the time to share the information with us.
    Amazing, it works.
    Have a good day

    ReplyDelete
  75. GratefuloneJuly 28, 2016 at 8:24 AM

    wow, only thing that actually worked!!!! Thank you!

    ReplyDelete
  76. AnonymousAugust 2, 2016 at 7:52 PM

    Henk, you ROCK!! Thanks for this blog post. I am going to subscribe to everything I find about you. I hope you can make some "click-money" so we can thank you properly.
    T....USA.

    ReplyDelete
  77. Tom WeustinkAugust 9, 2016 at 4:42 PM

    After a couple of months, off and on, we started looking deeper into log files (SCCM 2012) and finally noticed the error code.

    Came here and this fixed it for us as well!
    Latest update seems to be KB3112343 fromDecember 2015.
    Also, the sc line to place wasn't needed for us, but can't hurt as it places wuauserv in it's own private memory.

    Anyway, thanks a lot for this!

    ReplyDelete
  78. AnonymousAugust 10, 2016 at 5:51 AM

    Henk bedankt alles werkt nu weer!

    ReplyDelete
  79. AnonymousAugust 10, 2016 at 5:53 AM

    Bedankt Henk, alles werkt nu weer!

    ReplyDelete
  80. AnonymousAugust 24, 2016 at 3:25 PM

    Hi-Here's the non-tech solution that worked on my HP with Marvell-Yukon Ethernet controller running Windows 7. I started windows update, and then I got out my Windows 7 distribution disk and ran it as if I were going to put a new system in. The disk starts by downloading temporary files, and then searches for installation updates. I let it run for quite awhile, until it said that it couldn't install a new Windows 7 system, because the running system is newer. Without any further interference, windows update finished with my 231 updates--all is well. I wonder if this will work for anyone else?.....

    ReplyDelete
  81. AnonymousNovember 14, 2016 at 4:50 AM

    Worked for me, thanks

    ReplyDelete
  82. AndyDecember 2, 2016 at 4:12 PM

    Mate you are a total hero. I have re-cloned from an original image a few times now, tried lord only knows how many "fixes" from MS, turned off DEP, seen posts talking through editing loads of registry keys ... you name it I've tried it. However YOUR SOLUTION WORKED!!
    (Windows 7 Home Premium 32 Bit if it helps anyone else). Just 287 Important Updates (1GB) to go now! :-)

    Thanks again, Andy.

    ReplyDelete
  83. AnonymousJanuary 4, 2017 at 3:50 PM

    This worked fine. Thank you!romania

    ReplyDelete
  84. Stanescu BogdanMarch 19, 2017 at 1:49 PM

    Do you know why I cannot install Update for Windows (KB3102810)? Even the previous one cannot be installed. Thanks.

    ReplyDelete
  85. souldeeperMarch 29, 2017 at 12:50 PM

    is the fix applicable for vista or windows 2008 SP2 (non-R2)

    ReplyDelete
  86. RakeshSeptember 21, 2017 at 12:03 PM

    Even I'm looking for a fix for server 2008 non R2

    ReplyDelete
  87. AjajDecember 31, 2018 at 4:03 PM

    Problem solved.
    thanks for helping me.
    this article very helpful at all
    Windows 10 Update Error Code 0x8024a105 – Fixed

    ReplyDelete
  88. AnonymousApril 18, 2019 at 10:01 PM

    i have been trying to get windows update for hours
    this is the only one that worked

    thank you

    ReplyDelete
  89. Sylvester BalchunasMay 4, 2020 at 1:04 PM

    Your blog post is very useful for me. Keep sharing!!

    Have a look at how to fix windows update error 0x8024a105

    ReplyDelete

Subscribe to: Post Comments (Atom)