packsbta.blogg.se

I right click on the device > properties > driver tab and then I click on "Uninstall" there is no box to tick to delete driver files. (Code 31)Īnd the best part of it all, it doesn't let me delete the drivers. Yet, in when I right click on the device and choose properties, it says: "The device is not working properly because windows cannot load the drivers required for this device. After I had used the "Killer cleaner" software, I rebooted my computer > then the driver for the usb stick automatically re-installed itself, but hey, guess what? When I hit "Search automatically for updated driver software", windows is so saying "The best driver for your device is already installed" So now I'm sitting here trying to find a solution for this nonsense. And it didn't make the ethernet adapter show up either. I ran the "Killer cleaner" software, and for some reason it messed up my wireless usb adapter's drivers too. I have driver files ready, but where am I supposed to install this?`Usually I just right click on the device in device manager > Update driver software > Browse my computer for driver software and pinpoint it to the directory of the drivers and windows will do the rest, but I can't do that now, can I?Īlso, I tried installing the drivers through "Killer Perfomance Suite", but this fails to install the drivers for some reason.Īight that's just friggin brilliant.

Now I'm lost as to what I can do to make it appear in Device Manager again. However, after I had uninstalled and deleted the driver, the "Killer e2200 Gigabit Ethernet Controller (NDIS 6.30)" disappeared from the tab "Network adapters" in Device Manager. I proceeded by uninstalling the drivers, and as I did that I also got an option to delete the driver, which I did cause I had the driver ready to be re-installed in a folder on my desktop. I then tried to disable this feature on my network card, but still no connection. As I was enabling the hyper v extensible virtual switch protocol on my ethernet adapter, I lost connection to the internet. It all started when I tried to setup a virtual machine with Hyper-V. Okay, so I'll keep this as short as possible.