Replies

Good question, thanks! I’ll keep an open mind. Meanwhile, AskWoody’s right: avoid Win11 if you can. I hadn’t any other option, I’m afraid.

Many thanks! Actually, it was my mistake: I took the advice on an AskWoody e-letter a few months ago to install Opatch. Looks like it was a waste of time. In any case, by sheer chance following this latest crash, I think I’ve found the problem. It was probably an update malfunction on the pre-installed Office suite on my new(ish) laptop. dealt with.

Well, I uninstalled Opatch, but the mystery crashes are still happening, periodically. I’m stuck with Win11 on my new laptop, so has anyone any more suggestions? Thanks!

Thanks! Much appreciated. I’ll uninstall it immediately.

Thanks to all for the replies. Since, mysteriously, the laptop will boot OK when on battery but unplugged from the mains, I’m working on a supposition along ‘Microfix’s’ lines. Possibly  Intel chip and Power Controller need updating.

I’ve just discovered two different versions of the patches update 8/10/2021 — strangely the pdf is dated  2021-7-31 (see attachment) but the sheet’s actually headed 8/10/2021 — the earliest, ref. 20H2, says ‘install’ for 5004237, the new (current) one doesn’t list 5004237 and defers both listed patches. Luckily, I avoided 5004237, though my wife found herself forced to install it on her laptop.

I’m completely flummoxed. What’s up?

Many thanks, but no W10 patches are listed as anything other than ‘Defer’ on 13 July sheet.

1 user thanked author for this post.

clivew

Hmmmmm… So my modest posting is classified as a ‘rant’? Could I have a rant about that………….? What would that be? A meta-rant? A mega-rant? A super-rant……………………?

All the same, I’m impressed by the standard of all the responses. Fascinating and very stimulating.

1 user thanked author for this post.

OscarCP

Yup, sure! All the postings about licences and upgrades/updates are very true, but frankly missing the point. The real issue is the misuse of those licences and implied permissions by Microsoft. No, actually, it’s the abuse of those licences and permissions, showing utter indifference to the interests of their customers, who often have no other choice but to use Windows OS.

Sorry! I don’t understand. Just checked, on the pdf for 14 July you still list all July patches for v.1903 as ‘defer’.

For what it’s worth, I’ve just noticed that WU on my W10 Home laptop — which worrying lost the ability to delay updates by more than a day or two last month but has now reverted to a ‘normal ‘ delay facility — no longer sports any warning/forecast on the upcoming W2004 whatsoever. It was there last time I checked, now it’s gone completely.

Clarification is very welcome. But I’d also welcome clear, detailed info about the workarounds, particularly for Home users. Thanks!

1 user thanked author for this post.

LHiggins

Thanks! That’s the point: I don’t as yet have any first-hand reports since, in applying the precautionary principle, I have to take account of other people’s critical reports including, as it happens, Woody’s own reports of bugs in current patches. Taking those on board, I’d be very foolish to apply the patches — not least because my first experience of all this entailed a total of five whole days spent negotiating with MS techs and putting right disastrous crashes. And, by the way, dealing with a senior MS tech who opined (in complete contradiction of MS’s own classic marketing) that the faults lay in out-of-date hardware, subsequently proved to be a tendentious falsehood. My last update/patching? 8 May 2020.

1 user thanked author for this post.

rontpxz81

The latest alert –‘ An unusually good month for installing updates’.

I’m sorry guys, but even a cursory search shows recent serious warnings about the dangers of KB4556799. Gordon Kelly says, ‘..steer well clear…’. Robert Zak: ‘…this update is one of the worst Windows 10 updates to date’. I apply the precautionary principle, not least because my own experience of this Windows 10 blight when it all kicked off was beyond appalling.

Sorry! It’s just not on!

1 user thanked author for this post.

JD

Very interesting! I too have been deferring updates (on v. 1903), but I’ve just noticed the system now won’t allow me to defer beyond 13 June. Any explanations/ suggestions? Or is this a side effect of the new warning about Win 2004 (why is MS regressing 16 years?) ?