4kn-native · shipping · also 4Kn, 4K native

4Kn native sectors

4Kn exposes 4096-byte logical sectors and 4096-byte physical sectors without 512-byte sector emulation.

The interface uses 4096-byte addressing units. A filesystem block is a separate abstraction; neither its size nor a device's sector format alone specifies an application's recovery contract.

Support tables: KB 2510009 groups Advance Format, AF, 4K Native, and 4Kn at reported logical 4 KB and physical 4 KB, on all Windows versions from Windows 8 and later versions and all Server versions from Server 2012 and later versions [5]. The compatibility update prints only Windows 8 and Windows Server 2012, while its platforms line continues through Windows Server 2016 [2].

Hyper-V in Windows Server 2012 makes it possible to store a VHD on a native 4 KB disk by a software read-modify-write, because the VHD driver issues 512-byte I/Os [8]. The impact was in the range of 30% to 80% and was even higher at times in the preceding 512e subsection, not the native 4 KB subsection [8].

NVMe logical block data size excludes metadata, is always a power of two, and may be 512 bytes, 1 KiB, 2 KiB, 4 KiB, 8 KiB, etc. [6]. A 32b Guard example sets LBA Data Size to Ch for 4 KiB, and a non-zero value less than 9 (i.e., 512 bytes) is not supported [6]. Publication 100870879 lists 4Kn sizes of 4096, 4160 or 4224 bytes per logical block and 2,441,609,216 blocks (hex 91880000) at sector size 4096 for 10TB [7]. Starting 2012, hard drive manufacturers will commence shipment of Generation One AF 4Kn at 4,096 bytes per sector [9].

Relations

related
Advanced Format (4K), NVMe, Direct I/O, Read-modify-write, Logical sector, Physical sector, 512e emulation, Partition alignment

Advantages

  • Removes the 512-byte addressing emulation used by 512e. [2]

Limitations

  • Software and the complete access path must support the logical sector size. [2]
  • Aligned addressing alone does not establish persistent completion through volatile caches. [3]
  • Fsutil fsinfo ntfsinfo treats Bytes Per Sector 4096 and Bytes per Physical Sector 4096 as 4K native, and 512 with 4096 as Advanced Format (also known as 512E). [5]
  • A reported size that is not 4 KB or 512 bytes is Not Supported. [5]
  • Creating a VHD on a native 4K sector drive with Disk Management or Hyper-V fails with Incorrect Function on Windows Server 2008 R2. [5]
  • System image backup and restore may fail with error 0x8078002A when the logical sector size is other than 512 bytes. [5]
  • Fast format between 4Kn and 512E is possible only if sector sizes are exact multiples of 8, and the selected sector size takes effect only after fast format or full format. [7]
  • Windows XP, Windows Server 2003, and Windows Server 2003 R2 do not support 512e or 4Kn media. [2]

Citations

  1. Microsoft: Advanced format disk compatibility update, sector formats and alignment issues (accessed 2026-10-12)
  2. Linux 6.12: Explicit volatile write back cache control (accessed 2026-10-12)
  3. Microsoft: Support policy for 4K sector hard drives (KB 2510009), dated 2026-02-12 (accessed 2026-11-01)
  4. NVM Express NVM Command Set Specification, Revision 1.0e (July 29, 2024) (accessed 2026-11-01)
  5. Seagate Exos 7E10 SAS Product Manual, Rev. E, publication 100870879 (October 2021) (accessed 2026-11-01)
  6. Microsoft: Hyper-V Support for Large Sector Disks Overview, dated 2016-10-25 (accessed 2026-11-01)
  7. IDEMA: Advanced Format in the Enterprise, Generation One AF 4Kn (accessed 2026-11-01)

Further reading

  1. 4Kn native sectors (accessed 2026-03-26)
  2. Hesela: 512e, 4Kn and alignment: geometry is not durability (accessed 2026-10-12)
Sources & caveats
  • KB 2510009 is dated 2026-02-12. It prints no drive count and no measurement date. The Except for Hyper-V note is on the 512e row, not the 4Kn row. [5]
  • Error 0x8078002A is system image backup and restore on a logical sector other than 512 bytes, and that paragraph names no Windows version. Incorrect Function is a separate Windows Server 2008 R2 failure when creating a VHD. [5]
  • Unsupported scenarios say a resolution is not guaranteed for an unsupported storage device, and the cost of an unresolved investigation is not refunded. [5]
  • The compatibility update 4Kn cell prints Windows 8 and Windows Server 2012 only. Its platforms line continues through Windows Server 2016. The caution after the XP sentence names 512e media, not 4Kn. [2]
  • On that page a physical sector is the unit for which read and write operations complete in a single operation, called the unit of atomic write. The walkthrough is a 512-byte logical write. No temperature is printed. [2]
  • The large-sector overview applies to Windows Server 2012 R2 and Windows Server 2012 and is dated 2016-10-25. The 30% to 80% range names no sample size and is in the 512e subsection. The VHD driver assumes a 512-byte physical sector. [8]
  • NVM Express NVM Command Set Specification Revision 1.0e, 29 July 2024, sections 1.4.3.5 and 2.1, Figure 98, and the 32b Guard example. The size list ends with etc., so 8 KiB is not a stated maximum. LBADS 0h means that format is not currently available. [6]
  • Seagate Exos 7E10 SAS Product Manual, publication 100870879, Rev. E, October 2021, sections 1.0, 3.1, 3.5, and 4.1.2. Default configuration is 512E for 512e / 4kn drives. The 10TB row at sector size 4096 is decimal 2,441,609,216 and hex 91880000. [7]
  • IDEMA's enterprise page says Generation One AF 4Kn uses 4,096 bytes per sector and that hard drive manufacturers will commence shipment starting 2012. Prospective wording, with no sample size, completion date, or temperature. [9]

JSON: /data/terms/4kn-native.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. 4Kn native sectors. Hesela. 2026-11-01. https://hesela.dev/terms/4kn-native/