Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is

OSR_Community_User · May 14, 2012, 4:56am

Hello All,

My driver is ACPI driver and I have a service running in user mode which is actually having handle to it and PnpdSurpriseRemoval Test is getting failed and error seems to be :- There is still an open handle of driver under test.

In my service I have registered for the Device notification and I am getting it (SERVICE_CONTROL_DEVICEEVENT )also but only for the device arrival (i.e. DBT_DEVICEARRIVAL). I am closing the handle in the DBT_DEVICEREMOVECOMPLETE or DBT_DEVICEQUERYREMOVE but none of the them is getting called during the Plug and Play test.

In driver I have set the PNP capabilities as:

WDF_DEVICE_PNP_CAPABILITIES_INIT(&PnpCapabilities);
PnpCapabilities.SurpriseRemovalOK = WdfFalse;
PnpCapabilities.Removable = WdfFalse;
WdfDeviceSetPnpCapabilities(wdfDevice, &PnpCapabilities);

SurpriseRemovalOK is set to false , It that test case still valid ? if not then who will notify about SERVICE_CONTROL_DEVICEEVENT and what type I mean is it DBT_DEVICEQUERYREMOVEFAILED ?

Thanks & Regards
Ravi Rathore

Alex_Grig · May 14, 2012, 9:32am

You need to register for DBT_DEVTYP_HANDLE when you open the device. You’ll get DBT_DEVICEQUERYREMOVE for it; close the handle at that time. You won’t get REMOVECOMPLETE while there is an open handle.

OSR_Community_User · May 16, 2012, 7:51am

Do I get DBT_DEVICEQUERYREMOVE in Surprise Removal ? or is it for graceful scenario ?

When I run with Surprise removal plug and play test , I didn’t get the DBT_DEVICEQUERYREMOVE , while if I do uninstall my driver from device manager it does.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@broadcom.com
Sent: Monday, May 14, 2012 7:02 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

You need to register for DBT_DEVTYP_HANDLE when you open the device. You’ll get DBT_DEVICEQUERYREMOVE for it; close the handle at that time. You won’t get REMOVECOMPLETE while there is an open handle.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Alex_Grig · May 16, 2012, 9:14am

I think you’ll get DBT_DEVICEREMOVEPENDING

OSR_Community_User · May 16, 2012, 9:24am

Is it good to close user mode handle there DBT_DEVICEREMOVEPENDING ?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@broadcom.com
Sent: Wednesday, May 16, 2012 6:44 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

I think you’ll get DBT_DEVICEREMOVEPENDING

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Doron_Holan · May 16, 2012, 9:43am

Yed, although iirc surprise remove come directly as remove complete, not a graceful remove. You can easily ser what happens by a quick experiment though

d

debt from my phone

From: Rathore, Ravi
Sent: 5/16/2012 6:23 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

Is it good to close user mode handle there DBT_DEVICEREMOVEPENDING ?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@broadcom.com
Sent: Wednesday, May 16, 2012 6:44 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

I think you’ll get DBT_DEVICEREMOVEPENDING

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

OSR_Community_User · May 17, 2012, 7:53am

IT works well if I run the plug and play surprise removal with WDK supplied exe, but when I did run with WHQL , I didn’t get any events only for this Test.

Is it possible that during WHQL - surprise removal test, Windows service will not be notified to close handle even I have register for RegisterDeviceNotificaion in service ? It could be WHQL issue also for windows 8.

Other way could be register pnpPowerCallbacks.EvtDeviceSurpriseRemoval in driver and then notify the user mode app to close handle.

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, May 16, 2012 7:13 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

Yed, although iirc surprise remove come directly as remove complete, not a graceful remove. You can easily ser what happens by a quick experiment though

d

debt from my phone

From: Rathore, Ravi
Sent: 5/16/2012 6:23 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)
Is it good to close user mode handle there DBT_DEVICEREMOVEPENDING ?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@broadcom.com
Sent: Wednesday, May 16, 2012 6:44 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

I think you’ll get DBT_DEVICEREMOVEPENDING

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Doron_Holan · May 17, 2012, 10:07am

Whql, and i think you mean the wlk, doesn’t make the notification system work differently. It just makes sure you are doing the right thing. Registering pnpPowerCallbacks.EvtDeviceSurpriseRemoval and notifying the app out of band is NOT the right fix. Are you registering for notifications on the file handle you open or just the device interface guid?

d

debt from my phone

From: Rathore, Ravi
Sent: 5/17/2012 4:53 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

IT works well if I run the plug and play surprise removal with WDK supplied exe, but when I did run with WHQL , I didn?t get any events only for this Test.

Is it possible that during WHQL - surprise removal test, Windows service will not be notified to close handle even I have register for RegisterDeviceNotificaion in service ? It could be WHQL issue also for windows 8.

Other way could be register pnpPowerCallbacks.EvtDeviceSurpriseRemoval in driver and then notify the user mode app to close handle.

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, May 16, 2012 7:13 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

Yed, although iirc surprise remove come directly as remove complete, not a graceful remove. You can easily ser what happens by a quick experiment though

d

debt from my phone

From: Rathore, Ravi
Sent: 5/16/2012 6:23 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)
Is it good to close user mode handle there DBT_DEVICEREMOVEPENDING ?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@broadcom.com
Sent: Wednesday, May 16, 2012 6:44 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

I think you’ll get DBT_DEVICEREMOVEPENDING

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

OSR_Community_User · May 17, 2012, 12:25pm

*. Yup Wlk 8319:

*. I have register for both interface guid for device arrival and after that register with file handle as below:

My service handle is register for dwControlsAccepted |= (SERVICE_ACCEPT_STOP | SERVICE_ACCEPT_POWEREVENT.
When service starts, I have register for inteface GUID, for device arrival as

DEV_BROADCAST_DEVICEINTERFACE NotificationFilter;
ZeroMemory( &NotificationFilter, sizeof(NotificationFilter) );
NotificationFilter.dbcc_size = sizeof(DEV_BROADCAST_DEVICEINTERFACE);
NotificationFilter.dbcc_devicetype = DBT_DEVTYP_DEVICEINTERFACE;
NotificationFilter.dbcc_classguid = InterfaceClassGuid;

hInterfaceNotify = RegisterDeviceNotification(
hWnd, // events recipient this is service handle
&NotificationFilter, // type of device
DEVICE_NOTIFY_SERVICE_HANDLE|
DEVICE_NOTIFY_ALL_INTERFACE_CLASSES // type of recipient handle
);

In Device Arrival: I am registering the file handle for device remove events as:

memset (&filter, 0, sizeof(filter)); //zero the structure
filter.dbch_size = sizeof(filter);
filter.dbch_devicetype = DBT_DEVTYP_HANDLE;
filter.dbch_handle = *p_handle;

hDeviceNotify = RegisterDeviceNotification(g_serviceStatusHandle, &filter, DEVICE_NOTIFY_SERVICE_HANDLE|

DEVICE_NOTIFY_ALL_INTERFACE_CLASSES);

One thing I forgot to unregister for the GUID interface at the end of the service. It might be the problem.

~ Ravi

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Thursday, May 17, 2012 7:37 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

Whql, and i think you mean the wlk, doesn’t make the notification system work differently. It just makes sure you are doing the right thing. Registering pnpPowerCallbacks.EvtDeviceSurpriseRemoval and notifying the app out of band is NOT the right fix. Are you registering for notifications on the file handle you open or just the device interface guid?

d

debt from my phone

From: Rathore, Ravi
Sent: 5/17/2012 4:53 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)
IT works well if I run the plug and play surprise removal with WDK supplied exe, but when I did run with WHQL , I didn’t get any events only for this Test.

Is it possible that during WHQL - surprise removal test, Windows service will not be notified to close handle even I have register for RegisterDeviceNotificaion in service ? It could be WHQL issue also for windows 8.

Other way could be register pnpPowerCallbacks.EvtDeviceSurpriseRemoval in driver and then notify the user mode app to close handle.

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, May 16, 2012 7:13 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

Yed, although iirc surprise remove come directly as remove complete, not a graceful remove. You can easily ser what happens by a quick experiment though

d

debt from my phone

From: Rathore, Ravi
Sent: 5/16/2012 6:23 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)
Is it good to close user mode handle there DBT_DEVICEREMOVEPENDING ?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@broadcom.com
Sent: Wednesday, May 16, 2012 6:44 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

I think you’ll get DBT_DEVICEREMOVEPENDING

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Doron_Holan · May 17, 2012, 12:42pm

Why are you specifying DEVICE_NOTIFY_ALL_INTERFACE_CLASSES in both registrations? It isn’t needed, you are asking for a specific dev interface GUID and a specific handle, not a generic broadcast of changes.

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Rathore, Ravi
Sent: Thursday, May 17, 2012 9:25 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

*. Yup Wlk 8319:

*. I have register for both interface guid for device arrival and after that register with file handle as below:

My service handle is register for dwControlsAccepted |= (SERVICE_ACCEPT_STOP | SERVICE_ACCEPT_POWEREVENT.
When service starts, I have register for inteface GUID, for device arrival as

DEV_BROADCAST_DEVICEINTERFACE NotificationFilter;
ZeroMemory( &NotificationFilter, sizeof(NotificationFilter) );
NotificationFilter.dbcc_size = sizeof(DEV_BROADCAST_DEVICEINTERFACE);
NotificationFilter.dbcc_devicetype = DBT_DEVTYP_DEVICEINTERFACE;
NotificationFilter.dbcc_classguid = InterfaceClassGuid;

hInterfaceNotify = RegisterDeviceNotification(
hWnd, // events recipient this is service handle
&NotificationFilter, // type of device
DEVICE_NOTIFY_SERVICE_HANDLE|
DEVICE_NOTIFY_ALL_INTERFACE_CLASSES // type of recipient handle
);

In Device Arrival: I am registering the file handle for device remove events as:

memset (&filter, 0, sizeof(filter)); //zero the structure
filter.dbch_size = sizeof(filter);
filter.dbch_devicetype = DBT_DEVTYP_HANDLE;
filter.dbch_handle = *p_handle;

hDeviceNotify = RegisterDeviceNotification(g_serviceStatusHandle, &filter, DEVICE_NOTIFY_SERVICE_HANDLE|

DEVICE_NOTIFY_ALL_INTERFACE_CLASSES);

One thing I forgot to unregister for the GUID interface at the end of the service. It might be the problem.

~ Ravi

From: xxxxx@lists.osr.com mailto:xxxxx [mailto:xxxxx@lists.osr.com]mailto: On Behalf Of Doron Holan
Sent: Thursday, May 17, 2012 7:37 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

Whql, and i think you mean the wlk, doesn’t make the notification system work differently. It just makes sure you are doing the right thing. Registering pnpPowerCallbacks.EvtDeviceSurpriseRemoval and notifying the app out of band is NOT the right fix. Are you registering for notifications on the file handle you open or just the device interface guid?

d

debt from my phone

From: Rathore, Ravi
Sent: 5/17/2012 4:53 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)
IT works well if I run the plug and play surprise removal with WDK supplied exe, but when I did run with WHQL , I didn’t get any events only for this Test.

Is it possible that during WHQL - surprise removal test, Windows service will not be notified to close handle even I have register for RegisterDeviceNotificaion in service ? It could be WHQL issue also for windows 8.

Other way could be register pnpPowerCallbacks.EvtDeviceSurpriseRemoval in driver and then notify the user mode app to close handle.

From: xxxxx@lists.osr.com mailto:xxxxx [mailto:xxxxx@lists.osr.com]mailto: On Behalf Of Doron Holan
Sent: Wednesday, May 16, 2012 7:13 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

Yed, although iirc surprise remove come directly as remove complete, not a graceful remove. You can easily ser what happens by a quick experiment though

d

debt from my phone

From: Rathore, Ravi
Sent: 5/16/2012 6:23 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)
Is it good to close user mode handle there DBT_DEVICEREMOVEPENDING ?

-----Original Message-----
From: xxxxx@lists.osr.com mailto:xxxxx [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@broadcom.com mailto:xxxxx
Sent: Wednesday, May 16, 2012 6:44 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

I think you’ll get DBT_DEVICEREMOVEPENDING

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx></mailto:></mailto:xxxxx></mailto:></mailto:xxxxx>

OSR_Community_User · May 18, 2012, 4:41am

Thanks Doron for help.

I was trying with that option also to get at least some events.

I made a stupid error of not installing the service properly on the target . I was just copy the service.exe in system32 and restart the service which works but until reboot. When I did the clean uninstall and install it works.

~ Ravi Rathore

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Thursday, May 17, 2012 10:11 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

Why are you specifying DEVICE_NOTIFY_ALL_INTERFACE_CLASSES in both registrations? It isn’t needed, you are asking for a specific dev interface GUID and a specific handle, not a generic broadcast of changes.

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Rathore, Ravi
Sent: Thursday, May 17, 2012 9:25 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

*. Yup Wlk 8319:

*. I have register for both interface guid for device arrival and after that register with file handle as below:

My service handle is register for dwControlsAccepted |= (SERVICE_ACCEPT_STOP | SERVICE_ACCEPT_POWEREVENT.
When service starts, I have register for inteface GUID, for device arrival as

DEV_BROADCAST_DEVICEINTERFACE NotificationFilter;
ZeroMemory( &NotificationFilter, sizeof(NotificationFilter) );
NotificationFilter.dbcc_size = sizeof(DEV_BROADCAST_DEVICEINTERFACE);
NotificationFilter.dbcc_devicetype = DBT_DEVTYP_DEVICEINTERFACE;
NotificationFilter.dbcc_classguid = InterfaceClassGuid;

hInterfaceNotify = RegisterDeviceNotification(
hWnd, // events recipient this is service handle
&NotificationFilter, // type of device
DEVICE_NOTIFY_SERVICE_HANDLE|
DEVICE_NOTIFY_ALL_INTERFACE_CLASSES // type of recipient handle
);

In Device Arrival: I am registering the file handle for device remove events as:

memset (&filter, 0, sizeof(filter)); //zero the structure
filter.dbch_size = sizeof(filter);
filter.dbch_devicetype = DBT_DEVTYP_HANDLE;
filter.dbch_handle = *p_handle;

hDeviceNotify = RegisterDeviceNotification(g_serviceStatusHandle, &filter, DEVICE_NOTIFY_SERVICE_HANDLE|

DEVICE_NOTIFY_ALL_INTERFACE_CLASSES);

One thing I forgot to unregister for the GUID interface at the end of the service. It might be the problem.

~ Ravi

From: xxxxx@lists.osr.com mailto:xxxxx [mailto:xxxxx@lists.osr.com]mailto: On Behalf Of Doron Holan
Sent: Thursday, May 17, 2012 7:37 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

Whql, and i think you mean the wlk, doesn’t make the notification system work differently. It just makes sure you are doing the right thing. Registering pnpPowerCallbacks.EvtDeviceSurpriseRemoval and notifying the app out of band is NOT the right fix. Are you registering for notifications on the file handle you open or just the device interface guid?

d

debt from my phone

From: Rathore, Ravi
Sent: 5/17/2012 4:53 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)
IT works well if I run the plug and play surprise removal with WDK supplied exe, but when I did run with WHQL , I didn’t get any events only for this Test.

Is it possible that during WHQL - surprise removal test, Windows service will not be notified to close handle even I have register for RegisterDeviceNotificaion in service ? It could be WHQL issue also for windows 8.

Other way could be register pnpPowerCallbacks.EvtDeviceSurpriseRemoval in driver and then notify the user mode app to close handle.

From: xxxxx@lists.osr.com mailto:xxxxx [mailto:xxxxx@lists.osr.com]mailto: On Behalf Of Doron Holan
Sent: Wednesday, May 16, 2012 7:13 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

Yed, although iirc surprise remove come directly as remove complete, not a graceful remove. You can easily ser what happens by a quick experiment though

d

debt from my phone

From: Rathore, Ravi
Sent: 5/16/2012 6:23 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)
Is it good to close user mode handle there DBT_DEVICEREMOVEPENDING ?

-----Original Message-----
From: xxxxx@lists.osr.com mailto:xxxxx [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@broadcom.com mailto:xxxxx
Sent: Wednesday, May 16, 2012 6:44 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Plug and Play Surprise Removal Failed :- User Mode Open handle Problem: (DBT_DEVICEREMOVECOMPLETE is not getting called)

I think you’ll get DBT_DEVICEREMOVEPENDING

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx></mailto:></mailto:xxxxx></mailto:></mailto:xxxxx>