Forum Discussion
SUGGESTION: change the UX when trying to access a volume with a newer ReFS version than supported
If you are trying to access to disk which is formatted with 3.9 (WS vNext + W11 22H2 RP / beta / insider) and you attach it to an earlier version of Windows Server (or client OS), File Explorer will first throw a message that the volume is unformatted.
This is dangerous.
If you choose to press cancel instead of format, it will bring up a more satisfying message.
[Window Title]
Location is not available
[Content]
E:\ is not accessible.
The volume does not contain a recognized file system.
Please make sure that all required file system drivers are loaded and that the volume is not corrupted.
[OK]
1st message
2nd message when you decide to not click "format disk"
suggestion: it should be the other way round, if possible outline it is a newer version of ReFS than supported by the current OS would be splendid.
9 Replies
lately the number of "complaints" about RAW devices surged on techcommunity. The problem seems to be an incompatibility of ReFS between Windows 11 and Windows Server vNext. I see this myself. Windows 11 cannot access ReFS volumes formatted in Windows 11 Beta / Dev or vNext.
We should resolve this mystery to users that are not familiar with this page
Windows ReFS versions · GitHub
And Microsoft on the other hand, next to solving the puzzle in UX, should really incorporate an own official page like the linked on in learn.microsoft.com.
I see no reason we must rely to third party Insiders (even a MSFT employee taking care about this gist for years now.
feedback hub link as this also affects Windows Client OS and Windows Server alike.
https://aka.ms/AAoi0jp- Better suggestion:
Push updates out to older versions of Windows so that never version numbers of ReFS can be recognized. The message could say something like "This volume is formatted with ReFS version 3.9, however this version of Windows only supports up to version 3.2 of ReFS. Please see <some URL> for a full list of Windows versions with the corresponding supported ReFS versions."
Another suggestion:
When mounting ReFS on newer versions of Windows, don't silently, automatically upgrade the volume to the newer ReFS version.- Not completely true, the ReFS version is written to the volume so you can easily obtain this (in fact if you check the event logs they *might* indicate it can't mount the volume due to version issues). Further, the structures of the file system are also written to the volume (this is partially how ReFS works with regard to backward compatability). I'm not across the specifics but I do know it exists based on reverse engineering papers I've read.
In short, yes it should be trivial for Microsoft to indicate that the volume can't be mounted because the version is too new (and provide the version number at a minimum).
- technically, fsinfo is unable to read the ReFS version used, so I am not sure if we can improve the error dlg. but I hope we can change the order.
- Well considering the amount of documentation and support/tooling for ReFS is close to non-existant since years, I highly doubt it. I wouldn't be surprised if Microsoft plainly drop the support of this filesystem in a near future.
- Hi Alban, this isn't true.
ReFS is still under active development and Windows Server 2022 and vnext have new versions and features, this is why I raised my suggestion.
In addition there are many day to day scenarios that benefit from storing data on (the lastest) ReFS.
- FSlogix containers
- Hyper-V S2D / Azure Stack HCI (by default)
- Citrix PVS
- Hyper-V on logical local drives or on Storage Spaces
- Exchange Server Databases + Logs
- SQL Server Databases + File Backups + Logs
Just to name some common scenarios
