• =?UTF-8?B?4oCcSWY=?= the November Windows update fails to install on your PC, =?UTF-8?B?aGVyZeKAmXMgd2hhdCB0byBkb+KAnQ==?=

    From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.advocacy,comp.os.ms-windows.advocacy on Thu Nov 12 23:04:53 2026
    From Newsgroup: comp.os.linux.advocacy

    <https://www.zdnet.com/tech/microsoft-windows-november-update-fails-install-some-pcs/>

    WasnrCOt there supposed to be some kind of automatic rollback so that a
    borked Dimdows machine could recover from a failed update by itself?

    Or was that automatic rollback mechanism also screwed by this update?
    (No big surprise there ...)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From JJ@jj4public@gmail.com to comp.os.linux.advocacy,comp.os.ms-windows.advocacy on Fri Nov 13 12:07:08 2026
    From Newsgroup: comp.os.linux.advocacy

    On Thu, 12 Nov 2026 23:04:53 -0000 (UTC), Lawrence DoOliveiro wrote:
    <https://www.zdnet.com/tech/microsoft-windows-november-update-fails-install-some-pcs/>

    Wasnot there supposed to be some kind of automatic rollback so that a
    borked Dimdows machine could recover from a failed update by itself?

    Or was that automatic rollback mechanism also screwed by this update?
    (No big surprise there ...)

    This is why I only do manual update after at least a month of the update release. I don't want to be a lab rat.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.advocacy,comp.os.ms-windows.advocacy on Fri Nov 13 06:19:18 2026
    From Newsgroup: comp.os.linux.advocacy

    On Fri, 13 Nov 2026 12:07:08 +0700, JJ wrote:

    On Thu, 12 Nov 2026 23:04:53 -0000 (UTC), Lawrence DrCOOliveiro wrote:
    <https://www.zdnet.com/tech/microsoft-windows-november-update-fails-install-some-pcs/>

    WasnrCOt there supposed to be some kind of automatic rollback so that
    a borked Dimdows machine could recover from a failed update by
    itself?

    Or was that automatic rollback mechanism also screwed by this
    update? (No big surprise there ...)

    This is why I only do manual update after at least a month of the
    update release. I don't want to be a lab rat.

    But then, if you wait a month, then itrCOs already time for the next update. --- Synchronet 3.22a-Linux NewsLink 1.2
  • From JJ@jj4public@gmail.com to comp.os.linux.advocacy,comp.os.ms-windows.advocacy on Sat Nov 14 11:48:44 2026
    From Newsgroup: comp.os.linux.advocacy

    On Fri, 13 Nov 2026 06:19:18 -0000 (UTC), Lawrence DoOliveiro wrote:

    But then, if you wait a month, then itos already time for the next update.

    Not every update is for the previous one. But if it is, it'll just be
    postponed even further. Because it means that, the previous update was half-a$$ed.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.advocacy,comp.os.ms-windows.advocacy on Sat Nov 14 04:58:04 2026
    From Newsgroup: comp.os.linux.advocacy

    On Sat, 14 Nov 2026 11:48:44 +0700, JJ wrote:

    On Fri, 13 Nov 2026 06:19:18 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    But then, if you wait a month, then itrCOs already time for the next
    update.

    Not every update is for the previous one. But if it is, it'll just
    be postponed even further. Because it means that, the previous
    update was half-a$$ed.

    But if you skip an update and go on to the next one, then you are
    running a configuration that Microsoft likely has not tested properly.
    I expect their testing regime for each update assumes that all prior
    updates have been applied, because it would get too expensive
    and cut into their profits otherwise.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.advocacy,comp.os.ms-windows.advocacy on Sat Nov 14 07:01:16 2026
    From Newsgroup: comp.os.linux.advocacy

    On Sat, 14 Nov 2026 04:58:04 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    But if you skip an update and go on to the next one, then you are
    running a configuration that Microsoft likely has not tested properly.
    I expect their testing regime for each update assumes that all prior
    updates have been applied, because it would get too expensive and cut
    into their profits otherwise.

    I skipped October. So far I'm 35 minutes into updating the laptop. I
    should have paid more attention but the 'updating Windows. Do not turn off
    the computer' took forever and a day. It rebooted and is going back for
    some more security updates. Another 4 minutes with three restarts. It
    tells me 26H2 is available. I don't think so. Maybe next year.

    I could have installed any Linux distro under the sun, updated it, and installed my usual workload faster. If I didn't already have 2 Linux
    laptops it would be a done deal.
    --- Synchronet 3.22a-Linux NewsLink 1.2