Simple DNS Plus
Edit this page

Did you notice something wrong or unclear, or want to add something more to this page?

Great !!

You can edit the source text of this page on GitHub (click here to learn how).

After you submit your changes ("pull request"), we will review it and update the page.

Simple DNS Plus service fails to start on computer reboot

If the Simple DNS Plus service doesn't automatically start up after you start the computer, and you find error events in the Windows Event Log / Application log like this:

"The Simple DNS Plus service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion"

and/or like this:

"Timeout (30000 milliseconds) waiting for the Simple DNS Plus service to connect."

Then it may be because your computer is a just too busy at startup - for example if the computer is low on memory and begins swapping to disk.

By default the Windows Service Manager gives a service 30 seconds to start, and then it kills the service process assuming something is wrong.

You may be able to get around this issue by overriding the 30 second default with a higher value by setting a Windows registry key.

From the Windows Start menu, select "Run", type in "regedit" and click OK, and browse to


If it is not already there, create a new DWORD value named "ServicesPipeTimeout":

Double click "ServicesPipeTimeout" and set the value to the number of milliseconds that the Windows Service Manager should wait for services to start. For example decimal 300000 (= 5 minutes):

Simple DNS Plus

  • Home
  • Search
  • Product details

  • Features
  • Screen shots
  • Plug-ins
  • Tools & Add-ons
  • Testimonials
  • What's new
  • Release notes
  • Download

  • Download
  • Buy

  • Pricing
  • New license
  • Additional license
  • Upgrade
  • Support

  • Overview
  • Lost License Key
  • Knowledge Base
  • Online documentation
  • Contact us