If you add a removable storage drive during the period between system start and user logon, the Removable Storage Access policy does not work correctly on a client computer that is running Windows Vista or Windows Server 2008

In a network environment, you enable some group policies in the following location:
However, if you add the removable storage drive during the period between system start and user logon, the Removable Storage Access policy does not work correctly on a client computer that is running Windows Vista or Windows Server 2008. However, you find that can unexpectedly perform operations on the removable storage drive.

For example, consider the following scenario:

• You enable the "Removable Disks: Deny write access" policy
• You start a client computer that is running Windows Vista
• You connect a USB storage drive to the computer
• You log on to the system

In this scenario, you can write files to the USB drive, or you can create files on the USB storage drive. However, you expect to receive an "Access is denied" message.

This problem occurs because the removable storage device is granted the read/write permission when the device is plugged into the computer. However, if the device is plugged into the computer during the period between the system start and the user logon, the user policy is not applied. This access permission is not removed until the device is unplugged and then replugged.

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 the problem described in this article. 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 a computer that is running Windows Vista, you must have Windows Vista Service Pack (SP1), or Windows Vista SP2 installed.

No prerequisites are required for computers that are running Windows Server 2008.

Restart requirement

You must 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.

Windows Vista and Windows Server 2008 file information notes

The MANIFEST files (.manifest) and the MUM files (.mum) that are 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 of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported IA-64-based versions of Windows Server 2008

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.