Microsoft explains the confusion over .NET 1809 update KB 4481031

Topic

New Reply

This is refreshing. Not the bugs, but the fact that we got a full explanation. (See Susan Bradley’s “Bring it on” post below.) You’ll recall my puzzle
[See the full post at: Microsoft explains the confusion over .NET 1809 update KB 4481031]

7 users thanked author for this post.

abbodi86, GreatAndPowerfulTech, Elly, columbia2011, b, PhotM, geekdom

Reply | Quote

Replies

woody wrote:

I take great umbrage at that “as is expected” stinger. I would guess that 99.99% of all the folks who click Check for updates don’t realize that they’re going to get all of the patches currently waiting in the queue – without a chance to review or accept them.

Has it ever been any different in the last four years?

Will you still express surprise in another four years?

You can rely on Automatic Update (turned on for all Technical Preview users) to eventually get the latest versions installed on your machine, but it wouldn’t hurt to prod manually as the bug you’re experiencing may already be solved. To run a manual update, click or tap Start –> PC Settings (on the left side of the Start Menu, remember?) –> Windows Update, then click or tap Check Now.
Windows 10 tip 2: Update

1 user thanked author for this post.

admin

Reply | Quote

Brilliant!

That was for the original Win10 Tech Preview – four and a half years go.

How times change!

(And I’m flattered that you remembered.)

1 user thanked author for this post.

GreatAndPowerfulTech

Reply | Quote

The problem is that users of previous Windows versions–XP, Vista, and Windows 7 and 8.x–were (reasonably) used to thinking that “check for updates” means exactly what it says: check for updates, period. Let’s see what’s available. Not “check for updates and then install them.” Now in Windows 10, they had no reason to expect the behavior to change when the phrasing didn’t.

When users move over to Windows 10, is there a clear, prominent, and persistent notification in the UI that Microsoft has reinterpreted the plain meaning of “check for updates” to “check for updates and install them”?

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

6 users thanked author for this post.

GreatAndPowerfulTech, Elly, Karlston, EstherD, Lars220, woody

Reply | Quote

Only if they read about it somewhere else…

3 users thanked author for this post.

Cybertooth, GreatAndPowerfulTech, Elly

Reply | Quote

This update got pushed to my work machine and killed my network connection. I uninstalled the update yesterday and after a few hours of trying, got my connection back. Last night it installs again, and now I’m back where I started. I’m no patch or network expert, and can’t find anyone else having this issue. Any chance you guys could help me sort it out? Apollo, I’m on mobile…

Reply | Quote

Can you please verify the KB number(s) of the update(s) that were installed on your computer in the last two days? There are two possibilities on v1809, a Cumulative Update for Windows KB4476976, and a .NET update KB4481031. It is important we know which one you are referring to.
Thanks.

1 user thanked author for this post.

admin

Reply | Quote

The bugs must be really buggy  this month Woody

as we’re still on MS – DEFCON – 2

Waiting for the all clear from you,won’t update otherwise.

Regards

Joulia

Windows 7,Home Premium 64 bit - Lenovo laptop
Group A - Intel (R)Core i7 Processors -

ASUS Chromebook C213 12.5 inch
64GB memory .

iphone 6,need to upgrade soon,bugger !

Reeder M7 Go 2019 Tablet !

Reply | Quote

Soo “Seeker” apply to all updates, not just LCU and Feature Update
that’s bad 🙂

Reply | Quote

I never realised that “seeker” was official MS terminology.

Reply | Quote