Raymond Chen, a longtime Windows engineer, made the point in a post on The Old New Thing blog dated November 18, 2026. Neowin picked it up on November 19. The post is a useful reminder for developers and IT administrators who read Microsoft Learn closely.
What Chen said
Many file system function pages on Microsoft Learn carry a Remarks line saying the function is supported by the following technologies. A table of file systems and network protocols follows.
Chen's reading is direct. The table lists the file systems and network protocols Microsoft has information about. If something is missing, that doesn't mean it lacks support. It means Microsoft doesn't know whether it has support.
An explicit "No" carries more weight. Chen says that if Microsoft were sure a technology didn't support an operation, it would appear in the table with a "No".
Neowin adds the practical reason. Many third parties develop technologies and protocols that can work with Windows operations, even when the documentation doesn't list them. It also says it isn't realistic to list and test every third-party implementation for every Windows operation.
The example table
Neowin illustrates the point with the GetVolumeInformationByHandleW page. Chen's own post shows the same table under GetFileInformationByHandle, so the pattern appears on more than one function page.
On the GetVolumeInformationByHandleW page, Microsoft says that in Windows 8 and Windows Server 2012 the support statuses are:
| Technology | Supported |
|---|---|
| SMB 3.0 protocol | No |
| SMB 3.0 Transparent Failover (TFO) | No |
| SMB 3.0 with Scale-out File Shares (SO) | No |
| Cluster Shared Volume File System (CsvFS) | Yes |
| Resilient File System (ReFS) | Yes |
Microsoft's page adds a short explanation under the table: SMB does not support volume management functions. That explains the three SMB "No" entries. The table covers this function and these technologies only. It is not a verdict on SMB in general.
How to read these tables
- "No" means no. Treat it as a firm statement for that technology and that function.
- "Yes" means Microsoft has information confirming support. Here that covers CsvFS and ReFS.
- A missing entry means Microsoft is silent. It is not a hidden "No." Chen's wording is that Microsoft doesn't know either way.
- The scope is narrow. The table applies to one function and, on this page, to Windows 8 and Windows Server 2012. The same page lists Windows Vista and Windows Server 2008 as the minimum supported versions, and those requirements are separate from the table.
What to do with an unlisted technology
The steps below are my own practical suggestions, not a Microsoft procedure.
- Check the exact function and technology. A "Yes" or "No" for one API doesn't carry over to another.
- Check the vendor's or project's documentation for the file system or protocol you plan to use.
- Test the real operation on your target Windows version. Microsoft can't have tested a third-party stack it doesn't know about, so you may be the first to try it.
- Record the result. Treat it as your own validation, not as Microsoft-backed support.
Why this matters
Support tables are easy to over-read. A cautious administrator might rule out a storage product because it isn't on the list. A developer might assume the opposite and ship something that was never tested. Both are mistakes.
The function's output shows why the details matter. GetVolumeInformationByHandleW returns flags that describe a volume's capabilities, such as sparse file or reparse point support, depending on what the file system reports. Those flags describe what a given volume reports. They are a different question from whether a named technology supports the function. Mixing the two up is an easy way to draw the wrong conclusion.
Chen's point also fits a limit that Microsoft Learn itself shows. The page for this function was last updated on September 27, 2022. A table can sit unchanged for years while third-party file systems and protocols keep changing. Silence in an old table says very little about today's ecosystem.
Bottom line
Read "No" as a firm answer and silence as an open question. When the technology you care about isn't listed, check the vendor's documentation and test it on your target Windows version.
References
- Don't assume Windows doesn't support something just because Microsoft doesn't document it - Neowin Neowin · 2026-11-19T22:32:01+00:00
- If the Windows documentation doesn't list a particular technology as supporting an operation, does that mean that it doesn't support it? - The Old New Thing devblogs.microsoft.com
- GetVolumeInformationByHandleW function (fileapi.h) - Win32 apps | Microsoft Learn learn.microsoft.com