Update: As reported it was search that was preventing ejecting in one instance. However, many processes will prevent ejecting for short periods of time and that was the case with Search.
Since removing the drive letter from search, the drive is easily ejected but only if it was not in the bay...
Thanks again @Fabler2. I removed the drive letter from Indexing, rebooted and the drive is ejectable now. I added the drive letter back to indexing and it is still ejectable, pointing to some glitch in Indexing. I'll hope it's not a glitch that repeats but if it does, I can live without Windows...
FWIW Removing drives hundreds or even thousands of times without ejecting them isn't proof you can't lose a write since I doubt you ever intentionally pulled a drive while you thought a write was actually in progress and may even have had cache disabled.
Anyway, @Fabler2 posted how to find the...
Awesome! Thanks. Just did this and see:
The application \Device\HarddiskVolume7\Windows\System32\SearchIndexer.exe with process id 5000 stopped the removal or ejection for the device SCSI\Disk&Ven_WDC&Prod_WD100EMAZ-00WJTA\4&fe99083&0&040000.
Process command line...
Thanks. This drive is not being accessed via USB. The IcyDoc has a MB SATA cable running to each of the 3 bays and is powered by TWO SATA power sockets, i.e. not one per bay. Was always curious about that since in almost every scenario, both power connectors would be off the same power supply cable.
Thanks, But I don't think so. The fact that there is a setting for caching the drive (which is enabled), means some writes may not yet be done to the HD at a particular moment. I may "think" I know what processes could/should be writing to the drive, but the fact that I don't know what is...
I just shucked a WD Elements drive I want to use in IcyDock MB830SPs I have installed in various Windows desktops. The drive has worked fine in the Elements for years BUT USB 3 is slower than SATA and more significantly, the WD Elements would put itself to sleep which then added 5 or more...
Display driver might be it. This started after the last Intel display driver update. But also after the last Windows update. I have rolled back the video driver.
I wish I had never started using Intel's update service. I've never seen a single update that wasn't just to address some gaming...
Has happened 4 or 5 times (that I know of, would not know if happened while PC is in lock status) in the last month.
I'll be typing or reading the screen and screens go black and a few seconds later both display the connection type (HDMI, etc). A few seconds later, the lock screen appears, and...