What you need to know
Which persistent-memory access model matches the application and filesystem requirements?
Potentially affected
Administrators evaluating persistent-memory storage on supported Windows Server platforms.
DSE recommendation
Have the application and storage owners choose the access model explicitly.
Source facts
Persistent memory retains its contents across power cycles and can be used as storage. Microsoft distinguishes block access through the normal filesystem and storage stacks from direct access, or DAX. Block access supports NTFS and ReFS; DAX is limited to NTFS. The guidance warns that incorrect DAX use can lose data and recommends a block translation table to reduce the risk of torn writes. Microsoft documentation.
Applicability
Identify the hardware, server release, application access model, filesystem, and supported deployment requirements. Review the application’s documented persistent-memory behavior before selecting DAX because of a latency goal.
DSE recommendation
Have the application and storage owners choose the access model explicitly. Record the required filesystem, protective configuration, and recovery method. Keep the access-model decision separate from whether a memory module is healthy or whether a persistent-memory region has been detected.
Verification
Deploy a representative supported test configuration and confirm that the application uses the intended access path. Validate controlled data writes and the approved recovery exercise, preserving configuration and outcome evidence. Investigate any unsupported access assumption before allowing important data onto the proposed design.
Official references
Microsoft Learn: Understand and deploy persistent memory. Source reviewed September 8, 2026.
Review the official source
Understand and deploy persistent memory · Verified September 8, 2026
Need help applying this guidance safely?
DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.
Talk with DSE