WiFi changes after Windows 10 update 10.0.16299 Build 16299, losing connection

After permitting Windows install latest windows update 10.0.16299 Build 16299, the wifi info is different than before and keep getting the wifi/internet disconnected.

The update  made the following changes:
- The Network Bridge, now has a different IP and subnet but same gateway
- Microsoft Network Adapter Multiplexor Driver, not checked  in Network Bridge
- The Hyper-V Virtual Ethernet Adapter and has the IP as always

Hyper-V Virtual Ethernet Adapter
IP Address	192.168.0.100, 172.21.134.81
IP Subnet	255.255.255.0, 255.255.255.240
Default Gateway . . . . . . . . . : 192.168.0.1

Microsoft Network Adapter Multiplexor Driver
IPv4 Address. . . . . . . . . . . : 192.168.0.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

Open in new window


Please advice on what to do to configure correctly or fix the internet connection.
rayluvsAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Sounds like someone really screwed up the network BEFORE the upgrade. So the upgrade probablybdid react weirdly to that.

With Hyper-v, a virtual switch is configured and only the virtual adapter should have an IP. Everything else gets disabled when the hyper-v switch is configured and bound to a physical NIC. That those had an IP address that changed is a good indication that someone went and messed with those settings  not understanding how hyper-v works.

How to fix really depends on how much they messed with. One reliable way would be to disable them re-enable the hyper-v role and reconfigure the hyperv network from scratch.
0
rayluvsAuthor Commented:
No one really worked with it.  I have been here all day.

If I delete the Hyper-V switch, would put the IP values on NICs?
0
JohnBusiness Consultant (Owner)Commented:
Yes. The upgrade did not change my Wi-Fi properties.

One possible fix is to run TCP/IP Reset.

Open cmd.exe with Run as Administrator
Then  netsh int ip reset c:\resetlog.txt
Also, ipconfig /flushdns followed by net stop dnscache followed by net start dnscache
Then restart the computer
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Cliff GaliherCommented:
I don't mean today. They could've mangled it months ago, but the upgrade happened today and so things went sideways today. If you aren't familiar with hyper-v and don't know the details of how that was configured then you should probably do an audit. Making changes ad-hoc isn't a wise troubleshooting method.
0
rayluvsAuthor Commented:
yes i know the details.  I have been responsible for the computers for the past month (I had a helper but always checked).  

FYI,
We had run ipconfig/all and only received 1 IP per computer.

We have another computer in the LAN and its as this one was prior update.

Just deleted the hyper-v switch from hyper-v manager (but they  are still in adapter, the bridge is gone).

Will try the RESET.
0
rayluvsAuthor Commented:
FYI,
the internet is faster now after deleting the hyper switch from the manager.
0
JohnBusiness Consultant (Owner)Commented:
I would still do the TCP/IP Reset as a way to completely refresh the Wi-Fi connection.
0
rayluvsAuthor Commented:
Note,
The lines:
net stop dnscache
net start dnscache

returns message "More help is available by typing NET HELPMSG"
0
JohnBusiness Consultant (Owner)Commented:
Thanks. Windows must have changed this as well. I have used this method for a long time.
0
rayluvsAuthor Commented:
you know the correct commands?
0
JohnBusiness Consultant (Owner)Commented:
I was looking.

Try:  ipconfig /flushdns  

That works.  https://www.technipages.com/flush-and-reset-the-dns-resolver-cache-using-ipconfig

You apparently do not need to stop and start the service.

If you wish to, you can restart the DNSCACHE service in Task Manager  Services tab.
0
rayluvsAuthor Commented:
DNSCACHE also gave an error "Unable to stop service... The operation could not be completed... Access is denied."
0
JohnBusiness Consultant (Owner)Commented:
It appears that Edge is dependent on the DNS service and that may prevent it from stopping.

If the DNSCACHE service is running, forget that part of it. Reset TCP/IP and DNS Flush and leave it at that.
0
rayluvsAuthor Commented:
Done, still same issue.
0
JohnBusiness Consultant (Owner)Commented:
I am not sure what might have happened to your connection. As Cliff says it could have been messed up.

Find the Wi-Fi driver from the manufacturer's support site. Download it. Now go to Device Manager and remove (uninstall) the wireless device.  Now restart and install the new driver.
0
rayluvsAuthor Commented:
Is there a way to delete the switch adapter from network connections?
0
JohnBusiness Consultant (Owner)Commented:
What switch adapter ?

You can delete a working network connection:

Open an admin command prompt:  NETSH WLAN Delete Profile name="profile name"

NETSH WLAN SHOW PROFILES to list what profiles you have.
0
rayluvsAuthor Commented:
The virtual switch created in Hyper-V option "Virtual Switch Manager" (this permits a VM connect LAN)
0
JohnBusiness Consultant (Owner)Commented:
I do not think you should delete this. Remove Hyper-V if you do not want it there.
0
rayluvsAuthor Commented:
No, just the adapter, not the Hyper-V as such.  We use the VM, not much but we do.  

Is there a way just to delete it so it can stop “bridging” WiFi with VM switch adapter?
0
JohnBusiness Consultant (Owner)Commented:
I am not familiar with Hyper-V enough to answer that. However just having the adapter there should not cause an issue.

Uninstall / restart / reinstall Hyper-V to correct the issue, if there is one to correct.
0
rayluvsAuthor Commented:
makes sense.

How about the adapters and its contents (see pix below):
network adapters
These are the only 2 adapters in "Control Panel\Network and Internet\Network Connections"

The Switch adapters I assume by uninstalling Hyper-V will disappear.

How about the WiFi adapter? what is the proper steps to delete or uninstall the adapter?
0
JohnBusiness Consultant (Owner)Commented:
1. In your Left section above, Client for Microsoft Networks must be checked. Enable it and restart the computer
2. File and Print sharing enabled only if you wish to share files. Unchecked means you cannot.
3. IPv4 is unchecked:  Enable it !
4. Enable QOS
5. The two Link Layer settings can be enabled.
6. I do not see value in disabling Hyper-V but you can disable it and try. That does not delete it.


How about the WiFi adapter? what is the proper steps to delete or uninstall the adapter?

Find the Wi-Fi driver from the manufacturer's support site. Download it. Now go to Device Manager and remove (uninstall) the wireless device.  Now restart and install the new driver.
0
rayluvsAuthor Commented:
Ok
0
rayluvsAuthor Commented:
After uninstall all, the manual IP 192.168.0.100 stood (always was the static IP we have set for this computer).

After reinstalling drivers and installing hyper-v, 2 new sets of IP appears:

---------------------------------------------------------------------------------
Name                    [00000014] Hyper-V Virtual Ethernet Adapter
---------------------------------------------------------------------------------
Adapter Type            Ethernet 802.3
Product Type            Hyper-V Virtual Ethernet Adapter
Installed               Yes
PNP Device ID           ROOT\VMS_MP\0000
Last Reset              11/17/2017 8:09 PM
Index                   14
Service Name            VMSMP
IP Address              192.168.201.65, fe82::a43f:fcf5:113b:8167
IP Subnet               255.255.255.240, 64
Default IP Gateway      Not Available
DHCP Enabled            Yes
DHCP Server             255.255.255.255
DHCP Lease Expires      Not Available
DHCP Lease Obtained     Not Available
MAC Address             ‪1A:10:2E:A1:0A:D6‬
Driver                  c:\windows\system32\drivers\vmswitch.sys (10.0.16299.15, 1.60 MB (1,677,824 bytes), 9/29/2017 7:41 AM)
                             
---------------------------------------------------------------------------------
Name                    [00000017] Microsoft Network Adapter Multiplexor Driver
---------------------------------------------------------------------------------
Adapter Type            Ethernet 802.3
Product Type            Microsoft Network Adapter Multiplexor Driver
Installed               Yes
PNP Device ID           COMPOSITEBUS\MS_IMPLAT_MP\{174191B4-4BE3-2638-AED1-56D5A1F7882D}
Last Reset              43056.8395833333
Index                   17
Service Name            NdisImPlatformMp
IP Address              192.168.0.10
IP Subnet               255.255.255.0
Default IP Gateway      192.168.0.1
DHCP Enabled            Yes
DHCP Server             192.168.0.1
DHCP Lease Expires      25575.7534722222
DHCP Lease Obtained     25568.7534722222
MAC Address             11:22:A8:0E:60:1D‬
Driver                  c:\windows\system32\drivers\ndisimplatform.sys (10.0.16299.15, 125.00 KB (128,000 bytes), 9/29/2017 7:41 AM)
                             
---------------------------------------------------------------------------------
Name                    [00000018] Hyper-V Virtual Ethernet Adapter
---------------------------------------------------------------------------------
Adapter Type            Ethernet 802.3
Product Type            Hyper-V Virtual Ethernet Adapter
Installed               Yes
PNP Device ID           ROOT\VMS_MP\0001
Last Reset              43056.8395833333
Index                   18
Service Name            VMSMP
IP Address              192.168.0.100, fe81::240a:4361:fed1:10e8
IP Subnet               255.255.255.0, 64
Default IP Gateway      192.168.0.1
DHCP Enabled            No
DHCP Server             Not Available
DHCP Lease Expires      Not Available
DHCP Lease Obtained     Not Available
MAC Address             ‪10:11:A2:1A:60:9B‬
Driver                  c:\windows\system32\drivers\vmswitch.sys (10.0.16299.15, 1.60 MB (1,677,824 bytes), 9/29/2017 7:41 AM)

Open in new window


So in conclusion, there has to be a change in the update the manner it works with network adapter maybe?

Please advice.
0
JohnBusiness Consultant (Owner)Commented:
One thing I did not ask you to enable was Microsoft Network Adapter Multiplexor Protocol and so I do not know why that driver is there unless Hyper-V needs it. That is probably the case.

Since you reinstalled Hyper-V, I would not be concerned with their adapters. They are probably just fine.
0
Cliff GaliherCommented:
No. There isn't anything in the update. This is a hyper-v configuration issue just as I said. It is not a coincidence those say hyper-v virtual Ethernet adapter.

Uninstalling hyper1v cleaned things up  or so you indicated. Then re-adding it and whatever you did introduced things again. And you didn't run the update (presumably) between uninstalling and reinstalling hyper-v. Yet that broke things. So how you concluded it is the update seems like a predetermined conclusion looking for evidence.

Time to bring in a hyperv consultant and let them help you sort it all out.
0
rayluvsAuthor Commented:
The microsof network adapter multiplexwr is not checked.  The list I sent was from system information >> network>>adapters.

I concluded it’s the update beciase it was working fine prior the updated.  Also I uninstalled it and then installed it.  I was the one who instálales hyper-v in the computer from the beginning.

But it’s just a thought.
0
JohnBusiness Consultant (Owner)Commented:
You know what I would do?   Uninstall Hyper-V completely.

Now run a Windows 10 Repair Install.  Start by keeping everything.

Go to the Media Creation Link

https://www.microsoft.com/en-us/software-download/windows10

Windows 10 is running, so click on the Download button (not Upgrade Button, select Open (Run) but NOT Save. Allow the program to run. Allow drivers to update. Then select Keep Everything.

Now see how your machine runs and only then install Hyper-V
0
rayluvsAuthor Commented:
Don't understand, you want me to reinstall Windows 10 Pro completely?
0
JohnBusiness Consultant (Owner)Commented:
No. A Repair Install for Windows 10 that Keeps Everything will reinstall your operating system, keep all your data (backup first anyway) and keep all your applications. Once done, everything is where you left it. I have done these numerous times. I keep good backups but I have never needed them.

A repair install will fix most things. It will not fix a damaged profile.
0
rayluvsAuthor Commented:
When you say “damaged profile” you mean user profile?

How long is this process of repair?
0
JohnBusiness Consultant (Owner)Commented:
1. Yes - Repair will not fix damaged Windows User profile.
2. Depending on internet, near an hour to download, 30 minutes to update all drivers and prepare the system, then another 30 minutes to do the actual repair. About 2 hours or so in total. After it updates the drivers, it will ask you to choose what to keep. The answer is Everything.
0
rayluvsAuthor Commented:
Understood.

Unfortunately, a repair/re-install of the OS will not guarantee the problem be fixed, which all points to a Hyper-V issue.

Nevertheless, will do this as last result.    

FYI,
I have uninstalled Hyper-V various times and and the result is the same: 1 IP for the PC.
When I reinstall Hyper-V, 3 IPs.

Note:
I have another Windows 10 Pro without version 1709 installed and has Hyper-v and only has 1 IP in the Hyper-V adapter.

So it does point to an issue Hyper-V.  Maybe something new or something need attention for this update.

Anyways, will continue.
0
rayluvsAuthor Commented:
Fixed!

Solution:

  • Deleted all Hyper-V switches
  • Uninstalled Hyper-V
  • Restarted PC
  • Cleaned up registry any orphan register pointing to Hyper-V
  • Deleted folder "C:\ProgramData\Microsoft\Windows\Hyper-V"
  • Re-installed/Re-enables Hyper-V
  • Done!

So what to do to configure correctly or fix the internet connection?  In  conclusion, I don't really think it was the update 1709 per se, as I thought.  However, seems that the process based itself on some sort of current configuration (maybe?).

Anyways, we still have some questions on the new install Hyper-V (now it creates a default Adapter/IP, etc.)  will place it future.

Thanx all!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rayluvsAuthor Commented:
Awarded our entry as best since the process fixed (the programdata folder was key, without deleting this, it problem persisted).
Awarded more to Cliff since it was directed to Hyper-V.
Awarded to john for the assistance and attention.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.