If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
windows Update 4 days
I got a new laptop this week from dell. I had them install windows 7 pro 64. I have been trying to get windows updates for 4 days and nights. The computer just keeps checking for updates its never checked for updates before I got it. Is there a problem with windows software ? 4 days seem like a long time to wait for updates. Any ideas or recommendations what I should try? Thanks Farmer -- "If you do not take an interest in the affairs of your government, then you are doomed to live under the rule of fools." ---- Plato |
Ads |
#2
|
|||
|
|||
windows Update 4 days
Farmer wrote:
I got a new laptop this week from dell. I had them install windows 7 pro 64. I have been trying to get windows updates for 4 days and nights. The computer just keeps checking for updates its never checked for updates before I got it. Is there a problem with windows software ? 4 days seem like a long time to wait for updates. Any ideas or recommendations what I should try? Thanks Farmer You could turn Windows Update off. That's one solution. If Microsoft can't make it work, why should you bother ? ******* The recipe for fixing this, changes after *every* Patch Tuesday. This means we cannot quote a recipe that is good for every individual who comes along. The root cause, is the supersedence calculation that wuauserv (wuaueng.dll) carries out during Windows Update. First, you'll see some scanning activity, while package info is collected. Windows Update may download some recent manifest info. Then, wuauserv sets to work, figuring out which updates are no longer necessary. For example, consider the poor ole MSRT package. It's not really a security update. It is adjunct software. Yet, it is delivered through Windows Update. MSRT changes every month. This means the January version, "supercedes" the December version. So wuauserv sits there spinning its wheels, doing a calc to "reject" everything except the Jan 2017 version. There are a number of software (and files), which when patched again and again, cause wuauserv to go nuts. Internet Explorer - Cumulative Updates supersede others MSRT - New version supersedes others Kernel files, GDIplus, ATM font manage crap - patched practically every month It is because of these "deep" dependency trees, that Windows Update cannot return with an update list in a timely manner. ******* Possible ingredients: First, note that there is *no* solution as such. When we produce these lists of update for you, they're bandaids. As the months pass, these become *immediately ineffective* !!! The Microsoft Catalog server, serves individual patches. You can download a patch from there, being careful to select x64 if you are using Win7 SP1 x64 and so on. Servicing Stack http://catalog.update.microsoft.com/...aspx?q=3020369 July 2016 update rollup for Windows 7 SP1 http://catalog.update.microsoft.com/...aspx?q=3172605 December 2016 Security Monthly Quality Rollup http://www.catalog.update.microsoft....aspx?q=3207752 In addition, there is the Convenience Rollup, which takes the place of a bunch of individual updates. 476.9 MB. http://catalog.update.microsoft.com/...px?q=KB3125574 To try these out: 1) Download them. 2) Disconnect the network cable. (This is an alternative to disabling Windows Update and running it in manual mode only.) Reboot. (This does the same thing as stopping wuauserv.) 3) Double-click the .msu files one at a time. Don't reboot, unless an update gives you no choice. 4) When the last one is installed, you can reboot and let it finish all the PendingDeletes and so on. Order - probably any order would work, except the 369 servicing stack is a "dependency: for the others. The others will report they are "Not Applicable" unless the Servicing Stack 369 is done first. 3020369 3125574 --- might take an hour 3172605 3207752 I can't guarantee this is enough. To guarantee it, I'd have to install Win7SP1 fresh and test. I've probably done that a half dozen times by now. I think you can see this is "annoying as hell". ******* If you download MBSA 2.3 (Microsoft Baseline Security Analyzer), it can tell you immediately [5 minutes], which security updates you are missing. But, it cannot show you the optional updates. I have updated a couple OSes using nothing but MBSA for guidance and got the Windows Update working on them well enough to list the Optional Updates. So MBSA 2.3 is available, if you want a second opinion on how many patches are missing. MBSA 2.3 doesn't do as good a job working out supersedence, which is why it comes back in five minutes. Microsoft is changing the delivery mechanism for Windows Update, but this *will not* alleviate suffering for people doing fresh installs, or people who just bought a laptop with Win7SP1 on it. ******* I can start a verification run now, and get back to you later if this doesn't appear to be working (today). I figured I'd send this first, to give you a head start... HTH, Paul |
#3
|
|||
|
|||
windows Update 4 days
On 08/01/2017 20:47, Farmer wrote:
I got a new laptop this week from dell. I had them install windows 7 pro 64. This is your problem. Why the **** did you do that? Why not use Windows 10 that gives you automatic updates on demand? -- If you want to filter all of my posts then please read this article: https://support.mozilla.org/en-US/kb/organize-your-messages-using-filters In step 7 select "Delete" With over 400 million devices now running Windows 10, customer satisfaction is higher than any previous version of windows. |
#4
|
|||
|
|||
windows Update 4 days
Paul wrote:
Farmer wrote: I got a new laptop this week from dell. I had them install windows 7 pro 64. I have been trying to get windows updates for 4 days and nights. The computer just keeps checking for updates its never checked for updates before I got it. Is there a problem with windows software ? 4 days seem like a long time to wait for updates. Any ideas or recommendations what I should try? Thanks Farmer You could turn Windows Update off. That's one solution. If Microsoft can't make it work, why should you bother ? ******* The recipe for fixing this, changes after *every* Patch Tuesday. This means we cannot quote a recipe that is good for every individual who comes along. The root cause, is the supersedence calculation that wuauserv (wuaueng.dll) carries out during Windows Update. First, you'll see some scanning activity, while package info is collected. Windows Update may download some recent manifest info. Then, wuauserv sets to work, figuring out which updates are no longer necessary. For example, consider the poor ole MSRT package. It's not really a security update. It is adjunct software. Yet, it is delivered through Windows Update. MSRT changes every month. This means the January version, "supercedes" the December version. So wuauserv sits there spinning its wheels, doing a calc to "reject" everything except the Jan 2017 version. There are a number of software (and files), which when patched again and again, cause wuauserv to go nuts. Internet Explorer - Cumulative Updates supersede others MSRT - New version supersedes others Kernel files, GDIplus, ATM font manage crap - patched practically every month It is because of these "deep" dependency trees, that Windows Update cannot return with an update list in a timely manner. ******* Possible ingredients: First, note that there is *no* solution as such. When we produce these lists of update for you, they're bandaids. As the months pass, these become *immediately ineffective* !!! The Microsoft Catalog server, serves individual patches. You can download a patch from there, being careful to select x64 if you are using Win7 SP1 x64 and so on. Servicing Stack http://catalog.update.microsoft.com/...aspx?q=3020369 July 2016 update rollup for Windows 7 SP1 http://catalog.update.microsoft.com/...aspx?q=3172605 December 2016 Security Monthly Quality Rollup http://www.catalog.update.microsoft....aspx?q=3207752 In addition, there is the Convenience Rollup, which takes the place of a bunch of individual updates. 476.9 MB. http://catalog.update.microsoft.com/...px?q=KB3125574 To try these out: 1) Download them. 2) Disconnect the network cable. (This is an alternative to disabling Windows Update and running it in manual mode only.) Reboot. (This does the same thing as stopping wuauserv.) 3) Double-click the .msu files one at a time. Don't reboot, unless an update gives you no choice. 4) When the last one is installed, you can reboot and let it finish all the PendingDeletes and so on. Order - probably any order would work, except the 369 servicing stack is a "dependency: for the others. The others will report they are "Not Applicable" unless the Servicing Stack 369 is done first. 3020369 3125574 --- might take an hour 3172605 3207752 I can't guarantee this is enough. To guarantee it, I'd have to install Win7SP1 fresh and test. I've probably done that a half dozen times by now. I think you can see this is "annoying as hell". ******* If you download MBSA 2.3 (Microsoft Baseline Security Analyzer), it can tell you immediately [5 minutes], which security updates you are missing. But, it cannot show you the optional updates. I have updated a couple OSes using nothing but MBSA for guidance and got the Windows Update working on them well enough to list the Optional Updates. So MBSA 2.3 is available, if you want a second opinion on how many patches are missing. MBSA 2.3 doesn't do as good a job working out supersedence, which is why it comes back in five minutes. Microsoft is changing the delivery mechanism for Windows Update, but this *will not* alleviate suffering for people doing fresh installs, or people who just bought a laptop with Win7SP1 on it. ******* I can start a verification run now, and get back to you later if this doesn't appear to be working (today). I figured I'd send this first, to give you a head start... HTH, Paul THese are the results of the test run in a VM. These results will be invalid after January 10, 2017, requiring another test run after that date. Win7SP1 x64 3020369 3172605 3207752 It took a relatively short time to install those three, then reboot after the third was in place. If it gets "stuck", it means you let wuauserv get into a loop again. You can enter the Windows Update settings and tell it to "not look for updates", the fifth option. After a reboot, it took five minutes for the Windows Update to list the updates. So those three are enough to get Windows Update to work in five minutes. https://s23.postimg.org/e6hum9bfv/369_605_752.gif "146 important 68 optional " It took about nine minutes total for this whopper to install 3125574 after which the Windows Update appeared a little faster. You can see how manu this has done for you. https://s27.postimg.org/9oe335glf/after_574.gif "36 important 33 optional " So just four updates applied manually, gets most of it. HTH, Paul |
#5
|
|||
|
|||
windows Update 4 days
On Sun, 8 Jan 2017 15:47:41 -0500, in alt.windows7.general Farmer wrote:
Is there a problem with windows software There was something about it being broken a while back. -- %randsig:C:\sig\sig.txt% |
#6
|
|||
|
|||
windows Update 4 days
His problem Good Guy is it WONT show or download and install the updates for window7 Pro.
-- AL'S COMPUTERS "Good Guy" wrote in message news On 08/01/2017 20:47, Farmer wrote: I got a new laptop this week from dell. I had them install windows 7 pro 64. This is your problem. Why the **** did you do that? Why not use Windows 10 that gives you automatic updates on demand? -- If you want to filter all of my posts then please read this article: https://support.mozilla.org/en-US/kb/organize-your-messages-using-filters In step 7 select "Delete" With over 400 million devices now running Windows 10, customer satisfaction is higher than any previous version of windows. |
#7
|
|||
|
|||
windows Update 4 days
On 1/8/2017 6:57 PM, Paul wrote:
Paul wrote: Farmer wrote: I got a new laptop this week from dell. I had them install windows 7 pro 64. I have been trying to get windows updates for 4 days and nights. The computer just keeps checking for updates its never checked for updates before I got it. Is there a problem with windows software ? 4 days seem like a long time to wait for updates. Any ideas or recommendations what I should try? Thanks Farmer You could turn Windows Update off. That's one solution. If Microsoft can't make it work, why should you bother ? ******* The recipe for fixing this, changes after *every* Patch Tuesday. This means we cannot quote a recipe that is good for every individual who comes along. The root cause, is the supersedence calculation that wuauserv (wuaueng.dll) carries out during Windows Update. First, you'll see some scanning activity, while package info is collected. Windows Update may download some recent manifest info. Then, wuauserv sets to work, figuring out which updates are no longer necessary. For example, consider the poor ole MSRT package. It's not really a security update. It is adjunct software. Yet, it is delivered through Windows Update. MSRT changes every month. This means the January version, "supercedes" the December version. So wuauserv sits there spinning its wheels, doing a calc to "reject" everything except the Jan 2017 version. There are a number of software (and files), which when patched again and again, cause wuauserv to go nuts. Internet Explorer - Cumulative Updates supersede others MSRT - New version supersedes others Kernel files, GDIplus, ATM font manage crap - patched practically every month It is because of these "deep" dependency trees, that Windows Update cannot return with an update list in a timely manner. ******* Possible ingredients: First, note that there is *no* solution as such. When we produce these lists of update for you, they're bandaids. As the months pass, these become *immediately ineffective* !!! The Microsoft Catalog server, serves individual patches. You can download a patch from there, being careful to select x64 if you are using Win7 SP1 x64 and so on. Servicing Stack http://catalog.update.microsoft.com/...aspx?q=3020369 July 2016 update rollup for Windows 7 SP1 http://catalog.update.microsoft.com/...aspx?q=3172605 December 2016 Security Monthly Quality Rollup http://www.catalog.update.microsoft....aspx?q=3207752 In addition, there is the Convenience Rollup, which takes the place of a bunch of individual updates. 476.9 MB. http://catalog.update.microsoft.com/...px?q=KB3125574 To try these out: 1) Download them. 2) Disconnect the network cable. (This is an alternative to disabling Windows Update and running it in manual mode only.) Reboot. (This does the same thing as stopping wuauserv.) 3) Double-click the .msu files one at a time. Don't reboot, unless an update gives you no choice. 4) When the last one is installed, you can reboot and let it finish all the PendingDeletes and so on. Order - probably any order would work, except the 369 servicing stack is a "dependency: for the others. The others will report they are "Not Applicable" unless the Servicing Stack 369 is done first. 3020369 3125574 --- might take an hour 3172605 3207752 I can't guarantee this is enough. To guarantee it, I'd have to install Win7SP1 fresh and test. I've probably done that a half dozen times by now. I think you can see this is "annoying as hell". ******* If you download MBSA 2.3 (Microsoft Baseline Security Analyzer), it can tell you immediately [5 minutes], which security updates you are missing. But, it cannot show you the optional updates. I have updated a couple OSes using nothing but MBSA for guidance and got the Windows Update working on them well enough to list the Optional Updates. So MBSA 2.3 is available, if you want a second opinion on how many patches are missing. MBSA 2.3 doesn't do as good a job working out supersedence, which is why it comes back in five minutes. Microsoft is changing the delivery mechanism for Windows Update, but this *will not* alleviate suffering for people doing fresh installs, or people who just bought a laptop with Win7SP1 on it. ******* I can start a verification run now, and get back to you later if this doesn't appear to be working (today). I figured I'd send this first, to give you a head start... HTH, Paul THese are the results of the test run in a VM. These results will be invalid after January 10, 2017, requiring another test run after that date. Win7SP1 x64 3020369 3172605 3207752 It took a relatively short time to install those three, then reboot after the third was in place. If it gets "stuck", it means you let wuauserv get into a loop again. You can enter the Windows Update settings and tell it to "not look for updates", the fifth option. After a reboot, it took five minutes for the Windows Update to list the updates. So those three are enough to get Windows Update to work in five minutes. https://s23.postimg.org/e6hum9bfv/369_605_752.gif "146 important 68 optional " It took about nine minutes total for this whopper to install 3125574 after which the Windows Update appeared a little faster. You can see how manu this has done for you. https://s27.postimg.org/9oe335glf/after_574.gif "36 important 33 optional " So just four updates applied manually, gets most of it. HTH, Paul Thanks to all for the help I found the solution to my problem at microsoft support here https://support.microsoft.com/en-us/kb/3200747 Farmer -- "If you do not take an interest in the affairs of your government, then you are doomed to live under the rule of fools." ? ---- Plato |
#8
|
|||
|
|||
windows Update 4 days
On 1/8/2017 6:57 PM, Paul wrote:
Paul wrote: Farmer wrote: I got a new laptop this week from dell. I had them install windows 7 pro 64. I have been trying to get windows updates for 4 days and nights. The computer just keeps checking for updates its never checked for updates before I got it. Is there a problem with windows software ? 4 days seem like a long time to wait for updates. Any ideas or recommendations what I should try? Thanks Farmer You could turn Windows Update off. That's one solution. If Microsoft can't make it work, why should you bother ? ******* The recipe for fixing this, changes after *every* Patch Tuesday. This means we cannot quote a recipe that is good for every individual who comes along. The root cause, is the supersedence calculation that wuauserv (wuaueng.dll) carries out during Windows Update. First, you'll see some scanning activity, while package info is collected. Windows Update may download some recent manifest info. Then, wuauserv sets to work, figuring out which updates are no longer necessary. For example, consider the poor ole MSRT package. It's not really a security update. It is adjunct software. Yet, it is delivered through Windows Update. MSRT changes every month. This means the January version, "supercedes" the December version. So wuauserv sits there spinning its wheels, doing a calc to "reject" everything except the Jan 2017 version. There are a number of software (and files), which when patched again and again, cause wuauserv to go nuts. Internet Explorer - Cumulative Updates supersede others MSRT - New version supersedes others Kernel files, GDIplus, ATM font manage crap - patched practically every month It is because of these "deep" dependency trees, that Windows Update cannot return with an update list in a timely manner. ******* Possible ingredients: First, note that there is *no* solution as such. When we produce these lists of update for you, they're bandaids. As the months pass, these become *immediately ineffective* !!! The Microsoft Catalog server, serves individual patches. You can download a patch from there, being careful to select x64 if you are using Win7 SP1 x64 and so on. Servicing Stack http://catalog.update.microsoft.com/...aspx?q=3020369 July 2016 update rollup for Windows 7 SP1 http://catalog.update.microsoft.com/...aspx?q=3172605 December 2016 Security Monthly Quality Rollup http://www.catalog.update.microsoft....aspx?q=3207752 In addition, there is the Convenience Rollup, which takes the place of a bunch of individual updates. 476.9 MB. http://catalog.update.microsoft.com/...px?q=KB3125574 To try these out: 1) Download them. 2) Disconnect the network cable. (This is an alternative to disabling Windows Update and running it in manual mode only.) Reboot. (This does the same thing as stopping wuauserv.) 3) Double-click the .msu files one at a time. Don't reboot, unless an update gives you no choice. 4) When the last one is installed, you can reboot and let it finish all the PendingDeletes and so on. Order - probably any order would work, except the 369 servicing stack is a "dependency: for the others. The others will report they are "Not Applicable" unless the Servicing Stack 369 is done first. 3020369 3125574 --- might take an hour 3172605 3207752 I can't guarantee this is enough. To guarantee it, I'd have to install Win7SP1 fresh and test. I've probably done that a half dozen times by now. I think you can see this is "annoying as hell". ******* If you download MBSA 2.3 (Microsoft Baseline Security Analyzer), it can tell you immediately [5 minutes], which security updates you are missing. But, it cannot show you the optional updates. I have updated a couple OSes using nothing but MBSA for guidance and got the Windows Update working on them well enough to list the Optional Updates. So MBSA 2.3 is available, if you want a second opinion on how many patches are missing. MBSA 2.3 doesn't do as good a job working out supersedence, which is why it comes back in five minutes. Microsoft is changing the delivery mechanism for Windows Update, but this *will not* alleviate suffering for people doing fresh installs, or people who just bought a laptop with Win7SP1 on it. ******* I can start a verification run now, and get back to you later if this doesn't appear to be working (today). I figured I'd send this first, to give you a head start... HTH, Paul THese are the results of the test run in a VM. These results will be invalid after January 10, 2017, requiring another test run after that date. Win7SP1 x64 3020369 3172605 3207752 It took a relatively short time to install those three, then reboot after the third was in place. If it gets "stuck", it means you let wuauserv get into a loop again. You can enter the Windows Update settings and tell it to "not look for updates", the fifth option. After a reboot, it took five minutes for the Windows Update to list the updates. So those three are enough to get Windows Update to work in five minutes. https://s23.postimg.org/e6hum9bfv/369_605_752.gif "146 important 68 optional " It took about nine minutes total for this whopper to install 3125574 after which the Windows Update appeared a little faster. You can see how manu this has done for you. https://s27.postimg.org/9oe335glf/after_574.gif "36 important 33 optional " So just four updates applied manually, gets most of it. HTH, Paul Thanks to all for the help I found the solution here https://support.microsoft.com/en-us/kb/3200747 Thanks Farmer -- "If you do not take an interest in the affairs of your government, then you are doomed to live under the rule of fools." ? ---- Plato |
#9
|
|||
|
|||
windows Update 4 days
Farmer wrote:
On 1/8/2017 6:57 PM, Paul wrote: Paul wrote: Farmer wrote: I got a new laptop this week from dell. I had them install windows 7 pro 64. I have been trying to get windows updates for 4 days and nights. The computer just keeps checking for updates its never checked for updates before I got it. Is there a problem with windows software ? 4 days seem like a long time to wait for updates. Any ideas or recommendations what I should try? Thanks Farmer You could turn Windows Update off. That's one solution. If Microsoft can't make it work, why should you bother ? ******* The recipe for fixing this, changes after *every* Patch Tuesday. This means we cannot quote a recipe that is good for every individual who comes along. The root cause, is the supersedence calculation that wuauserv (wuaueng.dll) carries out during Windows Update. First, you'll see some scanning activity, while package info is collected. Windows Update may download some recent manifest info. Then, wuauserv sets to work, figuring out which updates are no longer necessary. For example, consider the poor ole MSRT package. It's not really a security update. It is adjunct software. Yet, it is delivered through Windows Update. MSRT changes every month. This means the January version, "supercedes" the December version. So wuauserv sits there spinning its wheels, doing a calc to "reject" everything except the Jan 2017 version. There are a number of software (and files), which when patched again and again, cause wuauserv to go nuts. Internet Explorer - Cumulative Updates supersede others MSRT - New version supersedes others Kernel files, GDIplus, ATM font manage crap - patched practically every month It is because of these "deep" dependency trees, that Windows Update cannot return with an update list in a timely manner. ******* Possible ingredients: First, note that there is *no* solution as such. When we produce these lists of update for you, they're bandaids. As the months pass, these become *immediately ineffective* !!! The Microsoft Catalog server, serves individual patches. You can download a patch from there, being careful to select x64 if you are using Win7 SP1 x64 and so on. Servicing Stack http://catalog.update.microsoft.com/...aspx?q=3020369 July 2016 update rollup for Windows 7 SP1 http://catalog.update.microsoft.com/...aspx?q=3172605 December 2016 Security Monthly Quality Rollup http://www.catalog.update.microsoft....aspx?q=3207752 In addition, there is the Convenience Rollup, which takes the place of a bunch of individual updates. 476.9 MB. http://catalog.update.microsoft.com/...px?q=KB3125574 To try these out: 1) Download them. 2) Disconnect the network cable. (This is an alternative to disabling Windows Update and running it in manual mode only.) Reboot. (This does the same thing as stopping wuauserv.) 3) Double-click the .msu files one at a time. Don't reboot, unless an update gives you no choice. 4) When the last one is installed, you can reboot and let it finish all the PendingDeletes and so on. Order - probably any order would work, except the 369 servicing stack is a "dependency: for the others. The others will report they are "Not Applicable" unless the Servicing Stack 369 is done first. 3020369 3125574 --- might take an hour 3172605 3207752 I can't guarantee this is enough. To guarantee it, I'd have to install Win7SP1 fresh and test. I've probably done that a half dozen times by now. I think you can see this is "annoying as hell". ******* If you download MBSA 2.3 (Microsoft Baseline Security Analyzer), it can tell you immediately [5 minutes], which security updates you are missing. But, it cannot show you the optional updates. I have updated a couple OSes using nothing but MBSA for guidance and got the Windows Update working on them well enough to list the Optional Updates. So MBSA 2.3 is available, if you want a second opinion on how many patches are missing. MBSA 2.3 doesn't do as good a job working out supersedence, which is why it comes back in five minutes. Microsoft is changing the delivery mechanism for Windows Update, but this *will not* alleviate suffering for people doing fresh installs, or people who just bought a laptop with Win7SP1 on it. ******* I can start a verification run now, and get back to you later if this doesn't appear to be working (today). I figured I'd send this first, to give you a head start... HTH, Paul THese are the results of the test run in a VM. These results will be invalid after January 10, 2017, requiring another test run after that date. Win7SP1 x64 3020369 3172605 3207752 It took a relatively short time to install those three, then reboot after the third was in place. If it gets "stuck", it means you let wuauserv get into a loop again. You can enter the Windows Update settings and tell it to "not look for updates", the fifth option. After a reboot, it took five minutes for the Windows Update to list the updates. So those three are enough to get Windows Update to work in five minutes. https://s23.postimg.org/e6hum9bfv/369_605_752.gif "146 important 68 optional " It took about nine minutes total for this whopper to install 3125574 after which the Windows Update appeared a little faster. You can see how manu this has done for you. https://s27.postimg.org/9oe335glf/after_574.gif "36 important 33 optional " So just four updates applied manually, gets most of it. HTH, Paul Thanks to all for the help I found the solution here https://support.microsoft.com/en-us/kb/3200747 Thanks Farmer Unbelievable. They wrote up the procedure the users cooked up. I hope you realize this is not a *complete* solution, neither is it an enduring solution. It's a bandaid. The '605 fixes **** all. In the months after '605 was released, it jammed up again. The '605 was actually a fix done to the manifest file, in the month of July, to aid Microsoft in the automatic delivery of unwanted Windows 10 installs to Windows 7 users. That was the real purpose. It wasn't some altruistic fix. And it was also not intended to be permanent. It was only to cause a bump in Win10 adoption rate in July of last year (for people who didn't know how to turn it off). So believe what you will, but '605 is no better than the other *half dozen* related "fake" Windows Update fixes. The only thing that was even remotely customer-focused, was when some IT people (in charge of thousands of computers), noted that the computers of some of their staff, were using 2GB of RAM for Windows Update. And for an hour, those people couldn't work. These were IT people who might typically use an internal WSUS server. The IT people asked for a fix, for Windows Update. The fix that was delivered some time later, reduced the RAM consumption to 20-25% of the initial value. Which allowed those computers to do useful work again. But, the fix did not do anything about the long scan time. So Microsoft cared so little at that point, to "half-fix" the problem in the name of its paying Enterprise customers. That's the closest thing we ever got to a fix. The problem amounts to an unscalable architecture, compounded by abuses by Microsoft of the delivery system. Like using 890830 over and over again, to deliver monthly MSRT updates. This kind of usage, causes wuauserv to work extra hard, figuring out all the old versions of 890830 are not applicable. I'm really surprised, if you *only* did 3020369 3172605 that Windows Update responded after that. It should require 3207752 to be installed too, because that one has kernel files, GDI files, or ATM (font related materials), which when installed, stops Windows Update for analyzing the dependency tree for those kinds of files. That's why Windows Update comes back. When the Jan2017 rollup comes out, it should "break" any benefit 3207752 brings, as long as the Jan2017 one has kernel files, GDI files, or ATM files. While 369 and 605 are a point-in-time fix, at least one more should be required in any given month, to make Windows Update usable again. Paul |
#10
|
|||
|
|||
windows Update 4 days
On 1/10/2017 4:11 PM, Paul wrote:
Farmer wrote: On 1/8/2017 6:57 PM, Paul wrote: Paul wrote: Farmer wrote: I got a new laptop this week from dell. I had them install windows 7 pro 64. I have been trying to get windows updates for 4 days and nights. The computer just keeps checking for updates its never checked for updates before I got it. Is there a problem with windows software ? 4 days seem like a long time to wait for updates. Any ideas or recommendations what I should try? Thanks Farmer You could turn Windows Update off. That's one solution. If Microsoft can't make it work, why should you bother ? ******* The recipe for fixing this, changes after *every* Patch Tuesday. This means we cannot quote a recipe that is good for every individual who comes along. The root cause, is the supersedence calculation that wuauserv (wuaueng.dll) carries out during Windows Update. First, you'll see some scanning activity, while package info is collected. Windows Update may download some recent manifest info. Then, wuauserv sets to work, figuring out which updates are no longer necessary. For example, consider the poor ole MSRT package. It's not really a security update. It is adjunct software. Yet, it is delivered through Windows Update. MSRT changes every month. This means the January version, "supercedes" the December version. So wuauserv sits there spinning its wheels, doing a calc to "reject" everything except the Jan 2017 version. There are a number of software (and files), which when patched again and again, cause wuauserv to go nuts. Internet Explorer - Cumulative Updates supersede others MSRT - New version supersedes others Kernel files, GDIplus, ATM font manage crap - patched practically every month It is because of these "deep" dependency trees, that Windows Update cannot return with an update list in a timely manner. ******* Possible ingredients: First, note that there is *no* solution as such. When we produce these lists of update for you, they're bandaids. As the months pass, these become *immediately ineffective* !!! The Microsoft Catalog server, serves individual patches. You can download a patch from there, being careful to select x64 if you are using Win7 SP1 x64 and so on. Servicing Stack http://catalog.update.microsoft.com/...aspx?q=3020369 July 2016 update rollup for Windows 7 SP1 http://catalog.update.microsoft.com/...aspx?q=3172605 December 2016 Security Monthly Quality Rollup http://www.catalog.update.microsoft....aspx?q=3207752 In addition, there is the Convenience Rollup, which takes the place of a bunch of individual updates. 476.9 MB. http://catalog.update.microsoft.com/...px?q=KB3125574 To try these out: 1) Download them. 2) Disconnect the network cable. (This is an alternative to disabling Windows Update and running it in manual mode only.) Reboot. (This does the same thing as stopping wuauserv.) 3) Double-click the .msu files one at a time. Don't reboot, unless an update gives you no choice. 4) When the last one is installed, you can reboot and let it finish all the PendingDeletes and so on. Order - probably any order would work, except the 369 servicing stack is a "dependency: for the others. The others will report they are "Not Applicable" unless the Servicing Stack 369 is done first. 3020369 3125574 --- might take an hour 3172605 3207752 I can't guarantee this is enough. To guarantee it, I'd have to install Win7SP1 fresh and test. I've probably done that a half dozen times by now. I think you can see this is "annoying as hell". ******* If you download MBSA 2.3 (Microsoft Baseline Security Analyzer), it can tell you immediately [5 minutes], which security updates you are missing. But, it cannot show you the optional updates. I have updated a couple OSes using nothing but MBSA for guidance and got the Windows Update working on them well enough to list the Optional Updates. So MBSA 2.3 is available, if you want a second opinion on how many patches are missing. MBSA 2.3 doesn't do as good a job working out supersedence, which is why it comes back in five minutes. Microsoft is changing the delivery mechanism for Windows Update, but this *will not* alleviate suffering for people doing fresh installs, or people who just bought a laptop with Win7SP1 on it. ******* I can start a verification run now, and get back to you later if this doesn't appear to be working (today). I figured I'd send this first, to give you a head start... HTH, Paul THese are the results of the test run in a VM. These results will be invalid after January 10, 2017, requiring another test run after that date. Win7SP1 x64 3020369 3172605 3207752 It took a relatively short time to install those three, then reboot after the third was in place. If it gets "stuck", it means you let wuauserv get into a loop again. You can enter the Windows Update settings and tell it to "not look for updates", the fifth option. After a reboot, it took five minutes for the Windows Update to list the updates. So those three are enough to get Windows Update to work in five minutes. https://s23.postimg.org/e6hum9bfv/369_605_752.gif "146 important 68 optional " It took about nine minutes total for this whopper to install 3125574 after which the Windows Update appeared a little faster. You can see how manu this has done for you. https://s27.postimg.org/9oe335glf/after_574.gif "36 important 33 optional " So just four updates applied manually, gets most of it. HTH, Paul Thanks to all for the help I found the solution here https://support.microsoft.com/en-us/kb/3200747 Thanks Farmer Unbelievable. They wrote up the procedure the users cooked up. I hope you realize this is not a *complete* solution, neither is it an enduring solution. It's a bandaid. The '605 fixes **** all. In the months after '605 was released, it jammed up again. The '605 was actually a fix done to the manifest file, in the month of July, to aid Microsoft in the automatic delivery of unwanted Windows 10 installs to Windows 7 users. That was the real purpose. It wasn't some altruistic fix. And it was also not intended to be permanent. It was only to cause a bump in Win10 adoption rate in July of last year (for people who didn't know how to turn it off). So believe what you will, but '605 is no better than the other *half dozen* related "fake" Windows Update fixes. The only thing that was even remotely customer-focused, was when some IT people (in charge of thousands of computers), noted that the computers of some of their staff, were using 2GB of RAM for Windows Update. And for an hour, those people couldn't work. These were IT people who might typically use an internal WSUS server. The IT people asked for a fix, for Windows Update. The fix that was delivered some time later, reduced the RAM consumption to 20-25% of the initial value. Which allowed those computers to do useful work again. But, the fix did not do anything about the long scan time. So Microsoft cared so little at that point, to "half-fix" the problem in the name of its paying Enterprise customers. That's the closest thing we ever got to a fix. The problem amounts to an unscalable architecture, compounded by abuses by Microsoft of the delivery system. Like using 890830 over and over again, to deliver monthly MSRT updates. This kind of usage, causes wuauserv to work extra hard, figuring out all the old versions of 890830 are not applicable. I'm really surprised, if you *only* did 3020369 3172605 that Windows Update responded after that. It should require 3207752 to be installed too, because that one has kernel files, GDI files, or ATM (font related materials), which when installed, stops Windows Update for analyzing the dependency tree for those kinds of files. That's why Windows Update comes back. When the Jan2017 rollup comes out, it should "break" any benefit 3207752 brings, as long as the Jan2017 one has kernel files, GDI files, or ATM files. While 369 and 605 are a point-in-time fix, at least one more should be required in any given month, to make Windows Update usable again. Paul Thanks Paul I don't no if 3207752 was in the batch of updates I received once it started the updates I received 45 on a computer that had never been updated. Farmer -- "If you do not take an interest in the affairs of your government, then you are doomed to live under the rule of fools." ? ---- Plato |
#11
|
|||
|
|||
windows Update 4 days
On 01/08/2017 03:57 PM, Paul wrote:
Paul wrote: Farmer wrote: I got a new laptop this week from dell. I had them install windows 7 pro 64. I have been trying to get windows updates for 4 days and nights. The computer just keeps checking for updates its never checked for updates before I got it. Is there a problem with windows software ? 4 days seem like a long time to wait for updates. Any ideas or recommendations what I should try? Thanks Farmer You could turn Windows Update off. That's one solution. If Microsoft can't make it work, why should you bother ? ******* The recipe for fixing this, changes after *every* Patch Tuesday. This means we cannot quote a recipe that is good for every individual who comes along. The root cause, is the supersedence calculation that wuauserv (wuaueng.dll) carries out during Windows Update. First, you'll see some scanning activity, while package info is collected. Windows Update may download some recent manifest info. Then, wuauserv sets to work, figuring out which updates are no longer necessary. For example, consider the poor ole MSRT package. It's not really a security update. It is adjunct software. Yet, it is delivered through Windows Update. MSRT changes every month. This means the January version, "supercedes" the December version. So wuauserv sits there spinning its wheels, doing a calc to "reject" everything except the Jan 2017 version. There are a number of software (and files), which when patched again and again, cause wuauserv to go nuts. Internet Explorer - Cumulative Updates supersede others MSRT - New version supersedes others Kernel files, GDIplus, ATM font manage crap - patched practically every month It is because of these "deep" dependency trees, that Windows Update cannot return with an update list in a timely manner. ******* Possible ingredients: First, note that there is *no* solution as such. When we produce these lists of update for you, they're bandaids. As the months pass, these become *immediately ineffective* !!! The Microsoft Catalog server, serves individual patches. You can download a patch from there, being careful to select x64 if you are using Win7 SP1 x64 and so on. Servicing Stack http://catalog.update.microsoft.com/...aspx?q=3020369 July 2016 update rollup for Windows 7 SP1 http://catalog.update.microsoft.com/...aspx?q=3172605 December 2016 Security Monthly Quality Rollup http://www.catalog.update.microsoft....aspx?q=3207752 In addition, there is the Convenience Rollup, which takes the place of a bunch of individual updates. 476.9 MB. http://catalog.update.microsoft.com/...px?q=KB3125574 To try these out: 1) Download them. 2) Disconnect the network cable. (This is an alternative to disabling Windows Update and running it in manual mode only.) Reboot. (This does the same thing as stopping wuauserv.) 3) Double-click the .msu files one at a time. Don't reboot, unless an update gives you no choice. 4) When the last one is installed, you can reboot and let it finish all the PendingDeletes and so on. Order - probably any order would work, except the 369 servicing stack is a "dependency: for the others. The others will report they are "Not Applicable" unless the Servicing Stack 369 is done first. 3020369 3125574 --- might take an hour 3172605 3207752 I can't guarantee this is enough. To guarantee it, I'd have to install Win7SP1 fresh and test. I've probably done that a half dozen times by now. I think you can see this is "annoying as hell". ******* If you download MBSA 2.3 (Microsoft Baseline Security Analyzer), it can tell you immediately [5 minutes], which security updates you are missing. But, it cannot show you the optional updates. I have updated a couple OSes using nothing but MBSA for guidance and got the Windows Update working on them well enough to list the Optional Updates. So MBSA 2.3 is available, if you want a second opinion on how many patches are missing. MBSA 2.3 doesn't do as good a job working out supersedence, which is why it comes back in five minutes. Microsoft is changing the delivery mechanism for Windows Update, but this *will not* alleviate suffering for people doing fresh installs, or people who just bought a laptop with Win7SP1 on it. ******* I can start a verification run now, and get back to you later if this doesn't appear to be working (today). I figured I'd send this first, to give you a head start... HTH, Paul THese are the results of the test run in a VM. These results will be invalid after January 10, 2017, requiring another test run after that date. Win7SP1 x64 3020369 I downloaded and 'saved' that one. Killed the wusWhatever so only one instance would be running. It's been "Searching for updates on this computer for maybe an hour now, and I'm going to let it run all night. I'd previously let it attempt to download the latest 2 essential updates for maybe 24 hours with no result. POS, but NO I'm not going to switch to win10. 3172605 3207752 It took a relatively short time to install those three, then reboot after the third was in place. If it gets "stuck", it means you let wuauserv get into a loop again. You can enter the Windows Update settings and tell it to "not look for updates", the fifth option. After a reboot, it took five minutes for the Windows Update to list the updates. So those three are enough to get Windows Update to work in five minutes. https://s23.postimg.org/e6hum9bfv/369_605_752.gif "146 important 68 optional " It took about nine minutes total for this whopper to install 3125574 after which the Windows Update appeared a little faster. You can see how manu this has done for you. https://s27.postimg.org/9oe335glf/after_574.gif "36 important 33 optional " So just four updates applied manually, gets most of it. HTH, Paul -- Cheers, Bev You know it's time to clean the refrigerator when something closes the door from the inside. |
#12
|
|||
|
|||
windows Update 4 days
The Real Bev wrote:
Win7SP1 x64 3020369 I downloaded and 'saved' that one. Killed the wusWhatever so only one instance would be running. It's been "Searching for updates on this computer for maybe an hour now, and I'm going to let it run all night. I'd previously let it attempt to download the latest 2 essential updates for maybe 24 hours with no result. POS, but NO I'm not going to switch to win10. These two should be enough to re-establish operation, until February 14. After the second Tuesday (Patch Tuesday), this will need to be re-tested again for efficacy. Servicing Stack http://catalog.update.microsoft.com/...aspx?q=3020369 July 2016 update rollup for Windows 7 SP1 http://catalog.update.microsoft.com/...aspx?q=3172605 Vista is a lot harder to fix, and Windows Update might never paint the screen with updates on that one. But I did get very lucky, and I found a single post from the wsusoffline forum with the list of updates to tip Vista upright again. The Wsusoffline guys have a text file with "prerequisites". These are patches they know they have to load first, before they call wuauserv. And while their methodology doesn't always work, it's the list of patches that I'm interested in. So I'll be "mining" that when necessary, from now on. If they know the answer, it'll be hiding in a file in their downloadable package. HTH, Paul |
#13
|
|||
|
|||
windows Update 4 days
On 02/07/2017 11:11 AM, Paul wrote:
The Real Bev wrote: Win7SP1 x64 3020369 I downloaded and 'saved' that one. Killed the wusWhatever so only one instance would be running. It's been "Searching for updates on this computer for maybe an hour now, and I'm going to let it run all night. I'd previously let it attempt to download the latest 2 essential updates for maybe 24 hours with no result. POS, but NO I'm not going to switch to win10. These two should be enough to re-establish operation, until February 14. After the second Tuesday (Patch Tuesday), this will need to be re-tested again for efficacy. I let that run for another hour with no result and killed it. Started up the download of the 2 essential updates, which is still running with no result roughly 12 hours later. People should NOT have to go to this much trouble. Heretofore I had assumed that it was a queueing problem and that M$ is running the update server on a 386 machine with a 64K modem, but now I'm not so sure :-( Servicing Stack http://catalog.update.microsoft.com/...aspx?q=3020369 July 2016 update rollup for Windows 7 SP1 http://catalog.update.microsoft.com/...aspx?q=3172605 Vista is a lot harder to fix, and Windows Update might never paint the screen with updates on that one. But I did get very lucky, and I found a single post from the wsusoffline forum with the list of updates to tip Vista upright again. The Wsusoffline guys have a text file with "prerequisites". These are patches they know they have to load first, before they call wuauserv. And while their methodology doesn't always work, it's the list of patches that I'm interested in. So I'll be "mining" that when necessary, from now on. If they know the answer, it'll be hiding in a file in their downloadable package. HTH, Paul I H too, but it didn't :-( -- Cheers, Bev "Anonymity is a shield from the tyranny of the majority." -- U.S. Supreme Court, McIntyre v Ohio Elections,1995 |
#14
|
|||
|
|||
windows Update 4 days
The Real Bev wrote:
I H too, but it didn't :-( What I couldn't believe, is when I got Vista to work :-) https://s29.postimg.org/fu3okxlw7/vi...t_finished.gif That might have been my third try, to get that working. And I didn't figure out the patches, someone else did. All I did is unearth the list with my shovel, by accident. If you've got the necessary patches installed, you can always try resetting Windows Update. That would be the script in "Option 2", as it would be nice to keep the Windows Update History intact. This script also works for Vista, but a section needs to be commented out. https://www.sevenforums.com/tutorial...ate-reset.html If one of the services won't play nice with the .bat, you can disconnect the network cable, reboot, then apply the .bat. When it's done, plug in the network cable and test. Paul |
#15
|
|||
|
|||
windows Update 4 days
In message , Paul
writes: [] If one of the services won't play nice with the .bat, you can disconnect the network cable, reboot, then apply the .bat. When it's done, plug in the network cable and test. Paul There have been times when I've felt like applying a bat to computers .. -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf Humans landed on the moon before we put wheels on our luggage. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|