Support for Windows XP will end on April 8, 2014. After this date, Microsoft has announced that it will will no longer provide updates for its 12-year old operating system — even though it still commands a whopping 29% share of all desktops, second only to Windows 7’s 48%. However, facing the reality of a potential security disaster, with viruses running unchecked without the usual defensive patches, Microsoft recently relaxed their stance and extended antimalware support of XP for an extra 15 months.
Here at Core Technologies, we will start to phase out support for Windows XP this year too. We’re not planning on removing any XP-specific features and capabilities from our software, but our team will no longer be testing or certifying new software releases on XP.
Will this cause you any problems? Please let us know!
Posted onDecember 28, 2013 (Revised April 30, 2021)
If you manage Windows Services and are comfortable working from the command line, then the Windows NET.EXE command should be in your toolkit. Use it to easily start, stop, pause or restart any service from an elevated command prompt, or in a convenient script/batch file.
Using NET to stop a Windows Service
To stop a service, run:
net stop <Service-Name>
where <Service-Name> is the name of the service. Be sure to enclose it in quotes if it contains a space!
For example, to stop the Print Spooler service (named “Spooler”), run:
net stop Spooler
Here is what it looks like on our Windows Server 2016 computer:
Notice that the NET command will wait for the service to stop before continuing. The only exception is when the service is unresponsive or takes more than 30 seconds to comply.
Starting a Windows Service with NET
To start an idle Windows Service, run:
net start <Service-Name>
If all goes well, your service (and any other service it depends on to operate) will be started after a few seconds:
How to Restart a Windows Service with NET.EXE
To restart a service, say from a batch file, chain the “net stop” and “net start” commands together like this:
net stop <Service-Name> net start <Service-Name>
NET will also Pause and Resume Windows Services
Not all services support pause and resume, but if you have one that does, NET can come in handy there as well.
Posted onNovember 28, 2013 (Revised November 10, 2019)
As AlwaysUp enters its 10th year of running any application as a Windows Service, we are excited to announce that readers of the popular Windows IT Pro Magazine have recognized it as a Best Windows Utility for 2013! AlwaysUp has earned the coveted silver medal, bested only by Microsoft’s incredible Sysinternals suite.
According to Windows IT Pro, the 2013 Community Choice Awards represent the cream of the crop in the various markets the magazine covers. Jason Bovberg, the magazine’s senior editor, reported:
“Participation in our 2013 Community Choice awards was excellent. The community both nominates and votes for the best products of the year, ensuring a nice breadth of inclusion in the surveys. Our winners have earned a unique honor to stand out among their peers as winners of our Community Choice Awards.”
Posted onOctober 30, 2013 (Revised March 19, 2022)
Hands down, the most important GUI utility for managing your Windows Services is Microsoft’s Services Control Panel Application — nicknamed “Services.msc” because it can be invoked with that command. This useful application (pictured below) lists every service installed on your PC and allows you to easily to start, stop or configure each one. It has been a fixture of Windows since the first release of NT, way back in 1993.
Starting the Services Application
You can launch the Services application in several ways:
With the Windows Key
Hold down the Windows Key and press R to open the Run window:
Type services.msc in the Open field and hit return. Services should start in a second or two.
From the Start button (Windows 7 and earlier)
Click the Start button
Type services.msc in the search field and hit return.
From the Control Panel
Click on the Start button and choose Control Panel. Or, on Windows 8/8.1, press Windows Key + I and select Control Panel from the charms menu on the right.
In the window that comes up, enter the word services in the search box in the upper right to filter the contents, and click on the View local services link to summon the Services window.
Using the Services Application
Start/stop/restart/pause/resume a service
Simply highlight the service on the list and click on the appropriate toolbar button. Note that most services don’t support pause & resume, so those buttons will probably be disabled.
You can also right-click on the service entry and start it from the context menu:
Modify a service
Double click a service (or right-click it and select Properties) to bring up the service’s Properties window:
From there you can start or stop the service, change the account that the service runs in, configure what to do if the service crashes and see what services must be started before this one.
Manage services on another computer
Assuming that your account has the necessary permissions to access the remote PC, simply select Connect to another computer… from the Action menu and enter the name (or IP address) of the other computer to see its list of services:
Change a service’s description (which can be achieved by editing the registry)
Nevertheless, Services is the best GUI tool for managing your Windows Services
Despite its few shortcomings, Services.msc remains an extremely valuable tool. It is easy to use, is available on every version of Windows, and effortlessly handles a wide range of basic tasks on local and remote computers. Look to it first when working with Windows Services!
Posted onSeptember 15, 2013 (Revised February 12, 2023)
Savvy programmers and administrators often use our free http-ping command line utility to check that their web servers up and serving pages. http-ping’s return code (the percentage of page downloads that succeeded) lets them know when the web server is not responding, enabling them to take the appropriate action (for example sending an email or rebooting the server). This works very well when a web server fails to respond but it can’t detect more subtle problems, such as when the server is responding but returning an error.
http-ping version 6.0 addresses that problem. By returning the HTTP status code from the server’s response, a script can detect 404’s (Not Found), 500’s (Internal Server Error) or any other non-standard replies.
@echooff:: This batch file uses the http-ping application to detect when:: a web server is not responding, or responds with a 5XX status:: code. It returns 0 if the server responds properly and 1 if not.:: It is intended for use with AlwaysUp:: (http://www.coretechnologies.com/products/AlwaysUp/):: or Service Protector:: (http://www.coretechnologies.com/products/ServiceProtector/).:: Copyright 2001-2013 Core Technologies Consulting, LLC. All:: rights reserved.:: Here are a few variables that you should adjust.:: ** Please specify the URL you wish to ping, and the full path:: to the http-ping executable on your system **SETurl=http://localhost:80
SEThttp-ping-exe-path="C:\Temp\http-ping.exe":: num-times-to-ping == The number of ping attempts that will be:: made. The default of 5 is probably OK, but you can increase:: it if errors are frequent (but tolerable).SETnum-times-to-ping=5:: num-seconds-between-pings == The time to wait between ping:: attempts. Increase this to give your server more time to get:: back on its feet after an error.SETnum-seconds-between-pings=10:: Loop "num-times-to-ping" times.FOR /L %%X IN (1,1,%num-times-to-ping%) DOCALL:loopbody%%X:: If we get here, then all ping attempts failed.echo All %num-times-to-ping% attempts of http-ping failed^! ^
Exiting with 1.
exit 1:loopbody:: Ping your web server once, returning the HTTP status code:: (or 0 if the ping failed to connect).%http-ping-exe-path% -e -n 1%url%:: http-ping returns the HTTP status code or 0 if the ping:: failed to connect. The list of HTTP status codes is:: described here::: http://en.wikipedia.org/wiki/List_of_HTTP_status_codes:: For this script, we'll panic on 0 or 5XX (server error):: and consider all other codes as a success.IF%ERRORLEVEL%GTR0 (
IF%ERRORLEVEL%LSS500 (
echo http-ping returned %ERRORLEVEL% - not an error. ^
Exiting with 0.
exit 0
) elseIF%ERRORLEVEL%GTR599 (
echo http-ping returned %ERRORLEVEL% - not an error. ^
Exiting with 0.
exit 0
)
)
echoOn attempt #%1, http-ping returned %ERRORLEVEL% - an error.
:: If this was not the last attempt, pause before trying again.:: Since DOS doesn't have a "sleep" command, use ping with an:: invalid address and a timeout (in milliseconds) to wait for:: a while. You can adjust the timeout value:: (num-seconds-between-pings) above.IF%1LSS%num-times-to-ping% (
SET /A milliseconds=%num-seconds-between-pings% * 1000echo Pausing for%num-seconds-between-pings% second^(s^)^
before the next attempt...
ping 1.1.1.1 -n 1 -w %milliseconds% > nul
)