tag:blogger.com,1999:blog-4399960513082382706.post3537198758310578357..comments2024-01-04T12:07:18.991-08:00Comments on Ultimate Outsider: How to Speed Up Windows Update's 'Check for Updates' Feature on Windows 7Ultimate Outsiderhttp://www.blogger.com/profile/09004247608053632633noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-4399960513082382706.post-27229217368516426462016-08-02T19:46:34.885-07:002016-08-02T19:46:34.885-07:00@Chuck - Thanks for the patch and link suggestion!...@Chuck - Thanks for the patch and link suggestion! I have updated my list.Ultimate Outsiderhttps://www.blogger.com/profile/09004247608053632633noreply@blogger.comtag:blogger.com,1999:blog-4399960513082382706.post-7688693739111680232016-08-02T19:32:54.082-07:002016-08-02T19:32:54.082-07:00The current Windows Update speed-up patch for Win7...The current Windows Update speed-up patch for Win7 (issued on July 12) is KB3168965. That may be superseded with Microsoft August 9 patch releases (as has happened many times in the past), but right now (August 2) it is enormously beneficial. There's an excellent website that keeps track of this issue; see http://wu.krelay.de/en/2016-07.htm for the current selection.Chuckhttps://www.blogger.com/profile/07183744848718715846noreply@blogger.comtag:blogger.com,1999:blog-4399960513082382706.post-49094831183487651502016-08-02T13:12:31.758-07:002016-08-02T13:12:31.758-07:00@wreckshere - I don't know anything about your...@wreckshere - I don't know anything about your hardware/setup, but if 32-bit Windows is working out for you, there's not much reason to upgrade to 64-bit. If I were you I'd stick with 32-bit unless you have more than 3GB of RAM installed (which you would need 64-bit Windows in order to fully utilize), or if you have some specific application or device driver that's 64-bit only (which is pretty rare).<br /><br />If you do end up performing a fresh 64-bit Windows 7 install, remember that the very first time you check for updates, it can take an extremely long time (as I mentioned a few comments up, the last time I did it, it took more than an entire day to perform the first update scan, but it worked fine after that). I don't know if the updates mentioned in my post will help you with that first-time scan (because they might have prerequisites that wouldn't already be installed on a fresh-from-disc Windows installation), but I would like to hear how it goes for you.<br />Ultimate Outsiderhttps://www.blogger.com/profile/09004247608053632633noreply@blogger.comtag:blogger.com,1999:blog-4399960513082382706.post-6107920821049841322016-08-02T12:56:44.635-07:002016-08-02T12:56:44.635-07:00Hello Friends! I have been trying to UPGRADE from ...Hello Friends! I have been trying to UPGRADE from win-7 32bit to win-7 x64bit so MANY TIME...wasting HOURS, etc...I finally gave up and reverted to trusty 32bit (several times) currently, I am using win-7 32bit which seems to work better for everything!<br />I will print your instructions about win update, and see if my x64BIT will again work? I have invested in CPU,RAM, harddrives...not to mention my TIME and frustration! wish me luck, rex thompsonwrecksherehttps://www.blogger.com/profile/01266466117396399771noreply@blogger.comtag:blogger.com,1999:blog-4399960513082382706.post-7801111599690122422016-08-02T12:30:03.305-07:002016-08-02T12:30:03.305-07:00Yup, it is truly getting ridiculous. Especially be...Yup, it is truly getting ridiculous. Especially because the RAM usage of the associated processes goes through the roof. I've taken to adding a day to reinstalls when giving customers quotes now, it's silly.Adam Piggotthttps://www.blogger.com/profile/07441114637411205483noreply@blogger.comtag:blogger.com,1999:blog-4399960513082382706.post-17997884476499051102016-08-02T12:19:25.864-07:002016-08-02T12:19:25.864-07:00@Adam - The reason I suggest doing the restart up ...@Adam - The reason I suggest doing the restart up front is based on experiences I've had attempting to install these patches over the past few weeks/months. Three or four times I've done it, on my first attempt to install one of the downloaded patches, the installer says "Checking your system for updates..." and just stays there without ever seeming to proceed. I've let it go as long as 45 minutes with no success- but every time this happened, if I restarted Windows and tried again, I was able to run the patch installer with no problems; the "Checking for updates" portion ran for less than a minute before proceeding.<br /><br />Anyway, I do appreciate your background info.<br /><br />By the way, have you tried running Windows Update on a brand new straight-off-the-disc Windows 7 install? I did it a few months ago, and the very first "check for updates" took <b>twenty eight hours</b> to complete. Just for the scan! I just let it run over night and when I came back from work the next day it was ready to install updates.Ultimate Outsiderhttps://www.blogger.com/profile/09004247608053632633noreply@blogger.comtag:blogger.com,1999:blog-4399960513082382706.post-51351543601131799332016-08-02T09:39:27.504-07:002016-08-02T09:39:27.504-07:00The reasons why Windows Vista and 7 are suffering ...The reasons why Windows Vista and 7 are suffering from increasingly-long scan and post-update servicing updates are, I believe two-fold:<br /><br />The process to check for applicable updates has more and more work to do each time a new update is added, as it has to check through the datastore and existing files to see if an update is applicable.<br /><br />Secondly, the Component-Based Servicing system checks for superseded updates and removes them from the datastore.<br /><br />Both of these suffer from increasing processing time the more updates are applied - which is why Vista is in an even worse state that 7 is, and is similar to the timeouts that Windows XP was getting via the Windows Update site. (XP doesn't use CBS, but the problem has a similar premise - overhead).<br /><br />You suggest that users first restart their computer to resolve the problem. I beg to differ - if the system is already busy on WU/CBS-related tasks, let it finish to save it having to waste time picking up where it left off. You can check to see if TrustedInstaller.exe or mscorsvw.exe are busy with CPU or I/O via Task Manager (or better - Sysinternals' Process Explorer).<br /><br />Thanks for the info!Adam Piggotthttps://www.blogger.com/profile/07441114637411205483noreply@blogger.com