Printer “Windows Update” - Why always so slow?












1














In every version of Windows I've tested, when you click the "Update Windows" button, before adding a printer, it is always so slow to complete updating. Even if you have top-notch hardware and a super fast internet connection, this is always slow.



What is going on behind the scenes that makes this process so slow and is there anything you can do about it besides "Have Disk"?



enter image description here










share|improve this question



























    1














    In every version of Windows I've tested, when you click the "Update Windows" button, before adding a printer, it is always so slow to complete updating. Even if you have top-notch hardware and a super fast internet connection, this is always slow.



    What is going on behind the scenes that makes this process so slow and is there anything you can do about it besides "Have Disk"?



    enter image description here










    share|improve this question

























      1












      1








      1







      In every version of Windows I've tested, when you click the "Update Windows" button, before adding a printer, it is always so slow to complete updating. Even if you have top-notch hardware and a super fast internet connection, this is always slow.



      What is going on behind the scenes that makes this process so slow and is there anything you can do about it besides "Have Disk"?



      enter image description here










      share|improve this question













      In every version of Windows I've tested, when you click the "Update Windows" button, before adding a printer, it is always so slow to complete updating. Even if you have top-notch hardware and a super fast internet connection, this is always slow.



      What is going on behind the scenes that makes this process so slow and is there anything you can do about it besides "Have Disk"?



      enter image description here







      windows-7 windows performance windows-update network-printer






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 13 '15 at 22:11









      LonnieBest

      58221933




      58221933






















          1 Answer
          1






          active

          oldest

          votes


















          2














          You may have top-notch nardware and super fast internet connection, but the server you're connecting to isn't that fast or is under heavy load all the time. This is why all Windows Update-related operations (including checking for updates and looking for drivers online) take so long.






          share|improve this answer

















          • 1




            That's too bad. When I do this task, I don't really want to update drivers, I just want to see a list of available drivers, select the driver I want, then have it download only that driver. Would be nice if it were designed like that. As slow as it is, it must be downloading a bunch of crap I don't even need. It should be a simple-quick database query, you'd think, to give a list of printer-drivers for my OS. Select Manufacturer, driver-name from database.table where OS='windows 7';
            – LonnieBest
            Feb 13 '15 at 22:26












          • Why do you think so? It's a time-consuming process, but it doesn't necessarily mean that your computer is downloading something all the time. I guess it's mostly waiting for the remote end to process your request and prepare a response.
            – gronostaj
            Feb 13 '15 at 22:29










          • Those types of queries should be cached for each OS already, and return a response lighting quick. As soon as you click the button it should already be downloading a list. This list could be saved in static file in the cloud, and updated daily by Microsoft. There's no excuse for such slowness in 2015.
            – LonnieBest
            Feb 13 '15 at 22:31












          • Unless it's not a static list, but rather something crafted for your system. I'm pretty sure Microsoft would use a faster (and cheaper to maintain) solution if it was possible. This is how they designed it and we have to deal with it. It's not perfect, but it works.
            – gronostaj
            Feb 13 '15 at 22:35






          • 1




            The sad thing is that Windows never gives useful feedback about downloading. The progress bar in IE6 worked like this: the first 50% was just a guess, based on computer speed or past download speeds. When it passed that 50% mark, it slowed down to half speed up to 75%. Then it became really slow, almost stopping at about 90%. And when the page finished, the progress bar filled up quickly. The same applies to many other progress bars in Windows 2000 and XP. In Windows 7 it doesn't work like this anymore, it just shows a thing that goes left and right and has no informational value at all.
            – SPRBRN
            Feb 13 '15 at 23:22











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f877721%2fprinter-windows-update-why-always-so-slow%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          You may have top-notch nardware and super fast internet connection, but the server you're connecting to isn't that fast or is under heavy load all the time. This is why all Windows Update-related operations (including checking for updates and looking for drivers online) take so long.






          share|improve this answer

















          • 1




            That's too bad. When I do this task, I don't really want to update drivers, I just want to see a list of available drivers, select the driver I want, then have it download only that driver. Would be nice if it were designed like that. As slow as it is, it must be downloading a bunch of crap I don't even need. It should be a simple-quick database query, you'd think, to give a list of printer-drivers for my OS. Select Manufacturer, driver-name from database.table where OS='windows 7';
            – LonnieBest
            Feb 13 '15 at 22:26












          • Why do you think so? It's a time-consuming process, but it doesn't necessarily mean that your computer is downloading something all the time. I guess it's mostly waiting for the remote end to process your request and prepare a response.
            – gronostaj
            Feb 13 '15 at 22:29










          • Those types of queries should be cached for each OS already, and return a response lighting quick. As soon as you click the button it should already be downloading a list. This list could be saved in static file in the cloud, and updated daily by Microsoft. There's no excuse for such slowness in 2015.
            – LonnieBest
            Feb 13 '15 at 22:31












          • Unless it's not a static list, but rather something crafted for your system. I'm pretty sure Microsoft would use a faster (and cheaper to maintain) solution if it was possible. This is how they designed it and we have to deal with it. It's not perfect, but it works.
            – gronostaj
            Feb 13 '15 at 22:35






          • 1




            The sad thing is that Windows never gives useful feedback about downloading. The progress bar in IE6 worked like this: the first 50% was just a guess, based on computer speed or past download speeds. When it passed that 50% mark, it slowed down to half speed up to 75%. Then it became really slow, almost stopping at about 90%. And when the page finished, the progress bar filled up quickly. The same applies to many other progress bars in Windows 2000 and XP. In Windows 7 it doesn't work like this anymore, it just shows a thing that goes left and right and has no informational value at all.
            – SPRBRN
            Feb 13 '15 at 23:22
















          2














          You may have top-notch nardware and super fast internet connection, but the server you're connecting to isn't that fast or is under heavy load all the time. This is why all Windows Update-related operations (including checking for updates and looking for drivers online) take so long.






          share|improve this answer

















          • 1




            That's too bad. When I do this task, I don't really want to update drivers, I just want to see a list of available drivers, select the driver I want, then have it download only that driver. Would be nice if it were designed like that. As slow as it is, it must be downloading a bunch of crap I don't even need. It should be a simple-quick database query, you'd think, to give a list of printer-drivers for my OS. Select Manufacturer, driver-name from database.table where OS='windows 7';
            – LonnieBest
            Feb 13 '15 at 22:26












          • Why do you think so? It's a time-consuming process, but it doesn't necessarily mean that your computer is downloading something all the time. I guess it's mostly waiting for the remote end to process your request and prepare a response.
            – gronostaj
            Feb 13 '15 at 22:29










          • Those types of queries should be cached for each OS already, and return a response lighting quick. As soon as you click the button it should already be downloading a list. This list could be saved in static file in the cloud, and updated daily by Microsoft. There's no excuse for such slowness in 2015.
            – LonnieBest
            Feb 13 '15 at 22:31












          • Unless it's not a static list, but rather something crafted for your system. I'm pretty sure Microsoft would use a faster (and cheaper to maintain) solution if it was possible. This is how they designed it and we have to deal with it. It's not perfect, but it works.
            – gronostaj
            Feb 13 '15 at 22:35






          • 1




            The sad thing is that Windows never gives useful feedback about downloading. The progress bar in IE6 worked like this: the first 50% was just a guess, based on computer speed or past download speeds. When it passed that 50% mark, it slowed down to half speed up to 75%. Then it became really slow, almost stopping at about 90%. And when the page finished, the progress bar filled up quickly. The same applies to many other progress bars in Windows 2000 and XP. In Windows 7 it doesn't work like this anymore, it just shows a thing that goes left and right and has no informational value at all.
            – SPRBRN
            Feb 13 '15 at 23:22














          2












          2








          2






          You may have top-notch nardware and super fast internet connection, but the server you're connecting to isn't that fast or is under heavy load all the time. This is why all Windows Update-related operations (including checking for updates and looking for drivers online) take so long.






          share|improve this answer












          You may have top-notch nardware and super fast internet connection, but the server you're connecting to isn't that fast or is under heavy load all the time. This is why all Windows Update-related operations (including checking for updates and looking for drivers online) take so long.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 13 '15 at 22:20









          gronostaj

          28k1368107




          28k1368107








          • 1




            That's too bad. When I do this task, I don't really want to update drivers, I just want to see a list of available drivers, select the driver I want, then have it download only that driver. Would be nice if it were designed like that. As slow as it is, it must be downloading a bunch of crap I don't even need. It should be a simple-quick database query, you'd think, to give a list of printer-drivers for my OS. Select Manufacturer, driver-name from database.table where OS='windows 7';
            – LonnieBest
            Feb 13 '15 at 22:26












          • Why do you think so? It's a time-consuming process, but it doesn't necessarily mean that your computer is downloading something all the time. I guess it's mostly waiting for the remote end to process your request and prepare a response.
            – gronostaj
            Feb 13 '15 at 22:29










          • Those types of queries should be cached for each OS already, and return a response lighting quick. As soon as you click the button it should already be downloading a list. This list could be saved in static file in the cloud, and updated daily by Microsoft. There's no excuse for such slowness in 2015.
            – LonnieBest
            Feb 13 '15 at 22:31












          • Unless it's not a static list, but rather something crafted for your system. I'm pretty sure Microsoft would use a faster (and cheaper to maintain) solution if it was possible. This is how they designed it and we have to deal with it. It's not perfect, but it works.
            – gronostaj
            Feb 13 '15 at 22:35






          • 1




            The sad thing is that Windows never gives useful feedback about downloading. The progress bar in IE6 worked like this: the first 50% was just a guess, based on computer speed or past download speeds. When it passed that 50% mark, it slowed down to half speed up to 75%. Then it became really slow, almost stopping at about 90%. And when the page finished, the progress bar filled up quickly. The same applies to many other progress bars in Windows 2000 and XP. In Windows 7 it doesn't work like this anymore, it just shows a thing that goes left and right and has no informational value at all.
            – SPRBRN
            Feb 13 '15 at 23:22














          • 1




            That's too bad. When I do this task, I don't really want to update drivers, I just want to see a list of available drivers, select the driver I want, then have it download only that driver. Would be nice if it were designed like that. As slow as it is, it must be downloading a bunch of crap I don't even need. It should be a simple-quick database query, you'd think, to give a list of printer-drivers for my OS. Select Manufacturer, driver-name from database.table where OS='windows 7';
            – LonnieBest
            Feb 13 '15 at 22:26












          • Why do you think so? It's a time-consuming process, but it doesn't necessarily mean that your computer is downloading something all the time. I guess it's mostly waiting for the remote end to process your request and prepare a response.
            – gronostaj
            Feb 13 '15 at 22:29










          • Those types of queries should be cached for each OS already, and return a response lighting quick. As soon as you click the button it should already be downloading a list. This list could be saved in static file in the cloud, and updated daily by Microsoft. There's no excuse for such slowness in 2015.
            – LonnieBest
            Feb 13 '15 at 22:31












          • Unless it's not a static list, but rather something crafted for your system. I'm pretty sure Microsoft would use a faster (and cheaper to maintain) solution if it was possible. This is how they designed it and we have to deal with it. It's not perfect, but it works.
            – gronostaj
            Feb 13 '15 at 22:35






          • 1




            The sad thing is that Windows never gives useful feedback about downloading. The progress bar in IE6 worked like this: the first 50% was just a guess, based on computer speed or past download speeds. When it passed that 50% mark, it slowed down to half speed up to 75%. Then it became really slow, almost stopping at about 90%. And when the page finished, the progress bar filled up quickly. The same applies to many other progress bars in Windows 2000 and XP. In Windows 7 it doesn't work like this anymore, it just shows a thing that goes left and right and has no informational value at all.
            – SPRBRN
            Feb 13 '15 at 23:22








          1




          1




          That's too bad. When I do this task, I don't really want to update drivers, I just want to see a list of available drivers, select the driver I want, then have it download only that driver. Would be nice if it were designed like that. As slow as it is, it must be downloading a bunch of crap I don't even need. It should be a simple-quick database query, you'd think, to give a list of printer-drivers for my OS. Select Manufacturer, driver-name from database.table where OS='windows 7';
          – LonnieBest
          Feb 13 '15 at 22:26






          That's too bad. When I do this task, I don't really want to update drivers, I just want to see a list of available drivers, select the driver I want, then have it download only that driver. Would be nice if it were designed like that. As slow as it is, it must be downloading a bunch of crap I don't even need. It should be a simple-quick database query, you'd think, to give a list of printer-drivers for my OS. Select Manufacturer, driver-name from database.table where OS='windows 7';
          – LonnieBest
          Feb 13 '15 at 22:26














          Why do you think so? It's a time-consuming process, but it doesn't necessarily mean that your computer is downloading something all the time. I guess it's mostly waiting for the remote end to process your request and prepare a response.
          – gronostaj
          Feb 13 '15 at 22:29




          Why do you think so? It's a time-consuming process, but it doesn't necessarily mean that your computer is downloading something all the time. I guess it's mostly waiting for the remote end to process your request and prepare a response.
          – gronostaj
          Feb 13 '15 at 22:29












          Those types of queries should be cached for each OS already, and return a response lighting quick. As soon as you click the button it should already be downloading a list. This list could be saved in static file in the cloud, and updated daily by Microsoft. There's no excuse for such slowness in 2015.
          – LonnieBest
          Feb 13 '15 at 22:31






          Those types of queries should be cached for each OS already, and return a response lighting quick. As soon as you click the button it should already be downloading a list. This list could be saved in static file in the cloud, and updated daily by Microsoft. There's no excuse for such slowness in 2015.
          – LonnieBest
          Feb 13 '15 at 22:31














          Unless it's not a static list, but rather something crafted for your system. I'm pretty sure Microsoft would use a faster (and cheaper to maintain) solution if it was possible. This is how they designed it and we have to deal with it. It's not perfect, but it works.
          – gronostaj
          Feb 13 '15 at 22:35




          Unless it's not a static list, but rather something crafted for your system. I'm pretty sure Microsoft would use a faster (and cheaper to maintain) solution if it was possible. This is how they designed it and we have to deal with it. It's not perfect, but it works.
          – gronostaj
          Feb 13 '15 at 22:35




          1




          1




          The sad thing is that Windows never gives useful feedback about downloading. The progress bar in IE6 worked like this: the first 50% was just a guess, based on computer speed or past download speeds. When it passed that 50% mark, it slowed down to half speed up to 75%. Then it became really slow, almost stopping at about 90%. And when the page finished, the progress bar filled up quickly. The same applies to many other progress bars in Windows 2000 and XP. In Windows 7 it doesn't work like this anymore, it just shows a thing that goes left and right and has no informational value at all.
          – SPRBRN
          Feb 13 '15 at 23:22




          The sad thing is that Windows never gives useful feedback about downloading. The progress bar in IE6 worked like this: the first 50% was just a guess, based on computer speed or past download speeds. When it passed that 50% mark, it slowed down to half speed up to 75%. Then it became really slow, almost stopping at about 90%. And when the page finished, the progress bar filled up quickly. The same applies to many other progress bars in Windows 2000 and XP. In Windows 7 it doesn't work like this anymore, it just shows a thing that goes left and right and has no informational value at all.
          – SPRBRN
          Feb 13 '15 at 23:22


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f877721%2fprinter-windows-update-why-always-so-slow%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Terni

          A new problem with tex4ht and tikz

          Sun Ra