While SC will happily install any script, batch file or executable as a service, the service it creates may not be usable! You are running into a common problem with the SC utility. SC is not picky it will install anything as a serviceĪs you have discovered, the “SC CREATE” command will create a new Windows Service. SC CREATE NotepadService binpath= "C:\Windows\Notepad.exe" Simple, right?įor example, to install the Windows Notepad application as a service called “NotepadService”, run this command from an administrative command prompt: (Yes - the space after “binpath=” is required!)Īpparently all you need to specify is a friendly name and the full path to your program for SC to work it’s magic. So, as we have shown, SC is firmly focused on basic installation - not operation. The fact that a service was created with SC does not mean that the service can ever start or run. Only a “true” Windows Service Application can be started as a serviceĮven though SC will install any program as a service, the reality is that only specially constructed executables can actually operate as a service. SPECCY WINDOWS 10 THE SERVICE CANNOT BE STARTED INSTALL Service applications implement the Windows Services API - a set of operations used to control and monitor services. With it, Windows can command any Service Application to: Windows uses the API to interact with Service Applications. Unfortunately regular desktop applications (like Microsoft Word, Google Chrome and Adobe Acrobat Reader) do not support the Windows Services API. SPECCY WINDOWS 10 THE SERVICE CANNOT BE STARTED INSTALL.
0 kommentar(er)
