https://support.microsoft.com/en-us/topic/may-25-2021-kb5003254-cumulative-update-preview-for-net-framework-3-5-and-4-8-for-windows-10-version-2004-windows-server-version-2004-windows-10-version-20h2-windows-server-version-20h2-and-windows-10-version-21h1-69caa82d-225c-4833-b5ab-8b6c7cacd02d)
was the update it gave me. I don't want prereleases! :(

Thank you for reading and hopefully answering. :)
--
RIP 2 the dead American military personnels & my over decade old EVGA X58 SLI (132-BL-E758; BIOS date 5/11/2010; v6.00 PG; release number IX58SZ64) mobo that was just cleaned on 5/30/2021. :(
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:
> https://support.microsoft.com/en-us/topic/may-25-2021-kb5003254-cumulative-update-preview-for-net-framework-3-5-and-4-8-for-windows-10-version-2004-windows-server-version-2004-windows-10-version-20h2-windows-server-version-20h2-and-windows-10-version-21h1-69caa82d-225c-4833-b5ab-8b6c7cacd02d)
> was the update it gave me. I don't want prereleases! :(
>
> Thank you for reading and hopefully answering. :)
>
Did you open Windows Update and 'Check for Updates'
- if so, the Preview is downloaded and installed

See
<https://devblogs.microsoft.com/dotnet/net-framework-may-2021-cumulative-update-preview-for-windows-10-versions-2004-20h2-21h1/>
Specifically => "Customers that rely on Windows Update will automatically
receive the .NET Framework version-specific updates"

--
....w¡ñ§±¤ñ
msft mvp 2007-2020

....w¡ñ§±¤n wrote:
> Ant wrote:
>> https://support.microsoft.com/en-us/topic/may-25-2021-kb5003254-cumulative-update-preview-for-net-framework-3-5-and-4-8-for-windows-10-version-2004-windows-server-version-2004-windows-10-version-20h2-windows-server-version-20h2-and-windows-10-version-21h1-69caa82d-225c-4833-b5ab-8b6c7cacd02d)
>>
>> was the update it gave me. I don't want prereleases! :(
>>
>> Thank you for reading and hopefully answering. :)
>>
> Did you open Windows Update and 'Check for Updates'
> - if so, the Preview is downloaded and installed
>
> See
> <https://devblogs.microsoft.com/dotnet/net-framework-may-2021-cumulative-update-preview-for-windows-10-versions-2004-20h2-21h1/>
>
> Specifically => "Customers that rely on Windows Update will
> automatically receive the .NET Framework version-specific updates"

This may be a reference to the notion of

"a seeker"

A seeker is a person who opens Windows 10 Settings
and selects the Windows Update section, to understand
what is there. This, in Microsofts opinion, means
the user is "receptive to a cavalcade of updates".

Now, one might ask, how can a person check
the queue, without invoking anything ?

Good question.

Notice there are "update delay" buttons.

"Pause updates for 7 days
Visit Advanced Options to change the pause period"

AFAIK, you can still manually activate the Check for Updates
during the pause period, and pull in updates.

The maximum pause period is likely designed to coincide
with a "Patch Tuesday cycle". This would allow an office
worker, doing customer presentations, to avoid updates
in the middle of showing the customer a PowerPoint
slide set.

Paul

On Tue, 01 Jun 2021 01:11:31 -0400, Paul <nospam@needed.invalid> wrote:

>Notice there are "update delay" buttons.
>
> "Pause updates for 7 days
> Visit Advanced Options to change the pause period"
>
>AFAIK, you can still manually activate the Check for Updates
>during the pause period, and pull in updates.

I simply selected "Resume Updates" during the pause period, and I got the .NET
Framework preview as well, which I did not want. Guess I'll have to wait until
the pause period expires on its own next time.

JB

Paul wrote:
> ...w¡ñ§±¤n wrote:
>> Ant wrote:
>>> https://support.microsoft.com/en-us/topic/may-25-2021-kb5003254-cumulative-update-preview-for-net-framework-3-5-and-4-8-for-windows-10-version-2004-windows-server-version-2004-windows-10-version-20h2-windows-server-version-20h2-and-windows-10-version-21h1-69caa82d-225c-4833-b5ab-8b6c7cacd02d)
>>>
>>> was the update it gave me. I don't want prereleases! :(
>>>
>>> Thank you for reading and hopefully answering. :)
>>>
>> Did you open Windows Update and 'Check for Updates'
>>  - if so, the Preview is downloaded and installed
>>
>> See
>> <https://devblogs.microsoft.com/dotnet/net-framework-may-2021-cumulative-update-preview-for-windows-10-versions-2004-20h2-21h1/>
>>
>> Specifically => "Customers that rely on Windows Update will
>> automatically receive the .NET Framework version-specific updates"
>
> This may be a reference to the notion of
>
>    "a seeker"
>
> A seeker is a person who opens Windows 10 Settings
> and selects the Windows Update section, to understand
> what is there. This, in Microsofts opinion, means
> the user is "receptive to a cavalcade of updates".
>
> Now, one might ask, how can a person check
> the queue, without invoking anything ?
>
> Good question.
>
> Notice there are "update delay" buttons.
>
>    "Pause updates for 7 days
>     Visit Advanced Options to change the pause period"
>
> AFAIK, you can still manually activate the Check for Updates
> during the pause period, and pull in updates.
>
> The maximum pause period is likely designed to coincide
> with a "Patch Tuesday cycle". This would allow an office
> worker, doing customer presentations, to avoid updates
> in the middle of showing the customer a PowerPoint
> slide set.
>
>    Paul
>
>
> Some of that has been the Win7 and earlier mindset to periodically check
for updates since for years the 'Update Tuesday' wasn't necessarily
followed by MSFT with multiple out-of-band updates delivered on any given
day after that 'second Tuesday'.
- inevitable conditioning the entire non_WSUS user base to routinely
check multiple times.
That same 'patching' deployment broken model held true through Win 8.0 and
10(through July 2018) when efforts to standardize evolved(B week - 2nd
Tues; C and D week - 3rd and 4th week of month).

..NET Previews are almost always a C-D release with the latter the most
common though if major security(gaping big hole) related the preview may
appear towards the 'end of the 'B' week'.

What's the user(consumer) to do? For the most part, stop routinely
checking for updates, Windows already checks automatically every day.

Whenever feature updates are released(usually the week after B week), the
check for updates quagmire starts again due to the inherent 'keeping up
with the Jone's' - *got a have it if not already offered because so and so
got it*
i.e. you might not get the feature, but after 'B' Tuesday, if a .NET
Preview is available, it's downloaded and installed and will be until the
day before the next month 'B Tuesday'. That next month 'B Tuesday' will
include the .NET update.

PITA, yes. The norm - always.

....w¡ñ§±¤ñ

On 01/06/2021 18.38, ...w¡ñ§±¤n wrote:

....

> .NET Previews are almost always a C-D release with the latter the most
> common though if major security(gaping big hole) related the preview may
> appear towards the 'end of the 'B' week'.
>
> What's the user(consumer) to do? For the most part, stop routinely
> checking for updates, Windows already checks automatically every day.

Which is a pain for those users that don't have Windows continuously
running, but instead boot the machine and choose a time to do all the
updates fast and be done, then power off and take the machine somewhere
else - say somewhere with limited internet. Or those users that do the
maintenance for other people, and have to give back the machine ready
for use with nothing pending.

--
Cheers, Carlos.

....w¡ñ§±¤n wrote:

> Some of that has been the Win7 and earlier mindset to periodically check
> for updates since for years the 'Update Tuesday' wasn't necessarily
> followed by MSFT with multiple out-of-band updates delivered on any
> given day after that 'second Tuesday'.
> - inevitable conditioning the entire non_WSUS user base to routinely
> check multiple times.
> That same 'patching' deployment broken model held true through Win 8.0
> and 10(through July 2018) when efforts to standardize evolved(B week -
> 2nd Tues; C and D week - 3rd and 4th week of month).
>
> .NET Previews are almost always a C-D release with the latter the most
> common though if major security(gaping big hole) related the preview may
> appear towards the 'end of the 'B' week'.
>
> What's the user(consumer) to do? For the most part, stop routinely
> checking for updates, Windows already checks automatically every day.
>
> Whenever feature updates are released(usually the week after B week),
> the check for updates quagmire starts again due to the inherent 'keeping
> up with the Jone's' - *got a have it if not already offered because so
> and so got it*
> i.e. you might not get the feature, but after 'B' Tuesday, if a .NET
> Preview is available, it's downloaded and installed and will be until
> the day before the next month 'B Tuesday'. That next month 'B Tuesday'
> will include the .NET update.
>
> PITA, yes. The norm - always.
>
>
> ...w¡ñ§±¤ñ

IDK. Why have an interface ?

I think it would be possible to have an interface with:

Installed patch list with details on failures.
Incoming patches list, so user can gauge machine maintenance state.

And a button for this, and a button for that.
Maybe a button labeled "I'd be a seeker, if there was a button for it".
You know, so you could choose to be a Seeker.

I'm just imagining us now, sitting in a conference/meeting room,
discussing Captain Obvious. And whether Captain Obvious
should have superhero boots and superhero gloves and
maybe a thing to wear on his head.

The next thing you know, I'll stoop to redesigning some icons.
To start with, they should be blue in color, and easily confused.
Those are the requirements from the Requirements Spec.

Paul

Paul wrote:
> ...w¡ñ§±¤n wrote:
>
>> Some of that has been the Win7 and earlier mindset to periodically check
>> for updates since for years the 'Update Tuesday' wasn't necessarily
>> followed by MSFT with multiple out-of-band updates delivered on any
>> given day after that 'second Tuesday'.
>>  - inevitable conditioning the entire non_WSUS user base to routinely
>> check multiple times.
>> That same 'patching' deployment broken model held true through Win 8.0
>> and 10(through July 2018) when efforts to standardize evolved(B week -
>> 2nd Tues; C and D week - 3rd and 4th week of month).
>>
>> .NET Previews are almost always a C-D release with the latter the most
>> common though if major security(gaping big hole) related the preview may
>> appear towards the 'end of the 'B' week'.
>>
>> What's the user(consumer) to do? For the most part, stop routinely
>> checking for updates, Windows already checks automatically every day.
>>
>> Whenever feature updates are released(usually the week after B week),
>> the check for updates quagmire starts again due to the inherent 'keeping
>> up with the Jone's' - *got a have it if not already offered because so
>> and so got it*
>>  i.e. you might not get the feature, but after 'B' Tuesday, if a .NET
>> Preview is available, it's downloaded and installed and will be until
>> the day before the next month 'B Tuesday'. That next month 'B Tuesday'
>> will include the .NET update.
>>
>> PITA, yes. The norm - always.
>>
>>
>> ...w¡ñ§±¤ñ
>
> IDK. Why have an interface ?
>
> I think it would be possible to have an interface with:
>
>    Installed patch list with details on failures.
>    Incoming patches list, so user can gauge machine maintenance state.
>
>    And a button for this, and a button for that.
>    Maybe a button labeled "I'd be a seeker, if there was a button for it".
>    You know, so you could choose to be a Seeker.
>
> I'm just imagining us now, sitting in a conference/meeting room,
> discussing Captain Obvious. And whether Captain Obvious
> should have superhero boots and superhero gloves and
> maybe a thing to wear on his head.
>
> The next thing you know, I'll stoop to redesigning some icons.
> To start with, they should be blue in color, and easily confused.
> Those are the requirements from the Requirements Spec.
>
>    Paul
:)
Skip the conference room meeting. Save those boots and gloves for
something more important and(lol...realistic). Windows Update will be the
same for the foreseeable future.

....w¡ñ§±¤ñ

Carlos E.R. wrote:
> On 01/06/2021 18.38, ...w¡ñ§±¤n wrote:
>
> ...
>
>> .NET Previews are almost always a C-D release with the latter the most
>> common though if major security(gaping big hole) related the preview may
>> appear towards the 'end of the 'B' week'.
>>
>> What's the user(consumer) to do? For the most part, stop routinely
>> checking for updates, Windows already checks automatically every day.
>
> Which is a pain for those users that don't have Windows continuously
> running, but instead boot the machine and choose a time to do all the
> updates fast and be done, then power off and take the machine somewhere
> else - say somewhere with limited internet. Or those users that do the
> maintenance for other people, and have to give back the machine ready for
> use with nothing pending.
>

It can be a pita.
Yet, for those users you noted, that need and approach has been the same
for at least or over 3 years. Hoping for it to change for that subset of
users from just about any expected vantage point would appear to be as
close to a pipe-dream as possible. You're not alone though to continue to
hold that position - many System Builders, shops, and SMB's not running
Enterprise or Education SKU's(i.e. those using Home and Pro consumer
editions) have the same or similar POV.

Especially when .NET Preview will be included automatically in the next
Cumulative update, and rarely ever different as a Preview vs. Cumulative
deployment. The only real advantage of the .NET Preview is to allow
advance use and testing for Enterprise or Developers or IoT that run or
rely on .NET software and applications.
- it be nice if the Preview wasn't available, but then it wouldn't
necessarily alleviate the other side of the existing complaining
spectra('Why is .NET included in the Cumulative Update').

Wish it was better. :(

--
....w¡ñ§±¤n