How to reset TCP/IP on Windows 8.1?
up vote
1
down vote
favorite
The following netsh command is not working on Windows 8.1.
netsh int ipv4 reset
It give “Access Denied” error and it is a VERY known issue, many people complaining about it all ove online forums.
There is no known equivalent PowerShell command.
One tedious solution is to use Process Monitor and track the registry that it needs to have
access to and grant access. This is not practical since the registry key includes a random guid on each machine.
What is the practical remedy for this?
Update:
@grawity, I tried the command in the elevated mode - Of course
networking powershell windows-8.1 netsh
|
show 3 more comments
up vote
1
down vote
favorite
The following netsh command is not working on Windows 8.1.
netsh int ipv4 reset
It give “Access Denied” error and it is a VERY known issue, many people complaining about it all ove online forums.
There is no known equivalent PowerShell command.
One tedious solution is to use Process Monitor and track the registry that it needs to have
access to and grant access. This is not practical since the registry key includes a random guid on each machine.
What is the practical remedy for this?
Update:
@grawity, I tried the command in the elevated mode - Of course
networking powershell windows-8.1 netsh
PowerShell?netsh
is a standalone command, it should work in any shell.
– grawity
Dec 6 '13 at 21:18
1
What is the problem you are trying to solve with this command? Perhaps there is a different approach.
– Paul
Dec 6 '13 at 22:07
@Paul: This command fixes many networking issues and rebuilds all P stack registry settings. I have been in many situations where the network access was slow or not working and this command did the magic. The fact that it stopped working on Win8.1 should not force us to question its use.
– Allan Xu
Dec 7 '13 at 2:14
4
...did you run it in an elevated shell or a regular one?
– grawity
Dec 7 '13 at 14:16
1
@AllanXu I am not questioning its use but it sounds like a driver issue from your description, and so addressing the underlying issue is an alternative approach to solving the problem.
– Paul
Dec 8 '13 at 20:53
|
show 3 more comments
up vote
1
down vote
favorite
up vote
1
down vote
favorite
The following netsh command is not working on Windows 8.1.
netsh int ipv4 reset
It give “Access Denied” error and it is a VERY known issue, many people complaining about it all ove online forums.
There is no known equivalent PowerShell command.
One tedious solution is to use Process Monitor and track the registry that it needs to have
access to and grant access. This is not practical since the registry key includes a random guid on each machine.
What is the practical remedy for this?
Update:
@grawity, I tried the command in the elevated mode - Of course
networking powershell windows-8.1 netsh
The following netsh command is not working on Windows 8.1.
netsh int ipv4 reset
It give “Access Denied” error and it is a VERY known issue, many people complaining about it all ove online forums.
There is no known equivalent PowerShell command.
One tedious solution is to use Process Monitor and track the registry that it needs to have
access to and grant access. This is not practical since the registry key includes a random guid on each machine.
What is the practical remedy for this?
Update:
@grawity, I tried the command in the elevated mode - Of course
networking powershell windows-8.1 netsh
networking powershell windows-8.1 netsh
edited Dec 7 '13 at 23:25
asked Dec 6 '13 at 20:36
Allan Xu
2702312
2702312
PowerShell?netsh
is a standalone command, it should work in any shell.
– grawity
Dec 6 '13 at 21:18
1
What is the problem you are trying to solve with this command? Perhaps there is a different approach.
– Paul
Dec 6 '13 at 22:07
@Paul: This command fixes many networking issues and rebuilds all P stack registry settings. I have been in many situations where the network access was slow or not working and this command did the magic. The fact that it stopped working on Win8.1 should not force us to question its use.
– Allan Xu
Dec 7 '13 at 2:14
4
...did you run it in an elevated shell or a regular one?
– grawity
Dec 7 '13 at 14:16
1
@AllanXu I am not questioning its use but it sounds like a driver issue from your description, and so addressing the underlying issue is an alternative approach to solving the problem.
– Paul
Dec 8 '13 at 20:53
|
show 3 more comments
PowerShell?netsh
is a standalone command, it should work in any shell.
– grawity
Dec 6 '13 at 21:18
1
What is the problem you are trying to solve with this command? Perhaps there is a different approach.
– Paul
Dec 6 '13 at 22:07
@Paul: This command fixes many networking issues and rebuilds all P stack registry settings. I have been in many situations where the network access was slow or not working and this command did the magic. The fact that it stopped working on Win8.1 should not force us to question its use.
– Allan Xu
Dec 7 '13 at 2:14
4
...did you run it in an elevated shell or a regular one?
– grawity
Dec 7 '13 at 14:16
1
@AllanXu I am not questioning its use but it sounds like a driver issue from your description, and so addressing the underlying issue is an alternative approach to solving the problem.
– Paul
Dec 8 '13 at 20:53
PowerShell?
netsh
is a standalone command, it should work in any shell.– grawity
Dec 6 '13 at 21:18
PowerShell?
netsh
is a standalone command, it should work in any shell.– grawity
Dec 6 '13 at 21:18
1
1
What is the problem you are trying to solve with this command? Perhaps there is a different approach.
– Paul
Dec 6 '13 at 22:07
What is the problem you are trying to solve with this command? Perhaps there is a different approach.
– Paul
Dec 6 '13 at 22:07
@Paul: This command fixes many networking issues and rebuilds all P stack registry settings. I have been in many situations where the network access was slow or not working and this command did the magic. The fact that it stopped working on Win8.1 should not force us to question its use.
– Allan Xu
Dec 7 '13 at 2:14
@Paul: This command fixes many networking issues and rebuilds all P stack registry settings. I have been in many situations where the network access was slow or not working and this command did the magic. The fact that it stopped working on Win8.1 should not force us to question its use.
– Allan Xu
Dec 7 '13 at 2:14
4
4
...did you run it in an elevated shell or a regular one?
– grawity
Dec 7 '13 at 14:16
...did you run it in an elevated shell or a regular one?
– grawity
Dec 7 '13 at 14:16
1
1
@AllanXu I am not questioning its use but it sounds like a driver issue from your description, and so addressing the underlying issue is an alternative approach to solving the problem.
– Paul
Dec 8 '13 at 20:53
@AllanXu I am not questioning its use but it sounds like a driver issue from your description, and so addressing the underlying issue is an alternative approach to solving the problem.
– Paul
Dec 8 '13 at 20:53
|
show 3 more comments
2 Answers
2
active
oldest
votes
up vote
0
down vote
With Powershell you could almost make your own command. Something like this might help:
$netadapt = Get-CimInstance CIM_NetworkAdapter | ? {$_.AdapterType -eq "Ethernet 802.3"}
$netadapt.Disable()
$netadapt.Enable()
The only caveat with this is that it's going to reset all network adapters that are "Ethernet 802.3". If that's an issue you can substitute $_.AdapterType
with $_.name
and also replace "Ethernet 802.3"
with an actual device name e.g. "Intel(R) 82579V Gigabit Network Connection."
add a comment |
up vote
-1
down vote
You can solve this problem with PowerShell. Just run the command:
Remove-NetIPAddress
It worked to me
– user379638
Oct 14 '14 at 19:28
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
With Powershell you could almost make your own command. Something like this might help:
$netadapt = Get-CimInstance CIM_NetworkAdapter | ? {$_.AdapterType -eq "Ethernet 802.3"}
$netadapt.Disable()
$netadapt.Enable()
The only caveat with this is that it's going to reset all network adapters that are "Ethernet 802.3". If that's an issue you can substitute $_.AdapterType
with $_.name
and also replace "Ethernet 802.3"
with an actual device name e.g. "Intel(R) 82579V Gigabit Network Connection."
add a comment |
up vote
0
down vote
With Powershell you could almost make your own command. Something like this might help:
$netadapt = Get-CimInstance CIM_NetworkAdapter | ? {$_.AdapterType -eq "Ethernet 802.3"}
$netadapt.Disable()
$netadapt.Enable()
The only caveat with this is that it's going to reset all network adapters that are "Ethernet 802.3". If that's an issue you can substitute $_.AdapterType
with $_.name
and also replace "Ethernet 802.3"
with an actual device name e.g. "Intel(R) 82579V Gigabit Network Connection."
add a comment |
up vote
0
down vote
up vote
0
down vote
With Powershell you could almost make your own command. Something like this might help:
$netadapt = Get-CimInstance CIM_NetworkAdapter | ? {$_.AdapterType -eq "Ethernet 802.3"}
$netadapt.Disable()
$netadapt.Enable()
The only caveat with this is that it's going to reset all network adapters that are "Ethernet 802.3". If that's an issue you can substitute $_.AdapterType
with $_.name
and also replace "Ethernet 802.3"
with an actual device name e.g. "Intel(R) 82579V Gigabit Network Connection."
With Powershell you could almost make your own command. Something like this might help:
$netadapt = Get-CimInstance CIM_NetworkAdapter | ? {$_.AdapterType -eq "Ethernet 802.3"}
$netadapt.Disable()
$netadapt.Enable()
The only caveat with this is that it's going to reset all network adapters that are "Ethernet 802.3". If that's an issue you can substitute $_.AdapterType
with $_.name
and also replace "Ethernet 802.3"
with an actual device name e.g. "Intel(R) 82579V Gigabit Network Connection."
answered Feb 13 '14 at 22:32
Qwilson
61848
61848
add a comment |
add a comment |
up vote
-1
down vote
You can solve this problem with PowerShell. Just run the command:
Remove-NetIPAddress
It worked to me
– user379638
Oct 14 '14 at 19:28
add a comment |
up vote
-1
down vote
You can solve this problem with PowerShell. Just run the command:
Remove-NetIPAddress
It worked to me
– user379638
Oct 14 '14 at 19:28
add a comment |
up vote
-1
down vote
up vote
-1
down vote
You can solve this problem with PowerShell. Just run the command:
Remove-NetIPAddress
You can solve this problem with PowerShell. Just run the command:
Remove-NetIPAddress
edited Oct 14 '14 at 20:09
Arjan
26.8k1065107
26.8k1065107
answered Oct 14 '14 at 19:26
user379638
11
11
It worked to me
– user379638
Oct 14 '14 at 19:28
add a comment |
It worked to me
– user379638
Oct 14 '14 at 19:28
It worked to me
– user379638
Oct 14 '14 at 19:28
It worked to me
– user379638
Oct 14 '14 at 19:28
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f685011%2fhow-to-reset-tcp-ip-on-windows-8-1%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
PowerShell?
netsh
is a standalone command, it should work in any shell.– grawity
Dec 6 '13 at 21:18
1
What is the problem you are trying to solve with this command? Perhaps there is a different approach.
– Paul
Dec 6 '13 at 22:07
@Paul: This command fixes many networking issues and rebuilds all P stack registry settings. I have been in many situations where the network access was slow or not working and this command did the magic. The fact that it stopped working on Win8.1 should not force us to question its use.
– Allan Xu
Dec 7 '13 at 2:14
4
...did you run it in an elevated shell or a regular one?
– grawity
Dec 7 '13 at 14:16
1
@AllanXu I am not questioning its use but it sounds like a driver issue from your description, and so addressing the underlying issue is an alternative approach to solving the problem.
– Paul
Dec 8 '13 at 20:53