XPost: comp.os.linux.advocacy   
   From: candycanearter07@candycanearter07.nomail.afraid   
      
   CrudeSausage  wrote at 20:30 this Friday (GMT):   
   > On 2026-01-02 15:13, rbowman wrote:   
   >> On Fri, 2 Jan 2026 07:56:49 -0500, CrudeSausage wrote:   
   >>   
   >>> On 2026-01-02 01:47, rbowman wrote:   
   >>>> On Thu, 1 Jan 2026 18:11:33 -0500, CrudeSausage wrote:   
   >>>>   
   >>>>> You're not wrong about machines no longer updating. Every honest   
   >>>>> person who's used Windows 10 or 11 for a long period of time will   
   >>>>> confirm that every so often, you'll come across updates that either   
   >>>>> failed or refused to install. From that point on, unless you know the   
   >>>>> cumbersome way to fix it, it will refuse to install any subsequent   
   >>>>> updates.   
   >>>>   
   >>>> When I had a machine on the Insiders program it got to that point. The   
   >>>> cumbersome way was a well trodden path for me but it didn't help.   
   >>>   
   >>> I always (eventually) managed to get it to work, but the way to fix it   
   >>> is definitely not intuitive. Even experienced, power users would find   
   >>> the instruction difficult to follow, so I can imagine what kind of a   
   >>> nightmare this would have become for casual users.   
   >>   
   >> You know you have a problem when you invoke the update troubleshooter and   
   >> it crashes.   
   >   
   > I liked learning that in Windows 11, if your system won't boot as a   
   > result of an update, the repair tools you're given don't function at all.   
      
      
   I wouldn't expect anything else.   
   --   
   user  is generated from /dev/urandom   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)