Set Win10 As NTP Server

Set Win10 As NTP Server

The following instructions are to used at your own risk.

  1. In REGEDIT navigate to:
  1. Current Control Set
  1. Services
  1. W32Time
  1. TimeProviders
  1. NtpServer
  1. Edit Enabled REG_DWORD value from 0 to 1



  1. Close REGEDIT
  2. Open FIREWALL – Advanced settings
  1. In Advanced settings, create an inbound rule

  1. Repeat procedure for outbound rules
  2. Close Firewall
  3. Open SERVICES
  1. Scroll down to Windows Time

  1. Change Startup Type to Automatic
  2. Under Service Status select START
  3. Apply and exit

    • Related Articles

    • Cannot Connect to NTP Server

      This is a common error message that we receive a lot of calls on. A NTP server is a network time protocol server.  Think of it as a master time clock.  Your projector and/or server attempts to connect to this master time clock on a regular basis ...
    • IMB Server not responding

      This is a very common call that we receive.  The call is that the (IMB) server is not responding to input from the web GUI.  This is a common complaint from servers that use a web browser (Chrome, Firefox, Opera, Internet Explorer or Edge) for ...
    • Dolby DSS Server not keeping proper time

      The Dolby server synchronizes with a NTP server (master time clock) when it boots up. If a server is left on for an extended period the time clock will drift. We suggest a weekly reboot of the server. This will synchronize the clock to the correct ...
    • Public NTP Time Servers

      Here are some time servers that can be used for the master clocks in servers/IMB's: Google: While the actual URL for the Google public NTP servers is, most servers can't handle a canonical domain name (ie., the actual ...
    • GDC TMS displaying incorrect schedule time after DST time change

      There is a known issue with GDC TMS systems that will cause them to display the incorrect time on the scheduler tab the days of the biannual time change. The actual computer clock in the system tray will show the correct time but the scheduler clock ...