From: this@ddress.is.invalid   
      
   Brian Gregory  wrote:   
   > On 23/12/2025 20:20, Frank Slootweg wrote:   
   [...]   
   > >    Did I already mention that I was a professional troubleshooter for a   
   > > large part of my working life? :-) It was always A) and only B) as a   
   > > last resort stop gap until the actual cause was found by continuing A).   
   > > (See my earlier comment about Five Nines and only 5 *minutes* maximum   
   > > downtime per *year*.)   
   >   
   > On Windows?   
   > I guess Windows servers can manage that, what with being free of users   
   > like me starting and stopping random things at their whim.   
      
     No, not on Windows. Like I said, on real systems (Windows is just one   
   FSVO 'real' :-)). They were Unix/UNIX systems in clusters of at least   
   three systems with most if not all component duplicated, 'even' things   
   like network interfaces, power supplies and the power 'cords'. The 5   
   minutes maximum downtime was documented in a SLA (Service Level   
   Agreement) and if we did not manage that, there were rather hefty   
   (financial) penalties.   
      
   [...]   
      
   > >    But if you feel better by doing frequent restarts/reboots, then by all   
   > > means do so. Your system, your rules. But also, my system, my rules.   
   >   
   > A lot of my work-arounds for software misbehaving are of the form lets   
   > try changing it so that program A doesn't start immediately the system   
   > starts up, lets put a 30 second delay and see if that helps. Frequently   
   > things that didn't seem to work well together can be made to behave that   
   > way, but obviously I have to test it by rebooting, usually multiple   
   > times. Without rebooting the fix is as good as meaningless.   
      
     Understood.   
      
     I don't know if this was/is the same on Windows 10 (I'm now on Windows   
   11), but on my system I see that programs started from Start-up [1] are   
   started much later (some five minutes) than programs which 'start   
   themselves' (i.e. have some setting, which says start at login). As I   
   hardly ever restart :-), I have not investigated where this delay comes   
   from.   
      
   [1]   
   C:\Users\\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)