View Single Post
  #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
Ads