Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Npcap's DiagReport uses Windows 10-only cmdlets #442

Closed
dmiller-nmap opened this issue Dec 16, 2016 · 1 comment
Closed

Npcap's DiagReport uses Windows 10-only cmdlets #442

dmiller-nmap opened this issue Dec 16, 2016 · 1 comment

Comments

@dmiller-nmap
Copy link
Contributor

@dmiller-nmap dmiller-nmap commented Dec 16, 2016

Get-NetAdapter does not work on Windows 7, for instance, resulting in output like:

*************************************************
Network Adapter(s) Info:
*************************************************
Get-NetAdapter : The term 'Get-NetAdapter' is not recognized as the name of a 
cmdlet, function, script file, or operable program. Check the spelling of the 
name, or if a path was included, verify that the path is correct and try again.
At C:\Program Files\Npcap\DiagReport.ps1:111 char:1
+ Get-NetAdapter
+ ~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-NetAdapter:String) [], Comm 
   andNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
@Varunram
Copy link

@Varunram Varunram commented Mar 10, 2017

I don't think there is any easy way to get the network adapter properties without using Net-Adapter. We could write a custom cmdlet and configure it to work with Npcap though.

@fyodor fyodor transferred this issue from nmap/nmap May 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants