Thanks @Christopher (Drashna)! Really appreciate the team looking at this. I have been very impressed with the responsiveness of your team.
I saw you have a defect tracking system... is there a bug open for this that I can subscribe to or track so that I can get notified on progress? Does Alex have a rough order of magnitude on getting this fixed (weeks, months, quarters, etc.)? Just trying to set my expectations accordingly.
I still have a case open with Microsoft tech support. It's been a frustrating experience as they've essentially been stating that *no* changes were made to the Dedupe role in Server 2019 other than the inclusion of ReFS support. So obviously there were changes. I'm trying to get the dev team to at least be able to explain what they changed in the enumeration code that broke all this, i.e. what they're looking for that breaks your code. Because while I appreciate that ultimately you (Covecube) will need to change your code to adapt to the new environment, Microsoft did not document or even recognize that they'd made a change that would break your product. If you could let me know whether I should continue pursuing this, I'd be most appreciative. My guess is that your dev team know what the issue is, so if I should just drop it with Microsoft, I can do so.
BTW - if it helps at all, the *exact* same error occurs with Drive Bender, which is the product I used to use. So Microsoft's change breaks more than Drive Pool.
I have been very happy with the move to your product suite! Very well put together and the reliability seems extremely high. And I say that as a storage/data management professional who works for one of the largest storage/data management companies in the industry...
Thanks,
- TheBigMan