Welcome to Microsoft Q&A!
Thank you for taking the time to provide such detailed information about your environment and the troubleshooting you have already performed.
Based on the available Microsoft documentation and the configuration you shared, Windows 10 Enterprise LTSC 1809 does include the native Windows Time Service PTP provider. A new PTP time provider was introduced in Windows 10 version 1809 and Windows Server 2019.
However, the information currently available does not establish that the installed Intel I210 driver exposes the packet-timestamping capabilities required by Windows. Therefore, I would not consider this is a confirmed Windows PTP defect at this stage.
1. Windows 10 LTSC 1809 PTP support
The native PTP functionality itself is present in Windows 10 version 1809, so using PtpClient/ptpprov.dll on Build 17763 is consistent with Microsoft's implementation.
This confirms feature availability, but it does not certify every NIC, driver, firmware, or Grandmaster combination.
2. Intel I210 and NDIS timestamping
This is the area I would investigate first.
Windows 10 version 1809 includes NDIS 6.82, and Microsoft's NDIS packet-timestamping interface begins with NDIS 6.82. This interface as the mechanism through which a miniport driver exposes its hardware timestamping capabilities to Windows.
Your Intel I210 driver is reporting NDIS 6.50. Therefore, the presence of PTP functionality in the I210 hardware should not by itself be taken as confirmation that driver 12.15.184.13 exposes the NDIS timestamping capabilities required by the Windows implementation.
The standardized timestamping INF keywords as:
- *PtpHardwareTimestamp
- *SoftwareTimestamp
The driver is responsible for reading these values and reporting the capabilities that are actually enabled to NDIS. Hardware and software timestamping cannot be enabled together.
For that reason, I would avoid enabling multiple hardware/software timestamp options simultaneously. The most useful validation is not simply whether the registry properties exist, but whether Windows can query the adapter's supported and active timestamp capabilities.
The following APIs for that purpose:
-
GetInterfaceSupportedTimestampCapabilities -
GetInterfaceActiveTimestampCapabilities -
CaptureInterfaceHardwareCrossTimestampfor hardware cross-timestamping
These APIs allow an application to determine what timestamping functionality the NIC/driver actually exposes to Windows.
3. PTP profile and transport
Microsoft's packet-timestamping currently scopes support to:
- PTPv2
- UDP transport
- two-step operation
- PTP event timestamping
- not raw Ethernet PTP
For two-step PTP, the timestamp is provided separately, for example through a Follow_Up message.
Therefore, the OEM7 configuration should be verified in a packet capture rather than assuming that basic Ethernet connectivity or opening UDP 319/320 is sufficient.
In particular, I would verify that the exchange contains:
- Announce
- Sync
- the corresponding
Follow_Up - Windows
Delay_Req - the corresponding Grandmaster
Delay_Resp
Also verify that the PTP domain, sequence IDs, two-step behavior, source/destination addresses, and other relevant PTP properties match on both sides.
Seeing only incoming Announce, Sync, and Follow_Up packets would confirm that PTP traffic reaches the machine but would not by itself confirm that Windows has accepted the Grandmaster as a usable time source.
4. PtpClient configuration
I would also retest using Microsoft's PTP configuration example as closely as possible.
In particular, use the explicit Grandmaster address:
PtpMasters = 172.17.28.11
Rather than relying on 0.0.0.0 as a discovery value.
Your Enabled, InputProvider, and DllName settings are consistent with loading the provider, but I would compare the complete configuration, including AnnounceInterval and DelayPollInterval, against the Microsoft W32Time PTP configuration samples before performing another test.
After changing the provider configuration, restart the Windows Time service before retesting.
5. Missing PTP Operational event log
I would not use the absence of Microsoft-Windows-Time-Service-PTP-Provider/Operational or PtpClient/Operational alone as evidence that PTP is unsupported or that ptpprov.dll failed to load.
Instead, first enumerate the event channels actually registered on this installation:
wevtutil el | findstr /i "Time-Service PTP"
If no PTP-specific channel is registered on the fully updated LTSC 1809 system, confirming whether this is expected for that exact Build 17763 servicing level would require Microsoft Support.
6. State Machine 0 and "no time data was available"
The current output below indicates that W32Time has not obtained an acceptable synchronization sample:
- State Machine: 0 (Unset)
- Stratum: 0
- Leap Indicator: 3
- Source: Local CMOS Clock
- no time data was available
Importantly, the generic Microsoft article for "The computer did not resync because no time data was available" is focused on NTP scenarios. Its NTP-specific causes, such as UDP 123 or NTP server advertisement, should therefore not be directly applied to this PTP configuration.
For this case, the failure still needs to be isolated between the NIC/driver timestamping layer, PTP provider configuration, and the actual PTP exchange with the OEM7.
I could not identify documentation establishing a known Microsoft issue specifically for the exact combination of Windows 10 LTSC 1809 + Intel I210 driver 12.15.184.13 + NovAtel OEM7. Therefore, I would avoid classifying this as a known Windows defect without confirmation from Microsoft and Intel.
7. Recommended next troubleshooting step
I recommend collecting the following before changing additional settings:
W32Time configuration
w32tm /query /configuration /verbose
w32tm /query /status /verbose
w32tm /query /source
w32tm /query /peers
w32tm /dumpreg
w32tm /dumpreg /subkey:TimeProviders\PtpClient
w32tm as the preferred command-line tool for configuring, monitoring, and troubleshooting W32Time, and /debug can be used to enable the W32Time private log.
Conclusion
At this point, I would focus first on driver timestamp-capability reporting and PTP interoperability, rather than treating the behavior as a confirmed Windows 10 LTSC 1809 issue.
Windows 10 version 1809 includes the native PTP provider, and Microsoft documents PTPv2-over-UDP and two-step timestamping support. However, the Intel driver reporting NDIS 6.50 is an important point to investigate because Microsoft's NDIS packet-timestamping interface starts with NDIS 6.82.
I would therefore recommend:
- Retest with the Microsoft
PtpClientconfiguration baseline and the explicit OEM7 address. - Enable only one supported timestamping method rather than hardware and software timestamping together.
- Verify the I210 driver's actual supported and active timestamp capabilities.
- Capture the complete PTP exchange, including
Delay_Req/Delay_Resp.
If the PtpClient still does not select an active master, I would recommend opening a Microsoft Support case with those traces and logs. The Intel driver capability information can likewise be provided to Intel to confirm whether this specific I210 driver version supports the required Windows timestamping interface.
I hope this helps clarify where the issue is most likely occurring and, more importantly, gives you a structured way to narrow it down without making unnecessary changes to the system.
References:
Overview of NDIS packet timestamping - Windows drivers | Microsoft Learn
Packet timestamping - Win32 apps | Microsoft Learn
Windows Time Service Tools and Settings | Microsoft Learn
Introduction to NDIS 6.82 - Windows drivers | Microsoft Learn
Insider preview for Windows Time Service features in Windows Server 2019 | Microsoft Learn
Standardized INF keywords for NDIS packet timestamping - Windows drivers | Microsoft Learn
If you find it useful, please click Accept Answer.
Thank you for choosing Microsoft Q&A.
Note: This is the Italiano (it-it) forum. I kindly recommend posting your question in Italiano, as this will make it easier for other forum members and subject matter experts to engage with your inquiry. If you prefer to post in English, you may also consider using the English forum, where a larger English-speaking audience can review and respond to your question. Thank you for your understanding.