From: nospam@needed.invalid   
      
   On Sat, 1/3/2026 7:06 AM, John K.Eason wrote:   
   > In article <10j96p9$ljj3$1@dont-email.me>, winstonmvp@gmail.com   
   (...w¡ñ§±¤ñ) wrote:   
   >   
   >>   
   >>   Fyi....KB5068164 is a Windows Recovery(WinRE file) update.   
   >>   You'll have to use Powershell or Command.com to determine the   
   >> status and version/build.   
   >>    - Win10 ESU, afiak, will continue to include WinRE updates   
   >> packaged with the security update.   
   >   
   > Ah ok. I've never had occasion to need to recover Windows in the 8 years or   
   so   
   > that it's been on this PC so I assumed it was a 'normal' update.   
   >   
      
   Just for the record, we don't care whether WinRE is up to date or   
   not. What we do care about, is when one of those updates   
   jams up Windows Update and prevents other, more important,   
   updates from getting into the machine.   
      
   I don't think I've ever seen any WinRE activity attempting   
   any sort of "recovery", actually work. It would be interesting   
   if someone had a success-case when that happens, and the   
   spinning balls are pretending to be doing something when   
   the OS tips over. It would be so so much better, if the   
   spinning balls thing just printed some text representing   
   the current activity (like scanning something or tasting   
   all the files, or so on, maybe a 3 second or 3 hour time estimate   
   as to how much scanning was left to do). At least that would prove it   
   wasn't just stuck, doing nothing nothing nothing at all.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)