Gnarfoz

Huh, I must have missed the email notification or something. Good thing I remembered to check the old-fashioned way! :-) Changing that setting works. The service still doing something every 15 seconds, but whatever that is it's not waking up the pool drives. (It's actually the same thing that shows being attributed to the service itself in my Process Monitor screenshot, vs the stuff attributed to wmiprvse.exe.) Is this something we need to keep in mind? Or will there be some kind of "oh, this pool contains a BitLocker device" detection at some point? Thanks in any case! :-)

That "tweak" is a no-op: https://tweakhound.com/2009/12/11/ntfsmemoryusage2-tweak/

Hi, there seems to be a problem with the DrivePool service (directly or via WMI) periodically querying drives (even non-pool drives) for some information, thus preventing them from going into standby mode. The queries happen in a 5-second interval (when looking at WMI) or 15-second interval (when looking at the DrivePool service itself). They actually show up as I/O activity in for example StableBit Scanner or Process Hacker/Explorer or even just Windows' Task Manager. If I stop the service, this behavior stops (both WMI and direct queries disappear) and drives spin down as intended. What does the service even do? It does not seem to affect pool operation at all. Granted, I'm really only using the basic pooling feature, no duplication or anything else. Versions: Windows 10 DrivePool 2.2.0.649 I've attached a filtered (DeviceIoControl operations only) SysInternals Process Monitor log showing the behavior: drivepool_service.zip Also, screenshots: http://imgur.com/oG6JMfI- I/O spikes every couple of seconds http://imgur.com/qJySOBy- Process Monitor http://imgur.com/JKQtEwa- StableBit Scanner

The above mentioned version 2.2.0.634 has been working fine for me. Are you having actual problems, or just asking?

I upgraded from 8.1 to 10 last night and DrivePool does not seem to recognize my pool members (or the pool they make up). It only offers to create a new pool using the remaining drives. The pool members are still mounted in the folders they were mounted in before. (I tried assigning a drive letter to one of the pool members instead, but it still does not show up in the DrivePool window.) Edit: I managed to fix it. Sadly, using a "we will never know" method. ;-) I saw this issue that got implemented in one of the beta builds of version 2.2 and it looked like it might fit my problem. So I tried upgrading to the latest beta build (2.2.0.634). However, the upgrade would just fail every time and not change anything. So I went ahead and uninstalled the stable version -- and here's where the "we will never know" part comes into play -- went straight to the 2.2 beta. The drives showed up after that. Might be that uninstalling and re-installing the stable version would have achieved the same. I had tried using the "repair" option of the stable installer before, though, and it didn't help.