[ntp:questions] NTP 4.2.8p10 released

David Taylor david-taylor at blueyonder.co.uk.invalid
Mon Mar 27 16:05:44 UTC 2017

On 27/03/2017 15:50, Martin Burnicki wrote:
> This is a bug which made it into ntpd 4.2.8p10. I've just found the
> reason and opened an issue on bugzilla:
> http://bugs.ntp.org/show_bug.cgi?id=3402
> I've also already a fix for this.
> The best solution for you is to specify the DLL name in a registry key
> instead of the environment variable.
> Run regedit and open this registry path:
> HKLM\System\CurrentControlSet\services\NTP
> Then create a new key as multipart string, with the name "PPSProviders",
> and the contents "loopback_pps_api_provider.dll".
> Or, as a temporary workaround for the environment variables, you could
> try to append a dummy DLL name to the real DLL name, e.g.:
> PPSAPI_DLLS=loopback_pps_api_provider.dll;dummy
> Martin

As it happens, on two Win-10/64 Pro PCs here the bug doesn't appear to 
exist, and they (continue) to run correctly with:


I've updated the bug.

Web: http://www.satsignal.eu

More information about the questions mailing list