Hello everyone,
I am executing windows driver certification test case which is related with driver uninstall and install cycle. However this case not tolerated with Windows reboot request. I found some logs in the setupapi.app.log same as below;
cmd: cscript.exe “Reinstall_With_IO.wsf” /WDTF /DeviceID:“PCI\VEN_000A&DEV_0001&SUBSYS_00000A&REV_01\3&11583659&0&10” /IOPeriod:20000 /Cycles:3 /logo
! dvi: Query-removal was vetoed by PCI\PCI\VEN_000A&DEV_0001&SUBSYS_00000A&REV_01\3&11583659&0&10 (veto type 5: PNP_VetoOutstandingOpen)
! dvi: Setting needs reboot
! dvi: Query-and-Remove failed: 0x17: CR_REMOVE_VETOED
So, how can one easily bypass this issue ?
Cheers
This line is the key
! dvi: Query-removal was vetoed by PCI\PCI\VEN_000A&DEV_0001&SUBSYS_00000A&REV_01\3&11583659&0&10 (veto type 5: PNP_VetoOutstandingOpen)
Do you have an app which is running which has an open handle to your device while the test is running?
d
Bent from my phone
From: xxxxx@gmail.commailto:xxxxx
Sent: ?4/?2/?2013 11:10 PM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: [ntdev] pnp device driver remove and re-install without reboot request
Hello everyone,
I am executing windows driver certification test case which is related with driver uninstall and install cycle. However this case not tolerated with Windows reboot request. I found some logs in the setupapi.app.log same as below;
cmd: cscript.exe “Reinstall_With_IO.wsf” /WDTF /DeviceID:“PCI\VEN_000A&DEV_0001&SUBSYS_00000A&REV_01\3&11583659&0&10” /IOPeriod:20000 /Cycles:3 /logo
! dvi: Query-removal was vetoed by PCI\PCI\VEN_000A&DEV_0001&SUBSYS_00000A&REV_01\3&11583659&0&10 (veto type 5: PNP_VetoOutstandingOpen)
! dvi: Setting needs reboot
! dvi: Query-and-Remove failed: 0x17: CR_REMOVE_VETOED
So, how can one easily bypass this issue ?
Cheers
—
NTDEV is sponsored by OSR
OSR is HIRING!! See http://www.osr.com/careers
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>
xxxxx@gmail.com wrote:
I am executing windows driver certification test case which is related with driver uninstall and install cycle. However this case not tolerated with Windows reboot request. I found some logs in the setupapi.app.log same as below;
cmd: cscript.exe “Reinstall_With_IO.wsf” /WDTF /DeviceID:“PCI\VEN_000A&DEV_0001&SUBSYS_00000A&REV_01\3&11583659&0&10” /IOPeriod:20000 /Cycles:3 /logo
! dvi: Query-removal was vetoed by PCI\PCI\VEN_000A&DEV_0001&SUBSYS_00000A&REV_01\3&11583659&0&10 (veto type 5: PNP_VetoOutstandingOpen)
! dvi: Setting needs reboot
! dvi: Query-and-Remove failed: 0x17: CR_REMOVE_VETOED
So, how can one easily bypass this issue ?
By not vetoing the “remove” request. Your driver must allow itself to
be removed. End of story.
By the way, 000A is not a valid PCI vendor ID. You can’t sell this
device unless you use a legitimate vendor ID.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Hi all thanks for your comments,
@Doron, that application *probably* hypervisor.
@Tim, I covered orginal pci vendor id
this product still prototype.
If you have an application or driver that has an open handle to the driver (ie has called IoGetDeviceObjectPointer or ZwCreateFile) then that component needs to register for file handle notifications on that handle for as long as the handle is open and properly respond to notifications (ie close the handle) when asked to.
In UM that would be RegisterDeviceNotification, http://msdn.microsoft.com/en-us/library/windows/desktop/aa363431(v=vs.85).aspx
In KM that would be IoRegisterPlugPlayNotification, http://msdn.microsoft.com/en-us/library/windows/hardware/ff549526(v=vs.85).aspx .
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Wednesday, April 3, 2013 2:27 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] pnp device driver remove and re-install without reboot request
Hi all thanks for your comments,
@Doron, that application *probably* hypervisor.
@Tim, I covered orginal pci vendor id
this product still prototype.
NTDEV is sponsored by OSR
OSR is HIRING!! See http://www.osr.com/careers
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