When you redirect the Documents folder on a Windows Vista-based computer to a network share, the folder name unexpectedly changes back to Documents. You expect the folder name to be the user name.

This behavior may create many Documents folders on the network share. If you try to rename one Documents folder, all the other Documents folders change to that name.

Consider the following scenario:

• On a Windows Vista-based computer, you redirect the Documents folder to a shared folder, and you make the Documents folder available offline.
• The computer has network connections. However, the computer cannot reach the shared folder in the current network environment.

In this scenario, the system is frequently unresponsive for 30 seconds. This behavior occurs regardless of whether you are accessing the files in the shared folder that is unreachable. For example, the system may become unresponsive when you try to open Windows Explorer or other applications.

On a Windows Vista-based computer, you open a remote shared folder in Windows Explorer that uses the Details view and for which the Preview Pane layout is enabled. When you try to open a Microsoft Office Excel 2007 Workbook from the remote shared folder, you may receive the following message:
File in Use file_name is locked for editing by user_name
However, in this case, no other user is using this document.

Note: This problem also occurs when you try to open other shared 2007 Office documents. Different users cannot exclusively edit such shared documents.

If you create a redirected folder, such as C:\NewPicturesFolder, and then set the new folder as the Pictures target folder by using Windows Explorer, when you start Windows Live Photo Gallery it does not recognize or open the new folder.

In an Active Directory directory service domain environment, you configure the Folder Redirection policy setting for Windows Vista-based client computers. In this situation, every time that this policy setting is applied, all the contents are pinned and are filled in the redirected folder. However, you expect only the updated contents to be pinned and to be filled when the Folder Redirection policy setting is applied.

This behavior results in lots of unnecessary disk writing operations. For example, the search index has to be updated both for the updated contents and for the original contents in the redirected folder. Also, this problem makes the network performance slow when the Folder Redirection policy setting is applied.

Note: The Folder Redirection policy setting will be applied if one the following conditions is true:

• The Folder Redirection policy setting is changed.
• You enable the Folder Redirection policy processing policy setting together with the Process even if the Group Policy objects have not changed option.

Consider the following scenario. On a Windows Vista-based computer, you manually configure the redirection feature for the Documents folder and for the Desktop folder. Or, you use Group Policy to configure the redirection feature for these two folders. The target folder names for these two folders are identical. In this scenario, the link for the Documents folder may be redirected to the Desktop folder. Additionally, when you check the Links folder, you find that the target folder for the Documents folder shortcut is the Desktop folder.

When you try to connect to a Web folder by using a network basic input/output system (NetBIOS) name on a computer that is running Windows Vista, you are prompted for the user name and the password.

This issue occurs even though the “Automatic logon with current user name and password” security option is set for the fully qualified domain name (FQDN) of the Web folder in the “Trusted Sites” zone and in the “Local intranet” zone.

For example, this issue occurs when you use one of the following NetBIOS names to connect to the Web folder:

• http://server_name/webdav
• http://server_name.company_name.com/webdav

Note You do not experience this issue in Microsoft Windows XP.

In Windows Vista, a folder on the All Programs menu does not open as expected.

You successfully install the Adobe Encore DVD 2.0 program files on a Windows Vista-based computer. However, the contents of the Library folder for Adobe Encore DVD 2.0 are not available. Additionally, the Library folder that contains the content files does not exist in the following folder:

Extract drive:\Extract folder\Program Files\Adobe\Adobe Encore DVD 2.0

Note: The Extract drive:\Extract folder placeholders represent the location that you specify when you install Adobe Encore DVD 2.0. By default, the Library folder is in the following folder:

%SystemDrive%\Program Files\Adobe\Adobe Encore DVD 2.0

An event that resembles the following is logged in the Application log:

Event Type: Error
Event Source: MsiInstaller
Event Category: Category
Event ID: 10005
Date: Date
Time: Time
User: User
Computer: ComputerName
Description: Product: Adobe Encore DVD FC -- Installer is designed to run on Windows XP SP2 or higher

If you enable Windows Installer logging on the computer, an event that resembles the following is logged in the Windows Installer log file:

Windows Installer installed the product.
Product Name: Adobe Encore DVD FC.
Product Version: 2.0.
Product Language: 1033.
Installation success or error status: 1603. 

On a Windows Vista-based computer, the Folder versions list is blank, or you receive the following message:

There are no previous versions available.

This issue occurs when you access the properties of a file or of a folder, and then you click the Previous Versions tab.

Additionally, if you use the command vssadmin list shadows at a command prompt, the volume that hosts the file or the folder will have a list of shadow copies that are associated with the volume.