A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Windows 10 1803 update died again



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old August 31st 18, 07:32 AM posted to alt.comp.os.windows-10
Tim[_10_]
external usenet poster
 
Posts: 249
Default Windows 10 1803 update died again

This is now the fourth time I have tried to install update 1803, to always
receive the IRQL not equal or less error with ndis.sys.

I have tried just about every solution I can find on the web. This last
time I uninstalled by VPN software and uninstalled all the WAN Miniport
network devices before starting. Still nothing. Anyone have any suggestions
other than installing from scratch?
Ads
  #2  
Old August 31st 18, 12:12 PM posted to alt.comp.os.windows-10
Keith Nuttle
external usenet poster
 
Posts: 1,844
Default Windows 10 1803 update died again

On 8/31/2018 2:32 AM, Tim wrote:
This is now the fourth time I have tried to install update 1803, to always
receive the IRQL not equal or less error with ndis.sys.

I have tried just about every solution I can find on the web. This last
time I uninstalled by VPN software and uninstalled all the WAN Miniport
network devices before starting. Still nothing. Anyone have any suggestions
other than installing from scratch?

After at least as many tries I finally gave up and disable the update
utilities.

My situation is a tablet with only 32GB of storage, that regardless of
how much I strip out the Updater sees as not enough storage.

--
2018: The year we learn to play the great game of Euchre
  #3  
Old August 31st 18, 03:22 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Windows 10 1803 update died again

Tim wrote:
This is now the fourth time I have tried to install update 1803, to always
receive the IRQL not equal or less error with ndis.sys.

I have tried just about every solution I can find on the web. This last
time I uninstalled by VPN software and uninstalled all the WAN Miniport
network devices before starting. Still nothing. Anyone have any suggestions
other than installing from scratch?


They seem to draw an association here between Intel Wifi and VPN add-ons.

https://community.sophos.com/product...---blue-screen

"Mostly, I believe it is all Intel NICS for Wireless
and Wired connections. we've tried old versions of
Intel drivers as well as newer ones.

We also tried to update the TAP driver with no success."

Nothing destabilizes things, like TAP and TUN drivers of
unknown parentage, where the provider has "lost the source"
and so on.

While there are procedures using pnputil or using dism, to
remove drivers (via their INF files in the INF folder),
the question is, what cleans up a TAP or TUN mess ?
Some of those are installed by just dropping a live file into
the system folder.

If you haven't been keeping careful notes, of all the
non-standard things you've been doing to that system...
then "nuke and pave".

It's also possible, that an "amateur night at the Bijou"
software package, installs a TAP or TUN driver, but
doesn't actually have uninstall code when the program
is uninstalled later, just leaving the TAP or TUN
driver sitting there like a discarded salami.

There are many possibilities as to how the mess occurred.
And amateur software developers play a part.

*******

In Device Managers, do Properties on a network hardware
entry, then select Details, then look for UpperFilter
and LowerFilter entries. Perhaps the TAP/TUN show up
there ? Just a wild guess. I don't know how TAP/TUN
work their injection magic, and a filter driver
might be a start at it.

The idea would be, you leave the errant network
device installed, then work on "cleaning its stack"
of stuff that doesn't belong. Only then, remove the
driver for the Wifi or NIC. You need the driver
for the Wifi or NIC to stay there, until you've
gathered as much info as possible about the
TAP/TUN mess.

*******

The most successful networking add-ons here, are
installed by virtual machine hosting softwares.
One of them, puts a separate entry for a virtual
hardware device, next to the other hardware
entries in Device Manager. Which gives you
a visible indication the materials are still
present. I doubt the VPN software was that
sophisticated.

Paul
  #4  
Old August 31st 18, 07:20 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Windows 10 1803 update died again

Paul wrote:
Tim wrote:
This is now the fourth time I have tried to install update 1803, to
always receive the IRQL not equal or less error with ndis.sys.

I have tried just about every solution I can find on the web. This
last time I uninstalled by VPN software and uninstalled all the WAN
Miniport network devices before starting. Still nothing. Anyone have
any suggestions other than installing from scratch?



An interesting breadcrumb.

This update mentions WIFI uses nwifi.sys.

http://support.microsoft.com/help/4346783

The ndis.sys sits above and below nwifi.sys,
as near as I can tell. And ndis.sys has a
control plane in the protocol stack, that
runs up the side of the Wifi miniport driver.
tcpip.sys sits on top of ndis.sys, and maybe
the breakage is at that level.

So it is possible for a Wifi to have broken ndis.sys,
as the two files ndis.sys and nwifi.sys are part
of the same stack.

It doesn't explain how they're packaged though.
ndis.sys might belong to the OS, and be an in-box item.

*******

What you need, is some way to "reset" the stack,
and throw out any garbage that doesn't belong there.
(Deleting the hardware ENUM key can do that. I've
tested that in my Win10 VM, and the system survived
and came back up again.)

And to make that worthwhile, you also need to
prevent your VPN software from "auto-starting"
at boot time. You don't want to touch VPN software
until 1803 is installed. And even then, the migration
logic could be triggering the VPN software during
the install, and enabling it again for the
first reboot into 1803.

Paul
  #5  
Old August 31st 18, 07:42 PM posted to alt.comp.os.windows-10
Tim[_10_]
external usenet poster
 
Posts: 249
Default Windows 10 1803 update died again

Paul wrote in news
Tim wrote:
This is now the fourth time I have tried to install update 1803, to
always receive the IRQL not equal or less error with ndis.sys.

I have tried just about every solution I can find on the web. This
last time I uninstalled by VPN software and uninstalled all the WAN
Miniport network devices before starting. Still nothing. Anyone have
any suggestions other than installing from scratch?


In Device Managers, do Properties on a network hardware
entry, then select Details, then look for UpperFilter
and LowerFilter entries. Perhaps the TAP/TUN show up
there ? Just a wild guess. I don't know how TAP/TUN
work their injection magic, and a filter driver
might be a start at it.


Paul

After I uninstalled all of the WAN Miniports all I had left was the Realtek
PCIe driver. No Wi-Fi here.

Since I needed my VPN I reinstalled it this morning and have the TAP and
all the WAN Miniport entries back again.
  #6  
Old August 31st 18, 07:45 PM posted to alt.comp.os.windows-10
Tim[_10_]
external usenet poster
 
Posts: 249
Default Windows 10 1803 update died again

Paul wrote in news
Paul wrote:
Tim wrote:
This is now the fourth time I have tried to install update 1803, to
always receive the IRQL not equal or less error with ndis.sys.

I have tried just about every solution I can find on the web. This
last time I uninstalled by VPN software and uninstalled all the WAN
Miniport network devices before starting. Still nothing. Anyone have
any suggestions other than installing from scratch?





And to make that worthwhile, you also need to
prevent your VPN software from "auto-starting"
at boot time. You don't want to touch VPN software
until 1803 is installed. And even then, the migration
logic could be triggering the VPN software during
the install, and enabling it again for the
first reboot into 1803.

Paul

That is an interesting point. Since my upgrade was hanging out there ready
to go I could not reboot after uninstalling my VPN software, so even though
I uninstalled it it is quite likely that there were pieces hanging around.
  #7  
Old August 31st 18, 07:49 PM posted to alt.comp.os.windows-10
Tim[_10_]
external usenet poster
 
Posts: 249
Default Windows 10 1803 update died again

=?UTF-8?B?8J+YiSBHb29kIEd1eSDwn5iJ?= wrote in
news

You have been told time after time to leave Windows update as it is.
You don't have to sit in front of your computer just to stare at the
screen as updates and upgrades comes in. It's plain silly to do that.

Have you thought of buying a new machine every time a new upgrade
comes out? It might only be the solution for people like you. Make
sure you buy from DELL so that if it fails within one year, you can
ask them to take away and give you a brand new one. Also tell them
you have serious mental problem to know how to switch it on.

Good luck.



You sir, are an ass. Nowhere did I say anything about sitting in front of
the screen watching nothing while the update didn't do its thing.

And not that it will make any difference to you, I have been supporting
Windows professionaly since 3.1.

And I build my own machines, thank you very much.
  #8  
Old August 31st 18, 08:59 PM posted to alt.comp.os.windows-10
😉 Good Guy 😉
external usenet poster
 
Posts: 1,483
Default Windows 10 1803 update died again

On 31/08/2018 19:49, Tim wrote:

And not that it will make any difference to you, I have been supporting
Windows professionaly since 3.1.


From time to time we get old geezers like you here complaining about
everything new. You seem to be one of them as far as I can see. Why are
you wasting time on Windows 10? It is for young vibrant people who
wants something new. Old Windows is for old people like you who can't
have the brain to learn new things. The grey cells are dead in your
skull and transplant is not possible.


And I build my own machines,


Jesus. You are just a time waster here it seems. Why spend all that
time building something they may or may not work. Are you a product of
a mad cow?

thank you very much.


Thank you for what? For telling you that you are an idiot?



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

 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 01:15 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.