none
Problem with Windows Network Diagnostic program

    Question

  • My internet stopped working last night, and I did what I always do which is click the internet icon in the task bar to run the troubleshooting program, and a box appeared in the middle of my screen.  Inside the box it stated,

    An error occurred while troubleshooting.

    An unexpected error has occurred.  The troubleshooting wizard can't continue.

    Package ID: NetworkDiagnostics

    Path:  C:\Windows\diagnostics\system\networking

    Error code: 0x8002801D

    Source:  Engine

    User Robert-PC\Robert

    Context:  Restricted

    I am running as the administrator.  I am using W7 Ultimate x64.  I have googled the error code, and I have not found a fix.  I have never had this happen before and I am at a loss on fixing it.

    Thanks.

     

    Monday, November 29, 2010 7:05 PM

Answers

  • Hi,

     

    Thanks for posting in Microsoft TechNet Forum.

     

    I would like to confirm if this error still occurs when you use another troubleshooting tool.

     

    Due to this error was occurred on last night; you could boot into last good known configurations or perform a System Restore to get back to a previous time point which Windows 7 worked fine. If system restore cannot fix this issue, you can undo system restore.

     

    You could take the following steps to check if it could fix this issue:

     

    1.    Re-registering the DiagPackage.dll.

    1)   Go to Start, select Run, and type:

    2)   regsvr32 DiagPackage.dll

    3)   Hit ENTER

     

    2.  Due to this problem caused by NetworkDiagnostics, you could try to copy the files of C:\Windows\diagnostics\system\networking folder from a normal Windows 7 to your Windows 7. Please backup the system first.

     

    3.  Meanwhile, you could try to Use the System File Checker tool to troubleshoot.

     

    Hope it helps.

     

    Alex Zhao

    TechNet Subscriber Support in forum.

    If you have any feedback on our support, please contact tngfb@microsoft.com

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, November 30, 2010 10:31 AM
    Moderator
  • Alex,

    Thank you very much for your time and the sharing of your knowledge, but I solved the issue.  I had the wrong external backup hard drive connected when I attempted to perform a System Restore.  After connecting the correct drive, all of my restore points were available to select from.  I went back one by one, until I found a point at which the diagnostics program worked successfully.  I only had to go back to the Nov 12, 2010 restore point, so I will see what programs I installed after that point that caused the issue.  Once again, thank you. 

    Friday, December 03, 2010 10:51 PM

All replies

  • Hi,

     

    Thanks for posting in Microsoft TechNet Forum.

     

    I would like to confirm if this error still occurs when you use another troubleshooting tool.

     

    Due to this error was occurred on last night; you could boot into last good known configurations or perform a System Restore to get back to a previous time point which Windows 7 worked fine. If system restore cannot fix this issue, you can undo system restore.

     

    You could take the following steps to check if it could fix this issue:

     

    1.    Re-registering the DiagPackage.dll.

    1)   Go to Start, select Run, and type:

    2)   regsvr32 DiagPackage.dll

    3)   Hit ENTER

     

    2.  Due to this problem caused by NetworkDiagnostics, you could try to copy the files of C:\Windows\diagnostics\system\networking folder from a normal Windows 7 to your Windows 7. Please backup the system first.

     

    3.  Meanwhile, you could try to Use the System File Checker tool to troubleshoot.

     

    Hope it helps.

     

    Alex Zhao

    TechNet Subscriber Support in forum.

    If you have any feedback on our support, please contact tngfb@microsoft.com

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, November 30, 2010 10:31 AM
    Moderator
  • Hello, I don't see Run in the start menu.  I do see the search box.  Do you mean type the string from #2 above at the command prompt?  Unfortunately, I only keep the lastest restore point on my drive, and unfortunately, it also contains the corrupted code. Edit - I ran the strings listed in #2 of your response using an elevated command propmt, and a box popped up that stated: "The module "DiagPackage.dll" failed to load Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .Dll files. The specified module could not be found."
    Tuesday, November 30, 2010 9:24 PM
  • Hi,

     

    Thanks for update.

     

    First, I would like to confirm whether other diagnostic tools can work normally.

     

    Due to this issue is caused by NetworkDiagnostics, to analyze it better, we could use PowerShell module to check if the issue persists:

     

    1.    Please type PowerShell in search box, select Windows PowerShell and open it.

     

    2.    Load the following module9 (type the following words in PowerShell):

     

         Import-Module TroubleshootingPack

     

    3.    Use networking pack:

     

     Get-TroubleshootingPack -Path "C:\Windows\diagnostics\system\Networking" | fl

     

    4.    Start network troubleshoot session:

     

         Get-TroubleshootingPack -Path "C:\Windows\diagnostics\system\Networking" | Invoke-TroubleshootingPack

     

         It should display as following:

     

         Starting network diagnostics......

     

         Instance ID

         Not to be specified outside of MSDT application.

         :

     

    5.    Click Enter key to choose which task we want to perform. For example, we can type “1” to troubleshoot the webconnectivity issue.

     

    Try using the method above to test, and tell us what the result is.

     

    Alex Zhao

    TechNet Subscriber Support in forum.

    If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, December 01, 2010 10:28 AM
    Moderator
  • Thank you for the reply.  I will try your recommendation when I get home this evening (it's 6:00 a.m. where I am).  Just so you know, I no longer have an internet connectivity issue.  The problem with the connection was my ISP (Comcast).  The internet came back on line a few hours later after going down that same night.  My issue is that when I attempted to run the diagnostic troubleshooting program that evening to determine the reason for the disconnect, it would not run (and still will not run).  I will post my results after implementing your suggestion.

    Edit - I opened the Powershell command box.  What came up in the following:

    PS C:\Users\Robert>

    When I type what you listed in #2 above and hit enter, it gives me the same line that I just listed above., so I entered what you have on #3 above.  The following is what came up:

    Path: C:\Windows\diagnostics\system\networking

    ID:  NetworkDiagnostics

    Version:  1.0

    Name:  Windows Network Diagnostics

    Description:  Detect problems with network connectivity.

    Minimum Version:  6.1

    PrivacyLink:  http://go.microsoft.com/fwlink/LinkId=104288

    Supports Client; SupportsServer; SupportsX86; SupportsAmd64; SupportsIA64; RequiresElevation; Interactive - All are true.

    Root causes:  {"%InterfaceName%" doesn't have a valid IP configuration.  Another computer on the network has the same IP address as this computer, "%InterfaceName%" doesnt have a valid IP configuration, "%InterfaceName%" doesnt have a valid IP configuration...}

    FoundRootCauses:

    Interactions:  {Select entry point.  Select the network adapter to diagnose.  Please select the issue Windows should troubleshoot.  What are you trying to do?...}

    ExtensionPoint:  #document

    PS C:\Users\Robert>

    When I type what you listed in #4 above the following comes up in red lettering:

    Invoke-TroubleshootingPack : Library not registered.  <Exception from HRESULTS:  0x8002801D <TYPE_E_LIBNOTREGISTERED>>

    At Line:1 char:102

    +Get-TroubleshootingPack -Path "C:\Windows\diagnostics\system\networking" | Invoke-TroubleshootingPack <<<<

    +CategoryInfo    :   InvalidArgument: <Microsoft.Windows>Diagnostics.DiagPack:DiagPack> [Invoke-TroubleshootingPack], COMException

    +FullyQualifiedErrorId : PackageDiagnoseFailed.Microsoft.Windows.Diagnosis.Command.InvokeTroubleshootingPack

    PS C:\Users\Robert>

    What is my next move?

    Thanks.

     

    Wednesday, December 01, 2010 11:11 AM
  • Hi,

     

    To get more useful information, please tell us what the result is when you use other diagnostics tools.

     

    According to the description of the result above, I suspect the process of running a troubleshooting pack failed. I doubt there are any system files get corrupted. We could perform the following steps to check it:

     

    1.    Use SFC command to check what the result.

     

    2.    Try the method I mentioned above if you have not tried:

         Copy the files of C:\Windows\diagnostics\system\networking folder from a normal Windows 7 to your Windows 7.

    Note: Please backup the system first.

     

    Alex Zhao

    TechNet Subscriber Support in forum.

    If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, December 02, 2010 10:50 AM
    Moderator
  • Hello,

    I have not run any other diagnostic tools.  Please let me know what diagnostic tools you want me to run.  I do not understand what you are suggecting in #1 in your above post.  Could you please explain what is meant by the SFC command?  I will try to copy the file that you mention in #2.  The only other installed copy of Windows 7 Ultimate that I have is 32 bit that is installed on my laptop.  It is the 64 bit version that is installed on my desktop that is giving me the diagnostic problem, but I don't think the diagnostic files would be different....or are they?  I will wait for your answer before attemting to copy the file.

    Thanks!

     

    Thursday, December 02, 2010 12:12 PM
  • I just attempted to run (as an administrator) the Windows Powershell Modules located in the Control Panel under Administrative Tools, and the following took place:

    A command prompt boxed opened  and inside was written:

    WARNING:  File C:\Windows\system32\WindowsPowerShell\v1.0\PSDiagnostics\PSDiagnostics.psm1 cannot be loaded because the execution of scripts is disabled on this system.  Please see "get-help about_signing" for more details.

    When I type "get-help about_signing" at the command prompt PS C:\Windows\System32>, it just gives me the same command line of PS C:\Windows\System32>

    Now what?

    Thanks.

    Thursday, December 02, 2010 10:34 PM
  • Hi,

     

    I would like to confirm whether this issue persists when you check other issues with Troubleshooting tool in Control Panel:

     

    1.    Go to Control Panel\All Control Panel Items\Troubleshooting.

    2.    Click Hardware and Sound and see if the items work. 

     

    I suspect there could be some corrupted system files in your Windows 7; therefore I suggest you use SFC command to check if it works:

     

    Use the System File Checker tool to troubleshoot

     

    Due to system architecture of 32bit and 64bit is different; if you have a Windows 7 64-bit computer, you can try copying the files to the problematic computer.

     

    In addition, regarding your new issue about PSDiagnostics.psm1 cannot be loaded, you could type the following command to check the result:

     

    Set-ExecutionPolicy Unrestricted

     

    Alex Zhao

    TechNet Subscriber Support in forum.

    If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, December 03, 2010 7:47 AM
    Moderator
  • Alex,

    Thank you very much for your time and the sharing of your knowledge, but I solved the issue.  I had the wrong external backup hard drive connected when I attempted to perform a System Restore.  After connecting the correct drive, all of my restore points were available to select from.  I went back one by one, until I found a point at which the diagnostics program worked successfully.  I only had to go back to the Nov 12, 2010 restore point, so I will see what programs I installed after that point that caused the issue.  Once again, thank you. 

    Friday, December 03, 2010 10:51 PM
  • Hi,

     

    Glad to hear that you have fixed this issue.

     

    System Restore is a useful and simple way to fix system issue.  

     

    If you have another question, you could post a new thread, we are willing to help you.

     

    Have a nice day.

     

    Alex Zhao

    TechNet Subscriber Support in forum.

    If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, December 06, 2010 2:07 AM
    Moderator
  • Same issue here.
    Wednesday, June 20, 2012 3:38 AM