Last updated on: October 28th, 2017 I have a long relationship with windows update error 0x800705b4. I fact I had helped thousands of users to fix this error on Windows 10 operating system for the best part of the last two years. It is only natural, or should I even say karma, that I will encounter this error on first server 2016 production deployment.
Luckily, solving the problem at the server side, is just as easy as fixing it on the client side.
For me it seems, that I simply installed the server using an early ISO version. As a result Windows Defender signatures were out out date and the update failed.
So in order to fix the problem, simply open the updates settings window, then click the “Advanced options” link.
At the advanced options window, enable (tick on) the option to receive updates for other Microsoft products.
Then return to the main updates page, and retry the update process.
This time Windows defender signatures will also be updated, and the entire update process will also be successful!
Your blog is great. I read a lot of interesting things from it. Thank you very much for sharing. Hope you will update more news in the future.
You got a really useful blog. I have been here reading for about an hour. I am a newbie and your success is very much an inspiration for me.
I like your blog post. Keep on writing this type of great stuff. I make sure to follow up on your blog in the future.
Thanks!
It works
Thanks you very much for this article! It has helped me highlight a discrepancy between two seemingly identical systems where the update succeeded in one and failed on the other. Both were server 2016 b1607 LTS. Interestingly enough, it succeeded on the system that had the Windows defender feature disabled and failed on the system that had the feature enabled. this was probably because we disallow our servers to reach out to the internet to get additional updates as our WSUS manages all updates for the infrastructure. Kudos!
This guided walk-through provides steps to fix problems with Windows Updates. Thank for sharing us.
Thanks that worked.
All other usual methods (kill softwaredistribution, reset update components etc) were all wrong, that simple thing fixed it. So annoying.
As for more details: I had this problems for quite a few month now, and each time I fixed it by downloading the full update from the uüdate catalogue. Luckily I don’t need to do that any more.
Thanks for the detailed comment Joachim.
I’m glad you got it sorted.
Thanks. That was very helpful.