Replies

[Geoff King]

It was quick ( less than 5 minutes on both machines ) , but that’s because it’s basically 1903, with the KB4517245 being an *enabler* of the 1909 features.

So, more a cumulative update than a feature update, as has been mentioned before.

New features pretty ho hum, as far as I’m concerned.

• This reply was modified 5 years, 5 months ago by Geoff King.

Susan, we mere users have to accept the fact that Microsoft listens to no-one.

If not for you, Woody and the other MVPs, we would be in a constant state of bewilderment at Microsoft’s pathetic treatment of its users.

Thanks to you guys, I’m managing to avoid most of the disasters that MS regularly imposes on us.  :-/

10 users thanked author for this post.

LH, HiFlyer, Norio, GoneToPlaid, GreatAndPowerfulTech, WildBill, ve2mrx, Pepsiboy, Pierre77, Fred

I use Paragon Backup and Recovery 17 Free version. Works well for all my needs.

2 users thanked author for this post.

rc primak, jburk07

[Geoff King]

On one machine, .Net Framework failed to install with the comment Retry.

Wonder if that’s a sneaky way for Microsoft to make you a ” Seeker ” !

• This reply was modified 5 years, 10 months ago by Geoff King.

I haven’t been a seeker for a long while, now.

I don’t have the time or the inclination, to faff around trying to fix what MS screws up.

I have Win Update Stop set to Disabled, and it will say that way until Woody gives 1903 the thumbs up ! Eventually, I hope ! 

Others can be the guinea pigs.

Forced on both my machines.

I did not seek them, but they arrived anyway.

MS up to their tricks again, it seems………….

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.

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…….. 

Never used Cortana, or Siri. Have no interest in using Alexa, ever.

Probably why my Win 10 1809 set up works so well, because I have 98% of Micofails’ options disabled !

We can discuss this issue until we’re blue in the face, but the situation for home users can be summed up in three words.

Microsoft doesn’t care, and therein lies the problem.  :-/

2 users thanked author for this post.

lurks about, WildBill

Given the typical chaotic situation with Win 10 updates, I’m gonna leave things as they are.

IOW, leave it to come down the tube whenever the Microfail gods decree it’s time.

I tried to manually invoke KB4458469 on both my machines yesterday AND today, and no dice, so am not intending to pull them down from the Update Catalog until we get some clarity on what’s going on in the MS madhouse !

b wrote:

woody wrote:

KB 4458469 takes Win10 version 1803 to build 17134.319

Installed on two laptops without any apparent issues.

Not seeing KB 4458469 on either of my otherwise up to date machines.

Possible phased roll out ?

 

I think Microsoft extends the life cycle on September Updates because they like to give their users an early Christmas present. Such a caring company………………

Entirely predictable response from Microsoft.

Pathetically handled response to Susan’s letter, and proof beyond doubt that Microfail just does not care about consumer concerns.

You just get fed what MS deems is appropriate, and if you don’t like it, well you know what you can do.

I will definitely be keeping Linux and other alternatives in mind for my next OS.

 

2 users thanked author for this post.

TXWizard_2018, johnf

Microfail wants me to pay them a monthly fee to *Manage* my systems ?

How do I do this ? Do I have to set up a monthly debit arrangement, or can I just post them a check every month ?

Yeah, as if ! Linux, here I come !

2 users thanked author for this post.

Cybertooth, johnf