On a computer that is running a Japanese version of Windows Vista, the items in the Recent Items folder on the Start menu may be unexpectedly listed in English.

On a Windows Vista-based computer, you click the Resource Monitor button. Then, the Performance Monitor (Perfmon.exe) process may continuously start and stop. Additionally, Windows Vista may stop responding.

Note: You click the Resource Monitor button to display the utilization details for the CPU, for memory, for the disk, and for the network.
Steps to reproduce the problem

• You log on to a Windows Vista-based computer by using an account that has administrator credentials.
• You disable the User Account Control (UAC) feature.
• You log on to the Windows Vista-based computer on which UAC has been disabled. Additionally, you use an account that does not have administrator credentials.
• On the Performance tab of the Windows Task Manager dialog box, you click the Resource Monitor button.

You start or run a network-capable program in Windows Vista. Then, the program stops unexpectedly (crashes) in either of the following cases:

• When the program tries to read valid data from a remote storage medium.
• When the program tries to write valid data to a remote storage medium.

Additionally, you receive an error message that resembles the following:

Program_name has caused an error and must be closed.
We apologize for the inconvenience. If you were in the middle of something, the information you were working on might be lost.
Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Program_name. We will treat this report as confidential and anonymous.
To see what data this error report contains, click here.

After you wake a Windows Vista-based computer from sleep or from hibernation, you experience the following symptoms:

• The network icon in the notification area at the far right of the taskbar is not updated to show the connectivity status of the computer.
• If you connect a network cable to the computer or if you connect to a wireless network, the network icon in the notification area incorrectly shows the connectivity status as disconnected.
• If you move the pointer over the network icon in the notification area, the Currently connected to ScreenTip does not appear as expected.
• If you click the network icon in the notification area, the Currently connected to ScreenTip does not appear as expected.

Note: In this case, the expected ScreenTip should contain a Connect to a network link and a Network and Sharing Center link.
You experience these symptoms even though you can successfully connect both to wired networks and to wireless networks.

You connect a USB keyboard to a Windows Vista-based computer. Then, you view the devices on the computer in Device Manager. When you view the Driver tab of the parent USB host controller, you notice that you do not have an option to disable the device. The Disable button on the Driver tab of the parent USB host controller appears dimmed, and it is not available.

If you disconnect the USB keyboard from the computer, and then you update the view in Device Manager, the Disable button is available.

Consider the following scenario:

• To prepare a computer for imaging and deployment to multiple computers, you use the Sysprep tool (Sysprep.exe) from one of the following language versions of Windows Vista:
  • Norwegian
  • Italian
  • French
• When you run Sysprep, you leave the default Shutdown option selected in the Shutdown Options list. Then, you click OK to prepare the image.

In this scenario, the computer does not shut down as expected after Sysprep.exe finishes preparing the Windows Vista image. Instead, the computer restarts unexpectedly in audit mode.

You experience this problem even though the Enter System Out-of-Box Experience (OOBE) option is selected in the System Cleanup Action list.

Note: You do not experience this problem if you use the English version of Sysprep.

After you enable the Credential Roaming feature for Windows Vista-based client computers in a domain, the size of the Ntds.dit file on the domain controller grows continually larger. Additionally, when Active Directory database changes are replicated to other domain controllers in the domain, the size of the Ntds.dit files on the other domain controllers also grows larger. Therefore, this growth eventually occurs on all domain controllers in the domain.

Seems like something that should have been officially released before Vista, or at least at the same time. At this rate, by the time they go gold, this product won’t be needed. (more…)

Hardware requirements just keep going up… (more…)

The updated version will include support for file sync on Windows Mobile 6 devices. (more…)