Windows 10 internet access issues?

Have there been problems with win10 and internet?
friend has Lenovo laptop with win10 which lost internet yesterday, it returns "no ip address" or similar message, on wireless or ethernet, my phone connects no problem.
Gf's Dell laptop with win10 has lost internet this evening, niether wireless or ethernet work, first time tried 'ipconfig' it returned a blank next to default gateway, does now return an address.
As you can see my win7 netbook works fine.

If by any chance it's PlusNet then there's a post on the Community Forum HERE

not plusnet, but seems a widespread problem, to tired to do much tonight will have a look tomorrow, cheers for link.

Looks more like TalkTalk.

EE are reporting similar but are rather vague as to circumstances. Is it EE?

i'm on talkTalk , their site is down, but my win7 netbook and phone can access rest of internet, my friend is on some other provider (can't recall name, a lesser known company) all other devises apart from his win10 laptop work.

Edited by burble (Fri 09-Dec-16 08:49:34)

As temp fix on friends have rolled back to last week and disabled auto updates, seems to work ok. Will do same on gf's tonight.

Problem fix described here

http://www.myce.com/news/users-around-world-lose-int...

I'm wondering how people with just 1 PC are going to get this fixed? They can't see the web reports and fixes, and they can't get a corrected update from Microsoft.

Interesting...

In reply to a post by Towerman:

Problem fix described here

http://www.myce.com/news/users-around-world-lose-int...

Well that fixed it on gf's, will update friends when I see him next week.

Edited by burble (Fri 09-Dec-16 19:08:20)

Yes, I've just got back from fixing it on a friend's desktop. His laptop is fine. He's with Virgin Media.

In reply to a post by burble:

In reply to a post by Towerman:

Problem fix described here

http://www.myce.com/news/users-around-world-lose-int...

Well that fixed it on gf's, will update friends when I see him next week.

It may be that this is only a temp fix, gf fired her laptop up again tonight and I had to do the 'fix' again.

I had an update yesterday on 2 machines, wonder if its the fix. Have to say my machines havent been affected.

In reply to a post by Banger:

wonder if its the fix

.. for me it was the usual 'unfix'. Every time my PC is updated the Wi-Fi adapter gets switched off!

In reply to a post by burble:

In reply to a post by burble:

In reply to a post by Towerman:

Problem fix described here

http://www.myce.com/news/users-around-world-lose-int...

Well that fixed it on gf's, will update friends when I see him next week.

It may be that this is only a temp fix, gf fired her laptop up again tonight and I had to do the 'fix' again.

This fix needs to be done ever time the pute is fired up.

In reply to a post by burble:

In reply to a post by burble:

In reply to a post by burble:

... nested quotes trimmed ...

Well that fixed it on gf's, will update friends when I see him next week.

It may be that this is only a temp fix, gf fired her laptop up again tonight and I had to do the 'fix' again.

This fix needs to be done ever time the pute is fired up.

Further to this - SWMBO's laptop had this problem

Sorted it, so it did not come back by following these steps as advised by MS on this link - https://support.microsoft.com/en-gb/help/10741/windo...

To run these networking commands in a command prompt window

In the search box on the taskbar, type Command prompt, press and hold (or right-click) Command prompt, and then select Run as administrator > Yes.
At the command prompt, run the following commands in the listed order, and then check to see if that fixes your connection problem:
Type netsh winsock reset and press Enter.
Type netsh int ip reset and press Enter.
Type ipconfig /release and press Enter.
Type ipconfig /renew and press Enter.
Type ipconfig /flushdns and press Enter.

So far so good - peace and quiet has returned

Edited by Towerman (Tue 13-Dec-16 12:46:30)

Yes, good old Microsoft. Windows 10 Update being blamed.

Update released to fix the update.

I wonder how those with no technical ability or ready access to such ability, free of course, will be able to get to the internet to download the update.

I wonder if many ISPs have seen an increase in their support calls?

I know. I have a feeling my brothers own PC was affected and so I will be around there at the weekend to fix it. People with little technical knowledge or with ready help can have a very difficult time with many areas of technology - unfortunately that is the way of the modern world.

Indeed. Many people round here know me and my willingness to go and help with PC problems. From time to time I'll get a call "so-and-so suggested I call you about this PC problem...". I'm usually able to pop round and help. I regard all such visits as learning experiences, both about the way PCs work, and the way people use them.

As for this Win 10 issue, one of our daughters-in-law, her father, and a good friend nearby, have all been affected.

Up till now have been doing the 'fix' under gf's username, last night I changed to admin to do 'fix', when she booted up tonight it was still working, but after 15mins lost connection, a restart with no other action and it's still ok, will never know now what fixed it.

I'm wondering why only some users, and it seems a relatively small percentage, are affected. What's the difference in their systems?

It's probably a driver issue with some particular NIC.

None of the fixes worked for me. Apparently the December update had failed, common problem it appears. Wifi and ethernet were affected
Rolled back to previous update restored internet connection. Updates downloaded and re-installed, now working fine.

In reply to a post by flippery:

None of the fixes worked for me. Apparently the December update had failed, common problem it appears. Wifi and ethernet were affected
Rolled back to previous update restored internet connection. Updates downloaded and re-installed, now working fine.

As per my earlier post, have you done the 'fix' as admin?
Seems to have worked on gf's, although just after earlier posting it lost t'internet, a reboot with no other action restored it.

In reply to a post by cheshire_man:

I'm wondering why only some users, and it seems a relatively small percentage, are affected. What's the difference in their systems?

Good point! Me too!

I did wonder if it could be only Win 10 Pro as there are far fewer of them. I'm on Home & unaffected. However been unable to get any feedback as to their systems from affected user on my patch.

If my brother's is affected (I think it is but won't know until the weekend) then his is Win 10 home.

I am on Windows 10 Home. Found problem only after the Dec Update had failed to install. Although Wifi problem had been reported prior to dec update. Resolved as previous post.

Two Win 10 Pro machines one wired one wifi, neither were affected.

In reply to a post by Banger:

Two Win 10 Pro machines one wired one wifi, neither were affected.

Did your Dec 2016 Update Install correctly?

Yes, although one machine is taking 15 minutes at the configuring windows updates stage.

Both my PCs are Win 10 Pro, one is up to date with Win 10 V1607. The other I've delayed the AU being applied.

Neither have had the problem.

I can put that idea to bed then

It is said that it had to do with fast start option and an old ip 169 issue.
This maybe why Microsoft said use restart to fix.
Restart does not use fast start option.

In reply to a post by flippery:

It is said that it had to do with fast start option

Which Win 10 has that? My Win 10 Home doesn't.

& what's "an ip 169 issue"?

In reply to a post by XRaySpeX:

In reply to a post by flippery:

It is said that it had to do with fast start option

Which Win 10 has that? My Win 10 Home doesn't.

& what's "an ip 169 issue"?

have a look at power options>choose what the power buttons do>click on change settings that are currently available and you'll see the check box for fast start.
I prefer it unchecked...

When I said I don't have the fast start option, I meant it. I know where to find it if I had it but it ain't there! All that shows is Sleep & Lock.

If hibernation is disabled it will prevent fast start from showing.

In reply to a post by XRaySpeX:

what's "an ip 169 issue"?

When Windows can't obtain an IP address from a DHCP server for an active LAN port (and not assigned as static address) - it will assign it an address starting 169.254 ( link local). So a if your LAN port has address starting 169 it could signify issues connecting to DHCP

I'm not aware of it being disabled. Where would I find it if it is?

Settings / System...Power/Power and Sleep/Additional Power Settings/Choose what the power button does

Simple

Edit: It may be different on the Home version.

Edited by cheshire_man (Fri 16-Dec-16 22:47:37)

From an elevated command prompt type

powercfg /a

for the supported power states

OIC! I think I've sussed it. Y'all taking about lappies; I was talking previously about my Desktop.

However my Win 10 Home lappy with fast start enabled does not suffer from this internet access issue.

I was quoting the route to the option on my desktop.

http://borncity.com/win/2016/12/14/windows-10-v1607-...

better explanation

And that's where I've been looking all this time. There is no "fast start" nor "disable hibernation" on my Win 10 Home Desktop. There is on my Win 10 Home lappy.

The Win 10 Home Desktop was preinstalled from new. The Win 10 Home lappy was an upgrade from Win 8.1.

So why aren't I seeing these things y'all talking about on my Win 10 Home Desktop?

Edited by XRaySpeX (Sat 17-Dec-16 18:35:12)

can't help on the desk top, but can confirm that either the MS update or renewing ipconfig under admin has fixed gf's win10home laptop, has been fine for several days now.

There isn't a GUI option to disable hibernation that I am aware of, it's done through the command line and once it's disabled fast start disappears.

I wonder if you have FastGo as mentioned in this article?

Or perhaps you have no hiberfil.sys file.

I don't have InstantGo on my desktop as far as I know. powercfg /a does not show the Standby (Connected) option. All it shows is:

The following sleep states are available on this system:
Standby (S3)

whereas my lappy shows all of:

The following sleep states are available on this system:
Standby (S3)
Hibernate
Hybrid Sleep
Fast Startup

My desktop has no hiberfil.sys file.

I conclude that my desktop was built w/out Hibernate & therefore w/out Fast Startup.

OK, can get my Win 10 Home desktop to same sleep states as my Win 10 Home lappy by issuing powercfg /h on under an admin command shell. Have since reversed it to put it back to as built.

Can we conclude that there were so few reports of this internet access issue cuz it occurs only after your PC wakes up from hibernation & it has "fast start" enabled? This would exclude many desktops if they were originally built as mine.

Possibly. The comment from MS about doing a Restart to get overt the problem suggests that might be true. As I understand it a Restart does a full reload including reloading the Kernel, and I'd guess, reacquires the various network parameters.

No.

Well this forum has done it again, thank you.

I had no issues with internet access but I had noticed that my Win 10 was taking longer and longer to start up. After finding out how to switch on fast start, (there was an advanced options link on the screen not mentioned above, that needed clicking) it seems to be starting up much faster.

I never cease to be amazed at how clever people are at finding all these obscure (to me at any rate) options

Now I must trail though all the start up programs again, to find out who rel culprits are and whether or not I really need them.

I'm also facing the same issues about the internet.Anyone know how can I fix this issue?