Netsh command/button no longer working

okay, I just want to make very clear upfront I am not a software developer or any kind of engineer of any degree so I am just posting this in the hopes that if there is an issue it is resolved and people can avoid what just happened to me, and if there isn't, oh well.

carrying over from my version 12 install I have a button on one of my toolbars simply labeled "network". within this button I have two more buttons labeled "enable" and "disabled". this is the code for both buttons respectively:

@admin
@runmode:hide
netsh interface set interface "Ethernet 3" admin=enable

@admin
@runmode:hide
netsh interface set interface "Ethernet 3" admin=disable

prior to version 13, if I were to left click the network button, it would enable my specified networking adapter ( notated above in quotes), and if I were to right-click it it would disable it. I had not used this button in quite some time and I needed to quickly deactivate and reactivate my network adapter today and reminded myself of the button and went ahead and used it.

here is where my disclaimer begins regarding if it's DO's doing or if it's some other bad actor on my computer - I'm in no way blaming DO, but seeing as it is a beta software I am more apt to believe that it played a significant role in what I'm about to describe, because I've done nothing out of the norm lately regarding installing software, hardware, etc. The only significant factor that would lead me to believe DO is behind this is simply because it's the only significant change that's occurred on my computer in some time.

once I used the button - i.e. right clicked and then left clicked in order to deactivate and then reactivate my LAN connector - nothing significant actually occurred to my immediate notice on my PC. The adapter did successfully turn off and then reactivate, and for the next half hour or so I went about my merry way. I then noticed when I looked at my system tray that my networking icon was missing and that puzzled me and sent me into this rabbits whole investigation of what the hell is going on here. at first I could not click on Windows 10 networking settings without it opening the window and then immediately closing before even populating with any information. I then ran a system file check three times and there was no indication of any corrupted system files. I then did a DISM and of the app stores apps and just did a clean install through the the DISM restore health function ->
"DISM /Online /Cleanup-Image /RestoreHealth"
I let that complete rebooted my computer. upon rebooting it made no change to the situation. I then had an idea to look into my startup and services portion of our Windows and discovered that a vast majority of my Windows services had been nullified. What I mean by nullified is that they weren't changed to some different startup option (automatic, delayed, etc.) there was simply no option selected whatsoever. many of these services pertaining to Windows 10 networking and I was able to reactivate enough of them to their default startup settings that I can open the networking settings window in Windows 10 but once I specifically tried to open my adapters property window it crashes yet again and immediately close the window. * I do want to make clear that during this entire time my adapter is working and I have Internet access like nothing ever happened but according to my computer my adapter is either not there or I had no network connection*
I have been fiddling around with further repairs but at this point I could have reinstalled Windows and had a significant portion of my settings reinstalled and reconfigured and had a fresh install by now instead of horsing around and trying to Band-Aid up this mess. I'm going to back up my files and just do a clean install of w10.

I know this is very verbose, but it pretty much is the most significant actually the only major instance of some kind of flaw in DO ( if it is in fact DO responsible for this) in its beta stage. if you want more details or have any questions just feel free to ask I am just trying to be a good serving member of the community in case I can prevent someone else from going through this or somehow we can find a way to make DO that much better.

now that I'm done with this post I am almost certain it's something I did because that's just the way the universe works with me lately LOL.

once again, thank you guys for your amazing product and are look forward to seeing it in its finished state!

netsh (network shell) is a command-line utility and part of Windows. Opus just hands it over to the OS to run. You will likely see the same effects if you run the commands from an elevated DOS prompt.

2 Likes

I was concerned that DO perhaps handled it incorrectly due to the script being written for 12 and 13 may have changed how it handles the utility. Again, that was my best assumption.
Do you have any idea what may have reset all of my services? What could possibly do that? I run anti virus and malware protection and nothing has been detected. More curious so that it doesn't happen again.

Check if Ethernet 3 is still the right name. Windows changes it sometimes when it thinks there's a whole new network for some reason.

I just saw my post retitled to what it is now... is that to say that I wasn't 100% wrong? Is 13 not agreeing with that command or did windows change something? Just want to confirm for my sake, I'm definetly getting rid of that button to not have to go through this nonsense again.

Oh and I checked nothing had changed regarding the names of my network connections.

Once again, thank you Monsieur @Leo

The issue probably doesn't involve Opus at all, unless something quite strange is going on.

Have you tried the commands from an admin Command Prompt? If they don't work there either then you know the problem doesn't involve Opus.

Well, to be honest, I am moments away from wiping and reinstalling. Right beforehand I'll check it out. But once I get into my new install, I'm just going to stay the hell away from this nonsense all together and disable/re-enable the old fashioned way. Wasn't trying to imply DO screwed anything up and you guys are responsible - just thought i'd put it out there for your considerations or whatnot during this Beta testing period.

Was just cruising google and found this - does this look like it pertains to what I'm experiencing? He uses a different command set, but they accomplish the same thing and sounds like the same problems?

https://community.spiceworks.com/topic/2294215-quick-script-to-disable-and-re-enable-network-adapter