This bug is for changes needs to be done in mingw-virt-viewer

Bug 845216 is for changes needs to be done in usb-clerk.

+++ This bug was initially created as a clone of Bug #845216 +++

Description of problem:
I believe we need to handle situation when usb device connected to a guest is not ejected/unmount properly better. In a situation when a user closes the remote-viewer client with usb device connected to the guest displayed by remote-viewer WinUSB driver remains to be installed on client machine which prevents users to use the USB device on the client machine.
I believe we should at least try to remove winusb driver on remote-viewer closure and consider to bring a solution for removal of winusb driver when active remote-viewer session is closed/crashed.

The Use case is for example following:
A user shuts the VM with a USB device connected down gracefully from inside of guest. The result is that winsusb driver is still installed and the user cannot use it on client machine. Workaround is to uninstall USB device from client machine including winusb driver and let Windows install a generic one again.

The true is that Users could be educated to unmount/eject USB devices properly but that would cost a lot of effort and bug reports.

Version-Release number of selected component (if applicable):
usbclerk-win-0.1-4

How reproducible:
Always

Steps to Reproduce:
1. Get a remote-viewer session to a guest with Any USB device connected to the guest.
2. Close remote-viewer while USB redirection is active.
3. Try to use the USB device on the client machine anyhow.
  
Actual results:
It's not possible to use USB device anyhow until you remove winusb driver and install a generic one.

Expected results:
winusb driver should be removed so Windows installs automatically a generic one -> user can use USB device on the client machine.