{"id":1877,"date":"2016-09-08T11:40:32","date_gmt":"2016-09-08T16:40:32","guid":{"rendered":"http:\/\/swildow.darktech.org\/wp\/?p=1877"},"modified":"2016-09-08T11:40:32","modified_gmt":"2016-09-08T16:40:32","slug":"windows-update-slowness","status":"publish","type":"post","link":"https:\/\/www.wildow.com\/blog\/?p=1877","title":{"rendered":"Windows Update Slowness"},"content":{"rendered":"

Windows Update Slowness<\/span><\/h3>\n
\n
\n\n\n\n
\n
We’ve heard a number of people report that Win7, when freshly installed, take a long<\/i> time and a lot of memory to apply the first round of updates. The ‘check for updates’ part of the sequence taking more than 30 minutes … in some cases several days<\/span>!<\/p>\n
<\/div>\n
This is due to a bug* in Windows Update (WU), which causes the processing (“checking” or “searching”) \u00a0stage to take far too long, when there are a great many updates to process. The bug is resolved with the new WU client delivered in the KB3172605<\/a>\u00a0update. However, the bug still applies while you are installing<\/i>\u00a0KB3172605, making it take a long time … unless you use this procedure.<\/div>\n
<\/div>\n
The procedure below is the result of a lot of experimentation. It is the speediest way we have yet found, for getting Windows fully updated.<\/p>\n
<\/div>\n
A trick we have learned:<\/div>\n
\n
    \n
  1. Download the appropriate (x64 or x86) versions of these three updates:\u00a0KB3020369<\/a>,\u00a0KB3172605<\/a>,\u00a0and\u00a0KB3125574<\/a>.\n
      \n
    1. Microsoft Update Catalog links: KB3125574<\/a>, KB3172605<\/a>, KB3020369<\/a><\/li>\n<\/ol>\n<\/li>\n
    2. Open an elevated PowerShell prompt and run the following commands, which will allow the next updates to install quickly:\n
        \n
      1. stop-service wuauserv<\/span><\/li>\n
      2. remove-item c:\\windows\\softwaredistribution\\WuRedir<\/span><\/li>\n<\/ol>\n<\/li>\n
      3. Double-click and run the\u00a0KB3020369 update (previously downloaded). Should take less than 2 minutes to run, and will not require a reboot.<\/li>\n
      4. Now double-click the\u00a0KB3172605\u00a0update you previously downloaded. Follow the prompts. Reboot when it says to. (This step should take about 1 minute).<\/li>\n
      5. Double-click and run the\u00a0KB3125574\u00a0update (previously downloaded). Should take about 12 minutes to run. It will require a reboot that takes 5 minutes to complete.<\/li>\n
      6. Begin WU (Windows Update) after completing the above steps. A list of 60+ available updates should be returned within 5 minutes.<\/li>\n
      7. Finish updating normally … rebooting when it says to. You will probably need to reboot and re-check for updates at least two more times.<\/li>\n<\/ol>\n

        In my own tests, using this method, I was able to take a Win7 SP1 Ultimate (64bit) system from fresh installed to fully updated\u00a0in about 1.5 hours.<\/span> The WuRedir directory (which I remove in step 2) will be rebuilt by Windows along the way, and the WU service will be restarted on its own.<\/div>\n

        \n
        For other WU issues, start with this omnibus troubleshooting article<\/a>.<\/div>\n
        <\/div>\n
        Fix Windows corruption errors by using the DISM or System Update Readiness tool<\/a><\/div>\n
        <\/div>\n
        Some folks advocate using wsusoffline<\/a>, which requires some preparation work. Of you may be interested in this PowerShell Windows Update Module<\/a>. Or this other one called PSWU<\/a>.<\/div>\n<\/div>\n
        <\/div>\n
        We hope to add more to this article. Please send suggestions to mota<\/a>.<\/div>\n<\/div>\n
        <\/div>\n
        *Microsoft have not formally said much about this bug. I was tipped off when I heard Microsoft Premier Field Engineer Clint Huffman<\/a>talk about it in this podcast<\/a>.<\/i><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

        Windows Update Slowness We’ve heard a number of people report that Win7, when freshly installed, take a long time and a lot of memory to apply the first round of updates. The ‘check for updates’ part of the sequence taking … Read More »<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-1877","post","type-post","status-publish","format-standard","hentry","category-windows"],"_links":{"self":[{"href":"https:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1877","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1877"}],"version-history":[{"count":1,"href":"https:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1877\/revisions"}],"predecessor-version":[{"id":1878,"href":"https:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1877\/revisions\/1878"}],"wp:attachment":[{"href":"https:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1877"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1877"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1877"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}