Oct 15 2022 09:15 AM - edited Oct 15 2022 09:19 AM
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.
Oct 15 2022 09:20 AM
Nov 04 2022 09:20 AM
Dec 12 2022 09:57 PM
Dec 26 2022 01:47 AM
Jan 08 2023 03:32 PM
Jan 19 2023 06:28 AM
Jan 21 2023 11:12 AM
May 06 2023 01:53 AM
Jan 07 2024 05:37 AM - edited Mar 06 2024 05:30 AM
Jan 07 2024 05:37 AM - edited Mar 06 2024 05:30 AM
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