Cannot Start Automatic Update Service Error 2
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 06 Oct 2016 06:04:42 GMT by s_hv999 (squid/3.5.20)
Windows Could Not Start The Windows Update Service On Local Computer Error 1053
Automatic Updates Service won't start - Error 2 Search Forums Show Threads Show Posts Advanced Search Find All Thanked Posts Search Google Enter your search terms http://www.vistaheads.com/forums/microsoft-public-windowsupdate/347552-automatic-updates-service-wont-start-error-2-a.html Submit search form Web www.vistaheads.com http://stackoverflow.com/questions/19799669/new-windows-service-installed-fails-to-start-system-error-2-system-cannot Go to Page... Welcome to the Microsoft Windows Vista Community Forums - Vistaheads, YOUR Largest Resource for Windows Vista related information.You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By not start joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today! If you have any problems with the registration process or your account login, please contact us. Automatic Updates Service won't windows could not start - Error 2 microsoft.public.windowsupdate Page 1 of 3 1 23 > LinkBack Thread Tools Display Modes #1 (permalink) 03-28-2009 shamrin Posts: n/a Automatic Updates Service won't start - Error 2 Trying to start Automatic Updates results in the error message: Could not start the Automatic Updates service on Local Computer. Error 2: The system cannot find the file specified I get the same error message when trying to start Background Intelligent Transfer Service. I believe both of these services have been hosed by viruses that have now been removed. I managed to do a manual update to SP3 but this has not resolved the problem. TIA /sch Sponsored Links #2 (permalink) 03-28-2009 PA Bear [MS MVP] Posts: n/a Re: Automatic Updates Service won't start - Error 2 You have much more work to do! 1. See if you can download/run the MSRT manually: http://www.microsoft.com/security/ma...e/default.mspx 2. Run the Windows Live Safety Center's 'Protection' scan (only!) in Safe Mode with Networking, if need be: http://onecare.live.com/site/en-us/center/howsafe.htm 3. Run a /thorough/ check for hijac
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 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 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 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, 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.