Default registry settings in Windows XP

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

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)

Back to the top

To manually change these settings to the default Windows Vista values, follow these steps:

1.	Click Start, type regedit in the Start Search box, and then click regedit in the Programs list. If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
2.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services W32Time Config
3.	Right-click LargePhaseOffset, and then click Modify.
4.	In the Value data box, type 02faf080, and then click OK.
5.	Right-click SpikeWatchPeriod, and then click Modify.
6.	In the Value data box, type 00000384, and then click OK.
7.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services W32Time TimeProviders NtpClient
8.	Right-click EventLogFlags, and then click Modify.
9.	In the Value data box, type 1, and then click OK.
10.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services W32Time TimeProviders NtpServer
11.	Right-click Enabled, and then click Modify.
12.	In the Value data box, type 0, and then click OK.
13.	Exit Registry Editor, and then restart the computer.

Back to the top

Back to the top

Back to the top

Note This problem also occurs when you create a new Storage Group, and then you try to mount the new database.

Back to the top

1. Click Start, click Run, type cmd, and then click OK.
2. At the command prompt, type the following command, and then press ENTER:
   cluster res Storage Group/Database (Exchange_CMS_Name) /priv

   For example, if Storage Group 4 is the nonworking Storage Group and if ExchangeCCR is the name of the clustered mailbox server (CMS), type the following command:

   cluster res Storage Group 4/Database4 (ExchangeCCR) /priv

   Note This command gives you information for the affected Storage Group. Note whether there is value information that is populated for the DatabaseGuid, StorageGroupGuid, and Network Name properties.

3. Compare the information for a working Storage Group with the information for the nonworking Storage Group.

   The following is sample information for a working Storage Group and for a nonworking Storage Group.

   Working Storage Group

   Listing private properties for 'Storage Group 10/Database10 (ExchangeCCR)': T  Resource                    Name                              Value-- --------------------------- --------------------------------- -----------------------S  Storage Group 10/Database10 (ExchangeCCR) DatabaseGuid         9c7d918b-8916-40c3-954f-2297ff7948faS  Storage Group 10/Database10 (ExchangeCCR) StorageGroupGuid     1b9333f7-5582-45c0-8b73-efc28a945604S  Storage Group 10/Database10 (ExchangeCCR) NetworkName          ExchangeCCRS  Storage Group 10/Database10 (ExchangeCCR) LatestOfflineTime    0S  Storage Group 10/Database10 (ExchangeCCR) LastMountedOnServer  Node Name

   Nonworking Storage Group

   Listing private properties for 'Storage Group 4/Database4 (ExchangeCCR1)': T  Resource                  Name                            Value-- ------------------------- ------------------------------- -----------------------S  Storage Group 4/Database4 (ExchangeCCR1) DatabaseGuid                   S  Storage Group 4/Database4 (ExchangeCCR1) StorageGroupGuid               S  Storage Group 4/Database4 (ExchangeCCR1) NetworkName 

   Note In the nonworking Storage Group example, there is no value information for the DatabaseGuid, StorageGroupGuid, and NetworkName properties. If you try to mount the database of this nonworking Storage Group, the database is not mounted, and you receive the error messages that are mentioned in the Symptoms section. This problem may occur when you use the Cluster Administrator instead the command shell to re-create instances multiple times.

4. Register the value information for the DatabaseGuid, StorageGroupGuid, and Network Name properties of the nonworking Storage Group. To do this, follow these steps:
   1. Click Start, click Run, type cmd, and then click OK.
   2. At the command prompt, type the following command to register the value for the DatabaseGuid property, and then press ENTER:
      cluster res Storage Group/Database (Exchange_CMS_Name) /priv Databaseguid=guid

      For example, assume that Storage Group 4 is the nonworking Storage Group, ExchangeCCR is the name of the clustered mailbox server (CMS), and the DatabaseGuid property value is 20e668c6-e4c6-4511-8c50-ca1f9805823c. In this scenario, type the following command:

      cluster res Storage Group 4/Database4 (ExchangeCCR) /priv DatabaseGuid=20e668c6-e4c6-4511-8c50-ca1f9805823c
   3. At the command prompt, type the following command to register the value for the StorageGroupGuid property, and then press ENTER:
      cluster res Storage Group/Database (Exchange_CMS_Name) /priv StorageGroupGuid=guid

      For example, assume that Storage Group 4 is the nonworking Storage Group, ExchangeCCR is the name of the clustered mailbox server (CMS), and the StorageGroupGuid property value is f0cc8edb-83a3-4397-8ba9-e52dfd4ed9aa. In this scenario, type the following command:

      cluster res Storage Group 4/Database4 (ExchangeCCR) /priv StorageGroupGuid=f0cc8edb-83a3-4397-8ba9-e52dfd4ed9aa
   4. At the command prompt, type the following command to register the value for the Network Name property, and then press ENTER:
      cluster res Storage Group/Database (Exchange_CMS_Name) /priv NetworkName=value

      For example, assume that Storage Group 4 is the nonworking Storage Group, ExchangeCCR is the name of the clustered mailbox server (CMS), and the NetworkName property value is ExchangeCCR. In this scenario, type the following command:

      cluster res Storage Group 4/Database4 (ExchangeCCR) /priv NetworkName=ExchangeCCR
   5. At the command prompt, type exit, and then press ENTER.

   Note To determine the values for DatabaseGuid and StorageGroupGuid properties, use the LDP GUI tool (LDP.exe).

5. Replicate the domain controllers. After the domain controllers are replicated, the previously nonworking Storage Group database can be mounted.

Back to the top

For more information about the LDP GUI tool, visit the following Microsoft Web site:

Back to the top

Back to the top

Back to the top

1.	Restart the computer. Typically, when the computer restarts, Windows Vista tries to detect the problem. Then, Windows Vista tries to complete the installation of the component. Or, Windows Vista tries to roll back to the system state that existed before the component was installed. If this step is successful, go to step 4. If this step is not successful, go to step 2.
2.	Use the Startup Repair tool.For more information about how to use the Startup Repair tool, see the Startup Repair: frequently asked questions Help topic in Windows Vista. To do this, visit the following Microsoft Web site: http://windowshelp.microsoft.com/Windows/en-US/Help/5c59f8c1-b0d1-4f1a-af55-74f3922f3f351033.mspx (http://windowshelp.microsoft.com/Windows/en-US/Help/5c59f8c1-b0d1-4f1a-af55-74f3922f3f351033.mspx) If this step is successful, go to step 4. If this step is not successful, go to step 3.
3.	Use the System Repair tool to restore the computer to an earlier, valid restore point. For more information about how to use the System Restore tool in Windows Vista, click the following article number to view the article in the Microsoft Knowledge Base: 936212 (/Feedback.aspx?kbNumber=936212/) How to repair the operating system and how to restore the operating system configuration to an earlier point in time in Windows Vista
4.	Start Windows Update, and then install one update. By doing this, you confirm that Windows Update is working as expected. You also clear any temporary Setup files from previous installations. Temporary Setup files may have caused this issue to occur. To start Windows Update and install one update, follow these steps: a. Click Start , point to All Programs, and then click Windows Update. b. Click to clear the check boxes for all the updates except one. Leave one check box selected. c. Click Install Updates. d. When the update is installed, restart the computer.

If you cannot start the computer after you follow these steps, search the Microsoft Knowledge Base for more information. Or, if you experience symptoms that differ from those that are described in the Symptoms section after you follow these steps, search the Microsoft Knowledge Base for more information. To search the Microsoft Knowledge Base, visit the following Microsoft Web site:

Then, type the text of the error message that you receive, or type a description of the problem in the Search field.

Back to the top

Methods that you can use to verify that the problem is resolved

After Windows Vista consistently restarts without any errors, you can use one of the following methods to verify that the problem is resolved.

Back to the top

Method 1: Try to turn on optional feature

To turn on optional feature in Windows Vista, follow these steps:

1.	Click Start , type programs and features in the Start Search box, and then press ENTER.
2.	Click Turn Windows features on or off.
3.	If you are prompted for an administrator password or for confirmation, type the password, or click Allow.
4.	Click to select the check box next to the feature, and then click OK.

Back to the top

Method 2: Try to install an update or a hotfix

To install a Windows update or a hotfix, visit the following Microsoft Web site:

This site will install all the updates and hotfixes that are required by Windows Vista. This includes the update or the hotfix that was being installed when the interruption occurred.

Method 3: Try to install a Windows Vista language pack

To install a Windows Vista language pack, follow these steps:

1.	Click Start , type Regional and Language Options in the Start Search box, and then press ENTER.
2.	Click the Keyboards and Languages tab.
3.	Under Display Language, click Install/uninstall languages, and then follow the instructions on the screen.
4.	If you are prompted for an administrator password or for confirmation, type the password, or click Continue.

Back to the top

In these scenarios, you cannot see the logon screen. Therefore, you cannot log on to the computer.

Back to the top

Back to the top

Back to the top

Back to the top

For more information about how to set up multiple monitors, visit the following Microsoft Web page:

Back to the top

Back to the top

Back to the top

For information about how to contact Sony, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:

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

Back to the top

Back to the top

Note This problem has been verified in the Japanese, Chinese (Taiwan), and Chinese (PRC) versions of Windows Vista. The problem does not occur in the Korean version of Windows Vista.

Back to the top

Back to the top

The following XML output shows how you can configure the Windows Setup UI language to display Chinese (PRC):

<SetupUILanguage>       <UILanguage>zh-cn</UILanguage></SetupUILanguage>

Note The Windows OEM Preinstallation Kit (OPK) documentation will be updated in Windows Vista Service Pack 1 (SP1) to indicate that this setting is mandatory.

Back to the top

Back to the top

Issues that this hotfix package fixes

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

•	When you open a shared Excel 2007 workbook in multiple Excel 2007 instances, the records in the workbook may lose data integrity.
•	You export a spreadsheet from a SharePoint site that does not have a root site. Then, you open the spreadsheet in Excel 2007, and you try to synchronize the list that is in the spreadsheet. However, you receive the following error message: A connection to the SharePoint site cannot be established. To synchronize or refresh your list, you must be able to connect to the SharePoint site.
•	Consider the following scenario: • In Excel 2007, you open a workbook that has a link to another workbook. For example, workbook A contains a link to workbook B. • You click the link in workbook A to open workbook B. In this scenario, when you try to save workbook A, Excel 2007 crashes.
•	On a client computer, the default path for saving the files is set to the path of a network share instead of the path of the My Documents folder. In Excel 2007, when you try to save a workbook in the PDF (.pdf) format or in the XPS Document (.xps) format, the default path for saving the workbook is unexpectedly changed to the path of the My Documents folder. However, if you try to save the workbook in other formats, the default path is the path of the network share expectedly.
•	In Excel 2007, when you run a macro that sets the Application.ScreenUpdating property to False before the macro calls the ActiveWindow.SelectedSheets.PrintPreview, the Print Preview tab will be missing.
•	In Excel 2007, you publish a workbook in the PDF format or in the XPS Document format. Then, when you use Microsoft Visual Basic for Applications (VBA) code to select a worksheet in the workbook, Excel 2007 crashes.
•	In Excel 2007, you try to use the ExportAsFixedFormat method to publish a protected chart in a workbook to either the PDF format or in the XPS format. Then, you receive the following error message: Run-time error ‘1004′; Application defined or object defined error is shown and No PDF is created However, you can use the ExportAsFixedFormat method to publish a non-protected chart in the workbook to either the PDF format or to the XPS Document format.

Back to the top

Hotfix information

A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

To apply this hotfix package, you must have Excel 2007 installed.

Restart information

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Registry information

To use one of the hotfixes in this package, 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 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.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb951996-fullfile-x86-glb.exe	12.0.6300.5000	20,598,544	25-Apr-2008	15:42	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Excel.msp	Not Applicable	11,931,648	25-Apr-2008	20:16	Not Applicable
Xlconv.msp	Not Applicable	11,759,616	25-Apr-2008	20:16	Not Applicable

After the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

Contents of the Excel.msp file

Contents of the Xlconv.msp file

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

Back to the top

Back to the top

This article contains information about the folders that may have to be excluded from antivirus scanning.

Back to the top

Folders that may have to be excluded from antivirus scanning for Windows SharePoint Services 3.0

You may have to configure the antivirus software to exclude the following folders and subfolders from antivirus scanning.

Note The Drive placeholder represents the drive letter in which you have installed Windows SharePoint Services 3.0 or SharePoint Server 2007.Typically, this drive letter is C.

•	Drive: Program Files Common Files Microsoft Shared Web Service Extensions If you do not want to exclude the whole Web Services Extensions folder from antivirus scanning, you can exclude only the following two folders: • Drive: Program Files Common Files Microsoft Shared Web Server Extensions 12 Logs • Drive: Program Files Common Files Microsoft Shared Web Server Extensions 12 Data Applications Note The Applications folder must be excluded only if the computer is running the Windows SharePoint Services Search service. If the folder that contains the index file is located in some other location, you must also exclude that folder.
•	Drive: Windows Microsoft.NET Framework v2.0.50727 Temporary ASP.NET Files
•	Drive: Documents and Settings All Users Application Data Microsoft SharePoint Config
•	Drive: Windows Temp WebTempDir Note The WebTempDir folder is a replacement for the FrontPageTempDir folder.
•	Drive: WINDOWS system32 LogFiles Note If you use a specific account for SharePoint services or application pools identities, you may also have to exclude the following folders: • Drive: Documents and Settings <ServiceAccount> Local Settings Application Data • Drive: Documents and Settings <ServiceAccount> Local Settings Temp

Back to the top

Folders that may have to be excluded from antivirus scanning for SharePoint Server 2007

You may have to configure the antivirus software to exclude the Drive: Program Files Microsoft Office Servers folder from antivirus scanning for SharePoint Server 2007. If you do not want to exclude the whole Microsoft Office Server folder from antivirus scanning, you can exclude only the following folders:

•	Drive: Program Files Microsoft Office Servers 12.0 Data. (This folder is used for the indexing process.)
•	Drive: Program Files Microsoft Office Servers 12.0 Logs
•	Drive: Program Files Office SharePoint Server Bin

Note When you install SharePoint Server 2007 or when you apply a hotfix to an existing installation of SharePoint Server 2007, you may have to disable the real-time option of the antivirus program. Or, you may have to exclude the Drive: Windows Temp folder from antivirus scanning if it is required.

Back to the top

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

Back to the top

• If you do not have an SMTP connector that includes the required address space type.
• If you have an address space that is scoped to the whole Exchange organization in a custom connector, and the custom connector is configured on a computer that is running Exchange 2000 Server or an Exchange Server 2003.

Back to the top

1. Create a new Send connector on the Exchange Server 2007 computer. Make sure that this connector includes the required custom address space type and that the connector points to a smart host. For more information about how to create a Send connector in Exchange Server 2007, visit the following Microsoft Web site:
   http://technet.microsoft.com/en-us/library/aa998814.aspx (http://technet.microsoft.com/en-us/library/aa998814.aspx)
2. Restart the Microsoft Exchange Information Store service in the Services snap-in. This updates the registry entry on the client.
3. Restart Outlook.
4. Send e-mail to the custom address.

Back to the top

This list in the registry is refreshed every time that Outlook starts a MAPI session in cached mode. This list is stored in the 01026687 registry entry under the following registry subkey:

Back to the top

For example, in the Run box, you type the universal naming convention (UNC) path of the share, such as ServerName ShareName. When you do this, it takes the Windows Explorer more than 10 seconds to open the share.

This issue occurs if the firewall of the server on which the share resides blocks traffic on port 80.

Back to the top

After you enter the share name in the Run box, an additional period (.) is appended to the server name. This behavior results in requests for the path ServerName .*. Because this path is an invalid network path for the server message block (SMB), the WebClient service tries to connect to the server through TCP port 80. If the firewall is enabled on the server, and the TCP port 80 is blocked, no response is sent by the server. Therefore, the client waits for the time out to expire. This results in a delay of 10 to 20 seconds.

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.

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, you must have Windows Server 2008 or Windows Vista SP1 installed on the computer.

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 Server 2008 and Windows Vista note

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

Back to the top

Additional file information for Windows Server 2008

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

Back to the top

• You map a local drive to a UNC path to share the files on the local drive with other users.
• In a Microsoft Office Word 2007 document, you insert a hyperlink that links to a file on the mapped local drive.

  Note The hyperlink resolves to file:/// <UNC path> <file name> as expected.

In this scenario, after you save and then reopen the document, the hyperlink resolves to file:/// <local drive letter>: <file name> unexpectedly.

When this problem occurs, it is impossible for this file to be shared with other users if they do not map the same local drive to the same UNC path.

To resolve this problem, install the Word 2007 hotfix package that is dated February 24, 2009. Then, set the SaveAbsolutePath4MappedDrive registry entry to enable the hotfix. To do this, follow these steps:

1. Install the Word 2007 hotfix package that is dated February 24, 2009.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
   962872  (/Feedback.aspx?kbNumber=962872/ ) Description of the Word 2007 hotfix package (Word.msp, Wordconv.msp): February 24, 2009
2. Set the SaveAbsolutePath4MappedDrive registry entry. To do this, follow these steps:
   1. Start Registry Editor.
      • In Windows Vista, click Start
        Collapse this imageExpand this image

        

        , type regedit in the Start Search box, and then press ENTER.

        Collapse this imageExpand this image

        

        If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.

      • In Windows XP, click Start, click Run, type regedit in the Open box, and then click OK.
   2. Locate and then select the following registry subkey:
      HKEY_CURRENT_USER Software Microsoft Office 12.0 Word Options
   3. On the Edit menu, point to New, and then click DWORD Value.
   4. Type SaveAbsolutePath4MappedDrive, and then press ENTER:
   5. Right-click SaveAbsolutePath4MappedDrive, and then click Modify.
   6. In the Value data box, type 1, and then click OK.
   7. On the File menu, click Exit to exit Registry Editor.

This problem does not occur if you install Windows Vista on both partitions.

Back to the top

Back to the top

Method 1: Use the System Properties dialog box

To use the System Properties dialog box to configure Windows Vista as the default operating system, follow these steps:

1.	Click Start, right-click Computer, and then click Properties.
2.	Under Computer name, domain, and workgroup settings, click Change settings. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
3.	In the System Properties dialog box, click the Advanced tab.
4.	Under Startup and Recovery, click Settings.
5.	Under System Startup, click Microsoft Windows Vista in the Default operating system drop-down list.
6.	Set the value of the Time to display list of operating systems box to 0, and then click OK.
7.	Click OK to close the System Properties dialog box.
8.	Close all the active windows, and then restart the computer.

Back to the top

Method 2: Use the Boot Configuration Data Editor

To prevent the operating system selection menu from appearing when you start the computer, you can use the Boot Configuration Data Editor (Bcdedit.exe) to remove the Windows XP startup option. To do this, follow these steps:

1.	Click Start, type cmd in the Start Search box, and then click Command Prompt in the application list.
2.	At the command prompt, type the following command, and then press ENTER: bcdedit /enum all Note This command displays the GUIDs of the installed operating systems. Note the GUID for the Windows XP operating system.
3.	At the command prompt, type the following command, and then press ENTER: bcdedit /delete ID For example, the bcdedit /delete {802d5e32-0784-11da-bd33-000476eba25f} command deletes the entry with ID {802d5e32-0784-11da-bd33-000476eba25f}. Note The ID placeholder specifies the GUID of the startup option for the operating system that you want to delete. If you do not specify the ID, the startup option for the current operating system will be deleted. If you specify a well-known GUID, you must force the deletion by using the /f switch. For example, type the following command: bcdedit /delete {default} /f
4.	Close the Command Prompt window.

Back to the top

The Bcdedit.exe file is in the Windows System32 folder on the Windows Vista partition.

In BIOS-based operating systems before Windows Vista, these parameters were in the Boot.ini file. In operating systems that were based on the Extensible Firmware Interface before Windows Vista, these parameters were in the nonvolatile RAM (NVRAM) entries.

For more information about the Boot Configuration Data Editor, visit the following Microsoft Web site:

Back to the top

This problem occurs if the document was created by right-clicking the desktop, pointing to New, and then clicking WordPad Document. When you do this is Windows XP, the WordPad document uses the .doc file name extension.

In this scenario, the Terminal Services session stops responding during the waiting for user profile service process. To continue, the terminal server must be restarted.

Back to the top

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

To apply this hotfix on the terminal server, you must have Windows Server 2008 or Windows Vista Service Pack 1 (SP1) installed.

Restart requirement

You must 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 Server 2008 and Windows Vista SP1, x86-based versions

Windows Server 2008 and Windows Vista SP1, x64-based versions

Windows Server 2008, Itanium-based versions

Back to the top

Back to the top

Back to the top

In this scenario, incorrect methods are called.

For example, consider the following scenario:

•	You have a 64-bit application that uses a 64-bit version of common language runtime (CLR).
•	The application has two managed P/Invoke functions that have the same signature. The signature points to a single native method.
•	The two P/Invoke functions rely on the LCIDConversionAttribute class for localization support.
•	You run the application.

In this scenario, you may receive an error message that resembles the following:

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Vista or .NET Framework 2.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have one of the following installed to apply this hotfix:

•	Windows Vista Service Pack 1
•	The .NET Framework 2.0 Service Pack 1

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, 32-bit versions, on a computer that is not running Windows Vista

The .NET Framework 2.0, Itanium-based versions, on a computer that is not running Windows Vista

The .NET Framework 2.0, 64-bit versions, on a computer that is not running Windows Vista

The .NET Framework 2.0 on a computer that is running a 32-bit version of Windows Vista with Service Pack 1

The .NET Framework 2.0 on a computer that is running a 64-bit version of Windows Vista with Service Pack 1

Back to the top

Back to the top

For more information about the lcid attribute, visit the following MSDN 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

This issue occurs if the following conditions are true:

• The time zone on the computer is set to Jerusalem.
• The Automatically adjust clock for Daylight Saving Time option is selected.

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.

Back to the top

Prerequisites

To apply this hotfix, you must have Windows Server 2008 installed on the computer.

Back to the top

Restart requirement

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

Back to the top

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Back to the top

Registry information

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

Back to the top

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 note

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 important 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

For all supported x64-based versions of Windows Server 2008

For all supported Itanium-based versions of Windows Server 2008

Back to the top

Back to the top

Additional file information for Windows Vista and Windows Server 2008

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

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

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

Back to the top

The message suggests that the computer is using an 802.11g wireless network adapter instead of an 802.11n wireless network adapter.

Back to the top

Back to the top

Back to the top