![]() Once it is up and running attach the adapter. Start the VM with the adapter unattached. ![]() Configure the VM to start with a USB device filter - don't add the one that appears on the menu, create your own more general fiter, specifying only the vendor ID (148F) and product ID (3070 for my model). Other things this video recommends may also be a factor:ġ. This makes total sense - if you do not do this the adapter is left in a bad state, and its state is persisted - rebooting Windows does not clear it. Once Kali is down, with the adapter still plugged in to the USB port, and Windows has control again, the icon to eject it will appear in the notification area in the system tray. I think the key is that you shutdown Kali with the adapter attached, and then you *must* eject the USB device from Windows. ![]() So a bit of searching with better keywords this time I found this: įollowing some key recommendations in this video, it works every time. Windows reboots did not clear it, something was being persisted. It doesn't bother Windows as it always works there, but it bothers Kali thru VB. It worked properly the first time after installing the drivers, but not subsequent times, so I was thinking that something was being left in a bad state. I had problems from installing the original ISO drivers and a nex update on the Alfa web site, so I removed both drivers and all the install directories and cleaned up the registry so I had a clean install of the drivers, with no red herrings to chase. This is finally fixed, for anyone with this problem.
0 Comments
Leave a Reply. |