Lynn McGuire wrote:
On 6/11/2019 12:46 AM, T. Ment wrote:
On Mon, 10 Jun 2019 22:56:19 -0500, Char Jackson wrote:

Windows 7 x64 Pro is the best ever.

IDK about that, but in 6 more months, time expires. Then you're out of
luck.

Not true.

Is true.


Nothing expires

When Windows 7 reaches its End of Life phase on January 14, 2020,
Microsoft will stop releasing updates and patches for the operating
system
...

Yup, just like Microsoft stopped releasing patches for Windows XP.
https://www.wired.com/story/microsof...very-bad-sign/

Lynn

You're not reading the tea-leaves properly.

Finding that patch is difficult.

It's not really integrated into Windows Update properly.

It should not be in WSUSSCN2.cab if you were to download
that file this very day. Opening WinXP Windows Update
and "Checking For Updates", won't show it. They're not
messing up WSUSSCN2.cab structure, just for this patch.

I had to check borncity, for a list of KBs, to find the
KB needed for WinXP. With KB in hand, you use
catalog.update.microsoft.com to get it.

So the message is:

"we care dearly about you, dear dear customers.

but for reasons just beyond our mental capacities,
many of the patches will not appear like magic for you,
requiring you to bob for apples to find them"

The Windows 7 patch is "conveniently" buried in a 100MB+
cumulative "Security Only" patch file, when, if they
really wanted high uptake of the package, they could
have just done it out-of-band and issued a 544KB patch
like the WinXP version happens to be.

As far as I know, it's likely that only one file needs
a new version. That's why the WinXP one is so small.
In the 544KB, most of that is installer code, and not
much of it is "payload" as such.

If Microsoft was "really really" worried, they would
have done more or done it a better way, if they were
actually concerned. Yes, it's great they patched WinXP,
but the "fit and finish" sends the wrong message as
far as I'm concerned. Just like the last time they
delivered "goods" this way. If you're not wide awake,
you could very easily lose the breadcrumbs needed to
find sufficient "goods" to "patch up to date".

It would not take much to "do a better job".

Simply take the defunct MBSA 2.3 package and
place all the out-of-band materials in their
own section so that customers will be aware
of their existence. Thus putting everything
needed in one place (as nearly as the customers
can determine). If they need to craft a file
in parallel with WSUSSCN2.cab, then they don't
need to damage the cab, and the parallel file
would only be there to update the MBSA 2.3 displayed
"you need these patches" list.

Even the G.D. CVE doesn't make you aware of the
WinXP patch!!! Such "really really cares" incompetence.
But as long as Borncity or similar happen to post a copy of
the necessary KBs, there's at least some third
party ways to find the info.

Like, as a test case, now go and find me the
KB for the WinXP SMBv1 patch. I think that one is
out-of-band, and Windows Update should not show it.
But, it's been a while, so I forget. Will there
still be breadcrumbs ? Will the blogs be erased ?

Paul