Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message in the Setupapi.log file when you try to remove a device


View products that this article applies to.

Symptoms

When you try to remove a device, you may receive an error message that is similar to the following in the Setupapi.log file
#W001 Query-removal during uninstall of "IDE\DISKIC35L040AVVA07-0_______________________VA2OA50K\5&269BD72D&0&0.0.0" was vetoed by "IDE\DiskIC35L040AVVA07-0________________________VA2OA50K\5&269bd72d&0&0.0.0" (veto type 6: PNP_VetoDevice)
When you try to remove a device, each driver in the driver stack for that device receives a Query-Remove Input/Output Request Package (IRP). If the query is denied by one or more of the drivers, a veto message is written to the Setupapi.log file by the PnP Manager.

Note This error message is incomplete because it does not indicate the name of the driver that is issuing the vetoing.

↑ Back to the top


Cause

This issue occurs because the IRP removal query does not track the name of the driver.

↑ Back to the top


Resolution

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 this specific problem. 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

No prerequisites.

Restart Requirement

A restart is required after you apply this hotfix.

Hotfix Replacement Information

This hotfix does not replace any other hotfixes.

File Information

The global version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
      Date         Time   Version            Size    File name
   --------------------------------------------------------------
   03-May-2003  00:00  5.2.3790.9      2,158,592  Ntkrnlmp.exe
   27-Apr-2003  06:51  5.2.3790.9      2,063,872  Ntkrnlpa.exe     
   27-Apr-2003  06:51  5.2.3790.9      2,106,368  Ntkrpamp.exe
   03-May-2003  00:04  5.2.3790.9      2,148,864  Ntoskrnl.exe   

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   03-May-2003  00:02  5.2.3790.9      5,603,840  Ntkrnlmp.exe     IA-64   

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

↑ Back to the top


More information

To use this hotfix, create a new DWORD value, and then set the Data value to "1" for the following registry key:
HKEY_Local_Machine\System\CurrentControlSet\Control\PnP\ReturnVetoDriverName

To do this, follow these steps.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and click the following registry key:
    HKEY_Local_Machine\System\CurrentControlSet\Control\PnP\ReturnVetoDriverName
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. In the right pane, double-click the new value.
  5. In the Value data box, type 1, and then click OK.
After you install this hotfix, the error message in the Setupapi.log file is expanded to include the following information, where Bus is the type of bus, Device is the unique identification number of the device, Instance is the unique instance identification number, and Driver Name is the name of the driver that vetoed the removal of the device, Bus\Device\Instance\Driver\Driver Name:
IDE\DISKIC35L040AVVA07-0________________________VA2OA50K\5&269BD72D&0&0.0.0 was vetoed by IDE\DiskIC35L040AVVA07-0________________________VA2OA50K\5&269bd72d&0&0.0.0\Driver\Disk
Note The error message does not always follow the Driver\Driver Name naming format. For example, when the NTFS file system vetoes the removal of the device, the error message says "FileSystem\Ntfs, instead of "Driver\Driver Name."

After you apply this hotfix and add the new registry value, certain PnP Configuration Manager Functions may behave differently. For example, if a device ejection request fails, the dialog box that is displayed by the CM_Request_Device_Eject_Ex function will not contain the friendly name of the device. Instead, the dialog box will contain the PnP ID with the driver name appended (such as IDE\DiskIC35L040AVVA07-0________________________VA2OA50K\5&269bd72d&0&0.0.0\Driver\Disk). If this behavior is not what you want, you can delete the registry key, and the behavior of the system will return to the default behavior (the way it behaved before the hotfix).

For more information about the CM_Request_Device_Eject_Ex function, visit the following Microsoft Web site:

The Setupapi.log file is located at the following location:
%windir%\setupapi.log


For more information about the Setupapi.log file, visit the following Microsoft Web site: http://msdn2.microsoft.com/en-us/library/ms791358.aspx

↑ Back to the top


Keywords: kbhotfixserver, kbqfe, kbbug, kbfix, kbqfe, kbwinserv2003presp1fix, kbautohotfix, KB818522

↑ Back to the top

Article Info
Article ID : 818522
Revision : 11
Created on : 7/24/2007
Published on : 7/24/2007
Exists online : False
Views : 431