Network Command Shell Error
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 23 Oct 2016 04:40:44 GMT by s_wx1157 (squid/3.5.20)
The How-To Geek Forums Have Migrated to Discourse How-To Geek Forums / Windows XP (Solved) - Network Command shell has encountered a problem and needs to close
Network Has Stopped Working Virus
(3 posts) Started 7 years ago by Harshal27 Latest reply from Harshal27 Topic Viewed net command has stopped working windows 7 5255 times Harshal27 Posts: 33 This post has been reported. Hiya, Please I have seen that from last 5 days no one has been replying to my problems I list on forums So I believe this would be some luck I was not able to enter windows firewall form at least a week I http://answers.microsoft.com/en-us/windows/forum/windows_other-performance/why-am-i-getting-network-command-shell-has-stopped/1850d960-cf36-415b-a265-52c722ebcd61 asked on the net and every one said me to do these steps:- 1)Start >> Run 2)Type cmd in run box 3)Type "netsh winsock reset" in command prompt to fix the problem But when I type "netsh winsock reset" in command prompt an error comes up saying "Network Command shell has encountered a problem and need to close. We are sorry for the inconvenience" Even if I type just http://www.howtogeek.com/forum/topic/network-command-shell-has-encountered-a-problem-and-needs-to-close "netsh" in the command prompt the same error comes up, Does this mean that netsh.exe is corrupt? And is there a way to fix this problem via internet or do I will have to re-install? It is not possible for me to perform a reinstall cause I don't have my "Windows XP service pack 3" CD with me Any help would be greatly appreciated, Thanx :( Reports: · Posted 7 years ago Top LH Posts: 20002 This post has been reported. You have been twice advised to re-install your OS. Your system is too messed up to fix. Reports: · Posted 7 years ago Top Harshal27 Posts: 33 This post has been reported. Please tell me the steps on "how to reinstall your OS" Thanx and rock on!!!! Reports: · Posted 7 years ago Top Topic Closed This topic has been closed to new replies. ABOUT About Us Contact Us Discussion Forum Advertising Privacy Policy GET ARTICLES BY EMAIL Enter your email address to get our daily newsletter. FOLLOW US Twitter Facebook Google+ RSS Feed Disclaimer: Most of the pages on the internet include affiliate links, including some on this site. Copyright © 2006-2016 How-To Geek, LLC All Rights Reserved
artwork motion Blog Subscribe to Blog Network Command Shell (netsh.exe) Error Fix Posted on July 10th, 2007 at exactly 4:12 pm (3390 days ago) | Warning: You are viewing this website with Javascript turned http://dbaines.com/blog/archive/network-command-shell-netshexe-error-fix/ off. Certain features will not work with Javascript turned off. Yesterday I booted in to Vista only to discover that almost every program that ran on startup crashed, followed by "Network Command Shell has stopped working". At first I thought this had knocked out my networking because my Internet wasn't working. I was looking all through my network settings and has stopped router settings trying to see if anything was wrong but it was all working kosher. After a lot of debugging I noticed 64 bit applications could access the Internet. IE7 x64 was successfully surfing. So I did a search for x64 related Internet issues. Turns out it's all NOD32's fault. Uninstalling NOD32 and rebooting fixed it. Fuckin' thing. Now I'm Anti-Virus has stopped working free and I'm Lovin' It. Looks like it's only an x64 issue. Unfortunate, after using Vista x64 for a couple of months now there doesn't really appear to be many reasons to keep it over the 32bit alternative July 10th, 2007 at exactly 4:12 pm windows crash, netsh.exe, network command shell, nod32, windows, x64 Sounds Pretty Serious Spider-Man 3 The Game Comments alpha says: July 20, 2007 at 4:26 am • Permalink Except for the fact that 32 bit can't address anything over 3 gigs of ram or over 512mb of video memory. Baines says: July 20, 2007 at 11:58 am • Permalink That's very true and since I have 4 gigs of ram it was really the only reason I didn't want to go back to 32 bit. 32 bit doesn't seem as snappy and agile as 64 either. EpE says: April 6, 2009 at 2:25 pm • Permalink That is wierd because a friend of mine has this problem in 64x Leave a Reply Comments are closed. Copyright © David Baines 2012 • About • Sitemap • Accessability