Skip to content


  1. Jon Beining
    January 26, 2017 @ 3:13 pm

    I installed this version and it is asking me to buy a new license. Is this correct?


    • Martin Rothschink
      January 26, 2017 @ 5:48 pm

      Hi Jon, probably yes.
      You should have a 30 day trial license after installation.
      You can’t use an existing 1.6 license. 2.0 is a major release and requires a new license.
      See day 29 and 30 of the blog series.


  2. Paul
    January 14, 2018 @ 9:12 pm

    When I run the client installer on Windows 10 I get the message “The service cannot be started, either because it is disabled or because it has no enabled devices associated with it”. What does this mean?


    • Martin Rothschink
      January 15, 2018 @ 7:52 am

      Paul, please restart the computer and try again. Should the issue persist, then please open a ticket here /osticket/



  3. Ken Bostock
    April 11, 2019 @ 10:27 pm

    Hi Martin,

    This is a great program! I’m setting up a home server with Windows 2012 R2 essentials installed. The question is whether LightsOut2 will work on a client (Windows 10 Pro PC) that has skipped the domain join protocol and joined the server as part of the homegroup?

    LightsOut2 installed on the server without a hitch. The problem started when I tried to access the client installation software from the server. That didn’t work so I created a preconfigured client package which I was able to install. That’s as far as I got. What I’m seeing is a ? in the light-bulb. Apparently that means it can client can’t find the server although, I’ve tried signing in as administrator as well as a standard user and in both cases have access to the server file folders.

    I’m beginning to think that LightsOut2 won’t work on a client that isn’t part of the domain.

    Thanks so much.



    • Martin Rothschink
      April 12, 2019 @ 10:06 am

      Hi Ken,

      it does not matter if the client is domain joined or not.
      If you can’t open the download page on http://your-server-name-here:7782, then a client connection will also fail.

      Please check if your server network is set to a domain or private network. It does not work if it’s a public network because the firewall blocks the connection for public networks. Go to “Network and sharing center” to verify.

      If that does not help, then please open a ticket and attach your server log files. Simply zip the whole folder c:\programdata\LightsOut2\Logs (via right click, send to compressed folder) and attach the archive to the ticket. If you do not see a folder c:\programdata, then open explorer options and enable “show hidden files and folders”.



      • Ken Bostock
        April 17, 2019 @ 8:03 pm

        Hey Martin,

        Problem solved! As you suggested, the network was set to public. After I changed the startup of Network Location Awareness service to Delayed Start the network was reset to Domain.

        I’ve run Lights-Out2 on my (home) Windows Server 2012 R2 for a week and the WOL and backups have worked flawlessly.

        I really appreciate the technical assistance even though I was using Lights-Out on a 30 day trial.

        Now that I know it works with my new server I’ve bought the home license.




  4. Frank Payte
    September 13, 2020 @ 10:29 pm

    I moved my server from windows 10 to windows server 2019 essentials and now I can’t connect to the server even to download the client. I tried manual install and it says can’t find package. I can connect to server folders and I can remote desktop but no connection to server. Any ideas?


Leave a Reply

Your email address will not be published. Required fields are marked *