Is yesterday’s .NET Preview, KB 4481031, being pushed onto 1809 machines?

Topic

New Reply

Microsoft’s documentation says that yesterday’s “January 22, 2019 — KB4481031 Preview of Cumulative Update for .NET Framework 3.5 and 4.7.2 for Window
[See the full post at: Is yesterday’s .NET Preview, KB 4481031, being pushed onto 1809 machines?]

3 users thanked author for this post.

PhotM, Elly, geekdom

Reply | Quote

Replies

If you can’t trust your documentation, what can you trust?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

It sure did get installed on all my machines.

Microsoft – one step forward, two steps backward, again.

Reply | Quote

pushed to my 3 pcs in BC, Canada

Reply | Quote

Yes, kb4481031 was pushed out to one of my 1809 machines this morning and identified as being a preview in the update history list.  After uninstalling it and rebooting, it is showing up in the wushowhide.diagcab list, but not identified as a preview.   Odd.

OTOH, kb4476976 is MIA here so far, no matter which update channel is chosen, even with 0 days selected for the quality update deferral.  Maybe they’re dribbling it out a little at a time, or maybe telemetry is blocking it here, who knows.

Reply | Quote

If this update is a forced install, how do you block it?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

You can run wushowhide.diagcab and hide it.  Easier still,  don’t click “Check for Updates.”

The behavior of the Check for Updates button is every bit as unethical as “The big red X means, yeah, sure, replace my Windows 7 with Windows 10” from the GWX days, especially now that they’re throwing in previews.

 

 

 

7 users thanked author for this post.

David F, Karlston, dlsdjh, BobbyB, woody, Elly, Microfix

Reply | Quote

Good point… but it seems like people are saying that the Preview patch was pushed onto their machines, without clicking Check for Updates.

Reply | Quote

No, Woody..

You recommended “checking for updates” to get the new CU for 1809, in your previous article.

When I did that, I got the .NET preview, but NOT the new CU…

Reply | Quote

Oops,  I said “pushed” in message 315651 but I clicked Check for Updates (expecting to see kb4476976), sorry.  I certainly wasn’t expecting the preview.  This was in a VM, so no worries.  It’s probably a good practice to always run wushowhide (or equivalent) before checking for updates, for those of us who just can’t help ourselves

 

1 user thanked author for this post.

woody

Reply | Quote

I think you’ll also find that I didn’t recommend clicking Check for Updates. I said that you could get it if you wanted it by becoming a Seeker. In general, click Check for Updates is very much the last resort. Almost never necessary.

Reply | Quote

Yep showed up here yesterday unannounced and was promptly hidden, what you cant see from the “Pic” is its marked LTSB.


@geekdom you can find details here: https://www.askwoody.com/forums/topic/windows-update-manager-wumgr/

3 users thanked author for this post.

geekdom, Karlston, Microfix

Reply | Quote

BobbyB wrote:

@geekdom you can find details here: https://www.askwoody.com/forums/topic/windows-update-manager-wumgr/

WUMGR and WUMT appear to be the only choices for blocking Windows 10 updates… and are third-party software.

Windows Update MiniTool
https://www.askwoody.com/forums/topic/how-to-absolutely-positively-block-the-forced-upgrade-to-win10-1809/#post-313005

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

WSUS shows as a standard update and not a preview.

Red Ruffnsore

1 user thanked author for this post.

Microfix

Reply | Quote

Yes, the .NET “preview” was pushed to an unguarded 1809 Home machine without any button clicking. The cumulative update was not.

Not a preview?

Reply | Quote

It was forced to my win10 home machine.

 

Reply | Quote

The word “Preview” seems to have disappeared from the title of the KB article:

https://support.microsoft.com/en-us/help/4481031/january-22-2019-kb4481031

It was there yesterday because I copied and pasted it.

2 users thanked author for this post.

geekdom, woody

Reply | Quote

That’s precisely what happened.

The original title was “January 22, 2019 — KB4481031 Preview of Cumulative Update for .NET Framework 3.5 and 4.7.2 for Windows 10, version 1809 and Windows Server 2019”

I, too, copied and pasted it. 

1 user thanked author for this post.

geekdom

Reply | Quote

It appears documentation is not to be trusted as it is modified without notice. How do Microsoft customers protect themselves? What is the next step?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

No automatic update here. Maybe because I have set my Ethernet as metered.

I miss Windows XP...

2 users thanked author for this post.

Karlston, BobbyB

Reply | Quote

The newest file update times in the update are December 19, 2018.

If I had to guess, I’d say that they decided to not have the usual public preview period for these updates because of the holiday season…. and, they had a full month to test them internally on production systems.

 

Reply | Quote

Pushed onto my two systems at home.  Was somewhat surprised…

J

Reply | Quote

It was not forced but it did show up when I checked for updates yesterday.

Nowhere that I can see dose it say preview.

Barry

 

Barry
Windows 11 v23H2

Reply | Quote

I got it today at 4:13, did a reboot to get it installed.  Nothing broke.  The only thing I have buttoned down in Windows 10 1809 is telemetry and updates from other PC’s.  I always have a drive image that’s less than a week old, so I’m not particularly concerned.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

1 user thanked author for this post.

woody

Reply | Quote

I have 5 Windows 10 1809 installations on 3 machines; my desktop which I dual boot, my laptop which I dual boot, and my NAS.  Only three are active at any one time, and only my desktop default OS received the update.  I didn’t “Check for updates”, it was pushed.

My laptop is docked but signed out, my NAS is signed out.  Only the desktop stays signed in most of the time.  I never turn any of them off, because I have multiple maintenance tasks run by Task Scheduler in the wee hours.

The old rule of thumb (that I still use) is to have the original and two copies of every piece of data that is precious to you.  My data is spread over three HDD’s on two machines plus OneDrive.  Periodically I also store an image on a backup HDD that I plug into the drive bay on top of my NAS.

I piddle in the OS a bunch, and I pooch it often, so I keep drive images on automatic, the oldest never older than a week.  If I plan on diving into the registry or something equally foolish, I’ll make a fresh drive image before I begin, so that I can get right back to where I started when I gum up the works.

I let updates/upgrades run freely (and sometimes use the MCT to get in early) because I have an easy out if things go south.  The original 1809 didn’t lose any of my data, but I discovered the first day that a test file got stored somewhere that I couldn’t find.  I restored an image and waited for Microsoft to get it sorted out, and when they did, I upgraded again.

I have had no problems with 1809 on any of my installations.  YMMV

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Got it on 3 of 6 test machines after clicking check for updates. All machines set up pretty much the same. All checked within about a 2 hour time frame this evening.

Windows updating has really gone off the rails stupid.

Reply | Quote

Popped up on both my 1809 machines, unbidden.

Installed quickly, and no issues.

Having said that, I no longer *seek* and just wait for updates to roll down the chute !

KB4476976 aka 1809 v 17763.292, has NOT yet shown its face. I can wait…….. 

Reply | Quote

Neither KB was pushed  to my laptop. Running Win 10 1809. Did NOT click  check for updates.  I let them roll out to me when released for automatic update.  Seems like advice here is not to click on check for updates to avoid getting preview releases.

Reply | Quote

home network cant see my windows 10 PC since the update

Reply | Quote

I’m on Win 10 for only a week now and perhaps have not configured the update system correctly (Everything is turned off as per the directions of a friend).  this update did install yesterday afternoon.  It does not appear that it has adversely impacted anything.

Reply | Quote

Microsoft admitted their mistake and added a Known Issues section for KB4481031:
https://support.microsoft.com/en-us/help/4481031/january-22-2019-kb4481031

They also added a note to their blog to explain why the term “preview” was removed:
https://blogs.msdn.microsoft.com/dotnet/2019/01/22/net-framework-january-22-2018-cumulative-update-for-windows-10-version-1809-and-windows-server-2019/

Francis

2 users thanked author for this post.

b, woody

Reply | Quote

Sunuvagun. They admitted that they used “Preview” incorrectly in the initial KB article, and they admitted that they pushed the NET update out the Automatic Update chute, before shutting it off.

At least they admitted it. Once upon a time, we only would’ve guessed….

2 users thanked author for this post.

abbodi86, Geoff King

Reply | Quote

Preview or not, .NET updates are generally safe
it does not worth all this hustle

P.S. i think the “Seeker” attribute only applies to general Cumulative and Feature Updates, not other updates like Adobe Flash and .NET cumulative

5 users thanked author for this post.

ch100, Geoff King, geekdom, b, woody

Reply | Quote

woody wrote:

Sunuvagun. They admitted that they used “Preview” incorrectly in the initial KB article, and they admitted that they pushed the NET update out the Automatic Update chute, before shutting it off. At least they admitted it. Once upon a time, we only would’ve guessed….

Genuine mistake, or deliberate mistake by MS ? We’ll never know.

Reply | Quote

I doubt that it was intentional. As @b noted, what would be the point of it?

Just another manifestation of the lack of care taken on the customer side of the fence.

Reply | Quote