Network Adapter Disabled on Disconnect
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Recently I acquired a Raspberry Pi Zero, which I have been using via a USB cable for ethernet & power. Up until recently, all Windows adapters have been working properly, including when the Raspberry Pi was shut down and disconnected (I assure you that this issue has very little to do with the Pi itself).
Upon disonnecting the Raspberry Pi, Ethernet 4, aka the USB Ethernet/RNDIS Gadget is Disabled, permanently.
Furthermore, no USB disconnect sound is played through my computer, which is an oddity given it usually does.
I have tried:
- Using ncpa.cpl to re-enable the adapter, to no avail. When clicking Enable, a message pops up saying
Enabling...and thenEnabled.- with no difference seen. - Using netsh to re-enable the adapter, to no avail.
- Attempting to uninstall & reinstall the USB
Ethernet/RNDIS Gadgetfrom devmgmt.msc. Every time I attempt to do so, MMC stops responding.
What works:
- Rebooting my laptop.
What I'm unable to do:
- I'm unable to do a complete Network Reset (it shouldn't be an issue with it anyway) - I have WiFi networks that I wish to retain and other settings along with them.
Other notable effects of this behaviour:
- My laptop is unable to go to sleep fully - the screen is off, yet the laptop remains active. (visible through external indicators).
- (edit) It appears my laptop is unable to fully shutdown, also.
However, the ideal solution is to not have this happen in the first place. Originally, it worked as intended: the adapter simply disappeared upon disconnecting, and reappeared on reconnecting. A demonstration of the recent behaviour is shown below:
networking usb ethernet
asked Feb 7 at 7:54
Alex M.Alex M.
6411
add a comment |
Recently I acquired a Raspberry Pi Zero, which I have been using via a USB cable for ethernet & power. Up until recently, all Windows adapters have been working properly, including when the Raspberry Pi was shut down and disconnected (I assure you that this issue has very little to do with the Pi itself).
Upon disonnecting the Raspberry Pi, Ethernet 4, aka the USB Ethernet/RNDIS Gadget is Disabled, permanently.
Furthermore, no USB disconnect sound is played through my computer, which is an oddity given it usually does.
I have tried:
- Using ncpa.cpl to re-enable the adapter, to no avail. When clicking Enable, a message pops up saying
Enabling...and thenEnabled.- with no difference seen. - Using netsh to re-enable the adapter, to no avail.
- Attempting to uninstall & reinstall the USB
Ethernet/RNDIS Gadgetfrom devmgmt.msc. Every time I attempt to do so, MMC stops responding.
What works:
- Rebooting my laptop.
What I'm unable to do:
- I'm unable to do a complete Network Reset (it shouldn't be an issue with it anyway) - I have WiFi networks that I wish to retain and other settings along with them.
Other notable effects of this behaviour:
- My laptop is unable to go to sleep fully - the screen is off, yet the laptop remains active. (visible through external indicators).
- (edit) It appears my laptop is unable to fully shutdown, also.
However, the ideal solution is to not have this happen in the first place. Originally, it worked as intended: the adapter simply disappeared upon disconnecting, and reappeared on reconnecting. A demonstration of the recent behaviour is shown below:
networking usb ethernet
asked Feb 7 at 7:54
Alex M.Alex M.
6411
Disabling it prior to disconnecting it does stop the issue from occurring (and re-enabling and reconnecting works too. I'll look into the event log. Also, I ran sfc and it did find corrupted files... unfortunately I don't know if it has anything to do with my current issue, as it wasn't able to repair those files.
– Alex M.
Feb 10 at 5:01
I can probably deal with having to disable & re-enable the device, yeah.
– Alex M.
Feb 10 at 5:04
1
I was able to rundism /online /cleanup-image /restorehealthand thensfc /scannowto corrupt all files. I'm going to confirm it worked + reboot my computer.
– Alex M.
Feb 10 at 5:49
Can confirm that repairing corrupt files did nothing to fix the issue. Additionally, and I just noticed this, there's an "Unidentified network" label present in the tooltip of the Wifi icon (sevr.org/i/06c379f2-48d3-43b0-8874-f335317ed22a.png).
– Alex M.
Feb 10 at 6:15
Thenetshenable/disable commands don't respond if the Pi was ejected without disabling the device first.
– Alex M.
Feb 10 at 7:07
add a comment |
Recently I acquired a Raspberry Pi Zero, which I have been using via a USB cable for ethernet & power. Up until recently, all Windows adapters have been working properly, including when the Raspberry Pi was shut down and disconnected (I assure you that this issue has very little to do with the Pi itself).
Upon disonnecting the Raspberry Pi, Ethernet 4, aka the USB Ethernet/RNDIS Gadget is Disabled, permanently.
Furthermore, no USB disconnect sound is played through my computer, which is an oddity given it usually does.
I have tried:
- Using ncpa.cpl to re-enable the adapter, to no avail. When clicking Enable, a message pops up saying
Enabling...and thenEnabled.- with no difference seen. - Using netsh to re-enable the adapter, to no avail.
- Attempting to uninstall & reinstall the USB
Ethernet/RNDIS Gadgetfrom devmgmt.msc. Every time I attempt to do so, MMC stops responding.
What works:
- Rebooting my laptop.
What I'm unable to do:
- I'm unable to do a complete Network Reset (it shouldn't be an issue with it anyway) - I have WiFi networks that I wish to retain and other settings along with them.
Other notable effects of this behaviour:
- My laptop is unable to go to sleep fully - the screen is off, yet the laptop remains active. (visible through external indicators).
- (edit) It appears my laptop is unable to fully shutdown, also.
However, the ideal solution is to not have this happen in the first place. Originally, it worked as intended: the adapter simply disappeared upon disconnecting, and reappeared on reconnecting. A demonstration of the recent behaviour is shown below:
networking usb ethernet
asked Feb 7 at 7:54
Alex M.Alex M.
6411
Recently I acquired a Raspberry Pi Zero, which I have been using via a USB cable for ethernet & power. Up until recently, all Windows adapters have been working properly, including when the Raspberry Pi was shut down and disconnected (I assure you that this issue has very little to do with the Pi itself).
Upon disonnecting the Raspberry Pi, Ethernet 4, aka the USB Ethernet/RNDIS Gadget is Disabled, permanently.
Furthermore, no USB disconnect sound is played through my computer, which is an oddity given it usually does.
I have tried:
- Using ncpa.cpl to re-enable the adapter, to no avail. When clicking Enable, a message pops up saying
Enabling...and thenEnabled.- with no difference seen. - Using netsh to re-enable the adapter, to no avail.
- Attempting to uninstall & reinstall the USB
Ethernet/RNDIS Gadgetfrom devmgmt.msc. Every time I attempt to do so, MMC stops responding.
What works:
- Rebooting my laptop.
What I'm unable to do:
- I'm unable to do a complete Network Reset (it shouldn't be an issue with it anyway) - I have WiFi networks that I wish to retain and other settings along with them.
Other notable effects of this behaviour:
- My laptop is unable to go to sleep fully - the screen is off, yet the laptop remains active. (visible through external indicators).
- (edit) It appears my laptop is unable to fully shutdown, also.
However, the ideal solution is to not have this happen in the first place. Originally, it worked as intended: the adapter simply disappeared upon disconnecting, and reappeared on reconnecting. A demonstration of the recent behaviour is shown below:
networking usb ethernet
networking usb ethernet
asked Feb 7 at 7:54
Alex M.Alex M.
6411
asked Feb 7 at 7:54
Alex M.Alex M.
6411
edited Feb 9 at 12:19
Alex M.
asked Feb 7 at 7:54
Alex M.Alex M.
6411
asked Feb 7 at 7:54
Alex M.Alex M.
6411
asked Feb 7 at 7:54
Alex M.Alex M.
6411
6411
Disabling it prior to disconnecting it does stop the issue from occurring (and re-enabling and reconnecting works too. I'll look into the event log. Also, I ran sfc and it did find corrupted files... unfortunately I don't know if it has anything to do with my current issue, as it wasn't able to repair those files.
– Alex M.
Feb 10 at 5:01
I can probably deal with having to disable & re-enable the device, yeah.
– Alex M.
Feb 10 at 5:04
1
I was able to rundism /online /cleanup-image /restorehealthand thensfc /scannowto corrupt all files. I'm going to confirm it worked + reboot my computer.
– Alex M.
Feb 10 at 5:49
Can confirm that repairing corrupt files did nothing to fix the issue. Additionally, and I just noticed this, there's an "Unidentified network" label present in the tooltip of the Wifi icon (sevr.org/i/06c379f2-48d3-43b0-8874-f335317ed22a.png).
– Alex M.
Feb 10 at 6:15
Thenetshenable/disable commands don't respond if the Pi was ejected without disabling the device first.
– Alex M.
Feb 10 at 7:07
add a comment |
Disabling it prior to disconnecting it does stop the issue from occurring (and re-enabling and reconnecting works too. I'll look into the event log. Also, I ran sfc and it did find corrupted files... unfortunately I don't know if it has anything to do with my current issue, as it wasn't able to repair those files.
– Alex M.
Feb 10 at 5:01
I can probably deal with having to disable & re-enable the device, yeah.
– Alex M.
Feb 10 at 5:04
1
I was able to rundism /online /cleanup-image /restorehealthand thensfc /scannowto corrupt all files. I'm going to confirm it worked + reboot my computer.
– Alex M.
Feb 10 at 5:49
Can confirm that repairing corrupt files did nothing to fix the issue. Additionally, and I just noticed this, there's an "Unidentified network" label present in the tooltip of the Wifi icon (sevr.org/i/06c379f2-48d3-43b0-8874-f335317ed22a.png).
– Alex M.
Feb 10 at 6:15
Thenetshenable/disable commands don't respond if the Pi was ejected without disabling the device first.
– Alex M.
Feb 10 at 7:07
Disabling it prior to disconnecting it does stop the issue from occurring (and re-enabling and reconnecting works too. I'll look into the event log. Also, I ran sfc and it did find corrupted files... unfortunately I don't know if it has anything to do with my current issue, as it wasn't able to repair those files.
– Alex M.
Feb 10 at 5:01
Disabling it prior to disconnecting it does stop the issue from occurring (and re-enabling and reconnecting works too. I'll look into the event log. Also, I ran sfc and it did find corrupted files... unfortunately I don't know if it has anything to do with my current issue, as it wasn't able to repair those files.
– Alex M.
Feb 10 at 5:01
I can probably deal with having to disable & re-enable the device, yeah.
– Alex M.
Feb 10 at 5:04
I can probably deal with having to disable & re-enable the device, yeah.
– Alex M.
Feb 10 at 5:04
1
1
I was able to run
dism /online /cleanup-image /restorehealth and then sfc /scannow to corrupt all files. I'm going to confirm it worked + reboot my computer.– Alex M.
Feb 10 at 5:49
I was able to run
dism /online /cleanup-image /restorehealth and then sfc /scannow to corrupt all files. I'm going to confirm it worked + reboot my computer.– Alex M.
Feb 10 at 5:49
Can confirm that repairing corrupt files did nothing to fix the issue. Additionally, and I just noticed this, there's an "Unidentified network" label present in the tooltip of the Wifi icon (sevr.org/i/06c379f2-48d3-43b0-8874-f335317ed22a.png).
– Alex M.
Feb 10 at 6:15
Can confirm that repairing corrupt files did nothing to fix the issue. Additionally, and I just noticed this, there's an "Unidentified network" label present in the tooltip of the Wifi icon (sevr.org/i/06c379f2-48d3-43b0-8874-f335317ed22a.png).
– Alex M.
Feb 10 at 6:15
The
netsh enable/disable commands don't respond if the Pi was ejected without disabling the device first.– Alex M.
Feb 10 at 7:07
The
netsh enable/disable commands don't respond if the Pi was ejected without disabling the device first.– Alex M.
Feb 10 at 7:07
add a comment |
1 Answer
1
active
oldest
votes
As a workaround solution from Device Manager (devmgmt.msc) navigate down to the Network Adapter in question (Ethernet/RNDIS Gadget), right click on it, and then select the Disable device option.
With it disabled from Device Manager, now disconnect the Raspberry Pi per your usual process and just keep it disabled. Whenever you are ready to plug the Raspberry Pi back in and start using it, simply do so and when it's ready, right click on the and select the Enable device option.
Essentially you will. . .
- disable the device from Device Manager before you disconnect it, and then
- enable the device from Device Manager after you connect it back when you're ready to use it again.
More Troubleshooting. . .
Furthermore, from an elevated command prompt, run SFC /SCANNOW, let that run and finish, and reboot Windows. You might also look around Event Viewer application and system logs to see if you see anything relevant to the MMC/Device Manager freeze.
answered Feb 10 at 5:15
Pimp Juice ITPimp Juice IT
25.5k114178
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f1403010%2fnetwork-adapter-disabled-on-disconnect%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
As a workaround solution from Device Manager (devmgmt.msc) navigate down to the Network Adapter in question (Ethernet/RNDIS Gadget), right click on it, and then select the Disable device option.
With it disabled from Device Manager, now disconnect the Raspberry Pi per your usual process and just keep it disabled. Whenever you are ready to plug the Raspberry Pi back in and start using it, simply do so and when it's ready, right click on the and select the Enable device option.
Essentially you will. . .
- disable the device from Device Manager before you disconnect it, and then
- enable the device from Device Manager after you connect it back when you're ready to use it again.
More Troubleshooting. . .
Furthermore, from an elevated command prompt, run SFC /SCANNOW, let that run and finish, and reboot Windows. You might also look around Event Viewer application and system logs to see if you see anything relevant to the MMC/Device Manager freeze.
answered Feb 10 at 5:15
Pimp Juice ITPimp Juice IT
25.5k114178
add a comment |
As a workaround solution from Device Manager (devmgmt.msc) navigate down to the Network Adapter in question (Ethernet/RNDIS Gadget), right click on it, and then select the Disable device option.
With it disabled from Device Manager, now disconnect the Raspberry Pi per your usual process and just keep it disabled. Whenever you are ready to plug the Raspberry Pi back in and start using it, simply do so and when it's ready, right click on the and select the Enable device option.
Essentially you will. . .
- disable the device from Device Manager before you disconnect it, and then
- enable the device from Device Manager after you connect it back when you're ready to use it again.
More Troubleshooting. . .
Furthermore, from an elevated command prompt, run SFC /SCANNOW, let that run and finish, and reboot Windows. You might also look around Event Viewer application and system logs to see if you see anything relevant to the MMC/Device Manager freeze.
answered Feb 10 at 5:15
Pimp Juice ITPimp Juice IT
25.5k114178
add a comment |
As a workaround solution from Device Manager (devmgmt.msc) navigate down to the Network Adapter in question (Ethernet/RNDIS Gadget), right click on it, and then select the Disable device option.
With it disabled from Device Manager, now disconnect the Raspberry Pi per your usual process and just keep it disabled. Whenever you are ready to plug the Raspberry Pi back in and start using it, simply do so and when it's ready, right click on the and select the Enable device option.
Essentially you will. . .
- disable the device from Device Manager before you disconnect it, and then
- enable the device from Device Manager after you connect it back when you're ready to use it again.
More Troubleshooting. . .
Furthermore, from an elevated command prompt, run SFC /SCANNOW, let that run and finish, and reboot Windows. You might also look around Event Viewer application and system logs to see if you see anything relevant to the MMC/Device Manager freeze.
answered Feb 10 at 5:15
Pimp Juice ITPimp Juice IT
25.5k114178
As a workaround solution from Device Manager (devmgmt.msc) navigate down to the Network Adapter in question (Ethernet/RNDIS Gadget), right click on it, and then select the Disable device option.
With it disabled from Device Manager, now disconnect the Raspberry Pi per your usual process and just keep it disabled. Whenever you are ready to plug the Raspberry Pi back in and start using it, simply do so and when it's ready, right click on the and select the Enable device option.
Essentially you will. . .
- disable the device from Device Manager before you disconnect it, and then
- enable the device from Device Manager after you connect it back when you're ready to use it again.
More Troubleshooting. . .
Furthermore, from an elevated command prompt, run SFC /SCANNOW, let that run and finish, and reboot Windows. You might also look around Event Viewer application and system logs to see if you see anything relevant to the MMC/Device Manager freeze.
answered Feb 10 at 5:15
Pimp Juice ITPimp Juice IT
25.5k114178
edited Feb 10 at 5:25
answered Feb 10 at 5:15
Pimp Juice ITPimp Juice IT
25.5k114178
answered Feb 10 at 5:15
Pimp Juice ITPimp Juice IT
25.5k114178
answered Feb 10 at 5:15
Pimp Juice ITPimp Juice IT
25.5k114178
25.5k114178
add a comment |
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.
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%2f1403010%2fnetwork-adapter-disabled-on-disconnect%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
Disabling it prior to disconnecting it does stop the issue from occurring (and re-enabling and reconnecting works too. I'll look into the event log. Also, I ran sfc and it did find corrupted files... unfortunately I don't know if it has anything to do with my current issue, as it wasn't able to repair those files.
– Alex M.
Feb 10 at 5:01
I can probably deal with having to disable & re-enable the device, yeah.
– Alex M.
Feb 10 at 5:04
1
I was able to run
dism /online /cleanup-image /restorehealthand thensfc /scannowto corrupt all files. I'm going to confirm it worked + reboot my computer.– Alex M.
Feb 10 at 5:49
Can confirm that repairing corrupt files did nothing to fix the issue. Additionally, and I just noticed this, there's an "Unidentified network" label present in the tooltip of the Wifi icon (sevr.org/i/06c379f2-48d3-43b0-8874-f335317ed22a.png).
– Alex M.
Feb 10 at 6:15
The
netshenable/disable commands don't respond if the Pi was ejected without disabling the device first.– Alex M.
Feb 10 at 7:07