Error 2 Cannot Find The File Specified Automatic Updates
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 17:18:04 GMT by s_ac15 (squid/3.5.20)
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn error 2 the system cannot find the file specified windows service more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered error 2 the system cannot find the file specified windows 7 Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a error 2 the system cannot find the file specified cmd python' u'-u' u'' minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Cannot start Server service in Windows 7. Error 2: File Cannot be Found http://answers.microsoft.com/en-us/windows/forum/all/windows-could-not-start-the-windows-update-service/f2e7a67a-b264-4c95-9e27-84b33013af0a?auth=1 up vote 5 down vote favorite 1 I'm having an issue when trying to start the Server service on my machine. I noticed that it wasn't started when I tried to access a share on my machine. I receive an error that states "Windows could not start the Server service on Local Computer. Error 2: They system cannot find the file specified." A snapshot of this error is below: I've tried doing an "upgrade" of Windows to http://superuser.com/questions/258877/cannot-start-server-service-in-windows-7-error-2-file-cannot-be-found repair it, but the upgrade fails as it says I already have the latest Windows. Any idea as to how I can repair this one file? windows-7 services share|improve this question edited Mar 17 '11 at 21:00 Ƭᴇcʜιᴇ007 85k12118175 asked Mar 17 '11 at 20:38 Jason N. Gaylord 2932514 Look in the Windows\System32 folder for "services.exe", is it 32bit W7 or 64bit? –Moab Mar 18 '11 at 1:10 Scan for malware...download.cnet.com/Malwarebytes-Anti-Malware/… –Moab Mar 18 '11 at 1:11 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote accepted 1) System File Checker 2) System Restore 3) Use Process Explorer to figure out what 'file' is being looked for when the Server service starts. share|improve this answer edited Mar 18 '11 at 2:53 answered Mar 17 '11 at 20:59 Ƭᴇcʜιᴇ007 85k12118175 1) Tried this and it didn't do anything –Jason N. Gaylord Mar 17 '11 at 21:40 2) No restore points available on this machine. I thought SP1 automatically took one, but apparently not. –Jason N. Gaylord Mar 17 '11 at 21:41 Added 3. You should get a restore point at every windows update, unless you've turned them off, so that's weird. –Ƭᴇcʜιᴇ007 Mar 18 '11 at 2:55 add a comment| Did you find this question interesting? Try our newsletter Sign up for our newsletter and get ou
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with http://stackoverflow.com/questions/19799669/new-windows-service-installed-fails-to-start-system-error-2-system-cannot us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up http://helpdeskgeek.com/windows-xp-tips/fix-background-intelligent-transfer-service-bits-missing-services/ New Windows Service installed, fails to start: “System error 2 … system cannot find the file specified” up vote 11 down vote favorite 1 I have installed several other custom .Net windows services successfully. A new one I had recently written was error 2 very similar to the others and while it installed without error - on starting it with the service controller it failed to start with the error dialog: System error 2 ... system cannot find the file specified. After time and consternation, the only thing I could think of that was significantly different about this service was that the path and executable name were at least 10 characters longer than any of my other services. On shortening both the path and .exe name and re-installing, cannot find the the service ran fine: no error! I can only assume my previous path or service or .exe name was too long. Also, It would be pertinent to mention I had used some borrowed "service driver" code built in to my exe to handle the install/uninstall of the service to the service controller via win API calls. It could be a character limit was hidden within that service driver module. I could not find any windows related docs to confirm if there is a system bound character limit to a path or service name that I had exceeded. I will dig in to the service driver when time permits and see if that turns out to be the problem. Meanwhile I welcome any insights. windows windows-services servicecontroller share|improve this question asked Nov 5 '13 at 21:46 Ho Ho Ho 206129 What was the total length of path before you shortened it. Also did your path have any unusual characters? If you could also provide the initial path used that would also assist anyone trying to answer your query –Chelseawillrecover Nov 6 '13 at 6:03 The working service now has an executable name length of 17. Unfortunately I didn't save the old one but it was closer to 30 or 35 characters. The service name (service controller name) was the same (without the .exe extension) and the service title showing in the service controller was around 40-50 chars. Total local full path to the exe had something near 100
Service (BITS) Missing from Services Back in the day, I wrote an article about the BITS (Background Intelligent Transfer Service) service not starting and how you can go about fixing that problem. Without this service running in the background, you can't download any Windows updates. It causes all kinds of other issues too, but the main problem that affects most people is when they can't download updates. For the most part, my previous article has helped me quite a few times over the last 5 years. Only until a few days ago did I run into a problem with BITS where the article didn't help. In this case, one of my computers had gotten a bad virus and in the process of cleaning it, the BITS service just disappeared from the list of services. Any command I tried to run to restart the service or reregister it simply wouldn't work. Eventually I found out that I had to recreate the BITS service altogether! At that point, I could register it again with Windows and then go to Services and start it up from there. In this article, I'll walk you through the steps for creating the BITS service manually and then registering it with Windows. Creating the BITS Service The first thing you can try to do is recreate the BITS service. You can do this by opening an administrative command prompt and copying and pasting the command below: sc create BITS type= share start= delayed-auto binPath= "C:\Windows\System32\svchost.exe -k netsvcs" tag= no DisplayName= "Background Intelligent Transfer Service" You can open an administrative command prompt by clicking on Start, typing in CMD and then right-clicking on command prompt and choosing Run as Administrator. If, for some reason, you can't get the above command to work properly, you can also try the command below, which is just a shortened version of it. If you can, try to copy and paste because you'll notice that after the = sign in several locations, there is a space immediately after. That's not by accident, you need that space otherwise the command won't work. sc create BITS binpath= "c:\windows\system32\svchost.exe -k netsvcs" start= delayed-auto Once the BITS service is installed, we need to make sure it's registered properly. If not, you can try to start it from the Services panel, but you'll probably get an