02-11-2021, 02:39 PM
Hello Asprex,
E-sys is Java based, and when it's launched (either standalone, or thru Launcher PRO), it calls javaw.exe located under jre\bin folder.
Do you have same behavior with original 32bit JRE, and 64bit JRE ?
When you start E-sys thru Launcher PRO, can you see in Windows task Manager (under details tab) the javaw.exe process starting, then suddently crashing ?
If you right mouse click on your jre\bin\jawaw.exe, then properties, and under compatibility tab, can you check if it works better with other compatibility modes (such as Windows 8) ?
You can also go to your Windows Events viewer, and see if you have any entry related to the E-sys application, that might give you more information what DLL exacty exited.
Now if you confirm that javaw.exe just crashes anytime you start E-sys via Launcher Pro, there are several methods to investigate JVMs crashes.
E-sys is Java based, and when it's launched (either standalone, or thru Launcher PRO), it calls javaw.exe located under jre\bin folder.
Do you have same behavior with original 32bit JRE, and 64bit JRE ?
When you start E-sys thru Launcher PRO, can you see in Windows task Manager (under details tab) the javaw.exe process starting, then suddently crashing ?
If you right mouse click on your jre\bin\jawaw.exe, then properties, and under compatibility tab, can you check if it works better with other compatibility modes (such as Windows 8) ?
You can also go to your Windows Events viewer, and see if you have any entry related to the E-sys application, that might give you more information what DLL exacty exited.
Now if you confirm that javaw.exe just crashes anytime you start E-sys via Launcher Pro, there are several methods to investigate JVMs crashes.
Password to all uploads is bimmerscene.com
![[-]](https://www.bimmerscene.com/images/collapse.png)
