Path: ...!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Frank Slootweg Newsgroups: alt.comp.os.windows-11,comp.os.linux.advocacy Subject: Re: This Is Why They Say Windows Is A Great OS -- If Your Time Is Worth Nothing Date: 3 Jan 2025 10:18:16 GMT Organization: NOYB Lines: 29 Message-ID: References: <8bk8njhp31eu4pri07cppsk95sfkcrtr2h@4ax.com> X-Trace: individual.net zsNXKWnASAyWpdK2pqzW6AmXmB+cyaHVJ0Aml6l3QWesKg8ran X-Orig-Path: not-for-mail Cancel-Lock: sha1:iV1vInbemftTOOd4Ypx0KRaTWD0= sha256:Og2atr6Mgr6ERjXEjCGELqpfTma0CJp3LkF9R8btb24= User-Agent: tin/1.6.2-20030910 ("Pabbay") (UNIX) (CYGWIN_NT-10.0-WOW/2.8.0(0.309/5/3) (i686)) Hamster/2.0.2.2 Bytes: 2337 Lawrence D'Oliveiro wrote: > On 2 Jan 2025 18:21:11 GMT, Frank Slootweg wrote: > > > Lawrence D'Oliveiro wrote: > >> > >> On Wed, 1 Jan 2025 23:59:53 -0500, Paul wrote: > >> > >> > People here have also achieved that (no updates) by breaking stuff > >> > :-) > >> > >> Microsoft itself has now come up with an update that does this, > >> too--kills the ability to receive further updates. As I mentioned in > >> the posting that started this thread. > > > > Sigh! It's *not* "an update [which] kills the ability to receive > > further updates". It's a corner case ... > > Which only started happening after a particular update. Duh! But - as I *wrote*, but you ignored and snipped - the risk of getting the problem existed only for a very short time and only in very uncommon scenarios. But don't let facts get in the way of your unsubstantiated contentless Microsoft/Windows bashing. If this is all the ammunition you have, you don't have much. And FYI, no-one in this Windows group has reported that they have actually experienced this 'problem'. I wonder why *that* is!?