I have been using internal linking for several weeks with no issues; however, yesterday when I started the TW program, I noticed it now said under internal linking...."Disabled because the Virtual AP is not available in your machine"
So I tried checking the settings in a command prompt to see if it was enabled or not using the following command:
netsh wlan show settings
Hosted network mode allowed in WLAN service: Yes
The hosted network is enabled but not necessarily started. So I ran the next command to see if the hosted network was started or not.
netsh wlan show hostednetwork
It showed it was not available.
So I tried to start the hosted network using this command:
netsh wlan start hostednetwork
"the hosted network couldn't be started. The group or resource is not in the correct state to perform the requested operation"
After some playing around and reading some forums relating to virtual networks and hotspots, I figured out that the network adapter driver was the culprit. Windows 10 updated the driver. I uninstalled the driver and used one of Windows 10's built in drivers from earlier this year. It solved the problem. I alerted HP of the driver issue and how it disabled Virtual Hosted Networks. Hopefully they will release a new driver that corrects the mistake
I hope this helps everyone out.
Thanks so much for sharing this info, Dave! With a newer operating system like Windows 10, it is understandable that some of Microsoft’s updates might be inadvertently interfering with both the hardware and software on your laptop. I am glad that you were able to find the version of the driver that allows you to use the Virtual Hosted Network feature again.
This question has received the maximum number of answers.