This article applies to Domain Time II.

Last Updated: 02 March 2026

Windows 11 version 24H2 (or later) running on Snapdragon X Arm64 processors includes an emulation layer called Prism that supports running native x64 applications directly.

Preparation

• Domain Time will automatically detect that it is running under emulation and adjust its internal parameters accordingly.
• Local or remote tools will report Arm64 instead of x64.
• You may install, upgrade, and manage Domain Time on Arm64 as if it were running on an AMD or Intel x64 processor. Just run setup.exe as if you were installing to a native x64 machine.
• Manager and Audit Server, along with support tools, operate correctly, whether running locally or remotely.
• For best timing results, use a PTP time source and a wired Ethernet connection.
Supported Configuration

• Domain Time II 5.2.b.20260302 or later
• Windows 11 24H2 or later Arm64 edition (25H2 or later preferred)
• Qualcomm Snapdragon X, X Elite, X Plus, X2 or later processor
Performance

• Domain Time under emulation performs as well as under equivalent native x64 processors.
• All Snapdragon processors fall into the class of "mobile processors." Mobile processors are designed to prioritize battery life (low power consumption) over processing power. Typical mobile processors from Intel include the U series and the Celeron series. Typical mobile processors from AMD include the U series and the Ryzen AI series.
• Mobile processors do not provide the stability and consistency of desktop or server processors, and are therefore more likely to service interrupts less quickly, and introduce other internal latency issues. While these factors do not generally affect day-to-day tasks, programs like Domain Time, which measure very tiny time intervals (sub-microsecond), can be affected more noticeably.
• Most machines using mobile processors are laptops, which usually rely on Wi-Fi rather than a dedicated Ethernet port. See KB2026.204 for timing issues related to Wi-Fi or USB-to-Ethernet dongles/docks.
• Here are example results from a Dell Latitude (Snapdragon X Elite), using a USB-to-Ethernet dongle, synchronizing to a local PTP time source:
  

      Timespan: 16 hours, 28 minutes, 8 seconds
   Largest Pos: +0.0000010 seconds (  1.0 µs)
   Largest Neg: -0.0000009 seconds (  0.9 µs)
        StdDev:  0.0000004 seconds (  0.4 µs)
        Median: +0.0000003 seconds (  0.3 µs)
       Average: +0.0000002 seconds (  0.2 µs)

  The worst offset was 1 microsecond, and the average was 2/10^ths of a microsecond. Your own results may vary.
Future Development

As the ARM64 platform matures, we will consider building native Arm versions of Domain Time if a native build provides better time synchronization than running under emulation. CPU times, RAM usage, and power consumption under emulation are equivalent to native x64 programs running on AMD or Intel processors.