@Nadellin_9Hello, thank you for your reply.
We have received the logs and are investigating the issue based on your information, but we have not yet determined the cause. There are no crash logs for the expected Cubism Editor in the logs, and it appears to be starting up normally. Furthermore, in the logs provided earlier, there are no logs for versions 5.0.03 or 5.0.05 beta1, causing confusion.
For further investigation, we would like to confirm the following:
1. Is it correct that versions of Cubism Editor that cannot start are 5.0.03 or later?
And is it correct that the version of Cubism Editor mentioned in the logs obtained from the call stack tool is 5.0.05 beta1?
This is necessary to speculate on what fixes are affecting the versions before and after.
2. Can you start 5.0.05 beta1 by exiting any resident or security software?
If these software programs are running, they may be affecting the startup process of Cubism Editor.
3. Are there any error logs related to Cubism Editor in the Windows Event Viewer? After double-clicking on the Cubism Editor that won't start, check to see if there are any logs for Cubism Editor in "Custom Logs - Administrative Events" or "Windows Logs - Application".
@Nadellin_9Logs were collected and sent using callstackgetter.
Thank you for your assistance in identifying the issue.
We have reviewed our investigation so far and it is unlikely that this is a licensing issue.
Therefore, we would like to confirm the behavior of Cubism Editor that is occurring in your PC environment through the Call Stack tool.
In order to identify the cause of this issue, we'd like you to collect logs with a tool "callstackgetter" which can be downloaded in this link.
https://dtbn.jp/ZGGUKgie
For instructions on how to use the tool, please read the readme.txt in the downloaded zip file answered.
Logs obtained by callstackgetter should be sent using this uploader.
https://biz.datadeliver.net/posts/txKzkLkJnQP4
We look forward to hearing from you.
Best regards.