On a Windows Vista based computer that runs Symantec AntiVirus 10.2 client, you enable EFS for documents on the Desktop or in the Documents folder. After you reboot the computer and log on again, the encrypted files cannot be decrypted.

The problem does not occur when folders are encrypted in other locations.

Also, when Symantec AntiVirus is uninstalled the problem goes away.

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. You try to upgrade a Windows XP-based computer to Windows Vista. When you run the Windows Vista Setup program, the upgrade option is disabled in the Install Windows window. Additionally, the Install Windows window displays the following text:

Upgrade has been disabled.
- Your Windows configuration cannot be upgraded.

The following message is logged in the Setupact.log file:

Date Time, Info MIG Expanding raw path D:\Documents and Settings
Date Time, Info MIG %ProfilesDirectory% (D:\Documents and Settings) is not on drive C
Date Time, Info [0x080755] MIG DoComplianceChecks: CheckUnsupportedConfig not satisfied (- Your Windows configuration cannot be upgraded.)
Date Time, Info MIG pCheckForPendingRunOnce: found 0 values
Date Time, Info MIG pCheckForPendingFileRename: PendingFileRenameOperations not found
Date Time, Info MIG DoExternalComplianceChecks: calling ntdsupg.dll [DsUpgradeCompatibilityCheck]
Date Time, Info MIG DoExternalComplianceChecks: calling fveupg.dll [FveUpgradeComplianceCheck]
Date Time, Info [0x080021] MIG IsCompliantForUpgrade: failed
Date Time, Info [0x080043] MIG Callback_Compliance: Not a compliant system
Date Time, Info [0x08003e] MIG Not a compliant system, upgrade is disabled

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.

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.

Consider the following scenario. You encrypt a user’s Documents folder on a Windows Vista Business-based computer. Then, you upgrade the computer to Windows Vista Ultimate. In this scenario, the encryption attributes for the Documents folder are not maintained. Specifically, the files and the folders in the Documents folder remain encrypted. However, new files that are created in the Documents folder are not automatically encrypted.

You log on to Windows Vista on a new computer after a Group Policy setting has changed the folder redirection location of the My Documents folder. After you do this, you do not see the expected files in the My Documents folder.