From: nospam@needed.invalid   
      
   On Sat, 2/14/2026 10:45 AM, knuttle wrote:   
   > Why does Microsoft feel that it is necessary to nag the user the minute the   
   Update is available? If you don't update when MS thinks you should, it nags by   
   randomly making simple things respond differently or not respond at all. The   
   events will occur    
   every few seconds until the update is installed.  Through the years I have   
   observed the same thing on several different computers using different mice.   
   >   
   > These events occur randomly, maybe one time the program does not open, and a   
   few minutes later it opens normally.  Maybe when you click on a function it   
   works normally, the next time it may not respond or act differently.  There   
   is not one thing    
   specifically, but many tiny random events to cause significant frustration.   
   >   
   > The minute the update is made, all these random events disappear, and   
   everything returns to normal   
   >   
      
   This is caused by services stopping and starting.   
      
   To update a file on a service "hot", one way to do it is   
   stop the service, insert the new files, then start the service again.   
      
   But this can have side effects on applications that might be   
   using the service! Even the StartExperience could be perturbed,   
   and there have been some "famously bad" incidents, such as the   
   "dancing icons" thing I experienced here once. This is why we   
   own powerful video cards, so the icons can dance faster.   
      
   A lot of the installation process can be done while the OS is   
   running. At shutdown/restart, the PendMoves can be completed, for   
   any materials that must wait for a quiet moment to be inserted.   
      
   None of it absolutely has to be done this way, but that is the   
   evolution story. They could maintain a constant service landscape,   
   by not working on services "in your face" so to speak. They   
   could easily shut down, and do any amount of installation   
   without you being able to use the screen. For example, the SearchIndexer   
   could be shut off, Sysmain could be shut off, Windows Defender could be   
   shut off, the installer could just concentrate on getting the job done.   
   Wouldn't that be neat ? Maybe I should get a job there, delivering   
   the mail.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)