Skip to main content

PowerShell check network adapters error


How to check network adapters for error?

How to whether network device is working properly?

How to diagnose specific errors in network adapters?

How to check whether network device driver registry is corrupted?

To all of the questions above, PowerShell will come to the rescue.

In Windows Task Scheduler the only thing you want to see 0X0, which basically means operation has completed successfully. Other than 0X0 means something went wrong and needs to hone your troubleshooting skills.

For network adapters it goes the same way as well. PowerShell script below reads the Windows 

Configuration Manager error code and display specific errors for network adapters issue.

Below is the table from MSDN that shows values for Windows Configuration Manager errors.

MSDN link: https://msdn.microsoft.com/en-s/library/aa394216%28v=vs.85%29.aspx#properties

Windows Configuration Manager error code.
Value
Meaning
0 (0x0)
Device is working properly.
1 (0x1)
Device is not configured correctly.
2 (0x2)
Windows cannot load the driver for this device.
3 (0x3)
Driver for this device might be corrupted, or the system may be low on memory or other resources.
4 (0x4)
Device is not working properly. One of its drivers or the registry might be corrupted.
5 (0x5)
Driver for the device requires a resource that Windows cannot manage.
6 (0x6)
Boot configuration for the device conflicts with other devices.
7 (0x7)
Cannot filter.
8 (0x8)
Driver loader for the device is missing.
9 (0x9)
Device is not working properly. The controlling firmware is incorrectly reporting the resources for the device.
10 (0xA)
Device cannot start.
11 (0xB)
Device failed.
12 (0xC)
Device cannot find enough free resources to use.
13 (0xD)
Windows cannot verify the device's resources.
14 (0xE)
Device cannot work properly until the computer is restarted.
15 (0xF)
Device is not working properly due to a possible re-enumeration problem.
16 (0x10)
Windows cannot identify all of the resources that the device uses.
17 (0x11)
Device is requesting an unknown resource type.
18 (0x12)
Device drivers must be reinstalled.
19 (0x13)
Failure using the VxD loader.
20 (0x14)
Registry might be corrupted.
21 (0x15)
System failure. If changing the device driver is ineffective, see the hardware documentation. Windows is removing the device.
22 (0x16)
Device is disabled.
23 (0x17)
System failure. If changing the device driver is ineffective, see the hardware documentation.
24 (0x18)
Device is not present, not working properly, or does not have all of its drivers installed.
25 (0x19)
Windows is still setting up the device.
26 (0x1A)
Windows is still setting up the device.
27 (0x1B)
Device does not have valid log configuration.
28 (0x1C)
Device drivers are not installed.
29 (0x1D)
Device is disabled. The device firmware did not provide the required resources.
30 (0x1E)
Device is using an IRQ resource that another device is using.
31 (0x1F)
Device is not working properly. Windows cannot load the required device drivers.

Here’s the script to check network adapters for any issues:

================================================

$nics_error = Get-WmiObject -class Win32_NetworkAdapter


foreach ($nic_values in $nics_error) {
     "Device name is: " + $nic_values.Name + " and Windows Configuration Manager error code is: " +  $nic_values.ConfigManagerErrorCode
}

================================================ 


Sample output:

Device name is: WAN Miniport (IP) and Windows Configuration Manager error code is: 0
Device name is: WAN Miniport (IPv6) and Windows Configuration Manager error code is: 0
Device name is: WAN Miniport (Network Monitor) and Windows Configuration Manager error code is: 0
Device name is: RAS Async Adapter and Windows Configuration Manager error code is: 0
Device name is: Microsoft ISATAP Adapter #2 and Windows Configuration Manager error code is: 0
Device name is: Teredo Tunneling Pseudo-Interface and Windows Configuration Manager error code is: 0
Device name is: Microsoft ISATAP Adapter #3 and Windows Configuration Manager error code is: 0
Device name is: VMware Virtual Ethernet Adapter for VMnet1 and Windows Configuration Manager error code is: 0
Device name is: VMware Virtual Ethernet Adapter for VMnet8 and Windows Configuration Manager error code is: 0
Device name is: Microsoft ISATAP Adapter #4 and Windows Configuration Manager error code is: 0


Cheers.. Hope it helps..

=====================

Catholic Rosary Guide  for Android:
Pray the Rosary every day, countless blessings will be showered upon your life if you recite the Rosary faithfully. 
https://play.google.com/store/apps/details?id=com.myrosaryapp

http://quickbytesstuff.blogspot.sg/2014/09/how-to-recite-rosary.html

Divine Mercy Chaplet Guide (A Powerful prayer) BFF = Be Filled Faith:


Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more