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.

Expand all | Collapse all

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

Collapse this tableExpand this table

Registry location	Value name	Value type and data
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config	LargePhaseOffset	dword:00138800 (Decimal:1280000)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config	SpikeWatchPeriod	dword:0000005a (Decimal:90)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient	EventLogFlags	dword:00000000 (Decimal:0)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer	Enabled	dword:00000001 (Decimal:1)

Default registry settings in Windows Vista

Collapse this tableExpand this table

Registry location	Value name	Value type and data
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config	LargePhaseOffset	dword:02faf080 (Decimal:50000000)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config	SpikeWatchPeriod	dword:00000384 (Decimal:900)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient	EventLogFlags	dword:00000001 (Decimal:1)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer	Enabled	dword: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.

Fix this problem

Note This wizard is temporarily 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 (http://support.microsoft.com/kb/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:

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.
Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
Right-click LargePhaseOffset, and then click Modify.
In the Value data box, type 02faf080, and then click OK.
Right-click SpikeWatchPeriod, and then click Modify.
In the Value data box, type 00000384, and then click OK.
Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient
Right-click EventLogFlags, and then click Modify.
In the Value data box, type 1, and then click OK.
Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer
Right-click Enabled, and then click Modify.
In the Value data box, type 0, and then click OK.
Exit Registry Editor.
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 (http://support.microsoft.com/contactus) .
We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog (http://blogs.technet.com/fixit4me/) , or send us an e-mail (mailto:fixit4me@microsoft.com?Subject=KB952660 - W32Time registry not updated after upgrade from XP SP2) message.

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

Collapse this tableExpand this table

Value name	Description
LargePhaseOffset	Specifies 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.
SpikeWatchPeriod	Specifies how long, in seconds, that a suspicious time offset must persist before it is accepted as correct.
EventLogFlags	Stores configuration data for the policy setting, Configure Windows NTP Client.
Enabled	Indicates whether the NtpServer provider is enabled in the current Time Service.

Back to the top