Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Some W32Time-related registry settings are not updated after you upgrade Windows XP Service Pack 2 to Windows Vista or to Windows Vista Service Pack 1


View products that this article applies to.

Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows.

↑ Back to the top


Symptoms

You upgrade Windows XP Service Pack 2 (SP2) to Windows Vista or to Windows Vista Service Pack 1 (SP1). However, the following Windows Time Synchronization service (W32Time)-related registry settings are not updated to the default Windows Vista values.

Default registry settings in Windows XP
Registry locationValue nameValue type and data
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\ConfigLargePhaseOffsetdword:00138800 (Decimal:1280000)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\ConfigSpikeWatchPerioddword:0000005a (Decimal:90)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClientEventLogFlagsdword:00000000 (Decimal:0)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServerEnableddword:00000001 (Decimal:1)
Default registry settings in Windows Vista
Registry locationValue nameValue type and data
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\ConfigLargePhaseOffsetdword:02faf080 (Decimal:50000000)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\ConfigSpikeWatchPerioddword:00000384 (Decimal:900)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClientEventLogFlagsdword:00000001 (Decimal:1)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServerEnableddword:00000000 (Decimal:0)
This article helps you fix the problem.

To have us fix this problem for you, go to the "Fix it for me" section. If you would rather fix this problem yourself, go to the "Let me fix it myself" section.

↑ Back to the top


Fix it for me

To fix this problem automatically, click the Fix this problem link. Then click Run in the File Download dialog box, and follow the steps in this wizard.





Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.

Now go to the "Did this fix the problem?" section.

↑ Back to the top


Let me fix it myself

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To manually change these settings to the default Windows Vista values, follow these steps:
  1. Click Start, type
    regedit in the Start Search box, and then click regedit in the Programs list. If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
  3. Right-click LargePhaseOffset, and then click Modify.
  4. In the Value data box, type
    02faf080, and then click OK.
  5. Right-click SpikeWatchPeriod, and then click Modify.
  6. In the Value data box, type
    00000384, and then click OK.
  7. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient
  8. Right-click EventLogFlags, and then click
    Modify.
  9. In the Value data box, type
    1, and then click OK.
  10. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer
  11. Right-click Enabled, and then click
    Modify.
  12. In the Value data box, type
    0, and then click OK.
  13. Exit Registry Editor.
  14. Restart the computer.

↑ Back to the top


Did this fix the problem

Check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you can contact support.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

Value nameDescription
LargePhaseOffsetSpecifies the time offset, in tenths of a microsecond (A tenth of a microsecond is equal to 10 to the power of -7). Times that are larger than or equal to this value are considered suspicious and possibly incorrect.
SpikeWatchPeriodSpecifies how long, in seconds, that a suspicious time offset must persist before it is accepted as correct.
EventLogFlagsStores configuration data for the policy setting, Configure Windows NTP Client.
EnabledIndicates whether the NtpServer provider is enabled in the current Time Service.

↑ Back to the top


Keywords: kb, kbmsifixme, kbfixme, kbtshoot, kbexpertisebeginner, kbprb

↑ Back to the top

Article Info
Article ID : 952660
Revision : 3
Created on : 4/23/2018
Published on : 4/23/2018
Exists online : False
Views : 299