Cloud & infrastructure

Boot From ReFS in Windows Server 2028: What It Means, Limits and When to Use It

Windows Server 2028 can boot from ReFS. Learn what Microsoft documents, the UEFI and Generation 2 limits, ReFS vs NTFS trade-offs, and how to test it in a lab.

By EpiFive Editorial TeamReviewed/updated 13 min readHow we check our guides
On this page

Windows Server 2028 can boot from ReFS, the Resilient File System, instead of requiring NTFS for the system drive. Microsoft's announcement lists "the ability to boot from ReFS" as a preview feature, and an earlier Insider post shows the setup step. It requires UEFI, is preview only, and is not ready for production system volumes.

Who this is for

This guide is for Windows Server admins and storage owners who have heard "boot from ReFS" and want to know what it means in practice. By the end you will know what Microsoft has documented, what ReFS gives a system volume that NTFS does not, what it still lacks, the hardware and VM limits, how to confirm a volume's file system, and a short plan for testing it without touching production.

Windows Server 2028 is a public preview. Microsoft's announcement says the security, performance and management features are available in preview through the Windows Server Insider Program. No general availability date and no pricing or licensing details were on the pages we read, so none are given here. For the wider release see Windows Server 2028 preview: what is new, and for a test VM see install the Windows Server 2028 preview in a Hyper-V lab.

What Microsoft has actually said

Two Microsoft posts matter, and one Microsoft doc page disagrees with them because it is older.

The Windows Server 2028 announcement on the Windows Server blog (Tech Community, updated November 17, 2026) says: "Windows Server 2028 adds native NVMe storage enabled by default and NVMe over TCP and RDMA transports," and adds "along with the ability to boot from ReFS." It gives no build number and no detail about how ReFS boot works.

The detail comes from "Announcing ReFS Boot for Windows Server Insiders" (Tech Community, February 26, 2026). It says:

  • Builds from 2/11/26 or later, with a minimum build number of 29531.1000.260206-1841, "include ReFS boot in setup."
  • ReFS boot requires UEFI firmware and does not support legacy BIOS boot.
  • Generation 1 VMs are not supported.
  • ReFS supports volumes up to 35 petabytes (35,000 TB), compared with NTFS's typical limit of 256 TB.
  • You enable it by formatting the system (C:) partition as ReFS in the setup UI, then verify with fsutil fsinfo volumeInfo C: or the drive's properties.

A Microsoft reply in the comments on March 3, 2026 adds that Secure Boot is not required and native NVMe is supported. Treat that comment as a lighter source than the post itself.

The older page is the ReFS overview on Microsoft Learn (last updated December 2025). Its feature table lists "Bootable" under features unavailable on ReFS, with NTFS marked as supported. That was true when the page was written. It does not describe the preview, so do not read it as a contradiction of the Insider post. Expect the page to change when the feature approaches general availability, but that is an expectation, not a Microsoft statement.

ReFS vs NTFS for a system volume

Microsoft's overview page lists these limits and capabilities. The comparison below is what changes when the volume that holds Windows is ReFS.

AreaReFSNTFSSource
Maximum volume size35 PB256 TBReFS overview
Metadata checksumsAlwaysNoReFS boot post
File data checksums (integrity streams)OptionalNoIntegrity streams page
Automatic repair with Storage Spaces mirror or parityYesNot listedReFS overview
Block cloningYesNoReFS overview
Fixed VHD creationSecondsMinutesReFS boot post
Disk quotasNoYesReFS overview
Short namesNo (not officially supported)YesReFS overview
Shrinking a volumeNoYesReFS overview
Page file supportYesYesReFS overview
BitLockerYesYesReFS overview

The size gap works out to 35,000 TB divided by 256 TB, about 136.7 times. For a boot volume that number rarely matters, because system drives are small. The reasons people care about ReFS boot are integrity checking and consistent tooling across the OS and data volumes.

What ReFS adds

Microsoft's ReFS boot post lists metadata checksums, optional integrity streams, a proactive error-detection scrubber, online integrity without chkdsk, and sparse provisioning as benefits of ReFS boot over NTFS boot.

Two caveats from the integrity streams page are worth keeping in mind. First, ReFS always uses checksums for metadata, but "doesn't, by default, generate or validate checksums for file data." Integrity streams for file data are optional. Second, Microsoft says integrity streams carry a performance cost, because writes become allocate-on-write and checksum work can add latency, and recommends leaving them disabled on performance-sensitive systems. On a bare drive with no mirror or parity space, ReFS can detect a corrupt file with integrity streams but cannot repair it; it returns an error instead of the corrupted data.

The scrubber runs every four weeks by default, and the interval can be changed in Task Scheduler under Microsoft\Windows\Data Integrity Scan. The page notes it can only validate file data for files that have integrity streams enabled.

What ReFS still lacks

The overview page lists transactions, object IDs, Offloaded Data Transfer (ODX), short names, disk quotas, removable media support and volume shrinking as unavailable on ReFS. Check whether anything on your server's system drive depends on those. Disk quotas and shrinking are the ones that most often come up in practice.

The page also says that for SANs, if features such as thin provisioning, TRIM/UNMAP or ODX are required, you must use NTFS. That note is about SAN-backed data volumes, but it is a reminder that ReFS has storage-layer prerequisites.

Limits to check before you try it

Requirement or limitWhat Microsoft saysSource
FirmwareUEFI required; legacy BIOS boot not supportedReFS boot post
Hyper-V VM generationGeneration 1 not supportedReFS boot post
Secure BootNot requiredMicrosoft comment, March 3, 2026
Native NVMeSupportedMicrosoft comment, March 3, 2026
Build29531.1000.260206-1841 or later for the February 2026 Insider buildsReFS boot post
Hardware supportReFS configurations must use Windows Server Catalog certified hardwareReFS overview
Release statusPreview, no general availability date announced2028 announcement

In practice that means a physical server set to UEFI mode, or a Generation 2 VM. The build number in the table is from the February post; the November 2028 preview builds are newer, and the announcement does not say which build to use, so download the current Insider ISO from the Windows Server Insider program instead of hunting for the older one. See the lab install guide for that.

What the sources do not tell you

Several questions that admins ask first are not answered on the pages we read:

  • Boot from mirrored Storage Spaces. A commenter on the Insider post asked about this and the page contains no answer.
  • Carry-over to general availability. Another commenter asked whether ReFS boot will be in the final release. No answer is on the page, and the 2028 announcement gives no date.
  • Recovery and repair tooling. The sources we read do not describe how Windows Recovery Environment, offline repair or backup products handle a ReFS system volume. Confirm that with your backup and imaging vendors before relying on it.
  • Performance of the OS itself. The Insider post says large file copies are independent of file size on ReFS, which fits block cloning, but it publishes no boot-time or application benchmark.
  • Integrity stream reliability. A commenter raised a data corruption concern linked to a Reddit post. A Microsoft reply on March 23, 2026 said the problem came from errors in the original script linked in that post, which was corrected. We did not reproduce this, so treat it as Microsoft's statement, not a result we confirmed.

Test ReFS boot in a lab

Do this on a throwaway VM or spare server. Do not use hardware that holds data you need.

Step 1: Prepare a UEFI target

Create a Generation 2 VM in Hyper-V, or set a spare physical server to UEFI boot. Attach the current Windows Server 2028 Insider preview ISO.

Step 2: Format the system partition as ReFS in setup

During Windows Server setup, when you reach the disk selection screen, follow Microsoft's post: format the system (C:) partition as ReFS in the setup UI. The post describes this as the way to enable the feature on a qualifying build. We did not run setup in this article, so the exact on-screen labels in the 2028 preview ISO are not quoted here.

Step 3: Verify the file system

After first sign-in, open PowerShell as administrator and run Microsoft's verification command:

fsutil fsinfo volumeInfo C:

Microsoft's fsutil page documents this command and describes its output as including the file system. The page's documented sample, for an NTFS volume, shows this line:

File System Name : NTFS

On a ReFS system volume you should see ReFS on that line instead. The Insider post names this command as the verification step, but it does not show sample ReFS output, so confirm the value on your own VM.

You can also list volumes with the Storage module:

Get-Volume -DriveLetter C

Microsoft's documented example output has the columns DriveLetter, FileSystemLabel, FileSystem, HealthStatus, SizeRemaining and Size, with NTFS in the FileSystem column for that example. Expect ReFS there on your test VM.

Step 4: Check integrity stream settings

Integrity streams for file data are optional. To see the setting for a file, Microsoft's page documents:

Get-FileIntegrity -FileName 'C:\Docs\TextDocument.txt'

and to change it:

Set-FileIntegrity -FileName 'C:\Docs\TextDocument.txt' -Enable $True

Because integrity streams change write behavior and Microsoft recommends leaving them off on performance-sensitive systems, leave them at the default on a first test and measure before enabling them on anything large.

Step 5: Run your own workload checks

Install the agents and tools the server would run in production: backup agent, antivirus or EDR, monitoring and management agents. Any one of them that assumes an NTFS system volume could fail. Record what works, what warns, and what fails. If you plan to measure disk performance, use the same method for both file systems; the native NVMe driver check and benchmark guide shows a repeatable DiskSpd approach.

Step 6: Practice recovery

Before drawing any conclusion, boot the VM from the install ISO into repair mode, take a checkpoint, break the boot configuration in the lab, and see whether your recovery steps work on ReFS. Microsoft's pages do not document this, so your own result is the only evidence you will have.

When ReFS boot makes sense, and when it does not

SituationSuggested approach
Production file, database or domain controller serversStay on NTFS system volumes. The feature is in preview.
Hyper-V or Storage Spaces Direct hostsKeep ReFS on data volumes as Microsoft documents; test ReFS boot in a lab only.
Lab VMs and image-testing pipelinesGood fit. Try ReFS boot and see how your tools behave.
Servers that need disk quotas, volume shrinking or ODX on the system driveStay on NTFS; ReFS does not support these.
Legacy BIOS or Generation 1 VMsNot possible; ReFS boot needs UEFI.
Applications or backup tools that require NTFSAsk the vendor for ReFS boot support before testing.

The fair summary: ReFS boot extends a file system you may already use for data volumes to the system volume, and the benefits Microsoft lists are integrity checking and consistent tooling. The costs are a preview-only status, unanswered recovery questions and a feature list that is smaller than NTFS.

Troubleshooting

  • Setup does not offer ReFS for the system partition. Confirm you booted a qualifying Insider build and that the machine started in UEFI mode. Microsoft's post says the feature is in builds from 2/11/26 and later, and not supported on legacy BIOS or Generation 1 VMs.
  • The VM will not boot after install. Check that it is Generation 2. The post lists Generation 1 as unsupported. If the VM is Generation 2, rebuild it and try again with an unmodified Insider ISO before suspecting ReFS.
  • fsutil returns an error. Run PowerShell or Command Prompt as administrator, and use the drive letter with a colon, as in Microsoft's syntax fsutil fsinfo volumeinfo <rootpath>:.
  • An agent refuses to install. Check the vendor's documentation for ReFS system volume support. Do not edit installer checks to get around it.
  • Corruption reports on forums. Read the original thread and Microsoft's reply on the Insider post before acting. The documented answer for one report was a script error, but test your own data before enabling integrity streams widely.

Checklist

  • Confirm the target is UEFI or a Generation 2 VM.
  • Download the current Windows Server Insider preview build and label every test machine "preview, not for production".
  • Format C: as ReFS in setup and verify with fsutil fsinfo volumeInfo C:.
  • Install your backup, security and monitoring agents and record the results.
  • Practice a recovery from the install media.
  • Leave integrity streams at the default until you have measured their cost.
  • Re-read Microsoft's ReFS overview before any production decision, since it still lists boot as unavailable.

See also

What we checked

  • Opened the Windows Server 2028 announcement on the Tech Community Windows Server blog on 2026-11-22. It states the release "adds native NVMe storage enabled by default and NVMe over TCP and RDMA transports" and "the ability to boot from ReFS". The page gives no build number and describes the features as available in preview.
  • Opened "Announcing ReFS Boot for Windows Server Insiders" (published 2026-02-26) on 2026-11-22. Confirmed the UEFI requirement, no legacy BIOS, no Generation 1 VMs, the minimum build 29531.1000.260206-1841, the 35 PB limit and the fsutil fsinfo volumeInfo C: verification step.
  • Cross-checked file system limits against the ReFS overview on Microsoft Learn (updated 2025-12-09): 35 PB vs 256 TB, and the list of features unavailable on ReFS. That page lists Bootable as unavailable on ReFS, which conflicts with the 2026 preview posts; we report the conflict instead of resolving it.
  • Opened the integrity streams page and the block cloning page on Microsoft Learn and confirmed that file data checksums are optional, the scrubber default is every four weeks, and block cloning needs source and destination on the same ReFS volume.
  • Opened the fsutil fsinfo and Get-Volume pages on Microsoft Learn. Documented fsutil sample output shows File System Name : NTFS; documented Get-Volume sample output shows an NTFS volume. We did not see ReFS output documented for either command.
  • Recalculated 35,000 TB divided by 256 TB: 136.72, rounded to about 136.7 times.
  • Not tested: we did not install the preview or format a ReFS system volume, so the setup screens, recovery behavior and application compatibility are not verified hands-on. Steps follow Microsoft's posts as of 2026-11-22.

Last tested: 2026-11-22

References

Questions people ask

Can Windows Server 2028 boot from ReFS?

Microsoft's Windows Server 2028 announcement says the release adds the ability to boot from ReFS, and Microsoft's Insider post shows how to format the system partition as ReFS in setup. It is a public preview only, with no announced general availability date, so treat it as a lab feature.

Does ReFS boot work on legacy BIOS or Generation 1 VMs?

No. Microsoft's ReFS boot post says it requires UEFI firmware and does not support legacy BIOS boot, and that Generation 1 virtual machines are not supported. Use a UEFI physical server or a Generation 2 VM.

How do I check whether the C drive is ReFS?

Run fsutil fsinfo volumeInfo C: and read the File System Name line, or open the drive's properties. Microsoft's post names both methods. Get-Volume -DriveLetter C also lists a FileSystem column.

Should I move production servers to ReFS boot volumes?

Not yet. The feature is in preview, Microsoft's ReFS overview page still lists boot as unavailable on ReFS, and the sources we read do not document recovery tooling or Storage Spaces boot. Keep NTFS for production system volumes and test ReFS boot in a lab.

Windows Server 2028ReFSNTFSUEFIWindows Server Insider