Christopher (Drashna)

Unfortunately, no, not currently.   The Windows apps (including XBOX apps) do some weird stuff that isn't supported on the pool.  And adding support for it isn't trivial (it's likely some very low level file system implementation that may be very difficult to implement).
That said, you *could* use StableBit CloudDrive and the local disk provider to create a drive on the pool, and install the games to that.  Because it's emulated at the block level rather than the file system level (like StableBit DrivePool), it shouldn't have the issues with the Windows/XBOX Apps

Yes, it is supported. 

Yes, it is supported. 

Namely, that Microsoft's support for the OS's ended October 2023, and we generally keep in lockstep with that.  That's primarily due to the lack of updates and fixes that may negetively impact our software.    
It may continue to operate without issues, but we don't guarantee that. 

Unfortunately, no.   It would take some code changes to facilitate that. 

I'll post it here too.  
There is a fix in the latest betas involving memory corruptions of file IDs.  
However, ... the issue may also be the wrong API being used: 
 
 

Hard Disk Sentinel Pro found an additional three HDD's that were "bad" or failing, on top of the 2 i already replaced, all due to bad sectors & running out of space to replace them.  Some were over 10 years old & all were over 5 years.  Pulled out the bad ones and went shopping.    Got my money's worth from them.  All new drives are server grade refurbs from the same company I bought one of the old drives from, they're online now, but still stand by their products & honor warranties so I feel pretty secure.  And as I read in another post, a sever crash/issue is a great excuse to upgrade your hardware.  My pool "accidentally" grew by 12Tb after I got it fixed.  😁  Best news was I turned on Pool Duplication and when I looked at was duplicating at the folder level, I found 2 miscellaneous folders that were not duplicating, changed them manually and YAY!  Measuring, Duplication and Balancing all finished OK.  Amazing what a hundred bucks or so of new equipment will do.  So my original issues were all equipment related after all. 

Yup, something broke on our end.  This should be fixed now, and updating should get the fixed version.

Yup, something broke on our end.  This should be fixed now, and updating should get the fixed version.

Yup, something broke on our end.  This should be fixed now, and updating should get the fixed version.

Thank you for the investigation!  That definitely helps a lot!
And there looks like there were UI fixes in 1600, so likely something broke there, accidentally. 
That said, I've created an issue for this: https://stablebit.com/Admin/IssueAnalysis/28956

Thank you for the investigation!  That definitely helps a lot!
And there looks like there were UI fixes in 1600, so likely something broke there, accidentally. 
That said, I've created an issue for this: https://stablebit.com/Admin/IssueAnalysis/28956

Are you sure that this was with StableBit DrivePool, and not Drive Bender?  
The reason I ask, is that we don't disable duplication, and we don't use the term "mirror" for file protection (it's always duplication).  
And because of the section in the licensing FAQ, and experience: 
https://stablebit.com/Support/DrivePool/Licensing
 
This is a topic that has come up from time to time, and we do have plans on if this were to happen.  Obviously, we don't want it to ever happen, but the future is uncertain. 
I believe the plan in that case was basically, disable the licensing altogether, and stop support completely for the software.  

To clarify, Windows 7 (and 8,) are no longer supported by Microsoft, and no longer receiving updates.
We follow suite with the Microsoft support lifecycles, since we can't ensure stability of the OS outside of the support lifecycle. Additionally, key components (such as .NET Framework and Visual C++ runtimes) may not be supported, anymore.  Especially in the case where we need/want to update this components. 
However, we haven't done anything to explicitly disable support for these OSes, so they may still work just fine.  However, the longer it's been since they've exited the support lifecycle, the more likely you are to have issues.
 
Additionally, Windows 10 leaves extended support Oct 2025. Yay....

Due to an unexpected glitch while updating the site, the Contact site is broken.
 
We're working on fixing this issue as quickly as possible.
 
 
We have fixed the issue with the Contact site. 
However, if you experience any issues with it, please let us know know right away.
You can do so, by contacting me directly at "christopher@covecube.com".
Just let us know what the issue with the site is, and what the issue that brought you to the site was.
 
 
We apologize for any trouble that this may have caused.

There should be absolutely no issue with doing so.  
 
Neither product does anything that takes exclusive control over anything, so it should be safe to run both products concurrently. 
 
 
 
 
What are you trying to monitor specifically, here? If you don't mind me asking.

To add to this, yes, the progress is saved.  The "scanning" percentage is based on what needs to be scanned currently, not on the whole disk.  Which can be misleading.
That said, you can see how the drive is tracked here: 
https://stablebit.com/Support/Scanner/2.X/Manual?Section=Disk Scanning Panel#Sector Map
And you may note that each sector has a date when it was last scanned.  Each region is tracked, and different regions on the same disk can and will have different dates and times.   Over time, this should actually help the software to "learn" when to scan the drives, by picking times when they are much less likely to be throttled. 

You absolutely can use StableBit DrivePool in a VM.  There shouldn't be any issues with doing so, if you're passing the whole disk through. 
The only caveat is that you may not get SMART support for the drives inside of the VM, but this depends on hypervisor and how things are configured. 

I'll post it here too.  
There is a fix in the latest betas involving memory corruptions of file IDs.  
However, ... the issue may also be the wrong API being used: 
 
 

To clarify (and make it simple to find), here is Alex's official definition of that "Other" space:
 
 

Folks, thank all for the ideas. I am not neglecting them but I have some health issues that make it very hard for me to do much of anything for a while. I will try the more promising ones as my health permits but it will take some time. From operation and the lack of errors during writing/reading it seems that I am in no danger except duplication won't work. I can live with that for a while.
Keep the ideas coming and, maybe, I can get this mess fixed and report back which tools worked for me.
I am making one pass through my pool where I remove a drive from the pool, run full diagnosis and file system diagnosis on that drive then I re-add it back to the pool. When completed that will assure that there are no underlying drive problems and I can proceed from there.
Thanks to all who tried to help this old man.  

You and your fibre broadband bubble
Fair enough, thank you for your response. We'll wait for a message from Alex.

Alex has said that he plans on postind on the forums an announcement about this, and it may be best to wait for that. 
That said, between the fact that Google Drive has always had a 750GB per account per day upload limit (which is pretty low), some of the odd issues that pop up with it, and that they've recently limited to 1TB (or 5TB) of data and lock the account if it exceeds it (eg, stops uploads),  the writing has been on the wall for a while.  

No.  There is some very hidden data that doesn't copy over, really.  But if the new drive is added to the pool, you could copy the contents of the PoolPart folder on the old drive to the PoolPart folder on the new drive.   Just make sure you remeasure after it's done. 

Alex has said that he plans on postind on the forums an announcement about this, and it may be best to wait for that. 
That said, between the fact that Google Drive has always had a 750GB per account per day upload limit (which is pretty low), some of the odd issues that pop up with it, and that they've recently limited to 1TB (or 5TB) of data and lock the account if it exceeds it (eg, stops uploads),  the writing has been on the wall for a while.