<https://www.reddit.com/r/Windows10/comments/zl2mcr/cumulative_updates_december_13th_2022/>

<https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22H2#2986msgdesc>

Seems to really hate some Sandy Bridge/Ivy Bridge machines, I use a
Fujitsu Lifebook which has some nice features like a VGA output (for
connecting to older projectors) and easily-replaceable battery and the
update took it down real good

On 12/23/2022 7:54 AM, bitrex wrote:
> <https://www.reddit.com/r/Windows10/comments/zl2mcr/cumulative_updates_december_13th_2022/>
>
> <https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22H2#2986msgdesc>
>
> Seems to really hate some Sandy Bridge/Ivy Bridge machines, I use a Fujitsu
> Lifebook which has some nice features like a VGA output (for connecting to
> older projectors) and easily-replaceable battery and the update took it down
> real good

My strategy with MS is to image the machine (the OS drive) before
every update. Then, I can get back to the prior state without
relying on MS knowing how to undo it's f*ckups.

But, I manually apply updates so I know when the risky exists.

Also, most machines are airgapped so there's very little reason for me
to apply an update; they alomst always fix security vulnerabilities
while "bugs" seem to be overlooked, forever.

On Friday, 23 December 2022 at 21:13:32 UTC+1, Don Y wrote:
> On 12/23/2022 7:54 AM, bitrex wrote:
> > <https://www.reddit.com/r/Windows10/comments/zl2mcr/cumulative_updates_december_13th_2022/>
> >
> > <https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22H2#2986msgdesc>
> >
> > Seems to really hate some Sandy Bridge/Ivy Bridge machines, I use a Fujitsu
> > Lifebook which has some nice features like a VGA output (for connecting to
> > older projectors) and easily-replaceable battery and the update took it down
> > real good
> My strategy with MS is to image the machine (the OS drive) before
> every update. Then, I can get back to the prior state without
> relying on MS knowing how to undo it's f*ckups.
>
> But, I manually apply updates so I know when the risky exists.
>
> Also, most machines are airgapped so there's very little reason for me
> to apply an update; they alomst always fix security vulnerabilities
> while "bugs" seem to be overlooked, forever.
never update Windows on old machine

Always buy n ew Windows with new machine every 3 years or when update released

bitrex <user@example.net> wrote in
news:ZijpL.91678$9sn9.46419@fx17.iad:

> <https://www.reddit.com/r/Windows10/comments/zl2mcr/cumulative_upda
> tes_december_13th_2022/>
>
> <https://learn.microsoft.com/en-us/windows/release-health/status-wi
> ndows-10-22H2#2986msgdesc>
>
> Seems to really hate some Sandy Bridge/Ivy Bridge machines, I use
> a Fujitsu Lifebook which has some nice features like a VGA output
> (for connecting to older projectors) and easily-replaceable
> battery and the update took it down real good
>

That is possibly the difference. I keep mine continually updated, so
"cummulative updates" are not as large for my machine. I also DL and
install large updates to the OS.

Mine is: Windows 10 Pro for Workstations Version 22H2
OS Build: 19045.2364

Under a: Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz

Which they (MicroSoft) fucked me on a Windows 11 upgrade.

Of all the CPUs being supported, one would think that workstation
Xeons would be included.

It is like Windows NT was... pure customer abandonment.