From: Paul    
   Subject: Re: when task manager is running in the system tray bug   
       
   John Doe wrote:   
   > John Doe  wrote:   
   >    
   >> Black Baptist  wrote:    
   >>   
   >>> If task manager is running in the system tray and I eject a   
   >>> thumb or partable drive windows won't release the drive.   
   >>> Windows 10 X64    
   >> I do not see the problem. What do you mean by "windows won't    
   >> release the drive"? And how is that a problem?   
   >    
   > And by the way... How can you eject a thumb drive? Does it shoot    
   > out of the USB port?   
       
   In the Notification area, is a "Safely Remove" icon for USB   
   flash sticks.   
       
   It can dismount all the partitions on a plugged-in device,   
   which causes the OS to do the equivalent of flush() and sync(),   
   so that no cache on the OS has any of your files. On some   
   Windows OSes, the Safely Remove operation causes the LED to   
   go out on the USB flash stick. Which is an indication there   
   is a state change. It is then safe to remove/unplug the stick.   
       
   If you look at the Safely Remove icon and its built-in menu,   
   even SATA drives, the drive containing C: will be listed.   
   This happens if the controller port is in AHCI mode,   
   and supports HotPlug. However, as soon as files like   
   "pagefile.sys" indicate they are busy, the attempt to   
   eject C: will fail. You cannot Safely Remove C: because   
   of the busy files on it.   
       
   As for why the Task Manager would actually have a handle   
   on a data disk, that's a mystery. There is a thing called   
   NTFS TXF (transaction oriented NTFS, which supports atomic   
   file operations), and it causes data disks to remain busy.   
   You might find a handle owned by "System, PID 4" for example,   
   and attempts to get a program name lead no-where. In such a   
   case, you cannot correlate what end-user software is   
   using TXF, and figure out why some media cannot be   
   unmounted.   
       
   The Sysinternals handle.exe program, can give details   
   on things with open handles. But in tough cases, only   
   using Disk Management and putting a disk in "Offline"   
   state, will cause it to be released. If it won't respond   
   to Offline either, then there might well be an identifiable   
   handle and source program doing it. Using handle.exe, or   
   using Process Explorer (sysinternals.com) and the   
   handle facility built into it, you can check whether   
   there is an easy answer or not.   
       
   Taskeng has no reason itself, to be examining any files.   
   There's no guarantee Handle.exe will be allowed to tell you   
   stuff about Taskeng. My lesson with TXF tells me that   
   certain "features" of the OS, cannot be debugged by mere   
   end-users.   
       
       Paul   
      
   --- ViaMAIL!/WC v2.00   
    * Origin: ViaMAIL! - Lightning Fast Mailer for Wildcat!  (1:261/20)