WIndows10 Home: No internet connection

On Sun, 04 Feb 2018 14:07:13 -0500, Paul wrote:

https://blogs.technet.microsoft.com/...4/01/15/using-
powershell-to-find-connected-network-adapters/

In there I saw the following command:

"neŧsh interface ipv4 show interfaces"

which coughed up the following output in tabular form which is easier
shown here as
follows:

"Idx=1 Met=50 MTU=4294967295 State=Connected Name=Loopback Pseudo-
Interface 1"

(No mention of Ethernet or WiFi)

Regards,
--
/\/\aurice
(Replace "nomail.afraid" by "bcs" to reply by email)

Maurice wrote:
On Sun, 04 Feb 2018 14:07:13 -0500, Paul wrote:

https://blogs.technet.microsoft.com/...4/01/15/using-
powershell-to-find-connected-network-adapters/

In there I saw the following command:

"neŧsh interface ipv4 show interfaces"

which coughed up the following output in tabular form which is easier
shown here as
follows:

"Idx=1 Met=50 MTU=4294967295 State=Connected Name=Loopback Pseudo-
Interface 1"

(No mention of Ethernet or WiFi)

Regards,

That's an artifact of the network stack, and not hardware that registered.
Loopback is related to "localhost" and "127.0.0.x" and friends. Everyone
should have that same entry.

*******

Did you try any of the other commands ? I'm hoping the ones
that claim to show "disabled" items will work.

Otherwise, you could re-install the proprietary network driver and
see what happens. For example, my Intel '579 receives a Windows driver
when you install Windows 10, but the tabs in Device Manager for such
a network item are missing. You cannot set any of the custom NDIS
parameters that way.

Whereas if I hunt down the Intel Pro driver package, and install
that, it puts an extra tab or two in the Device Manager properties,
which allows "offloading" to be enabled, or "interrupt reduction"
(squeezing the servicing of multiple packets, into one interrupt event).
That sort of thing.

If you have a RealTek NIC, the RealTek site has drivers.
RealTek is generous with their drivers. Some other companies
aren't nearly as helpful. There are specific RealTek NICs (PCI bus)
to be avoided (like the one that drives a Linux distro
nuts here, so you can't do anything - it's some sort
of interrupt loop behavior - Windows shows similar issues
but doesn't loop like that). It's possible the PCI Express
ones are OK.

Paul

On Sun, 04 Feb 2018 15:50:23 -0500, Paul wrote:

f you have a RealTek NIC, the RealTek site has drivers.
RealTek is generous with their drivers.

WIll take a look there; thank you.

There are specific RealTek NICs (PCI bus)
to be avoided (like the one that drives a Linux distro nuts here, so you
can't do anything - it's some sort of interrupt loop behavior

Presumably that is when the Linux version is installed into a Linux
install.

In my case it would be a Windows10 in a Windows10 install.

One puzzling thing here on this W10 is that it managed to re-find the
Realtek
network adaptors after I had uninstalled them, yet elsewhere the system
says "No
network adaptors found" !!

Regards,
--
/\/\aurice
(Replace "nomail.afraid" by "bcs" to reply by email)

On 05/02/2018 16:32, Maurice wrote:
In my case it would be a Windows10 in a Windows10 install. One
puzzling thing here on this W10 is that it managed to re-find the
Realtek network adaptors after I had uninstalled them, yet elsewhere
the system says "No network adaptors found" !! Regards,

How long has this been going on? Why don't you reformat the HD and
start again? You've wasted nearly a month on this problem and still no
resolution.

The choice is pretty clear:

1) Reinstall Windows 10 and start again;
2) pay somebody to fix it for you.

I hope you don't start blaming Microsoft like most stupid people here
do. they don't like Microsoft but they continue to use Microsoft
products. They should be using Linux where they'll find like mined
people with no problems!!!!!!!!

Windows 10 is not for everybody and that is why Microsoft has stopped
giving away free OS to nutters and people of low intelligence who didn't
go for it from day one.





--
With over 600 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

On Tue, 06 Feb 2018 00:43:49 +0000, Good Guy wrote:

How long has this been going on? Why don't you reformat the HD and
start again?

Too long!

Not re-starting from empty machine, as I have non-Windows apps running on
the laptop
and they have higher priority.

Well, the Windows10 problem appeared after I had stifled an update that
ignored my
'ignore updates' setting, so in a way it's my fault...

But the resulting mess (e.g. one part of W10 finds the network adaptors
but another
says there are none) looks as though there is a left-hand/right-hand
problem in
there somewhere.

So if no solution will just leave it as it is. At least I can do non-
internet
things if needed for dual-booting adjustment purposes.
It's just that I would have liked to be able to run 1 or 2 apps when
away from
base that I otherwise now have to run on my Windows7 on desktop back at
base.

Regards,
--
/\/\aurice
(Replace "nomail.afraid" by "bcs" to reply by email)

On 2/6/2018 7:22 AM, Maurice wrote:
On Tue, 06 Feb 2018 00:43:49 +0000, Good Guy wrote:

How long has this been going on? Why don't you reformat the HD and
start again?

Too long!

Not re-starting from empty machine, as I have non-Windows apps running on
the laptop
and they have higher priority.

Well, the Windows10 problem appeared after I had stifled an update that
ignored my
'ignore updates' setting, so in a way it's my fault...

But the resulting mess (e.g. one part of W10 finds the network adaptors
but another
says there are none) looks as though there is a left-hand/right-hand
problem in
there somewhere.

So if no solution will just leave it as it is. At least I can do non-
internet
things if needed for dual-booting adjustment purposes.
It's just that I would have liked to be able to run 1 or 2 apps when
away from
base that I otherwise now have to run on my Windows7 on desktop back at
base.

Regards,

I'll admit I did not read every entry in this saga so my suggestion
might already have been tried and found wanting.

Rather than going into the networking menu's try going Control
Panel|System|Device Manager and scroll down to Network Adapters, if it's
present. If the Network Adapters option is not present as a hardware
device then don't bother reading any further...

Then locate any network adapters and tell the system to uninstall them.
The first time just do that and then do a reboot and let the system
re-learn any network card(s). With luck this will fix things for you as
it may force the software parts of windows to take a new look at things.

If it does not work the first time, try it again but when it asks tell
it to also delete any drivers associated with any network hardware it
displayed. Then try a reboot. With luck Windows will find the hardware
and try different drivers, if needed.

I have had to do this a on a number of machines after Microsoft
installed the wrong drivers during one of it's many "updates". True the
roll back to an older driver might work as well but by the time I get
asked to "fix" someone's machine they have usually already loaded the
same incorrect driver a number of times...

On Tue, 06 Feb 2018 23:39:27 -0600, GlowingBlueMist wrote:

If it does not work the first time, try it again but when it asks tell
it to also delete any drivers associated with any network hardware it
displayed. Then try a reboot. With luck Windows will find the hardware
and try different drivers, if needed.

Tried that, but - alas - still in the same boat... :-(

But many thanks for the info - much appreciated!

Regards,
--
/\/\aurice
(Replace "nomail.afraid" by "bcs" to reply by email)

GlowingBlueMist wrote:
On 2/6/2018 7:22 AM, Maurice wrote:
On Tue, 06 Feb 2018 00:43:49 +0000, Good Guy wrote:

How long has this been going on? Why don't you reformat the HD and
start again?

Too long!
Not re-starting from empty machine, as I have non-Windows apps
running on
the laptop
and they have higher priority.

Well, the Windows10 problem appeared after I had stifled an update that
ignored my
'ignore updates' setting, so in a way it's my fault...

But the resulting mess (e.g. one part of W10 finds the network adaptors
but another
says there are none) looks as though there is a left-hand/right-hand
problem in
there somewhere.

So if no solution will just leave it as it is. At least I can do non-
internet
things if needed for dual-booting adjustment purposes.
It's just that I would have liked to be able to run 1 or 2 apps when
away from
base that I otherwise now have to run on my Windows7 on desktop back at
base.

Regards,

I'll admit I did not read every entry in this saga so my suggestion
might already have been tried and found wanting.

Rather than going into the networking menu's try going Control
Panel|System|Device Manager and scroll down to Network Adapters, if it's
present. If the Network Adapters option is not present as a hardware
device then don't bother reading any further...

Then locate any network adapters and tell the system to uninstall them.
The first time just do that and then do a reboot and let the system
re-learn any network card(s). With luck this will fix things for you as
it may force the software parts of windows to take a new look at things.

If it does not work the first time, try it again but when it asks tell
it to also delete any drivers associated with any network hardware it
displayed. Then try a reboot. With luck Windows will find the hardware
and try different drivers, if needed.

I have had to do this a on a number of machines after Microsoft
installed the wrong drivers during one of it's many "updates". True the
roll back to an older driver might work as well but by the time I get
asked to "fix" someone's machine they have usually already loaded the
same incorrect driver a number of times...

Do you happen to know what "step" causes the freshly installed
hardware to "register" with the networking subsystem ?

There seems to be a gap, between having a "healthy looking"
Device Manager entry, and having a Networking entry show
up for Ethernet or whatever.

Reinstalling the Ethernet driver, you would think that would
repeat the registration process. Why wouldn't that be working
I wonder ? Now, the slightly funny part, is on my machine the
wired connection is called just "Ethernet", instead of
"Network Connection 2" or "Network Connection 3". There's
an implication here, that the registration scheme is
static or something, in Windows 10. I see no way to "request"
a new Network Connection be made.

I'd be tempted to run Sysinternals ProcMon, while the proprietary
network install utility is running, and see what files or
registry entries it's writing to. Just to get some idea
where things should go. Then see if the install is actually
failing, go look in Event Viewer for "hints" that some other
part of the OS doesn't like the new material it's getting.

It could even be some specific service, that if it's
not running, *nothing* registers at run time, and that's
why it's broken. Maybe a happy afternoon going through
Services will highlight something.

Paul