I had the same symptoms and it turned out an app that I had run at windows startup conflicted with LiteStep startup for some reason. I just disabled the automatic startup of the app and it fixed the problem.