Hi,
I wrote a driver which emulated a virtual disk to OS( like VHD) and it worked well in Win 7/8. However, when I loaded it in Win 10, the disk management panel could not be opened and reported a failure saying “Unable to connect to virtual disk service”. Ran cmd “diskpart.exe” also returned the same failure.
Windbg showed that my driver received the following IOCTL codes(IOCTL_STORAGE_BASE based) when running diskpart:
2d1190 2d118c 2d148c 2d1480
These IOCTL codes are new in Windows 10 and we didn’t see them in Win 7/8. I am not sure whether they are related to system’s virtual disk service start failure. Do you know what they are and how to handle them? Any help will be highly appreciated.
Thanks,
Jason
The first two are not present in the WDK. They have function code 0x463 and 0x464 and are not defined in Winioctl.h.
//
// IOCTLs 0x0463 to 0x0468 reserved for dependent disk support.
//
but no one is defined.
The last two are IOCTL_EHSTOR_BANDMGMT_QUERY_CAPABILITIES and IOCTL_EHSTOR_BANDMGMT_ENUMERATE_BANDS and are present in WDK 8.1 (ehstorbandmgmt.h).
Thanks for the clarification.
The virtual disk service still could not be connected in disk management
panel, even after I implemented the IOCTL_EHSTOR_BANDMGMT_QUERY_CAPABILITIES
and IOCTL_EHSTOR_BANDMGMT_ENUMERATE_BANDS .
Do you know which IOCTLs or what I need to care about in Win 10 to make
the disk management panel work?
Thanks,
Jason
2017-04-14 2:06 GMT+08:00 :
> The first two are not present in the WDK. They have function code 0x463
> and 0x464 and are not defined in Winioctl.h.
>
> //
> // IOCTLs 0x0463 to 0x0468 reserved for dependent disk support.
> //
>
> but no one is defined.
>
> The last two are IOCTL_EHSTOR_BANDMGMT_QUERY_CAPABILITIES and
> IOCTL_EHSTOR_BANDMGMT_ENUMERATE_BANDS and are present in WDK 8.1
> (ehstorbandmgmt.h).
>
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:></http:>
> Do you know which IOCTLs or what I need to care about in Win 10 to make the disk management panel work?
No, you have to do some debugging to find out what is failing.
You should look at the system log. The disk management service may queue some entries if something goes wrong.
How is the disk showing in the device manager ? In the disk’s property page, you have a tab where you can « populate » partitions. Have you tried this ? You could grab an error code.
I have solved the issue and make disk management console work successfully,
thanks a lot for your guidance!
I checked the system log as you mentioned and found vds.exe, which was
invoked by Win10’s virtual disk service, encountered a APP_CRASH with
failure code 0xc0000005. After debugging with windbg, I finally caught the
bug in IOCTL dispatch routine of my driver.
This issue could not be fixed without your help, thanks again!
Jason
2017-04-17 22:04 GMT+08:00 :
> > Do you know which IOCTLs or what I need to care about in Win 10 to
> make the disk management panel work?
>
>
>
> No, you have to do some debugging to find out what is failing.
>
>
>
> You should look at the system log. The disk management service may queue
> some entries if something goes wrong.
>
>
>
> How is the disk showing in the device manager ? In the disk’s property
> page, you have a tab where you can « populate » partitions. Have you tried
> this ? You could grab an error code.
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:></http:>