When you use Remote Desktop Connection to connect to a Windows Vista-based computer, you receive an error message that resembles the following:

The requested session access is denied.

You open the root directory that contains offline files on a Windows Vista-based computer. When you try to synchronize the offline files with the file server for the first time, the synchronization is unsuccessful. In this situation, Windows Vista does not resume the synchronization. Additionally, when you click the offline files that are not synchronized, you receive an access denied message.

Note: When the synchronization is unsuccessful, Windows Vista creates broken branches of the synchronization tree.

When you run an application on a computer that has Windows Internet Explorer 7 installed, you receive an error message that resembles the following:

Access is denied

This problem occurs when you develop an application that starts new processes from an impersonated context.

Note: This problem does not occur on a computer that has Microsoft Internet Explorer 6 installed.

Consider the following scenario:

• You develop an application that sends an IOCTL_SFFDISK_DEVICE_COMMAND request to a Secure Digital (SD) card.
• You compile the application on a 32-bit version of Windows Vista.

In this scenario, the application obtains a “Success” value from the SD card. However, when a 64-bit version of Windows Vista uses the Microsoft Windows-32-on-Windows-64 (WOW64) subsystem to run the 32-bit application, the application obtains the following error message from the SD card:

ERROR_ACCESS_DENIED

On Windows Vista-based computer, you cannot use Registry Editor to load a registry hive file that is on a shared network resource. You receive the following error message:

Cannot load \\HivePath\FileName: Access is denied.

This problem occurs even if the user account that you use is granted Full Control permission to the registry hive file.

This problem also occurs if you use another utility to load a registry hive file that is on a shared network resource, and the utility uses the RegLoadKey API.

Consider the following scenario. In Windows Vista, you use Encrypting File System (EFS) to create an EFS-encrypted file. Or, you edit an EFS-encrypted file in Windows Vista. Then, you try to open the file in Microsoft Windows XP or in Microsoft Windows Server 2003. In this scenario, you receive an error message that resembles the following:

Access is denied

You cannot open an EFS-encrypted file in Windows XP or in Windows Server 2003 after the file has been opened in Windows Vista.

Consider the following scenario. In an application that is running on a Windows Vista-based computer, you try to map the HKEY_CLASSES_ROOT registry subtree to another registry subtree. For example, you try to map the HKEY_CLASSES_ROOT registry subtree to the HKEY_CURRENT_USER registry subtree. When the application calls the RegisterTypeLib API to register a type library, you may receive the following error message:

Access denied

Additionally, the RegisterTypeLib API returns the TYPE_E_REGISTRYACCESS (0×8002801c) value.

This problem occurs if User Account Control (UAC) is enabled, and the application is running under the Limited User Account.

When you try to move a folder in Windows Vista to a mount point folder that is located on the same disk, you receive the following error message:

Destination Folder Access Denied – You need permissions to perform this action

This problem does not occur when you move the folder to a mount point on a different disk. Additionally, this problem does not occur when you copy the folder to the mount point folder instead of moving the folder.

This problem occurs regardless of the User Account Control (UAC) settings or the user account permissions that are configured in Windows Vista.

Consider the following scenario:

• You try to add a shared printer to a Windows Vista-based computer.
• The Windows Vista-based computer is connected to a peer-to-peer network.
• The shared printer was configured on a Microsoft Windows XP Service Pack 2 (SP2)-based computer.

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

Windows cannot connect to the printer. Access is denied.

When you use the netdom renamecomputer command to rename a computer that is running Windows Vista, you receive the following error result:

This operation will rename the computer [OriginalComputerName] to [NewComputerName].

Certain services, such as the Certificate Authority, rely on a fixed machine
name. If any services of this type are running on [OriginalComputerName],
then a computer name change would have an adverse impact.

Access is denied.

The command failed to complete successfully.

You experience this problem when you try to rename the computer from a remote computer. If you run the command on the computer that you want to rename, the command works.

Note: You experience a similar problem if you try to use the NetRenameMachineInDomain function to rename a remote Windows Vista-based computer.