KyungWoon Cho

@bihailantian655 : Weird.. Please try to install again with `-d` (debug) option like as `usbip.exe -d install`.

@kdschlosser : The recent tag version which supports is [v0.1.0](https://github.com/cezanne/usbip-win/releases/tag/v0.1.0). All upper versions do not support Win7 or 8 because usbip-win started to use kernel libraries of Win10.

@kdschlosser : > maybe a change to the README is needed then. Thanks. README should be fixed. However, conditional build for Win7 or 8 would be more preferable even though...

@bartlomiejcieszkowski : It's an interesting issue. But network connection would be lost even though vhci manages to establish connection state. Thus, a solution might be a matter of reconnection. I...

@charleliedesmet : Which version did you test? I believe that the usbip tools in _dev_ branch(d10576d) may resolve your issue. Here is a temporary package [usbip-win-d10576d.zip](https://github.com/cezanne/usbip-win/files/8883786/usbip-win-d10576d.zip). Can you try this?

@skajacore : I agree vhci log is not pretty good to understand. However, your log looks a bit more complicated. How did you extract it? Here is my log from...

@koudis: It's great to hear the news from you. EV certificate will be required for using usbip-win at production level. But usbip-win kernel drivers are still unstable and lacks some...

@Ale268 : > When do you expect the Project to be this far? My hope answers that this project requires 4~6 months until vhci(UDE) deserves an EV certificate. 😕

@forlayo: I would appreciate your EV certificate. However, usbip-win vhci drivers should get attestation sign at MS partner portal after the EV certificate is registered in my partner portal. But...

@MinHyukPark121 : > Could we know when the current EV Certificate will expire? Maybe after 3 months. However, once signed package can be safely installed with no test mode even...