The cause of
Error 1053 can be as a result of Error starting a Windows Service or probably corrupt system files
Signs of Error starting a Windows Service
When you stop or pause a managed Microsoft Windows service, and the process of stopping or pausing the service takes more time than the default configured time, you receive the following error message:
Could not stop the Windows service name service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.
Note: Windows service name is a placeholder for the name of the Windows service that you have created.
The ServiceBase class calls the OnStop method directly from the Service command handler that is defined in the ScDispatcherLoop of the
Advapi32.dll file. After 30 seconds, if the ScDispatcherLoop thread is not ready to receive a new service command from the service control manager, Windows Service Controller marks the service as
time out. Therefore, you receive this error message.
To resolve this problem, obtain the latest service pack for the
Microsoft .NET Framework 1.1.
Follow the steps to complete the installation. Once the updated
service pack is installed you should no longer see the
Error 1053 message appear when you try to start, stop or pause a Windows service.
Run a System File Checker scan to fix any corrupt system files
You may run a System File Checker (SFC) scan to fix any corrupt system files.
To do this, follow the steps mentioned below:
- Click Start, All programs and then Accessories. Click Command Prompt
(Ensure you run as administrator).
System File Checker gives an administrator the ability to scan all protected files to verify their versions. If System File Checker discovers that a protected file has been overwritten, it retrieves the correct version of the file from the cache folder
(%Systemroot%\System32\Dllcache) or the Windows installation source files, and then replaces the incorrect file. System File Checker also checks and repopulates the cache folder. You must be logged on as an administrator or as a member of the Administrators group to run System File Checker. If the cache folder becomes damaged or unusable, you can use the
sfc /scannow, the
sfc /scanonce, or the
sfc /scanboot commands to repair its contents.
System File Checker Tool Syntax
Sfc [/Scannow] [/Scanonce] [/Scanboot] [/Revert] [/Purgecache] [/Cachesize=x]
/Scannow: Scans all protected system files immediately and replaces incorrect versions with correct Microsoft versions. This command may require access to the Windows installation source files.
/Scanonce: Scans all protected system files one time when you restart your computer. This command may require access to the Windows installation source files when you restart the computer. The **SfcScan DWORD** value is set to 2 in the following registry key when you run this command:
/Scanboot: Scans all protected system files every time you start your computer. This command may require access to the Windows installation source files every time you start your computer. The SfcScan DWORD value is set to 1 in the following registry key when you run this command:
/Revert: Returns scan to the default setting (do not scan protected files when you start the computer). The default cache size is not reset when you run this command. This command is equivalent to the /Enable switch in Windows 2000.
/Purgecache: Purges the file cache and scans all protected system files immediately. This command may require access to the Windows installation source files.
/Cachesize=x: Sets the file cache size to xmegabytes (MB). The default size of the cache is 50 MB. This command requires you to restart the computer, and then run the /purgecache command to adjust the size of the on-disk cache. This command sets the SfcQuota DWORD value to x in the following registry key:
After the scan has completed, close the
command prompt window,
restart the computer and check for the issue.
Resources: Error 1053,