Windows 10: Microsoft Wi-Fi Direct Virtual Adapter #2 - Code 45

Recently I've installed the new windows 10 version 1511 update, everything seems to be working fine except for one thing.

This would be my "Microsoft Wi-Fi Direct Virtual Adapter #2" driver, because prior to the installation of the new update it was working just fine. It seems that is not the case now, as windows claims that it's not functioning properly and has given it a "code 45" flag.

Is there anyway to fix this, or this a problem that's inherent with the new update and can only be fixed by its developers later?

Any advice on my situation would be appreciated, thank you.

I shall also provide pictorial examples to to better express my issue.













:)

 

disable permanently Microsoft Wi-Fi Direct Virtual Adapter

Have you contacted your ISP regarding the MAC Address of it??

See AndreyT's explanation here : Microsoft Wi-Fi Direct Virtual Adapter #2 - Code 45 - Windows 10 Forums

 

Wi-Fi virtual adapter

I am unable to create a wi-fi hotspot on my laptop (HP pavillion ab-032tx model) after upgrading to windows 10. I cannot find Microsoft WI-Fi direct Virtual adapter in the listed adapters (control pannel->network sharing center) . However Microsoft Wi-Fi
direct Virtual adapter and Microsoft Wi-Fi direct Virtual adapter #2 are listed in hidden drivers (device manager-> view tab, faded icons). Upon checking for hardware changes, there are no unkown devices being shown. Microsoft Wi-Fi direct Virtual adapter
#3 is also found in the view tab , but its icon is not faded. All my drivers are updated. Still i am unable to create a hotspot. Pl help me with the same.

 

Did you try to just uninstall that offending virtual WiFi adapter #2 and forget about it?

Or maybe a better idea would be to just uninstall both of your virtual WiFi adapters and then just do "Scan for hardware changes" to make Windows discover and reinstall it from scratch.

 

I have not, as said offending driver was working just fine yesterday. Also, seeing as there is no guarantee that Windows will re-detect the driver once it's uninstalled, I will have to forgo that method for the moment.

 

"Did you try to just uninstall that offending virtual WiFi adapter #2 and forget about it?" This shouldn't be an option either, seeing as the component was being utilized by my system with no issues until now for the longest period of time. At best, this could be a bandage for what could be a "serious" problem.

 

Well, the device is NOT being utilized by your system anymore. The device is displayed in your Device Manager in faded color, which means that it is a hidden device. It is a device that, as Windows believes, is no longer connected to your computer, no longer exists. Which is exactly what Windows is telling you in your second screen shot.

Since Windows believes that this device no longer exists, it cannot possibly "utilize" it.

Your screenshots clearly show that Windows did successfully detect and install the Microsoft Wi-Fi Direct Virtual Adapter device (the one without #2). That's the device your system "utilizes" now. The other one - with #2 in the name - is some sort of glitch, apparently. It appears to be an "orphaned" device entry that probably used to refer to the same device as the first one.

We see such things quite often with all kinds of devices (like USB devices being pulled out of one USB port and plugged into another an such). For which reason, it is a good idea to do periodic cleanup of your Device Manager from old "orphaned" hidden device entries. The way you do it is you ask your Device Manager to show hidden devices and just uninstall everything that seems unnecessary, especially if it has these #2, #3 and such in their names.

If you accidentally uninstall a device entry that corresponds to a real, existing device. Windows will automatically redetect and reinstall it for you. It has never been an issue.

In other words, not only it is an option, it is actually something that you might want doing on periodic basis, just to keep your OS installation well-maintained.

 

"Well, the device is NOT being utilized by your system anymore. The device is displayed in your Device Manager in faded color, which means that it is a hidden device. It is a device that, as Windows believes, is no longer connected to your computer, no longer exists. Which is exactly what Windows is telling you in your second screen shot."

How do you mean? I have numerous devices that are part of the "hidden" category that aren't faded out at all, just the one that had been working prior to the update I installed yesterday. However, if what you say is true, then my problem is even more anomalous then I originally thought.

"We see such things quite often with all kinds of devices (like USB devices being pulled out of one USB port and plugged into another an such). For which reason, it is a good idea to do periodic cleanup of your Device Manager from old "orphaned" hidden device entries. The way you do it is you ask your Device Manager to show hidden devices and just uninstall everything that seems unnecessary, especially if it has these #2, #3 and such in their names."

Again, this should not be the case. The device/driver was there and functioning properly when I had first installed Windows 10, and I can assure you I had no hand in its creation outside of what windows had installed for me when I first installed it. I do not have many peripherals, nor are they in anyway associated with the "Microsoft Wi-Fi Direct Virtual Adapter #2," as far as i'm concerned. If anything, I believe it's an integral part of my system, meant to serve a purpose and not at all unnecessary.

"If you accidentally uninstall a device entry that corresponds to a real, existing device. Windows will automatically redetect and reinstall it for you. It has never been an issue."

Perhaps, but this had not been the case for me. When I was still using Windows 8.1, my "Microsoft Device Association Root Enumerator" driver grayed out and I had the idea even then to uninstall it, reboot, and let windows re-install it. It did not do so, and I was short of one driver that was only re-installed when I had installed 10.

"In other words, not only it is an option, it is actually something that you might want doing on periodic basis, just to keep your OS installation well-maintained."

I'm not discounting your advice, but I do not think this's something I can remove without repercussion. Especially with my previous attempts ending in failure.

 

was wondering if you ever fixed problem? if so how? i am having same problem...ty