What to do if The Omada Controller Will Not Start in a Windows System (Controller 4.1.5 or above)
Suitable for Omada Controller V4.1.5 or above.
In some cases, the Omada Controller Start Page may not pop up automatically when you double-click the start icon, and we can’t start the Omada Controller successfully.
This can be caused by a high Java version (Java 8 should be used to run the Controller) or an incorrect Java start path in the Windows Registry Editor. In this article, we will explore solutions to fix this issue.
1. Start the Omada Controller via “start.bat”
- Go to the “bin” folder of the Omada Controller installation path and double-click the “start.bat” file to verify whether the Controller can be started successfully. The default path of “start.bat” is C:\Users\Administrator\Omada Controller\bin\start.bat.
2. Start the Omada Controller via CLI command.
- Open a Command Prompt window as an administrator.
- Use the
cdcommand to navigate to the "lib" folder of the Omada Controller installation path. The default path is: cd C:\Users\<USERNAME>\Omada Controller\lib
- Note: Ensure you are using Command Prompt; not Windows PowerShell.
2) There should be a local-starter-<YOUR_OMADA_VERSION>.jar file in this folder. Start the Controller by running the following command:
java -jar local-starter-<YOUR_OMADA_VERSION>.jar (for example, java -jar local-starter-5.11.8.jar).
Note: Replace <YOUR_OMADA_VERSION> with the version of the Omada Controller that you are using.
3. Modify the running path of java in the Windows Registry Editor
1) Use the “Win+R” key combination to open the run shell. Type regedit to open the Registry Editor.
2) Navigate to the following key: HKEY_CLASSES_ROOT\jarfile\shell\open\command to inspect the running data of the java running environment.
3) Java 8 (JRE 1.8.0) is required to run the Omada Controller.
- Ensure the JRE version in the Value data is 1.8.0. If not, please install Java 8 first, or change the value to the actual path of Java 8 on your PC, such as:
- “C:\Program Files\Java\jre1.8.0_271\bin\javaw.exe”.
- If the value data does not contain this path, or if it contains a different version of Java, edit the value data to correct the path.
If you are still unable to start the Omada Controller after following these steps, please contact technical support for assistance.
Is this faq useful?
Your feedback helps improve this site.
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.