Last night, I was checking out my TRIM status, as I do maybe a couple times per year with the usual command which always returns a value of 0.
fsutil behavior query disabledeletenotify
I then noticed while all was OK with NTFS, there was another file system that TRIM hadn't yet been setup on, ReFS. The result was ReFS DisableDeleteNotify isn't currently set. I never installed the ReFS file system, sound like something taken from a similar Linux one (Reiser File System).
Note that it's been over a year since I participated in the Windows Insider Program, anyone who isn't in that program should not be subjected to experimental file systems & any other offerings that not 100% stable. Furthermore, customers deserves to know about these issues in an advance notice, so that we can research the changes & make an informed decision in regards to what's best for us.
This reeks of more of Satya Nadella's underhanded tactics, like shipping out 'node.js' to those with the latest NVIDIA cards, a product of the Linux Foundation, a couple of months before announcing that Microsoft was becoming a Platinum Member (purchased) of that Foundation. The really bad thing was, and one would have to be running Secunia PSI installed to know, was that the latest node.js wasn't in the NVIDIA driver package. However, there's a site for node.js that allows one to download the latest version. Like Flash Player & Java, it's best to manually remove the old node.js version before installing the new, to avoid security risks, rather than piling one update on top of another.
Yet this new file system does much deeper than node.js, it's going to convert NTFS (which has lots more features) to basically an experimental one. Look at this, ReFS has 8 less features than NTFS, one has to go to the bottom of the page to see in a side by side comparison.
Now, for those who are willing to deal with ReFS, here's the fix on this page, the second group of commands, again, at the bottom of the page (Step #5). And it's no wonder when I ran CHKDSK /F which required a reboot, that it was stuck at 100% for over two hours before I forced shutdown & rebooted, than it showed 100% again & proceeded to load into Windows.
As a file system, ReFS is not only good for resiliency, it is great for maintaining extremely large amounts of data. With data integrity and recovery features built-into the file system, there is no need to wait for CHKDSK to run to fix corruption. What if you needed to store 500 billion gigabytes in one place?. But why stop there?
Now what consumer has 500 Billion GG of data to store? This sounds to be more of a solution for servers (just as in the Linux world the Btrfs is over ext4, what end users runs), and like Btrfs, what we don't know about ReFS, is it going to hammer our SSD's with writes to destroy these? Sure my SATA-3 512GB Samsung 850 Pro has a 10 year warranty, yet it also has a lifecycle of so many TBW written to the SSD, if that number is reached first, then the 10 year warranty is for nil. I also have a more expensive M.2 512GB Samsung 950 Pro NVMe SSD that's 3.5 times faster than my 2nd best SSD (listed above), and it has only a 5 year warranty.
I'll have choices to make if ReFS becomes the norm, am not going to have my SSD's hammered until they die like those publications who benchmarks them by performing a couple of full write cycles across the drives before each test to help us determine which is best for us. That's their duty, not ours, to hammer these SSD's to the max.
As for the one PC that I discovered the ReFS file system on, have the last Windows 7 backup image before upgrading to W10 (same for the rest of my upgrades), and after a secure erase of the drive, will restore it. There will be a black screen at first, yet after an update cycle & reboot, this will go away. Will run W7 until EOL, then go with my favorite OS that I use 95% of the time, Linux Mint. Most of my Windows use is restricted to assisting others, and it's been since early 2012 (nearly 5 years) when I last made a transaction on a Windows install, too much Malware, too much placing a new roof on top of an old one, the can has been kicked down the road too far for my comfort. And evidently other also, as until recently, for over a decade, month after month, Microsoft enjoyed a steady 90% of usershare, that's dropped off in the last few months.
Sure there was the bloated 'Modern UI' (codenamed 'Metro') & later improvements, yet underneath, it's still the same. One can go into the Control Panel & type in 'Turn Windows feature on or off', and enable the unsupported .NET 2.0 & 3.5 (just like what came with XP), this option should be greyed out for Home users to prevent Malware infection, only those who knows what they're doing should be enabling such features.
Yet my main concern and Topic is about ReFS, it's pros & cons, is it really appropriate for Home users with 120GB to 2TB HDD's or SSD's to have this file system enabled or in use? And how is it accomplished w/out a clean install of the OS, the upgrades keeps the user files in place, only a Reset or clean install can make it reality, unless Microsoft has a way of doing things w/out telling us, not unusual since Satya Nadella took over, hopping on every latest trend that comes along. Seems like this file system is more appropriate for a Server that rarely gets shut down, whereas there could be corruption by shutting down several times daily.
Finally, just how many Home users, even running Pro, actually takes advantage of Hyper-V? It was introduced with the Windows 8 Pro promo ($40) in 2012, yet few Home users bothers with it, complicated to setup & most uses VirtualBox or VMware Workstation Player (both free), as Microsoft freely gave it to us, yet there were no tutorials on how to implement the feature included, and still isn't with new computers shipping today with 8.1 or 10 Pro. Users has to figure out on their own, or be working in an environment that's running these VM's,
So does this mean clean install = ReFS formatting? Not much use I see for the Home user, and nowhere can I find the impact on SSD's.