Re: FW: Advice on npcap uninstall

[Daniel Miller <bonsaiviking () gmail com>]

Ed,

Thanks again for this really useful info. Did you happen to use either
the "Fresh Start" or "Reset this PC" options when installing the
Creators Update? I'm working on reproducing the issue here and
hopefully we'll be able to make our next installer robust against this
sort of thing.

Dan

On Mon, Jul 17, 2017 at 2:46 AM, Edmund Marr
<edmund.marr () btopenworld com> wrote:
> Hi,
>
> I found nmap-dev before github, hence the double route.
>
> There may be another possibility -
>
> Perhaps what I found first was actually a perfectly good version of Npcap, but not Winpcap compatible, and the 
> Creator version installation had looked up what application were previously installed, and then installed the default 
> version - so the uninstall of the winpcap compatible version never ran, and files were left behind. It is these files 
> that that the install finds, which makes it think winpcap is installed.
>
> Ed
>
> -----Original Message-----
> From: Daniel Miller [mailto:bonsaiviking () gmail com]
> Sent: 17 July 2017 05:35
> To: Edmund Marr
> Cc: Nmap-dev
> Subject: Re: FW: Advice on npcap uninstall
>
> Ed,
>
> Thanks for this detailed report! We're tracking this issue over at Github, but I see you've already participated in 
> that thread:
> https://github.com/nmap/nmap/issues/906
>
> An initial guess is that the Creators Update to Windows 10 modified the system so that Npcap doesn't detect itself 
> installed, but sees the remnants of the install and assumes they belong to WinPcap. I hope to have a solution to this 
> relatively quickly, but I would encourage you to update to Npcap 0.92 in the meantime, since it has fixes for a few 
> other installation-related issues.
>
> Dan
>
> On Fri, Jul 7, 2017 at 10:50 AM, Edmund Marr <edmund.marr () btopenworld com> wrote:
> > Hi,
> >
> >
> >
> > I was (on Windows 10 64 bit) happily using Npcap 0.86 with the PDP11
> > simulator simh, sometimes regularly sometimes from time to time.
> >
> >
> >
> > I came to use it today after a while of not using it, and it wasn’t working.
> > Just taking the simple path, I did a restart. No joy, so I decided to
> > remove and reinstall.
> >
> >
> >
> > The remove seemed to work, but the reinstall (with WinPcap
> > compatibility) failed, saying that  Winpcap was installed, and would
> > be removed, but its removal failed as WinpCap was not installed in the
> > first place. The same happened with the latest version.
> >
> >
> >
> > I recovered Windows to about 3 weeks ago, but it looks like that was
> > after a recent significant ‘upgrade’ to my Windows 10.
> >
> >
> >
> > It looks as if Microsoft has left me with a half installed,
> > non-running Npcap which does not uninstall cleanly, and what is left
> > messes up a re-install. There are a number of registry entries which
> > mention Npcap (some are for PnPCapabilities though).
> >
> >
> >
> > Are there any particular registry entries I can delete manually that
> > will then allow a fresh install? I can get a full list of those that
> > mention Npcap if it would help.
> >
> >
> >
> > Regards
> >
> >
> >
> > Ed Marr
> >
> >
> > _______________________________________________
> > Sent through the dev mailing list
> > https://nmap.org/mailman/listinfo/dev
> > Archived at http://seclists.org/nmap-dev/
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/