back to article Microsoft to intro checkpoint cumulative updates for Win 11

Microsoft is making yet another attempt to combat update bloat with checkpoint cumulative updates coming to both Windows 11 24H2 and Windows Server 2025. Windows Insiders on the Dev Channel can already preview what Microsoft is planning in build 26120.1252. Microsoft previously endeavored to reduce the size of updates via …

  1. TrevorH

    It's not the bloody size, it's the TIME it takes. I can update 100 linux systems while the progress bar on Windows Update is still spinning. How can it possibly take longer to patch an installed windows system than it does to install it in the first place?

    1. may_i Silver badge

      That's a very good question! I've long failed to understand why any windows update, differential or otherwise, takes several orders of magnitude more time to install than a bunch of updates on any Linux system that I run.

    2. DS999 Silver badge

      I'm not sure

      But I bet it has a lot to do with the registry.

      On Linux you're just replacing a bunch of files. On Windows you're replacing a bunch of files but also having to update registry information since it uses that as a central store for everything and mostly avoids text configuration files.

      The problem is that the registry is a single choke point, with no parallelism possible when updating it. If they want to improve the speed of patching, my guess would be making the registry into a proper database that allows multiple threads to make changes in parallel would be a far bigger win than anything that reduces the bandwidth consumed by downloading updates.

      1. xanadu42

        Re: I'm not sure

        "If they want to improve the speed of patching, my guess would be making the registry into a proper database that allows multiple threads to make changes in parallel would be a far bigger win than anything that reduces the bandwidth consumed by downloading updates."

        Changing the registry to a "proper database" wouldn't improve this much as the updating of the registry files would still be a bit of a bottleneck...

        I think a better solution would be to revert back to INI files - say one for each of the various subsystems...

        And think of the benefits... Backup one small INI file (a few kilobytes) before implementing a change and if the change stuffs up do a restore - much quicker than backup/restore of the 100 or so megabytes of registry...

        And you could even use a text editor of your choice!

        1. seven of five Silver badge

          Re: I'm not sure

          blink.

          double blink.

          well. duh... you know who's the greatest and bestest whizzzkid at Micros~1 these days? Kinda controversial guy, has had a past run in with linux? Not the one to fancy plain text, read- and editable ini files...

          I mean, it DOES make a lot of sense to me, but ... that might be hard to sell with them.

          And this "(text editor) of you choice" ... quite sure Micros~1 doesn't mean the same thing as we do do when it comes to "your" and "choice".

        2. thosrtanner

          Re: I'm not sure

          Urgh. The registry is evil. It stops you being able to back up your settings and restore them on a new machine. I can understand this for *some* bits of the system, but every damn application uses this for all of their settings, the vast majority of which have no relationship to what the machine you're running on is.

        3. PeterM42
          FAIL

          Re: I'm not sure

          I have always felt that the registry is a major security hole in Windows NT.

          A simple .reg file cqn cause havoc.

    3. WereWoof

      Also why does Windows Update slow a machine to swimming in molasses speed when Linux updates do not?

  2. RAMChYLD Bronze badge
    Coat

    Oh, yay. More frequent reboots.

    > End users are unlikely to notice much difference, except that updates will often be smaller.

    You sure I wont notice it when my computer has to reboot to apply updates more frequently?

  3. Anonymous Coward
    Boffin

    Why Windows update takes ages.

    @may_i: “That's a very good question! I've long failed to understand why any windows update, differential or otherwise, takes several orders of magnitude more time to install than a bunch of updates on any Linux system that I run.

    Windows mixes functionality throughout the OS. Therefore making it difficult to clone. That also making it difficult to update. I've had problems uninstalling app(a) and app(b) decides it's become unlicensed. Windows, a right royal pain!

    1. PeterM42
      Facepalm

      Re: Why Windows update takes ages.

      The mixing of applications and OS is a major design failing of Windows (and many other OSs).

      To ensure better security (and efficiency), the OS should be as isolated from applications as possible, with only well-defined links between the 2.

      And don't get me started on DLLs!

  4. David Hicklin Silver badge

    Individual Patches

    Whilst they are at it why not go back to the original individual patches like we used to have so that if one borks things then we can just roll that one back

    Then every now and again you can have a "roll up" package....they used to be called service packs.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

Other stories you might like