What to do if The Omada Controller Will Not Start in a Windows System (Controller 4.1.5 or above)

SG2428LP , TL-SG2008P( V1 ) , EAP225-Wall( V2 ) , TL-R605( V1 ) , EAP225-Outdoor( V1 ) , EAP245( V3 ) , EAP265 HD( V1 ) , EAP230-Wall( V1 ) , TL-SG2210P( V3.20 ) , EAP620 HD( V1 ) , SG2428P , SG2008P , SG2210MP , ER7206( V1 ) , EAP115( V4 ) , SG2210P , Omada Software Controller , ER605( V1 ) , S5500-8MHP2XF , TL-ER7206( V1 ) , S4500-8GHP2F , EAP660 HD( V1 ) , AP9665 , EAP110( V4 ) , EAP235-Wall( V1 ) , TL-SG2210MP( V1 ) , TL-SG3210XHP-M2( V1 ) , EAP225( V3 ) , EAP110-Outdoor( V3 ) , TL-SG2428P( V1 ) , EAP115-Wall( V1 )
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device, and check either the Datasheet or the firmware section for the latest improvements added to your product. Please note that product availability varies by region, and certain models may not be available in your region.
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
cd
command 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.
Looking for More
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.

TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
SESSION, JSESSIONID, accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Zendesk
OptanonConsent, __cf_bm, __cfruid, _cfuvid, _help_center_session, _pendo___sg__.<container-id>, _pendo_meta.<container-id>, _pendo_visitorId.<container-id>, _zendesk_authenticated, _zendesk_cookie, _zendesk_session, _zendesk_shared_session, ajs_anonymous_id, cf_clearance
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au