Hello Raphael

I had these problems again and again and had to activate the network adapter as an administrator for ages.

I now have the Windows 10 Pro Insider Preview Version Build 14986 rs_ prelelance 161202-1928: and this version actually seems to work…all previous previews did not work with the internet connection. Works with both WiFi and Ethernet. Well, no one knows how long…

Hope this information is helpful for you.

Greetings mazel

@RaphaelG FYI

@heuby @WalterB Setting the IP permanently is not recommended, see here:

[https://www.heise.de/newsticker/melde/Windows-10-Computer-vom-LAN-und-Internet-abschnitt-3567942.html](https://www.heise.de/newsticker/melde/ Windows-10-computer-cut-off-from-LAN-and-internet-3567942.html)

Quote from Heise Online:

Some users also report that manually assigning a fixed LAN IP address resolves the issue. However, it also happens that despite having previously set up a static IP address, Windows 10 also uses an address from the 169 range, switches back and forth between the two uselessly and still does not have a usable IP configuration. Therefore, we do not recommend this method.

The cause could be in the quick start procedure of Windows 10, incorrect caching of the IP configuration or incorrect handling of expired DHCP leases. This suggests that turning off the quick start option helps. This may also explain why the problem does not occur at all in some environments: administrators who have switched off the quick start option on the computers they manage do not notice this problem.

So for me, two laptops installed the update without any problems, only the internet box was smeared again for 15 minutes:smileymad:

The problem is that you can’t apparently turn off automatic updates on all computers and have to leave them on standby.

@user109

I was able to solve the problem with fixed IP addresses for two users without any problems!

---

@WalterB wrote:

I was able to solve the problem with fixed IP addresses for two users without any problems!

---

It was similar for me.

Although Heise is admittedly considered very competent and when it says that you shouldn’t use fixed IP addresses, that’s usually well-founded.

Still, it’s definitely worth a try if the other workarounds don’t work. Maybe Microsoft will get it done by next patch day (December 13th). The whole thing is pretty frustrating.

I assigned a fixed IP to two computers… even before this bug and it works perfectly

I suspect the problem with the fixed IP addresses may have something to do with activating the quick start because it is deactivated for me and others!

@WalterB it was also in the first sentence that it can work with a fixed IP, but that only partially fixed the problem (it can work, but doesn’t have to) @heuby has already said : Heise-Verlag is a very reputable publisher with IT professional editors who know what they are writing.

So it’s best to deactivate the quick start function in Windows.

Microsoft recommends restarting your PC

Don’t turn it off, just restart it.

Why: Windows does not shut down the system completely and the incorrect network settings are cached and written back into the system when it boots.

https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/problems-connecting-to-the-internet/f121306e-fab5-411d-833f-e4490ecb8b5c

Strangely enough, I not have this problem!

- KB3201845 has been there since last night.

- Fast startup in power options is enabled

- The computer was both restarted and completely switched off

- Windows 10 Pro 64 is in use

The network configuration looks like this:

- ASUS USB-AC53 802.11ac Wireless USB Adapter, AP is an ASUS RT-AC66U

- Except for the “Microsoft multiplexor protocol…” all protocols are activated (even IPv6, I have no idea why, I thought that was out…).

- DHCP active, IP, DNS etc. everything on automatic

- The internal, wired network adapter is used for control (no connection to the router, Internet, etc.) and is reduced to IP v4 and has a fixed IP address.

However, Google DNS is entered in the Swisscom router! (this may be the only “anomaly”)

Router is the thing here, I deactivated IP v6 on Swisscom at some point.

Technical Readout Number Item Details

I recommend only using Apple Mac OS…:cathappy:

Hello

For me it was enough to log in with the original administrator account!

The restricted user account also worked afterwards.

Good luck!

But it will be quite difficult with Windows Home

@Lorenzo - Thanks for the tip

I can only repeat. Restarting your PC is enough!

Shutting down and restarting does not have the same effect as restarting unless the Quickboot option is disabled.

Alternatively, the Shift key can be pressed while pressing shutdown. Then the computer shuts down completely and not in hybrid mode. -> But I didn’t test it because I don’t have Win 10.

I just installed the updates 100%, restarted and it worked without any problems.

I’ve had the problems described for about a week. Yesterday I “installed” KB3201845 and haven’t had any problems since.

---

@hed wrote:

I had the problems described for about a week. Yesterday I “installed” KB3201845 and haven’t had any problems since.

---

Interesting insight!

It’s amazing that your problem was solved with the update (and existed before). Maybe there are two problems. I remember that my InternetBox received an update last Tuesday and restarted.

Maybe your problem only arose with the update of the InternetBox and has now been resolved with the Windows Update?

Please no one should feel offended by this hypothesis.

Checking whether the InternetBox has the latest firmware and whether Windows Update has been installed certainly doesn’t hurt.

Hello, I’ve read somewhere that only W10 1607 version with 4GB RAM might have the issue, can’t find where I’ve read this. But I have no problems on my

- surface book 8GB RAM 1607 14393.479 - KB3201845

- lenovo thinkpad10 4GB RAM 14393.479 - KB3201845

- HP envy 8″ 2GB RAM 14393.447

EDIT:

I’ve solved the issue on a PC from a friend with the “shift” + “power down” procedure