Barb Bowman reports preview NET kicks reboot

Topic

New Reply

https://twitter.com/barbbowman/status/1356973915734761478 Barb Bowman reports that on her 20H2 that she received the preview .NET update KB4598299 and
[See the full post at: Barb Bowman reports preview NET kicks reboot]

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Replies

I had this happen to me last night.  I’m running Win10 Home 2004.  My  updates were un-paused as of a few days ago for the Jan updates, and I was planning on re pausing this weekend.  Last night I got a notification that my computer required a restart.  the Feb .NET preview decided to auto-update as I did not click on check for updates

Reply | Quote

Sames messages being seen on workstations here as well. Why a preview shows up in regular updates instead of optional updates mystifies me.

Reply | Quote

optional updates section is only for regular Cumulative Update Preview and Feature Update
recently they added drivers too

.NET updates are processed by the legacy WUA like flash updates, whether they named Preview or not

Reply | Quote

abbodi86 wrote:

recently they added drivers too

what kind of drivers — Microsoft drivers? Intel drivers pushed by Microsoft? The same kind of drivers that GP “Do not include drivers with Windows Updates” affects?

Are these drivers marked OptionalInstall?

Are all updates marked OptionalInstall delegated to the lower section of WU where there is a “download and install” link?

So, does the rule in #2309326 that says “FU Deferral + TargetReleaseVersion = you don’t get FU or CU Preview” become “= you don’t get FU or CU Previews or Drivers”?

In other words, I’d like to mesh this new info about drivers with what’s already been said here about OptionalInstall and the Optional Updates section on the WU screen.

Reply | Quote

Any drivers deployed via WU

some are regular (forced), some are optional

in v2004 ad later, it’s now “view optional updates” link, which enter the above “Optional updates” page

i didn’t test deferrals or TargetReleaseVersion to see if they affect optional drivers

Reply | Quote

abbodi86 wrote:

Any drivers deployed via WU

Is ExcludeWUDriversInQualityUpdate still one of your configured policies?
See #2308869 and #2309148.

Reply | Quote

abbodi86 wrote:

in v2004 ad later, it’s now “view optional updates” link, which enter the above “Optional updates” page

In 2004 and regarding the appearance of the “download and install” link, does the WU screen you get depend on whether you have GP=2 (notify download/install)?

See No GP=2

and GP=2

Reply | Quote

Yes, ExcludeWUDriversInQualityUpdate was set when i got the drivers

yes, i always set GP=2 (notify download/install), but that’s affect the regular top part
optional updates are optional regardless

Reply | Quote

abbodi86 wrote:

optional updates are optional regardless

Yes, I understand that. But, how the “Download and install” link appears on the WU screen seems to be different, depending on GP configurations or not.

In the GP not=2 screen, the “Download and install” link is side by side with the “View optional updates” link, but on the GP=2 screen, you can’t see the “Download and install” link until you click on “View optional updates” link.

Reply | Quote

Are you sure about GP effect?

the link changed to “View optional updates” since announced with OS Build 19041,450

Reply | Quote

abbodi86 wrote:

Are you sure about GP effect?

Actually, I was asking you if GP settings make a difference in the WU display.

19041.450 is dated Aug 11, 2020. The screenshots above for GP=2 (from Bradley) and GP not=2 (from you) in #2342893 are dated Nov 1, 2020.

Reply | Quote

Well, not seeing any ‘Previews’ on 20H2 Pro, probably due to the GP ‘Preview prevention’ settings within WU for Business settings Thanks to Woody, abbodi86 and PKCano from a good while back.

Windows - commercial by definition and now function...

Reply | Quote

Microfix wrote:

Well, not seeing any ‘Previews’ on 20H2 Pro,

Not seeing any .NET previews in 1909 either, for the same GP Preview Prevention reason.

Reply | Quote

1909 didn’t have a .net preview which is why you aren’t seeing it.

The WUfor business “don’t show me previews” only refers to Insider editions, not these .net preview patches.  I honestly have no idea why some are and some aren’t seeing this.  In my opinion this is a detection problem.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Alex5723

Reply | Quote

v1909 did get .NET PreviewKB4598301

Reply | Quote

@microfix – could you please post a link to the instructions for Preview Prevention in GP.

Thanks

Mike

Reply | Quote

Make your settings exactly as described here in #2339762.
That should produce those effects.

1 user thanked author for this post.

Microfix

Reply | Quote

Thanks, I’ll give it a go

Reply | Quote

[WSmichael_b]

Weren’t there several patches last year where patches were released as “preview” in the C and D weeks and then not renamed for normal B week release?

Anyway, I am on 20H2 Enterprise edition, but I didn’t see this (but I have “pause updates for 7 days” set).

• This reply was modified 4 years, 2 months ago by WSmichael_b.

Reply | Quote

After clicking on “check for updates” Windows applies the referenced update (which does want a reboot), and then notes that another patch is available, as shown in the image.

Reply | Quote

i am also seeing this on my Windows 10 Pro 20H2 Toshiba Satellite computer. I have not asked it to download and install.

Reply | Quote

Win10 pro – 2004 and haven’t seen this preview.  As a matter of fact I haven’t seen any .NET updates since the last security one in the fall – I’m not sure why.

Reply | Quote

Because there has been no new security bits – only non security.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I seem to remember I would be presented both non-security and security .NET patches.  Now I only seem to see the security ones.  Any idea why?

 

Reply | Quote

I have an Intel NUC 8i3 running pro 20H2 that I use to “experiment” on. I’m in Berlin, and my Win 10 version is originally German, but it’s set to English.

I check for updates every few days, and I got the .NET preview yesterday (03 Feb).

It installed fine, and no reboot was required. Windows says I can uninstall it if I want, but I’m going to leave it to see what happens. I haven’t had any problems with it so far.

Reply | Quote

I didn’t get it on this two-month-old install Win10 Pro 20H2, currently updated to 19042.746.

After updating two days ago to .746 with KB4598242 CU, i re-blocked updates with WinUpdate Blocker. Previews and drivers are blocked in GP.

Asus Z370 (Intel) mobo and an old MSI laptop using Intel HM170 mobo…

Win10 Pro 20H2,backups with Macrium Reflect home edition

Reply | Quote

Win 10 Pro 20H2 with GP settings of download only and quality update deferrals set to 15 days. I’m not seeing this update. I do not use the Pause/Resume feature.

Reply | Quote

On Windows 10 Home 20H2 last Tuesday evening, after booting up, the main Windows update page showed the cumulative update preview available, with no other updates (aside from virus definitions) available on either the main update page or the optional update page (other than drivers). So I downloaded and installed the cumulative update preview and rebooted as instructed.  Then I went back to the main Windows update page and saw that the .Net framework update preview was already downloading and installing without me choosing it, selecting it, or searching for updates. It just started on its own right after the reboot. And it was not even shown as available or even optional before the reboot. Apparently Microsoft is requiring it to be installed whether you want it or not. Big Brother Microsoft does whatever it chooses with your equipment, because choosing their operating system means you give up partial ownership of your machine, I guess.

 

Reply | Quote

This also happened to my Windows 10 Pro version 2004. Downloaded Cu Update and later discovered the infernal Net Preview had also been downloaded and installed without notification or my knowledge.  This occured in January updates.

Reply | Quote

See the question here and answer below.

1 user thanked author for this post.

Cee Arr

Reply | Quote

[Alex5723]

anonymous wrote:

because choosing their operating system means you give up partial ownership of your machine

Choosing Windows OS mean that you give Microsoft free hand in managing the OS. Read the EULA.
Remembers, Windows OS is not your it is just licensed to use..

• This reply was modified 4 years, 2 months ago by Alex5723.

Reply | Quote

[GoneToPlaid]

Barb Bowman asked why .NET updates might require a reboot.

Some installed AV programs may use .NET. I can think of at least a few AV programs which use .NET. Other installed software may also use .NET. Your Windows computer’s Prefetch and SuperFetch settings can cause programs to silently load, unbeknownst to you, in your computer’s memory. These silently loaded programs might also rely on .NET in order to load and run.

Windows Prefetch and SuperFetch settings are a separate discussion since I never allow Windows to silently load programs, based on when Windows anticipates when that I would want to load and launch such programs, unless I instead and deliberately choose to load and run said programs.

So there you have it. There are a variety of reasons why installing .NET updates may require a reboot. I use Panda Dome antivirus. Panda Dome does use .NET for its VPN functionality. Thus and every time that I install any .NET update, Windows tells me that I have to reboot my computer.

• This reply was modified 4 years, 2 months ago by GoneToPlaid.

3 users thanked author for this post.

abbodi86, doriel, Alex5723

Reply | Quote

Had this as well on 20H2 Home. Windows Update had been unpaused for Jan, I’d only looked with a view to pausing again and saw the preview download itself , install and ask for a restart. Seems fine but I’ll try to remember to pause sooner after updating in future.

Reply | Quote

Set the network connection to “metered” and it won’t auto-install anything. Don’t need to use pause then.

cheers, Paul

1 user thanked author for this post.

Wibbly

Reply | Quote

On the other hand, February’s .Net preview update gets rid of the ESENT warnings in the event viewer that appear with every boot or reboot, or perhaps the cumulative update preview does it — one or the other.

 

Reply | Quote

I’m on Win 10 Pro 2004, Configure Automatic Updates=2, TargetReleaseVersion=2004 via group policies. No install or reboot, just the following listed in Windows Update:

 

Reply | Quote