The BitLocker Drive Preparation Tool is available. You can use this tool to prepare the computer for BitLocker Drive Encryption.

This article describes how to obtain this tool. This article also provides an operational overview of the tool. This overview includes system requirements and command-line parameters. Finally, this article describes the most common problems that you may encounter when you use the tool.

Back to the top

How to obtain the BitLocker Drive Preparation Tool

Windows Vista Ultimate

If you are using Windows Vista Ultimate, follow these steps to obtain the tool:

1.	Click Start, type Windows Update in the Start Search box, and then press ENTER.
2.	Click Check for updates.
3.	Click View available Extras.
4.	Click to select the BitLocker and EFS enhancements check box, and then click Install.

Windows Vista Enterprise

If you are using Windows Vista Enterprise, use the following services to obtain this tool:

•

Microsoft Customer Support Services For a complete list of Microsoft Customer Support Services telephone numbers, visit the following Microsoft Web site:For more information, visit the following Microsoft Web page: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Back to the top

When you install this tool, the tool adds an item to the Start menu. To start the BitLocker Drive Preparation Tool, use one of the following methods:

•	Click Start, point to All Programs, click Accessories, click System Tools, click BitLocker, and then double-click BitLocker Drive Preparation Tool.
•	Click Start, type BitLocker in the Start Search text box, and then click BitLocker Drive Preparation Tool in the Programs list.

After the tool finishes preparing the drive, you must restart the computer. Then, you can use the Security item in Control Panel to enable BitLocker.

Back to the top

How to prepare the hard disk for BitLocker Drive Encryption

To encrypt drives and to verify boot integrity, BitLocker requires at least two partitions. These two partitions make up a split-load configuration. A split-load configuration separates the main operating system partition from the active system partition from which the computer starts.

The BitLocker Drive Preparation Tool automates the following processes to make the computer ready for BitLocker:

•	Creating the second volume that BitLocker requires
•	Migrating the boot files to the new volume
•	Making the volume an active volume

When the tool finishes, you must restart the computer to change the system volume to the newly created volume. After you restart the computer, the drive will be configured correctly for BitLocker. You may also have to initialize the Trusted Platform Module (TPM) before you turn BitLocker on.

Back to the top

System requirements

To create a new partition or to merge unallocated space with an existing partition, the target system must meet the following requirements:

•	A genuine version of Windows Vista Ultimate or Windows Vista Enterprise must be installed.
•	The active partition must contain boot configuration data and boot files.
•	The target partition must meet the following requirements: • The partition must be on a simple disk that is initialized for basic storage. • The partition must be a primary partition. Extended drives and logical drives are not supported. • The partition must be formatted by using the NTFS file system. • The partition must not be compressed. • The cluster size of the partition must be less than 4 KB or equal to 4 KB. • The partition is not using software spanning, software mirroring, or software RAID. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 314343 (/Feedback.aspx?kbNumber=314343/) Basic storage versus dynamic storage in Windows XP Note This tool works correctly in hardware RAID configurations. • For a split operation, at least 10 percent of the active partition must remain free after the partition size is reduced by 1.5 gigabytes (GB). • For a merge operation, the partition’s total capacity must be at least 1.5 GB. Also, the partition must have at least 800 MB of free disk space.

The following chart shows the target system requirements.

Back to the top

Operational overview

Target system configurations

The BitLocker Drive Preparation Tool supports Windows Vista Ultimate and Windows Vista Ultimate Enterprise. This tool successfully creates a split-load configuration when the active state, the system state and the boot state are all assigned to the same simple volume.

Default operational procedure

When the BitLocker Drive Preparation Tool starts, it tries to create a split-load configuration by using the following methods, in order of preference:

•	Merge unallocated space with a type 0×7 Windows Recovery (WinRE) partition
•	Create a new partition from unallocated space
•	Split an existing partition Note The tool tries to split the current active partition. If this action fails, the tool splits the largest available partition.
•	Merge unallocated space with the smallest suitable partition

Preferred order of operations

The following chart shows the preferred order of operations that the BitLocker Drive Preparation Tool follows.

Back to the top

Command-line parameters

The BitLocker Drive Preparation Tool uses a simple set of command-line parameters. These parameters make integration with enterprise deployment tools more flexible. Enterprise deployment tools include Microsoft Systems Management Server (SMS) and Microsoft Business Desktop Deployment (BDD). The parameters also provide customized deployment options. The following table lists the parameters. The parameters are not case-sensitive.

Parameter	Description	Notes
[-?] [/?]	Help – Provides a brief description of the tool’s purpose and parameters
[-driveinfo]	Displays the drive letter, the total size, the maximum free space, and the partition characteristics	Only valid partitions are listed. Characteristics are noted only for WinRE, operating system, and unallocated partitions.
[-target {unallocated ¦ drive: {shrink ¦ merge}}]	Indicates the desired operation for target partition: create a new partition from unallocated disk space, split the target partition to create a new partition, or merge unallocated space with the target partition	Cannot merge unallocated spaced with the operating system partition. Unallocated space is not listed if four primary or extended partitions already exist.
[-newdriveletter] ¦ DriveLetter:]	Indicates the drive letter for the newly created partition	Letters A, B, and C are excluded. If no letter is indicated, the first available drive letter backward from S is applied.
[-size ¦ SizeInMegabytes]	Indicates the size in megabytes for the new partition	The minimum size is 1500 MB. At least 10 percent of the target partition must be free after the new partition is created.
[-quiet]	Suppresses confirmation text to avoid user interaction
[-restart]	Restarts the system immediately after all operations are complete	Restarts immediately, regardless of open files or other users logged in.

Example scenario 1

The target system has a single partition. To prepare the computer for BitLocker, you want to split the operating system partition. You want the following conditions to be true:

•	The size of the new partition is 1500 MB.
•	The new partition uses X for the drive letter.
•	During the operation, confirmation dialog boxes do not appear.
•	The system restarts when the operation is complete.

To use these settings, run the following command at a command prompt:

Example scenario 2

The target system has more than one partition. To prepare the computer for BitLocker, you want to merge unallocated space with an existing partition. You want the following conditions to be true:

•	During the operation, confirmation dialog boxes do not appear.
•	The system restarts when the operation is complete.

To use these settings, run the following command at a command prompt:

Back to the top

A common problem

You may receive the following error message when you use the BitLocker Drive Preparation Tool:

This error may occur in one of the following scenarios.

Scenario 1: You do not have sufficient free disk space

At least 10 percent of the active partition must remain free after the partition size is reduced by 1.5 gigabytes (GB). To resolve this error, move files to another partition or delete files.

Scenario 2: The partition contains files that cannot be moved

The BitLocker Drive Preparation Tool may resize partitions to prepare a hard disk for BitLocker. Occasionally, some unmovable files may prevent the tool from defragmenting and resizing partitions. These files may include any of the following items:

•	Page files
•	Hibernation files (Hiberfil.sys)
•	The registry
•	NTFS metadata files. These files include the following files and others: • $mftmirr • $secure • $volume

This issue may occur even if the operating system is newly installed.

To work around this error, use one of the following methods:

•	Temporarily disable hibernation option and hard disk paging. Then, use the Windows Preinstallation Environment to delete the Hiberfil.sys file and the Pagefile.sys file. Restart the computer in Windows Vista. Then, run the BitLocker Drive Preparation Tool again.
•	Reinstall Windows Vista.

Back to the top

You receive an error message when you try to enable the BitLocker Drive Preparation Tool on an IBM portable computer

When you try to enable the BitLocker Drive Preparation Tool on an IBM portable computer that is running Windows Vista, you may receive the following error message:

To resolve this problem, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

1.	Click Start, type regedit in the Start Search box, and then click regedit in the Programs list.
2.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Session Manager Memory Management
3.	Verify the data type of the PagingFiles registry entry. If the data type is REG_SZ, follow these steps: a. Note the value data for the PagingFiles registry entry. b. Back up the following registry subkey: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Session Manager Memory Management c. Right-click PagingFiles, and then click Delete. d. Click Yes when you are prompted. e. On the Edit menu, point to New, and then click Multi-String Value. f. Type PagingFiles, and then press ENTER. g. On the Edit menu, click Modify. h. In the Value data box, type the value data that you noted in step 3a, and then click OK. i. Exit Registry Editor.
4.	Restart the computer.

For more information about security for portable computers that are running Windows Vista, visit the following Lenovo Web site:

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Back to the top

On a Microsoft Exchange Server 2007 Service Pack 1 (SP1) Edge server, when you use a Send connector that uses the BasicAuthRequireTLS value, the Edgetransport.exe process may crash intermittently. Additionally, the following errors may be logged in the Application log:

Event Type: Error
Event Source: MSExchangeTransport
Event Category: PoisonMessage
Event ID: 10003
Description:
The transport process failed during message processing with the following call stack: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at
Microsoft.Exchange.Security.Cryptography.CapiNativeMethods.CertGetCertificateChain(S afeChainEngineHandle engine, IntPtr pCertContext, IntPtr time, SafeCertStoreHandle hAdditionalStore, CertChainParameter& parameters, ChainBuildOptions flags, IntPtr reserved, SafeChainContextHandle& chainContext)
at
Microsoft.Exchange.Security.Cryptography.X509Certificates.ChainEngine.BuildAsAnonymo us(X509Certificate2 certificate, ChainBuildOptions options, ChainBuildParameter parameter)
at
Microsoft.Exchange.Protocols.Smtp.CertificateValidator.ChainValidateInternal(String domain, X509Certificate2 cert, Boolean validateAsAnonymous)
at
Microsoft.Exchange.Protocols.Smtp.CertificateValidator.ChainValidateAsAnonymous(X509 Certificate2 cert)
at
Microsoft.Exchange.Protocols.Smtp.SmtpOutSession.TlsNegotiationComplete()
at
Microsoft.Exchange.Protocols.Smtp.SmtpOutSession.TlsNegotiationComplete(IAsyncResult asyncResult)
at
Microsoft.Exchange.Net.LazyAsyncResult.Complete(IntPtr userToken)
at
Microsoft.Exchange.Net.NetworkConnection.InvokeSendCallback(LazyAsyncResultWithTimeo ut asyncResult, Object result)
at
Microsoft.Exchange.Net.NetworkConnection.SendTlsNegotiationCompleted(IAsyncResult asyncResult)
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

Event Type: Error
Event Source: MSExchange Common
Event Category: General
Event ID: 4999
Description:
Watson report about to be sent to dw20.exe for process id: <xxxx>, with parameters: E12, c-RTL-AMD64, 08.01.0240.006, edgetransport, M.E.Net, M.E.S.C.CapiNativeMethods.CertGetCertificateChain, System.AccessViolationException, 4d3a, 08.01.0240.005. ErrorReportingEnabled: True

Event Type: Error
Event Source: Microsoft Exchange Server
Event Category: None
Event ID: 5000
Description:
EventType e12, P1 c-rtl-amd64, P2 08.01.0240.006, P3 edgetransport, P4 m.e.net, P5 m.e.s.c.capinativemethods.certgetcertificatechain, P6 system.accessviolationexception, P7 4d3a, P8 08.01.0240.005, P9 NIL, P10 NIL.

Back to the top

To resolve this problem, install Update Rollup 2 for Exchange Server 2007 Service Pack 1. For more information about Update Rollup 2 for Exchange Server 2007 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

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

Back to the top

For more information about BasicAuthRequireTLS, visit the following Microsoft Web site:

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

For more information about the naming schema for Exchange Server software updates, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

You have a computer that is running Windows Vista or Windows Server 2008. However, the computer may stop responding (hang) under certain conditions. For example, the computer may stop responding during a storage stress test or under similar conditions. When this issue occurs, you have to restart the computer.

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 Web site:

Note 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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, the computer must run one of the following:

• Windows Vista SP1
• Windows Server 2008

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

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

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately . 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 (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and Windows Vista

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

For all supported Itanium-based versions of Windows Server 2008 and Windows Vista

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

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

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and Windows Vista

Additional files for all supported Itanium-based versions of Windows Server 2008

The following policy is enabled on a Windows Server 2008-based computer or on a Windows Vista SP1-based computer:

When you open the Failover Cluster Management window on this computer to perform the Validate a Configuration task, the validation process fails. Additionally, you receive the following error message:

This problem occurs because Windows Server 2008 and Windows Vista Failover Cluster Validation uses a non-FIPS compliant algorithm. Therefore, the validation fails after the System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing policy is enabled.

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 Web site:

Note 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.Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix on Windows Vista-based computers, you must have Windows Vista SP1 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

You must have Windows Server 2008 or Windows Vista Service Pack 1 installed to apply this hotfix. Apply hotfix 960334 on all computers that have the Failover Cluster Management window installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

The .manifest files and the .mum files that are installed in each environment are listed separately in the Additional file information for Windows Server 2008 and for Windows Vista section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

For all supported 32-bit versions of Windows Server 2008 and of Windows Vista

For all supported 64-bit versions of Windows Server 2008 and of Windows Vista

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

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

For more information about the System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing policy, visit the following Microsoft Web site:

Additional file information for Windows Server 2008 and for Windows Vista

Additional files for all supported 32-bit versions of Windows Server 2008 and of Windows Vista

Additional files for all supported 64-bit versions of Windows Server 2008 and of Windows Vista

Additional files for all supported IA-64-based versions of Windows Server 2008

You try to apply a theme to an ASP.NET 2.0 Web page. If the Web page contains a control that has the ToolboxBitmap attribute defined, you may receive the following error message:

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 Web site:

Note 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

You must have the Microsoft .NET Framework 2.0 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

The .NET Framework 2.0, x86-based versions

The .NET Framework 2.0, Itanium architecture versions

The .NET Framework 2.0, x64-based versions

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

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

Consider the following scenario:

•	You have a print server that is running Windows Server 2008, Windows Vista, Windows Server 2003, or Windows XP.
•	You try to create Point and Print client driver download packages for drivers that have multiple operating system .inf files.

However, the operation fails because the Internet Printer Protocol (IPP) does not support this functionality.

Back to the top

This issue occurs because additional files that are listed for operating systems that differ from the print server’s operating system are not copied to the print server. Therefore, when a client computer connects to a print server, and that client computer is using a different operating system from the print server’s, the version files that are listed in the .inf file are not located on the print server. Therefore, the packaging attempt fails.

Back to the top

To work around this issue, use one of the following methods:

•	Manually copy the missing files to the print server.
•	Use a single operating system .inf file that copies all the necessary files to the print server.

Back to the top

Assume that you connect an external Serial Advanced Technology Attachment (eSATA) device to a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008. However, you do not see a safe removal icon in the notification area. Or, the safe removal tool does not list the eSATA device. Therefore, you cannot safely remove the eSATA device.

This problem occurs if the eSATA device uses the Microsoft Advanced Host Controller Interface (AHCI) driver that is provided by the system. This problem may not occur if you use the driver for the eSATA device that is provided by the vendor of the eSATA device.

Note Safe removal makes sure that all read and write operations are committed before you unplug the eSATA device.

The Microsoft AHCI driver that is built into the system does not support removable hot-plugging functionality for eSATA controller ports.

By default, the following hotfix is disabled after it is applied. You can enable it through a registry entry. To function correctly, this hotfix requires certain BIOS behavior. Therefore, OEMs can use this registry entry together with an updated BIOS. If you enable the hotfix without updating the BIOS, the system will present all devices as removable, and this may cause unexpected issues.

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

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 Web site:

Note 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 on a Windows Vista-based computer, you must have Windows Vista SP1 installed.

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

No prerequisites are required for Windows Server 2008-based computers.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Registry setting information

OEMs can apply the following registry setting to work with their BIOS systems:

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

• 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.
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.0.6000.16xxx	Windows Vista	RTM	GDR
  6.0.6000.20xxx	Windows Vista	RTM	LDR
  6.0.6001.18xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	GDR
  6.0.6001.22xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR

• Service Pack 1 is integrated into Windows Server 2008.
• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. 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 (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

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

For all supported Itanium-based versions of Windows Server 2008

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

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

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported Itanium-based versions of Windows Server 2008

Source: Microsoft Support

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

This article discusses the Firewall application requirements necessary for Toredo to coexist with those firewalls on a Windows operating system-based computer.

In order for client firewalls to coexist with Teredo, the firewalls must follow the guidelines listed below.

 

 

1. The client firewall must allow resolution of teredo.IPv6.microsoft.com.

2. The client firewall must exempt UDP IPv4 traffic to/ from remote UDP port 3544.

        a. Port 3544 allows the client to communicate to the Teredo Server.

3. Client firewalls must support the following ICMPv6 error messages & discovery functions:

        a. ICMPv6 Neighbor Solicitation / Neighbor Advertisement

                1. The codes for these are 135 and 136

        b. ICMPv6 Echo Request/ Reply

                1. The codes for these are 128 and 129

        c. Packet Too Big

                1. The code for this is 2

        d. Parameter Problem

                1. The code for this  is 4

        e. Time Exceeded

                1. The codes for this is 3

        f. Destination Unreachable

                1. The code for this is 1

 

Note:  If the above ICMPv6 messages cannot be specifically allowed, then the exemption of all ICMPv6 messages should be enabled on the firewall

 

4. The client firewall should allow the system to send and receive UDP/IPv4 packets to UDP port 1900 

        a. Port 1900 allows UPnP discovery traffic to flow, and while is not necessary, will improve connectivity rates.

 

To troubleshoot if you are having a Teredo problem, please run the command from a command prompt:

netsh int teredo show state

 

Review the “State field in the Teredo parameters using the command above and do the following:

·         If the Teredo State is offline then follow steps 1, 2 and 3 above

·         If the Teredo State is dormant or qualified, then do step 3 only

 

Note: Perform step 4 to achieve best performance.

 

For more information on Teredo please refer to the following article below

http://www.microsoft.com/technet/network/ipv6/teredo.mspx (http://www.microsoft.com/technet/network/ipv6/teredo.mspx)

 

Note: Windows XP SP1 must have the Advanced Networking Pack for Windows XP (http://www.microsoft.com/downloads/details.aspx?familyid=E88CC382-8CE6-4739-97C0-1A52A6F005E4&displaylang=en) installed

 

 

 

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Consider the following scenario:

• The Network Load Balancing (NLB) feature is enabled on a Windows Server 2008-based computer.
• NLB is configured to run in multicast mode.
• There is a router between the NLB cluster nodes and the client devices.
• The NLB cluster nodes have not recently communicated with any device on the client’s subnet.

In this scenario, clients may experience intermittent connectivity failures when they try to communicate with a server that is part of this NLB cluster. Attempts to connect to the node-specific IP are successful. Outbound connection attempts from any NLB server nodes that use a node-specific IP are also successful.

When you try to respond to a client on a different subnet, the server must first send an ARP request for its default gateway. In multicast mode, this ARP request contains a combination of the unicast Virtual IP of the cluster and the multicast MAC address of the interface. Because some routers are designed or configured not to reply to packets with this mix of unicast and multicast, the server cannot discover the address of the default gateway. Therefore, the server cannot respond to the client’s request.

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 Web site:

Note 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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, the Network Load Balancing feature must be installed on the Windows Server 2008-based computer.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

The .manifest files and the .mum files that are installed in each environment are listed separately in the Additional file information for Windows Server 2008 and for Windows Vista section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

For all supported x86-based versions of Windows Server 2008

For all supported x64-based versions of Windows Server 2008

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

To work around this problem, create a static ARP entry on each NLB node for the gateway. If you cannot do this, use some method for creating an outbound connection to a non-local device from the NLB node to populate the ARP cache. This method must support continuous communication between the devices to prevent the ARP cache entry from timing out.

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

The specific symptoms that you experience depend on the switch or the router and how it reacts to ARP when ARP is using both unicast IP and multicast MAC.

Additionally, a network sniff might be required to confirm the presence of the problem that is described in the Cause section. If the sender MAC address starts with 03-BF, this means that NLB is using the following multicast MAC address:

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Additional files for all supported IA-64-based versions of Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008

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

•	The issues that the hotfix package fixes.
•	The prerequisites for installing the hotfix package.
•	Whether you must restart the computer after you install the hotfix package.
•	Whether the hotfix package is replaced by any other hotfix package.
•	Whether you must make any registry changes.
•	The files that the hotfix package contains.

Back to the top

Issues that the hotfix package fixes

List of issues that are fixed

This hotfix fixes the following issues:

•	954540 (/Feedback.aspx?kbNumber=954540/) The changes in the TOC and PageRef fields do not appear when you compare Word 2007 documents
•	954541 (/Feedback.aspx?kbNumber=954541/) The Ref field is updated incorrectly when you print a Word 2007 document

This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

•	When you compare and merge documents that are written in Chinese characters or in Japanese characters in Word 2007, the text that is marked as deleted and inserted is much larger than the text that is actually changed. For example, if you delete only one character or one word, a large chunk of text around this character or word is marked as deleted. Additionally, the chunk of text is marked as reinserted, except for the character or for the word that is actually deleted. Note The issue occurs for both character-level comparison and word-level comparison. However, this issue does not occur if you delete the word or the character at the end of the sentence.
•	Consider the following scenario. You create and then save a new document from a template on a trusted network share. This template contains Microsoft Visual Basic for Application (VBA) code. Then, you open the document again. In this scenario, you cannot save the document again. Additionally, you receive the following error message: The save failed due to out of memory or disk space.
•	Consider the following scenario. You create and then save a document that contains a table. You delete one row, and you modify the content in the following row. Then, you save the document as a different name. In this scenario, if you compare the revised document to the original document, the result is incorrect.
•	Consider the following scenario. You create a Microsoft Office Word 2003 document, and you apply a new style such as Style1 to some paragraphs that have outline numbering enabled. Then, you change the number format of Style1. To change this number format, you add text before the number in that document. In this scenario, when you use the Compare Documents functionality to compare the revised document to the original document, the comparison document shows the formatting as the formatting in the original document. However, the comparison document should show the formatting as the formatting in the revised document.
•	You create a document that is based on a template that has customized Ribbons. When you open the document, Word 2007 may not display the Ribbon customizations. This issue can occur if the following conditions are true: • The template uses the editing restriction, Filling in forms. Note This issue does not occur if the template is unprotected or if the template uses one of the following editing restrictions: • Comments • No changes (Read only) • Tracked changes • The document is saved in one of the following file formats: • Word 2003 XML Document (*.xml) • Word XML Document (*.xml) • Word Document (*.docx) • Word Macro-Enabled Document (*.docm) Note This issue does not occur if the document is saved in a rich text format (RTF) or in a binary document file format. However, the template is still correctly loaded as a base template.
•	When you add one or more letters at the beginning or at the end of a word, a word-level comparison only marks the inserted letters as an insertion, as if the inserted characters are a separate word. The expected behavior is that the original word should be marked as deleted, and the new word should be marked as an insertion.
•	If you click to clear the White space check box in the Compare Documents dialog box, the closing paragraph mark of an insertion is ignored. The expected behavior is that the closing paragraph mark should be displayed as part of the insertion, and the closing paragraph mark should not be ignored.
•	When you insert or delete a text box in the revised document, and then you compare this document to the original document, there is a revision bar next to the border of the text box. However, there is no revision markup in the text box.
•	If two plain text content controls are grouped, you may experience the following issues when you run the Spelling and Grammar check: • The last word in the first content control is selected together with part of the first word of the second content control. This behavior occurs when the following conditions are true: • There is no space after the last word in the first content control. • The last word of the first content control is proofed in the Spelling and Grammar dialog box. This issue occurs whether the last word of the first content control is spelled correctly. • After the last word of the first content control is proofed, the Spelling and Grammar check is complete. However, misspelled words are not checked in the second content control.

Back to the top

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 this specific problem. 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 Web site:

Note 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

There are no prerequisites for installing this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix package does not replace any other hotfix packages.

Registry information

You do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The Global version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb954576-fullfile-x86-glb.exe	12.0.6320.5000	15,929,040	19-Jun-2008	14:28	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,252,608	19-Jun-2008	18:33	Not Applicable
Wordconv.msp	Not Applicable	6,301,696	19-Jun-2008	18:33	Not Applicable

Word.msp file information

File name	File version	File size	Date	Time	Platform
Msword.olb	12.0.6300.5000	768,024	06-Dec-2007	17:05	Not Applicable
Winword.exe	12.0.6320.5000	349,720	19-Jun-2008	15:00	x86
Wwlib.dll	12.0.6320.5000	17,491,480	19-Jun-2008	15:00	x86

Wordconv.msp file information

File name	File version	File size	Date	Time	Platform
Wordcnv.dll	12.0.6320.5000	4,281,368	19-Jun-2008	22:42	x86
Wordconv.exe	12.0.6300.5000	24,584	13-Dec-2007	01:08	x86

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

Back to the top

You use Remote Desktop Connection (RDC) 6.1 to connect to a Windows-based terminal server from a client computer that is running Windows XP with Service Pack 3 (SP3), Windows Vista with Service Pack 1 (SP1), or Windows Server 2008. You run an application in the Terminal Services session for some time. Eventually, you may experience that some components of the application are not displayed correctly.

Additionally, you may experience the following behavior when this problem occurs:

• If you disconnect from and then reconnect to the terminal server, the problem is resolved.
• If you redraw the components in the application, this problem is not resolved. For example, if you may try to make the components smaller or larger, this problem is not resolved.
• If you capture a screen shot of the Terminal Services session, you see the components are drawn correctly in the screen shot.

This problem does not occur with RDC 6.0 or earlier versions.

To resolve this problem, install the following hotfix on the RDC 6.1-based client computer.

Hotfix information

Windows XP

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 this specific problem.

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, submit a request to 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 Web site:

Note 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 have Windows XP Service Pack 3 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows XP with Service Pack 3, x86-based versions

Windows Vista and Windows Server 2008

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 Web site:

Note 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 on Windows Vista-based computer, you must have Windows Vista SP1 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

No prerequisites are required for Windows Server 2008-based computers.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes
The MANIFEST files (.manifest) and MUM files (.mum) that are installed for each environment are listed separately. 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 (attributes not listed) are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and Windows Vista

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

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

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

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

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and Windows Vista

Additional files for all supported IA-64-based versions of Windows Server 2008

In Windows Vista, you use Windows Fax and Scan to create an account on a fax server. However, the status of every fax that you receive from this server is read, regardless of whether you have read the fax.

This issue occurs if the fax server is running Microsoft Windows Server 2003 or an earlier version of Windows. This issue occurs because the Windows Vista feature that recognizes the status of a fax is not available.

Consider the following scenario:

•	On a computer that is running Windows Vista or Windows Server 2008, an application uses legacy methods to query performance counter values. For example, the application uses the RegQueryValueEx function to perform a global query for performance counter data.
•	Counter data is returned from more than 64 counter sets that are registered by performance counter version 2.0 APIs. For example, the application performs a global query on a system on which more than 64 of these counter sets are registered.

In this scenario, the application may crash.

Back to the top

This problem occurs because of incorrect memory management behavior in the performance counter version 2.0 interface.

Back to the top

Windows Vista 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 this specific problem. 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 Web site:

Note 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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Advapi32.dll	6.0.6000.20836	770,560	17-May-2008	03:29	x86
Regsvc.dll	6.0.6000.20836	106,496	17-May-2008	03:33	x86

Windows Vista with Service Pack 1, x86-based versions

File name	File version	File size	Date	Time	Platform	SP requirement
Advapi32.dll	6.0.6001.22181	798,720	17-May-2008	03:21	x86	SP1
Regsvc.dll	6.0.6001.22181	107,008	17-May-2008	03:26	x86	SP1

Windows Vista, x64-based versions

File name	File version	File size	Date	Time	Platform
Advapi32.dll	6.0.6000.20836	1,032,192	17-May-2008	03:36	x64
Regsvc.dll	6.0.6000.20836	203,776	17-May-2008	03:40	x64

Windows Vista with Service Pack 1, x64-based versions

File name	File version	File size	Date	Time	Platform	SP requirement
Advapi32.dll	6.0.6001.22181	1,062,400	17-May-2008	03:49	x64	SP1
Regsvc.dll	6.0.6001.22181	206,848	17-May-2008	03:55	x64	SP1

Windows Vista with Service Pack 1, Itanium-based versions

File name	File version	File size	Date	Time	Platform
Advapi32.dll	6.0.6001.22181	1,960,448	17-May-2008	03:36	IA-64
Regsvc.dll	6.0.6001.22181	354,816	17-May-2008	03:45	IA-64

Back to the top

Windows Server 2008 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 this specific problem. 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 Web site:

Note 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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008, x86-based versions

File name	File version	File size	Date	Time	Platform	SP requirement
Advapi32.dll	6.0.6001.22181	798,720	17-May-2008	03:21	x86	SP1
Regsvc.dll	6.0.6001.22181	107,008	17-May-2008	03:26	x86	SP1

Windows Server 2008, Itanium-based versions

File name	File version	File size	Date	Time	Platform
Advapi32.dll	6.0.6001.22181	1,960,448	17-May-2008	03:36	IA-64
Regsvc.dll	6.0.6001.22181	354,816	17-May-2008	03:45	IA-64

Windows Server 2008, x64-based versions

File name	File version	File size	Date	Time	Platform	SP requirement
Advapi32.dll	6.0.6001.22181	1,062,400	17-May-2008	03:49	x64	SP1
Regsvc.dll	6.0.6001.22181	206,848	17-May-2008	03:55	x64	SP1

Back to the top

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

Back to the top

Performance counter version 2.0 APIs provide a new architecture for collecting counter data in Windows Vista and in Windows Server 2008. For more information about these performance counter APIs, visit the following Microsoft Web site:

For more information about how an application can provide performance counter data by using the performance counter version 2.0 APIs, visit the following Microsoft Web site:

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

Back to the top

Consider the following scenario:

• You use Microsoft iSCSI Initiator to connect to an iSCSI target from a computer that is running Windows Vista or Windows Server 2008.
• An iSCSI Protocol Data Unit (PDU) is rejected by the target for one of the reasons that are outlined in section 10.17.1 of iSCSI Specification Request for Comment (RFC) 3720.

In this scenario, iSCSI Initiator should resend the PDU that was rejected by the iSCSI target. However, iSCSI Initiator may be unable to communicate with the iSCSI target for several minutes.

Specifically, iSCSI Initiator cannot communicate with the target for a period of five times the Disk Timeout value that is specified in the following registry entry:

After a period of five times the Disk Timeout Value elapses, iSCSI Initiator performs session recovery, and then the iSCSI session is dropped and reestablished. Eventually, iSCSI Initiator may be able to communicate with the iSCSI target again.

This problem may occur because of a defect in how iSCSI Initiator determines how many times it has re-sent a rejected PDU. This defect makes the iSCSI target unresponsive. Therefore, iSCSI Initiator performs LUN resets in order to communicate with the iSCSI target. It does this instead of immediately retrying the rejected PDU.

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

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 Web site:

Note 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 on a Windows Vista-based computer, you must have Windows Vista Service Pack 1 installed.

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

No prerequisites are required for Windows Server 2008-based computers.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

• 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.
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.0.6000.16xxx	Windows Vista	RTM	GDR
  6.0.6000.20xxx	Windows Vista	RTM	LDR
  6.0.6001.18xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	GDR
  6.0.6001.22xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR

• Service Pack 1 is integrated into Windows Server 2008.
• The MANIFEST files (.manifest) and MUM files (.mum) that are installed for each environment are listed separately. 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 (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

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

For all supported Itanium-based versions of Windows Server 2008

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

For more information about iSCSI Specification RFC 3720, visit the following Internet Engineering Task Force (IETF) Web site:

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

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

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported Itanium-based versions of Windows Server 2008

You install a High Definition (HD) Audio function driver on a Windows Vista-based or Windows Server 2008-based computer. The driver can expose multiple non-Pulse Code Modulation (PCM) audio formats and some PCM or non-PCM audio formats that are encrypted.

However, you may notice that the audio application cannot play the following formats:

• The latest non-PCM formats, such as Dolby True HD
• Both PCM and non-PCM audio formats that are encrypted

The audio formats that are mentioned in the Symptoms section are expressed in a KSDATARANGE_AUDIO structure with a unique SubFormat GUID. The GUID comes from the WAVEFORMATEXTENSIBLE structure.

When the audio application selects a specific audio format to transfer stream data, the audio miniport driver should see the corresponding KSDATAFORMAT structure that contains the specific GUID and other parameters in the miniport’s handlers. For example, the audio miniport driver should see the NewStream() parameter. When the audio driver encounters these parameters, the driver takes some action, based on the specific GUID.

However, in Windows Vista-based or Windows Server 2008-based computers, the system audio stack (Portcls.sys) may pass a KSDATAFORMAT instance with a different GUID to the WaveRT miniport’s NewStream() parameter.

For example, there can be two data ranges that have the same sample rates, but the data ranges have a different number of channels. In this case, the system may detect one data range that is the first data range that matches the sample rate and the sample bit in the array. However, the channel number is incorrect.

Therefore, the audio driver does not obtain the correct data format. Because the driver does not obtain the correct data format, the audio driver cannot function correctly with regard to the audio format that was selected in the application, and the function fails.

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 Web site:

Note 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

No prerequisites are required to install this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

• The files that apply to a specific product, milestone (RTM, SPn) can be identified by examining the file version numbers as shown in the following table:
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.0.600 0 . 20 xxx	Windows	RTM	LDR
  6.0.600 1 . 22 xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR

• Service Pack 1 is integrated into Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
• The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately. 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 (attributes not listed) are signed with a Microsoft digital signature.

For all supported 32-bit versions of Windows Server 2008 and of Windows Vista

For all supported 64-bit versions of Windows Server 2008 and of Windows Vista

For all supported Itanium-based versions of Windows Server 2008

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

For more information about KSDATARANGE_AUDIO, visit the following Web site:

For more information about WAVEFORMATEXTENSIBLE, visit the following Web site:

For more information about KSDATAFORMAT, visit the following Web site:

For more information about WaveRT, visit the following Web sites:

Additional file information for Windows Server 2008 and for Windows Vista

Additional files for all supported 32-bit versions of Windows Server 2008 and of Windows Vista

Additional files for all supported 64-bit versions of Windows Server 2008 and of Windows Vista

Additional files for all supported Itanium-based versions of Windows Server 2008