Share via

Netsh failing in Windows 11 Version 10.0.22621.674

Anonymous
2022-11-11T19:56:27+00:00

I was having issues with my VPN client not connecting properly. After doing some troubleshooting I went to run netsh winsock reset

(yes, I know I misspelled "winsock" above... regardless the issue remains.

which as you can see did not have the normal response.. after further investigation any netsh command would fail similarly

results in the following event log error entry
Faulting application name: netsh.exe, version: 10.0.22621.1, time stamp: 0x13af0815

Faulting module name: netsh.exe, version: 10.0.22621.1, time stamp: 0x13af0815

Exception code: 0xc0000005

Fault offset: 0x0000000000005399

Faulting process id: 0x0x5360

Faulting application start time: 0x0x1D8F60670F5B08B

Faulting application path: C:\Windows\System32\netsh.exe

Faulting module path: C:\Windows\System32\netsh.exe

Report Id: 3ad62a91-e990-435e-94d1-89becf3c1884

Faulting package full name: 

Faulting package-relative application ID: 

and one information entry

Fault bucket 2282702454688773064, type 4

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: netsh.exe

P2: 10.0.22621.1

P3: 13af0815

P4: netsh.exe

P5: 10.0.22621.1

P6: 13af0815

P7: c0000005

P8: 0000000000005399

P9: 

P10: 

Attached files:

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8e619298-d65f-4da8-934c-8c5ad6bb726b.tmp.dmp

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.44657116-c68d-4624-ad92-97f870307eaa.tmp.WERInternalMetadata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.65232648-4d8c-432a-97c7-b99afdbb9c02.tmp.csv

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f0aab694-c135-4936-bfb4-d94fc29b04ca.tmp.txt

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.24593dea-8876-4a5f-9c9c-ee1cb441d513.tmp.xml

These files may be available here:

\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_netsh.exe_99874bff378d5dac2ac1a2cb48fba6e286be97_2659a3f9_0fd41451-ac8f-4e08-bb9a-62457fc31b41

Analysis symbol: 

Rechecking for solution: 0

Report Id: 3ad62a91-e990-435e-94d1-89becf3c1884

Report Status: 268435456

Hashed bucket: 108b6971987b1ea16fadc9c9cba2f3c8

Cab Guid: 0

Windows for home | Windows 11 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

7 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-01-04T15:08:55+00:00

    I had the exact same issue after installing RSAT (Remote Server Administration tools)

    This is **** , Microsoft must fix this issue.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  2. Anonymous
    2022-12-22T14:32:33+00:00

    We had the same issue, but after removing the RSAT tools, the netsh command is now working.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  3. Anonymous
    2023-02-01T13:18:23+00:00

    Hi All,

    Recently we have upgraded our Windows11 (22H2 build 22621.1105) from Windows10 and after the upgrade, netsh.exe is stopped working and this was the main component for SDP VPN that we are using.

    we have tried to repair the windows using sfc scan and etc but no luck.

    Any suggestions how we can resolve this issue?

    Event Log screenshot:

    Log Name:      Application

    Source:        Application Error

    Date:          1/31/2023 3:24:34 PM

    Event ID:      1000

    Task Category: Application Crashing Events

    Level:         Error

    Keywords:      

    User:          MIC\a2-adshaikh

    Computer:      LTPAUH-PK1LSZ7w.xxxxxxxxx

    Description:

    Faulting application name: netsh.exe, version: 10.0.22621.1, time stamp: 0x13af0815

    Faulting module name: netsh.exe, version: 10.0.22621.1, time stamp: 0x13af0815

    Exception code: 0xc0000005

    Fault offset: 0x0000000000005399

    Faulting process id: 0x0x3E50

    Faulting application start time: 0x0x1D935669842F58D

    Faulting application path: C:\Windows\System32\netsh.exe

    Faulting module path: C:\Windows\System32\netsh.exe

    Report Id: 9f6c1cea-07bc-4281-89ef-dc3595d631f3

    Faulting package full name: 

    Faulting package-relative application ID: 

    Event Xml:

    <Event xmlns=http://schemas.microsoft.com/win/2004/08/events/event>

      <System>

        <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />

        <EventID>1000</EventID>

        <Version>0</Version>

        <Level>2</Level>

        <Task>100</Task>

        <Opcode>0</Opcode>

        <Keywords>0x8000000000000000</Keywords>

        <TimeCreated SystemTime="2023-01-31T11:24:34.9774308Z" />

        <EventRecordID>4924</EventRecordID>

        <Correlation />

        <Execution ProcessID="20748" ThreadID="6444" />

        <Channel>Application</Channel>

        <Computer>LTPAUH-PK1LSZ7w.mic.mubadala.cloud</Computer>

        <Security UserID="S-1-5-21-1877474138-1686948599-2071293619-1521" />

      </System>

      <EventData>

        <Data Name="AppName">netsh.exe</Data>

        <Data Name="AppVersion">10.0.22621.1</Data>

        <Data Name="AppTimeStamp">13af0815</Data>

        <Data Name="ModuleName">netsh.exe</Data>

        <Data Name="ModuleVersion">10.0.22621.1</Data>

        <Data Name="ModuleTimeStamp">13af0815</Data>

        <Data Name="ExceptionCode">c0000005</Data>

        <Data Name="FaultingOffset">0000000000005399</Data>

        <Data Name="ProcessId">0x3e50</Data>

        <Data Name="ProcessCreationTime">0x1d935669842f58d</Data>

        <Data Name="AppPath">C:\Windows\System32\netsh.exe</Data>

        <Data Name="ModulePath">C:\Windows\System32\netsh.exe</Data>

        <Data Name="IntegratorReportId">9f6c1cea-07bc-4281-89ef-dc3595d631f3</Data>

        <Data Name="PackageFullName">

        </Data>

        <Data Name="PackageRelativeAppId">

        </Data>

      </EventData>

    </Event>

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-11-14T22:12:27+00:00

    I could not run your suggestions as netsh was crashing, hence the netsh winsock reset wouldn't run or work. ipconifg's run, but are irrelevant to the problem.

    Anyway, I ended up rolling back to win 10, then re-updating to win 11 22H1 which seemed to resolve the issue. I believe this is a problem with win 11 22H2 which is what I was on..

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  5. Anonymous
    2022-11-12T03:33:04+00:00

    Hello Rob Kopp,

    Welcome to Microsoft Community.

    I understand that your VPN client is unable to connect and is experiencing problems resetting the network.

    Does your VPN client have any error messages about not being able to connect?

    You can try resetting the network again using the following command.

    Search CMD, open the command prompt (administrator)

    In the command box that pops up, type 

    ipconfig /release

    Press the Enter key.

    Type 

    ipconfig /renew

    Press the Enter key.

    Type 

    ipconfig /flushdns

    Press the Enter key.

    Type 

    netsh int ip reset

    Press enter.

    Type 

    netsh winsock reset

    Press Enter.

    Restart the computer and see if the problem is solved.

    If the above commands still do not reset the network and you are currently experiencing problems with VPN not connecting, I hate to give you bad news, but this question is out of reach of the response support community. The best place to get help with network is Microsoft Learn(English only), which aims to support more advanced users like you.

    Here is a link to the forum where you can raise specific scenarios and share your idea to help solve the problem.

    I won't be able to help you, but I'll leave that question open in case one of our amazing volunteers has ideas for you.

    If there is anything not clear, please do not hesitate to let me know.

    Best Regards,

    Lenka-MSFT| Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments