Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Windows Microsoft Operating Systems

Microsoft Says Windows May Need Up To 8 Hours of Online Time To Update (tomshardware.com) 124

According to a post on the Microsoft IT Pro Blog, Windows computers will need at least eight hours of online time to obtain and install the latest OS updates successfully. Tom's Hardware reports: Another revelation in the post is that Microsoft tracks how long PCs are connected to Windows Update, calling the statistics "Update Connectivity." The data is available to IT managers in the InTune app, a component of the Endpoint management suite. The post details Microsoft's attempts to figure out why some Windows devices aren't getting the latest quality and feature updates, and discovered that two hours of continuous connectivity was required to get updates. It then took six hours after the release of the patch for a machine to update itself reliably.

Microsoft's figures show that 50 percent of Windows devices left behind by Windows Update and running a build of Windows 10 that's no longer serviced do not spend enough time connected to have the patches downloaded and installed in the background. This figure drops to 25 percent for customers using a serviced build of the operating system that lags behind in security updates by 60 days or more.
The goods news, as noted by Tom's Hardware, is that "Windows 11 updates are smaller than their Windows 10 counterparts due to improved compression [and] new Microsoft Graph APIs," which should help speed up the update process.
This discussion has been archived. No new comments can be posted.

Microsoft Says Windows May Need Up To 8 Hours of Online Time To Update

Comments Filter:
  • by Major_Disorder ( 5019363 ) on Tuesday February 01, 2022 @07:29PM (#62228505)
    8 hours to update? Just updating? Seriously? WTF
    • During which time the machine cannot be used. WTF.

      • No, that is background download time. Perhaps Microsoft only allows each connection a tiny data rate, and it more of an administration/resources problem that a Windows OS problem.

        • I don't care why it happens. The point is it is an absurd amount of time.
          • by awwshit ( 6214476 ) on Tuesday February 01, 2022 @07:56PM (#62228579)

            Its not really anything new. It used to be that if you installed Windows fresh, from say the CD the computer came with, you have to download potentially hundreds of updates. Now each one of those updates didn't take long but collectively they did take a while. But once you were up to date, Windows Update would only deliver the specific updates that you needed moving forward. At some point Microsoft moved to Cumulative Updates so you get one download that contains all of the history, but of course its bigger as a single update. Microsoft releases that Cumulative update monthly. No wonder it takes longer than in the past. But really I think its probably more about infrastructure and bandwidth limits. Also, Windows can be setup to pull updates from other computers on the LAN that already have them.

            You can always find the updates, download them, and install them manually. I'll bet its faster than Windows Update.
            https://www.catalog.update.mic... [microsoft.com]

            • by Z00L00K ( 682162 )

              I don't have a problem with the cumulative update when I do install a fresh computer, but for a computer that only needs a few since last time it's a headache for anyone with a slow or spotty internet connection.

              Microsoft has done a lot of not so smart things throughout their presence, some of them have been resulting in things like "Melissa" and "SQL Slammer".

              And it seems to come in waves as well, so maybe it's that each time Microsoft has a generation shift then similar mistakes are repeated.

            • I worked a year on a Windows PC behind a "corporate black network". When going "public", Windows update (the Windows XP days as I remember) took about half a day.

        • Yes, I think it's data rate. It's absurdly slow even on a fast computer with a high speed connection.

      • Comment removed based on user account deletion
      • by kiminator ( 4939943 ) on Tuesday February 01, 2022 @07:59PM (#62228587)
        That's not how I read it. This isn't the time spent actively updating. Rather, if the machine isn't online for 8 hours at a stretch, the auto-update feature running in the background may simply fail to complete and the actual install will never start.
      • Yeah, it doesn't say that in any way whatsoever.
    • And that's with a solid state drive. Imagine the time required for a 5400 rpm platter drive. What takes the process so long? You can install Ubuntu probably 20-30 times from scratch in 8 hours.

      • And that's with a solid state drive. Imagine the time required for a 5400 rpm platter drive. What takes the process so long? You can install Ubuntu probably 20-30 times from scratch in 8 hours.

        And pull down all the patches each time.

        • Re: (Score:2, Troll)

          by batkiwi ( 137781 )

          - install ubuntu that's a 2 years old and isn't an LTS
          - ***throttle your downloads for apt-get so that no one on your network would notice the data usage***
          - - Windows defaults that to 2.6 Mbps so do that. Mbps, not MBps
          - turn your machine on and use it for 2 hours
          - turn it off

          You're telling me that it would fully update and upgrade to the latest release?

          • Updating maybe. Bandwidth will be the biggest issue.
            It will come close at least. Windows does patch after patch after patch on on the same item. Linux just goes to the latest version in one go.

            Upgrading to the latest distro version is more comparable to a new version of Windows, not normal updating.
      • This is what pissed me off so much about Windows. I would have updates that would take hours sometimes, while linux could always update within minutes. I don't miss moving on from windows.

      • by BranMan ( 29917 )

        What takes so long? Having 100s of GIGABYTES of executable code in an operating system. That's what.

        The bloat was astonishing a decade ago. Now it's just embarrassing.

    • by tlhIngan ( 30335 )

      8 hours is on the low end.

      Try provisioning a Windows 7 machine from scratch today - yes I know Windows 7 is out of date, but you'll probably spend 24 hours of checking updates and downloading and installing updates. If you install the rollup pack, it brings it down to about half that.

      What makes it worse is that you can't just click "get me every damn update" - you have to get a bunch of updates, let it install, reboot, then click check updates again, get more updates, install, click again, get more updates,

      • by Wolfrider ( 856 )

        Have you been living under a rock? This is why you keep a WSUS OFFLINE update ISO around for win7 and do it all without Internet

    • 8 hours to update? Just updating? Seriously? WTF

      No not seriously. 8 hours on a very slow connection to download and provision the update. For me, the time taken between hitting the install now button and actually having Windows 11 running was less than an hour. During that time I kept using my computer for above 40min.

      In other news: Downloading requires you to be online.

    • by dddux ( 3656447 )

      Fun fact: it takes me 20 minutes to install Debian Linux 10 from the network with a network installation ISO and start browsing the Internet after installing uBlock Origin and NoScript add-ons. :)

    • by Kaenneth ( 82978 )

      Massive improvement.

      I once did a factory reset on a Surface tablet, and it took over 36 hours to re-update.

    • by gweihir ( 88907 )

      8 hours to update? Just updating? Seriously? WTF

      Microsoft is a bureaucracy. Bureaucracies thrive on "binding" (i.e. wasting) the time of others and measure their importance by how much hours of others they can so control. And bureaucracies always want more and never produce solid results when they actually do work themselves.

  • by battingly ( 5065477 ) on Tuesday February 01, 2022 @07:32PM (#62228517)
    This is how you know your software is excessively bloated.
  • Gets the job done in a few minutes. Just saying.

    • by godrik ( 1287354 )

      even when I update my debian from one stable to the next stable, it does not take 8 hours. It takes, maybe 2 hours.

      WTF are they doing?

  • Seriously, my PC is connected 24/7 to the internet. What the hell is MS talking about?
    • Less than 1% of your connection is used for downloading the updates. The other 99% is allocated by Microsoft for data collection on your system (aka telemetry).
  • Maybe too sparse for developed countries like the US.

    But here in Venezuela, my BW is 14Mbps down, 750Mps up. windows Update has never been a problem in terms of the machine hogging the net connection.

    I do not like the stream on my TV interrupted/freezed by a computer updating, nor my other machines (or phones) become unable to browse the net because one machine is hoging the net for an update (like it happens to me when any of my two macs update).

    Having said that, yes, the update mechanism somehow renders t

  • by Goatbot ( 7614062 ) on Tuesday February 01, 2022 @07:58PM (#62228583)
    Ran into this issue for two reasons. One because I didn't have the bandwidth to update 128Kbps satellite internet. Two, devices that stay powered off for extended periods. When you go to use the system after being off for few months or more the computer is almost unusable until it finishes updating.
    • I'm pretty sure you can install just about any version of Linux faster than 8 hours and then you'll never run into the forced update again. Heck, you can probably do a clean install of any OS, including Windows, in less than 8 hours.

    • by Waccoon ( 1186667 ) on Tuesday February 01, 2022 @10:18PM (#62228991)

      It's not just updates. I've occasionally turned on a Win10 machine after leaving it dormant for a few months, and the system is locked up solid for literally a couple hours until it finishes doing things in the background. Once, it took several minutes just to launch Notepad. The trouble is, the machines do this even while the Internet is disconnected.

      No wonder updates are so slow. The background maintenance tasks go out of their way to look for problems that aren't there when nothing has changed.

      • 100% it is compounded by the fact people heavily use mobile devices as an alternative. I really only turn on a Windows machine when I need one now as just leaving it running was eating electricity and not providing any functionality. It's actually easier to run windows as virtual machine nowadays.
      • My windows machine gets turned on for about an hour, maybe two, each morning, four hours Friday afternoons and a few hours on Saturday. Inevitably, one of the times each week I turn it on, it's unusable for several minutes to an hour and a half. Which is really frustrating when I have limited time and want to accomplish something with it.

        If I could get Scrivener and PDF PRO working on Linux, I'd stay on that partition permanently.

  • Failure (Score:4, Interesting)

    by quonset ( 4839537 ) on Tuesday February 01, 2022 @08:06PM (#62228611)

    If it takes 8 hours to get an "update", you have failed. Miserably. It is wholly incomprehensible to claim this is the norm. Not in the 21st century. Are they pushing it out via dial-up?

    On the other hand, seeing how slow Windows 10 is at doing the simplest of tasks, this shouldn't be surprising. Want to log into a machine for the first time? Go get a drink. Want to restart your machine? Go get a book. It is excruciating how slow 10 is. It's always preparing to do something, telling you this might take a while, telling you to wait while it spins it hamster wheel. Rarely does it just do something.

    • If it takes 8 hours to get an "update", you have failed.

      I guess Linux is a failure then. It took me 8 hours to download it back before I got cable as well.

      Hint: No it doesn't take 8 hours to update. Windows update doesn't start downloading until your computer has been up for a significant period of time, and with low background priority will use very little bandwidth.

      When you don't piss off the user by saturation their connection while they are trying to use the PC, except the update to take a while. That isn't a failure. It is the very definition of respectful

  • Business ?? (Score:1, Flamebait)

    by jmccue ( 834797 )

    What about businesses, is M/S asking for 8 hours of downtime for their Business Customers ?

    I thought my Work workstation running RHEL forcing a reboot after a chrome patch was bad (I found a workaround for this). But this shows RHEL an other distros are far more sane then what Windows is pushing out. Not that I needed proof :)

    I wonder what the cost to the S&P 500 will be for this ?

    • Re: (Score:3, Insightful)

      RHEL forcing a reboot after a chrome patch?

      Chrome is Google's web browser. Why in the world would it require a reboot? Just close and re-open your web browser and you're all set.

      There are a few occasions when you need to reboot after an update, but Chrome isn't one of them. (And even when you do need to reboot you can usually do it at your convenience, it isn't "forced".)

    • by batkiwi ( 137781 )

      What about businesses, is M/S asking for 8 hours of downtime for their Business Customers ?

      Did you read the summary let alone the article?

      No where does it discuss 8 hours of down time.

      8 hours of ONLINE time in order to background download the patches without disrupting their net connection if you're not using a local SCCM patch server.
      If your users only turn on their desktops for an hour or two a day (eg light admin usage) and then turn them off they might never get patched fully.

      The same exact thing will happen with RHEL if you don't patch it for 1.5 years and then pull down patches in a throttl

    • Most business users have their machine turned on long enough for the updates to download and install. It's the mom & pop that turn the computer on to get their e-mail or look something up on the web for an hour that don't get the updates, and that's even worse. Unlike business users whose machines are managed they don't know that they're missing out on important fixes. All they see is a bubble that their Norton/McAfee has updated and they think they're fine.
      • First of all, let me make clear that I think it is best if computers run on fully updated software.

        But being a Devil's advocate here:
        Are those systems that are turned on an hour or so a day a really big security risk? As long as they are turned off, they are not part of any botnet. Even if those computers were infected, I mean.

        Computers that are not turned on for very long periods of time, do usually a specific task and not much more. This also reduces risk of possible infections.

        In short, is this not perce

  • IT admins everywhere are stocking up on coffee and warm hats for the long nights. 8 hours is ludicrous.
  • What is structurally different between Linux and Windows here?

    I've never been able to figure out why both checking and installing updates takes so long on Windows. Say you have 5000 components, surely you send a packet with 5000 id/version pairs and get a response as to which can be upgraded. Even with complicated interdependencies, how does solving this take more than a few milliseconds on a modern CPU in their update server farm? Is it something to do with Windows being unable to replace binaries on disk

    • The biggest structural difference I can think of is that Linux and applications for Linux are designed to tolerate deleting a file while it is open. If a file is deleted and replaced, processes that already had that file open continue to see the previous file, whereas newly started processes that open the file see a new file. The old file is actually deleted once the last process closes it. This lets package managers use rename-and-replace on system libraries. Processes continue running with the old version

      • by Kaenneth ( 82978 )

        And good luck if the replaced-while-running component needs to communicate with other instances of itself (like resource sharing, or updating the same database file) and the versions are incompatible.

      • by gweihir ( 88907 )

        Indeed. I would say the older approach (UNIX) is better, but the folks at MS probably do not even know what UNIX did and Linux does now because they are far too full of themselves.

    • by Kaenneth ( 82978 )

      An example from Windows history.

      The TCP/IP component had help files, so depended on the Help system being installed.

      The Help system needed to display HTML to the user, so depended on Internet Explorer being installed.

      Internet Explorer needed network access, so depended on TCP/IP being installed.

      If you need to update all of those, which do you do first?

      Unwinding that type of spaghetti from Windows was (and probably still is) a major project at MS, reworking Windows into distinct layers progressively.

      https:// [wikipedia.org]

    • by BranMan ( 29917 )

      Structural differences between them are legion. Linux has a kernel design - one small monolithic executable that runs the hardware (loading drivers, talking to hardware, etc.) in kernel space while everything else - as much as humanly possible - is in user space. You can replace anything in user space while the system is up.

      Microsoft has a massive executable footprint in kernel space - device drivers, etc. too, but also the UI, web browser, all the shared libraries that all the other applications use, etc

  • Holy cow. My routine Debian updates take minutes, counting both download time and time to apply the updates. Even going from Buster to Bullseye was maybe 30 minutes of download time and an hour to apply.

    What the heck does the Windows update architecture look like to take that long?

  • If only there was a way to download a cumulative set of updates as one big update. I nominate we call it a Service Pack. Shame that we don't have the technology for this advanced feature. /s

  • Normal. (Score:4, Insightful)

    by putnamca ( 5596549 ) on Tuesday February 01, 2022 @10:34PM (#62229035)
    We've normalized this. It's normal. Nothing to see, here.
    • No it's not normal. It's a worst case scenario for a failure of the update process to start. "Normal" is your computer asking you to reboot, and being greeted with Windows 11 up and running 10-15min later. That's how 99.9% of upgrades happen.

    • by Wolfrider ( 856 )

      > We've normalized this

      You know what slashdot, FUCK your lameness filter.

      So MUCH this. When you start using different non-windows-based OSes and take a couple of steps back from what you have to-now considered "normal" you realize a few things:

        Windows is a shitshow and has been for YEARS

        MS is an abusive company that doesn't care about your uptime or productivity

        They FIRED their ENTIRE QA team YEARS ago

  • Expect more and more people to Google for patches/hacks to stop auto updating thus not getting the patches at all.

    If it takes 8 hours, then something is really fucked up with the Windows ecosystem.

    And of course, that huge amount of bloat will require more future patches and updates to fix everything that's broken.

    Stick a fork in it, it's done. It's so bloated and archaic now that not even a team of M$'s programmers really understand how the OS works anymore. Now the only options left are to leave Windows as

    • "then something is really fucked up with the Windows ecosystem." It has been since Windows 8 and especially when Satya Nadella took over. He creeps me out with all his telemetry. Digital pervert.
  • So that user perceives value and makes time to install them. We need to handle "or else you will get hacked and have to pay ransom" in some other way. Most users run a small number of local apps, so those can be either prescreened by a reputable app store or open source and open to public scrutiny. If you are running a business, you can be required to buy malpractice/negligence insurance to be listed in app store, and insurance can take interest in your practices. If you are not interested in running busine

  • We've reached the new Singularity, in which Microsoft is writing patches faster than computers can download them. It's only a matter of time before people realize it's faster to install earlier (read: smaller) versions of Windows, and start downgrading to Windows 7, then XP, then 2000, etc.
  • by EnsilZah ( 575600 ) <EnsilZah.Gmail@com> on Wednesday February 02, 2022 @01:11AM (#62229341)

    8 hours during which Windows won't nag me about restarting to install updates? I'll take it.

  • by peppepz ( 1311345 ) on Wednesday February 02, 2022 @03:44AM (#62229487)
    Microsoft's programmers live in an alternate reality where they are entitled to any kind of disservice to their customers. You pay 300+ bucks for a software that constantly spies on you, takes 8 hours to update (when it doesn't fail), won't let you decide if and when to install updates or even *know* what's inside an update before installing it, is in perpetual beta test, is slow even on very expensive hardware, serves you ads as part of the user interface, fools you with its user interface, pardon, "experience", and with every update removes critical features that you need to work. Because of their company's monopolistic position, they don't work for you, they work for themselves, and then the fact that you happen to use their product is just a side effect.
    • > Microsoft's programmers live in an alternate reality where they ...
      Assume the point of the computer is running windows/MS products, it is never turned off (let alone for longer periods), has permanent broadband connectivity and the user uses it exactly how they thought up the "flow"

      You can substitute any other sw company name for Microsoft, it would still work.

      • True, but the peculiarity of Microsoft products is that you have to use them because everyone else is. You don't really have a choice, and this means that they get to do whatever they want.

        Also, the things that I have seen with Microsoft's post-Metro user interfaces, I have seen nowhere else.

    • Oh stop it with the horseshit. Microsoft programmers know what they are doing and do it *because* of their customers. The reason it takes 8 hours on a slow connection is precisely because the update process throttles back the download while the user is using their PC, it also runs the upgrade process itself in the lowest system priority allowing a user to happily use their computer for 7hours and 50min of this 8 hour period (which MS quotes as a worst case).

      When you're done talking out of your arse join us

      • Oh stop it with the horseshit. Microsoft programmers know what they are doing and do it *because* of their customers.

        You mean that they rebooted my computer without a warning and without my consent, causing me to lose my work, in order to install a completely undocumented "update", *because* they knew that they'd upset me?
        I don't think this is the case, though. You're being too harsh to them.

        • You mean that they rebooted my computer without a warning and without my consent

          No it's 2022 meaning you're a dumbass who wasn't paying attention. Windows introduced warnings that sit in your notification telling you when it reboot as well as instructions on how to set your active hours back in 2018. If Windows has at all interrupted your work at any point in the past 4 years it's literally 100% *your* fault.

          Learn how to use your computer. It's simple, all you have to do is look at a popup.

          • Do you work at Microsoft perchance? Because you seem to live in the same alternate reality as them, where it's my duty to actively prevent them from rebooting my computer while I have unsaved work.
    • by gweihir ( 88907 )

      While true, the 2nd half of the problem is customers that take the abuse and ask for more. If MS became adequate feedback for all the time and effort of others they have been wasting, they would have gone out of business a long time ago. Instead, they can basically do whatever they like to their customers now and never suffer any consequences.

  • I guess the 'intelligent' in Background Intelligent Transfer Service should be changed to 'unintelligent'
  • I like the last bit

    The goods news, as noted by Tom's Hardware, is that "Windows 11 updates are smaller than their Windows 10 counterparts due to improved compression [and] new Microsoft Graph APIs," which should help speed up the update process.

    So, this tell me that they need to make there shit better.

  • Is it possible that the problem, much like the problem with Make, is that full dependency checking is an exponential problem?

  • How is that a sane update process?

    I don't think I've had the displeasure of using Windows for 8 hours in the last year... cumulatively.

    I don't miss dealing with this kind of hostility.

  • As a tech helper at my local library, I often dealt with computers that had not been run for 6 months at a time. I always advise people "Plug it in, connect to the internet and leave it on overnight, watch it when it first starts and if it asks "Do you want to install this update?" click Yes. Check it in the morning ... and possibly do it all again the next night. Once it is done, it should run OK. If it bogs down again: rinse & repeat!

    I'm typing this on a desktop running Xubuntu ...

God help those who do not help themselves. -- Wilson Mizner

Working...