如何弹出USB可移动磁盘/卷，类似于Windows资源管理器中的“弹出”功能？

Question

Do you know what is the API, or sequence of API calls that windows uses to accomplish the "Eject" function which is available on the shell context menu for removable volumes?

So far I've tried two things:

1. using CM_Request_Device_Eject , I enumerate the removable disks (using the SetupDiXXX APIs ), find the one that I'm interested in, walk the device manager hierarchy (using CM_XXX APIs ) and finally call CM_Request_Device_Eject on the devInst of the device I'm interesed in. This works in the sense that it does remove the volumes from My Computer and makes the device "safe to remove" (ready to be removed) but it is not the same as the shell context menu "Eject" function. The way I know this is because the device that I'm trying to eject is supposed to do something when it is ejected and that something is not happening when I do the eject using CM_Request_Device_Eject .

2. using DeviceIoControl with the IOCTL_STORAGE_EJECT_MEDIA control code. The sequence of events is:

   • obtain a handle to the volume I'm interested in using CreateFile as suggested in the documentation
   • try to lock the volume with FSCTL_LOCK_VOLUME
   • try to dismount it using FSCTL_DISMOUNT_VOLUME
   • disable the prevent storage media removal using IOCTL_STORAGE_MEDIA_REMOVAL
   • and finally execute the IOCTL_STORAGE_EJECT_MEDIA function.

   This doesn't work at all. Each one of the DeviceIoControl calls fails with ERROR_IVALID_FUNCTION (0x00000001). I don't know why the calls fail. I've verified that other calls to DeviceIoControl work fine for the same file handle (such as IOCTL_STORAGE_GET_DEVICE_NUMBER )

Finally, my development machine is running Windows 7 x64, and in order to get the second method to work I've tried running my application with Administrator privileges and that did not change anything.

EDIT

Eventually, I found out where I was making a mistake with approach #2. It turns out that for some reason I was not setting the desired access correctly when opening the handle to the volume using CreateFile . The correct access mode is GENERIC_READ | GENERIC_WRITE GENERIC_READ | GENERIC_WRITE and I was passing 0. After correcting my error I was able to successfully eject the device using DeviceIoControl - IOCTL_STORAGE_EJECT_MEDIA , as well as with method #1, using CM_Request_Device_Eject .

And it turns out that method #2 is indeed the method used by the shell context menu's "Eject" function. Using this method the device reacts correctly.

Answer 1

Eventually, I found out where I was making a mistake with approach #2.

It turns out that for some reason I was not setting the desired access correctly when opening the handle to the volume using CreateFile.

The correct access mode is GENERIC_READ | GENERIC_WRITE GENERIC_READ | GENERIC_WRITE and I was passing 0 . After correcting my error I was able to successfully eject the device using DeviceIoControl - IOCTL_STORAGE_EJECT_MEDIA, as well as with method #1, using CM_Request_Device_Eject.

Finally, it turns out that method #2 is indeed the method used by the shell context menu's "Eject" function. Using this method the device reacts correctly.

Answer 2

I came here accidentally while doing a search on "CM_Request_Device_Eject", and saw that it was similar to a solution I'd recently done by pulling together similar pieces of a solution. Forgive the late answer.

I've summarized the steps I've done for this on my project in this SO answer .