ReFS port to Win10

That's why it's good to keep NTFS even if it doesn't have all that nonsense, same version formatted in Windows XP, works in Windows 11.

 

If you want to use ReFS with Windows 10 (or 11, I'd recommend 10) it works fine with Windows 10 IoT LTSC -- you can format partitions and volumes in ReFS and they're faster and more reliable.

Windows 10 IoT LTSC is a better SKU of Windows 10 in just about every way: less base installed crap, more performant, has all the Enterprise level utilities (if you need them), runs everything consumer SKUs run, and it's still supported.

Arguments that 'NTFS doesn't have all that nonsense' is like suggesting you should be formatting in FAT, or riding thirty miles to work on a horse, it's ridiculous, even ReFS isn't a very modern and performant file system compared to the options available on *NIX operating systems...

 

.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

What claim? Which file systems? On which platform? Espionage724 didn't specify. There are many: five major file systems on Linux, well over a dozen more esoteric filesystems, some built for performance, some for robustness, some have even been ported to Windows.

A simple search regarding the file systems you or he are interested in, or ask any AI regarding those that interest you and you can get very specific benchmarks comparing aspects of performance and robustness that apply to your specific use case. How can I be expected to be anyone's research assistant that hasn't even made the effort to be specific about what they're asking and are taking a thread way off topic? Which seems disingenuous at best...

The on topic point, which was specific, is you can easily use ReFS on Windows 10, any Enterprise SKU in fact, but IoT LTSC is still supported and ReFS is a much more modern and robust than NTFS, it's not "nonsense" -- there are very valid reasons that sebus may want to use it...

 

refs is win11

 

.

 

ReFS is a File System, Windows 11 is an Operating System...

Surely if your assumptions and wants are sincere, you could have searched this faster than typing it here? But the assumption here is all yours, I made no argument favoring ReFS.

Even running with your assumption this will turn into a not very productive discussion as there are use cases where either will be faster, but I explicitly said and meant performant.

Summarily more modern file systems will outperform older file systems (NTFS is an over thirty years old, closed source, proprietary mess like everything Microsoft) if you weigh a full context of performance.

If you weight data R/W speed with mean time to failure and mean time to recovery NTFS can be less performant than FAT in some contexts. All the raw speed in tiny file R/W doesn't mean anything if you don't get to the finish line and lose important data that's unrecoverable due to file system design flaws...

Spoiler: TLDR

Virtually all native Linux file systems are significantly faster than NTFS when running on their native operating systems. Here are the primary Linux file systems that are faster than NTFS, categorized by what they do best:

1. ext4 (Fourth Extended Filesystem)

• The Verdict: The "just works" speed king for general use.
  
  
• Why it’s faster than NTFS:
  • Delayed Allocation: ext4 holds data in system memory and writes it to the disk in large, contiguous blocks all at once. This drastically reduces disk fragmentation and speeds up write times.
    
    
  • Extents: Instead of mapping every single block of a file (like NTFS), ext4 maps files in contiguous ranges of blocks ("extents"), which greatly speeds up the reading of large files.
    
    
  • Lightweight: It has significantly less metadata overhead than NTFS.

2. XFS

• The Verdict: The heavy-lifter for massive files, databases, and enterprise servers.
  
  
• Why it’s faster than NTFS:
  • Parallel I/O: XFS is designed for high-performance multithreading. It divides the storage into "Allocation Groups" that can be read from and written to simultaneously, meaning multi-core CPUs can write to the disk in parallel without bottlenecking.
    
    
  • Large File Handling: It scales incredibly well. For multi-gigabyte or terabyte-sized files (like video editing raw files or large database files), XFS routinely beats both ext4 and NTFS.

3. F2FS (Flash-Friendly File System)

• The Verdict: The absolute fastest option for NVMe SSDs, SD cards, and mobile storage.
  
  
• Why it’s faster than NTFS:
  • Built for Flash: Traditional file systems (including NTFS and ext4) were originally designed with spinning hard drives in mind. F2FS was built from the ground up by Samsung specifically for NAND flash memory.
    
    
  • Log-Structured Design: It minimizes random write operations (which degrade SSDs and slow them down) and turns them into sequential writes, making it blistering fast on modern solid-state drives.

4. Btrfs

• The Verdict: Faster in specific operations, feature-rich, and highly modern.
  
  
• Why it’s faster than NTFS:
  • Copy-on-Write (CoW): When you copy a file on Btrfs, it doesn't actually copy the data immediately; it just points to the original data. The "copy" is virtually instantaneous.
    
    
  • Note: Btrfs focuses heavily on data integrity, snapshots, and built-in RAID. Because of this extra safety overhead, its raw sequential write speeds can sometimes be slightly slower than ext4, but it still easily outpaces NTFS in system responsiveness and file duplication.

 

Per my original post if you read it -- if you want to use ReFS with Windows 10 (or 11, I'd recommend 10) it works fine with Windows 10 IoT LTSC -- and most Enterprise Windows 10 SKUs, you'll be able to format, read and write ReFUS partitions.

Windows 10 IoT LTSC is a better SKU of Windows 10 in just about every way: less base installed crap, more performant, has all the Enterprise level utilities (if you need them), runs everything consumer SKUs run, it's still supported, and it's FREE...

If you're using a consumer SKU of Windows you're past due where it's smart to install something that's still supported...

I don't understand how this doesn't answer your question...

 

You need to login to view this posts content.