Symptoms

Consider the following scenarios:

Scenario 1

  • You have a computer that is running Windows Server 2008, Windows 7, or Windows Server 2008 R2.

  • You configure the complementary metal-oxide semiconductor (CMOS) clock according to Coordinated Universal Time (UTC).

  • You configure a DWORD type registry key named RealTimeIsUniversal in the following path, and set the value to 1:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation

  • The CMOS clock does not match the Windows clock.

  • The computer starts the daylight saving time (DST) changeover.

In this scenario, the computer uses 100 percent of CPU resources. The CPU usage remains at 100 percent until both the CMOS clock and the Windows clock pass the DST changeover time.

Scenario 2

  • You deploy a Hyper-V virtual machine that is running Windows Server 2008, Windows 7, or Windows Server 2008 R2.

  • The clock on the host server that runs the virtual machine is set to the UTC time zone.

  • You change the time zone of the Windows clock on the virtual machine to a local time zone.

  • After you restart the virtual machine, the Windows clock on the virtual machine does not reflect the local time zone, and is instead set to the UTC time zone.

  • You configure a DWORD type registry key named RealTimeIsUniversal in the following path on the virtual machine, and set the value to 1:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation

  • The CMOS clock does not match the Windows clock.

  • The virtual machine and the host server start the DST changeover.

In this scenario, the virtual machine uses 100 percent of CPU resources. The CPU usage remains at 100 percent until both the clock on the host computer and the Windows clock on the virtual machine pass the DST changeover time.

Cause

This issue occurs because the hardware abstraction layer (HAL) uses the CMOS clock time incorrectly, and this causes a conflict. This behavior occurs when the RealTimeIsUniversal registry key is configured.

Resolution

For more information about how to download the hotfix for Windows 7 SP1, Windows Server 2008 R2 SP1, or Windows Embedded Standard 7 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

2922223 You cannot change system time if RealTimeIsUniversal registry entry is enabled in Windows
NoteThe update for Windows Server 2008 also contains another update. That update resolves a similar issue that occurs during the transition to a new year in Windows Server 2008.

For more information about how to work around this issue in Windows XP and Windows Vista, click the following article number to view the article in the Microsoft Knowledge Base:

2687252 System may become unresponsive during Daylight Saving Time (DST) changeover if RealTimeIsUniversal is set

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:

  • Windows Server 2008 Service Pack 2 (SP2)

  • Windows 7 Service Pack 1 (SP1)

  • Windows Server 2008 R2 SP1

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in UTC. The dates and the times for these files on your local computer are displayed in your local time together with your current DST bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008, Windows 7, and Windows Server 2008 R2 file information notes Important Only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to Windows Server 2008, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.0.600
    2.23xxx

    Windows Server 2008

    SP2

    LDR

    6.1.760
    1.22xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Ntkrnlpa.exe

6.0.6002.23037

3,605,352

09-Feb-2013

05:28

Not applicable

Ntoskrnl.exe

6.0.6002.23037

3,553,656

09-Feb-2013

05:28

Not applicable

For all supported x64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Ntoskrnl.exe

6.0.6002.23037

4,682,088

09-Feb-2013

05:17

x64

For all supported IA-64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Ntoskrnl.exe

6.0.6002.23037

9,471,864

09-Feb-2013

05:06

IA-64

For all supported x86-based versions of Windows 7

File name

File version

File size

Date

Time

Platform

Appid-ppdlic.xrm-ms

Not applicable

3,013

25-Dec-2013

02:26

Not applicable

Appid.sys

6.1.7601.22551

50,176

25-Dec-2013

01:12

x86

Appidapi.dll

6.1.7601.22551

50,688

25-Dec-2013

02:03

x86

Appidcertstorecheck.exe

6.1.7601.22551

16,896

25-Dec-2013

01:12

x86

Appidpolicyconverter.exe

6.1.7601.22551

97,792

25-Dec-2013

01:12

x86

Appidsvc.dll

6.1.7601.22551

29,696

25-Dec-2013

01:12

x86

Csrsrv.dll

6.1.7601.18113

38,912

19-Mar-2013

04:48

x86

Csrsrv.dll

6.1.7601.22551

38,912

25-Dec-2013

02:03

x86

Ntkrnlpa.exe

6.1.7601.18352

3,969,984

26-Dec-2013

02:03

Not applicable

Ntoskrnl.exe

6.1.7601.18352

3,914,176

26-Dec-2013

02:03

Not applicable

Ntkrnlpa.exe

6.1.7601.22551

3,974,080

25-Dec-2013

02:10

Not applicable

Ntoskrnl.exe

6.1.7601.22551

3,918,784

25-Dec-2013

02:10

Not applicable

Apisetschema.dll

6.1.7600.16385

6,656

14-Jul-2009

01:03

x86

Smss.exe

6.1.7601.18113

69,632

19-Mar-2013

02:49

x86

Apisetschema.dll

6.1.7601.22551

6,656

25-Dec-2013

02:03

x86

Smss.exe

6.1.7601.22551

69,632

25-Dec-2013

00:56

x86

Apisetschema.dll

6.1.7600.16385

12,648

02-Apr-2010

03:07

x86

Smss.exe

6.1.7601.18113

69,632

19-Mar-2013

02:49

x86

Apisetschema.dll

6.1.7601.22551

6,656

25-Dec-2013

02:03

x86

Smss.exe

6.1.7601.22551

69,632

25-Dec-2013

00:56

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Appid-ppdlic.xrm-ms

Not applicable

3,013

25-Dec-2013

02:51

Not applicable

Appid.sys

6.1.7601.22551

61,952

25-Dec-2013

01:32

x64

Appidapi.dll

6.1.7601.22551

58,368

25-Dec-2013

02:28

x64

Appidcertstorecheck.exe

6.1.7601.22551

17,920

25-Dec-2013

01:32

x64

Appidpolicyconverter.exe

6.1.7601.22551

148,480

25-Dec-2013

01:32

x64

Appidsvc.dll

6.1.7601.22551

34,304

25-Dec-2013

02:28

x64

Csrsrv.dll

6.1.7601.18229

43,520

02-Aug-2013

02:12

x64

Csrsrv.dll

6.1.7601.22551

43,520

25-Dec-2013

02:29

x64

Ntoskrnl.exe

6.1.7601.18352

5,550,016

26-Dec-2013

02:31

x64

Ntoskrnl.exe

6.1.7601.22551

5,553,088

25-Dec-2013

02:35

x64

Apisetschema.dll

6.1.7601.18229

6,656

02-Aug-2013

02:12

x64

Smss.exe

6.1.7601.18229

112,640

02-Aug-2013

00:59

x64

Apisetschema.dll

6.1.7601.22551

6,656

25-Dec-2013

02:28

x64

Smss.exe

6.1.7601.22551

112,640

25-Dec-2013

01:12

x64

Apisetschema.dll

6.1.7601.18229

6,656

02-Aug-2013

02:12

x64

Smss.exe

6.1.7601.18229

112,640

02-Aug-2013

00:59

x64

Apisetschema.dll

6.1.7601.22551

6,656

25-Dec-2013

02:28

x64

Smss.exe

6.1.7601.22551

112,640

25-Dec-2013

01:12

x64

Appidapi.dll

6.1.7601.22551

50,688

25-Dec-2013

02:03

x86

Apisetschema.dll

6.1.7601.18229

6,656

02-Aug-2013

01:48

x86

Apisetschema.dll

6.1.7601.22551

6,656

25-Dec-2013

02:03

x86

Apisetschema.dll

6.1.7601.18229

6,656

02-Aug-2013

01:48

x86

Apisetschema.dll

6.1.7601.22551

6,656

25-Dec-2013

02:03

x86

Ntkrnlpa.exe

6.1.7601.18352

3,969,984

26-Dec-2013

02:03

Not applicable

Ntoskrnl.exe

6.1.7601.18352

3,914,176

26-Dec-2013

02:03

Not applicable

Ntkrnlpa.exe

6.1.7601.22551

3,974,080

25-Dec-2013

02:10

Not applicable

Ntoskrnl.exe

6.1.7601.22551

3,918,784

25-Dec-2013

02:10

Not applicable

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Appid-ppdlic.xrm-ms

Not applicable

3,013

25-Dec-2013

01:56

Not applicable

Appid.sys

6.1.7601.22551

131,584

25-Dec-2013

00:59

IA-64

Appidapi.dll

6.1.7601.22551

116,736

25-Dec-2013

01:33

IA-64

Appidcertstorecheck.exe

6.1.7601.22551

39,424

25-Dec-2013

00:59

IA-64

Appidpolicyconverter.exe

6.1.7601.22551

282,624

25-Dec-2013

00:59

IA-64

Appidsvc.dll

6.1.7601.22551

74,240

25-Dec-2013

01:33

IA-64

Csrsrv.dll

6.1.7601.18229

94,720

02-Aug-2013

01:25

IA-64

Csrsrv.dll

6.1.7601.22551

94,720

25-Dec-2013

01:34

IA-64

Ntoskrnl.exe

6.1.7601.18352

11,115,968

26-Dec-2013

01:40

IA-64

Ntoskrnl.exe

6.1.7601.22551

11,126,720

25-Dec-2013

01:40

IA-64

Apisetschema.dll

6.1.7601.18229

6,656

02-Aug-2013

01:25

IA-64

Smss.exe

6.1.7601.18229

207,872

02-Aug-2013

00:34

IA-64

Apisetschema.dll

6.1.7601.22551

6,656

25-Dec-2013

01:33

IA-64

Smss.exe

6.1.7601.22551

207,872

25-Dec-2013

00:41

IA-64

Appidapi.dll

6.1.7601.22551

50,688

25-Dec-2013

02:03

x86

Apisetschema.dll

6.1.7601.18229

6,656

02-Aug-2013

01:48

x86

Apisetschema.dll

6.1.7601.22551

6,656

25-Dec-2013

02:03

x86

Ntkrnlpa.exe

6.1.7601.18352

3,969,984

26-Dec-2013

02:03

Not applicable

Ntoskrnl.exe

6.1.7601.18352

3,914,176

26-Dec-2013

02:03

Not applicable

Ntkrnlpa.exe

6.1.7601.22551

3,974,080

25-Dec-2013

02:10

Not applicable

Ntoskrnl.exe

6.1.7601.22551

3,918,784

25-Dec-2013

02:10

Not applicable


Status

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

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×