11-01-2025, 12:08 PM
(11-01-2025, 05:01 AM)al3x Wrote:(10-31-2025, 01:46 PM)admin Wrote: Could you try installing V5.5.2.0 again after installing v5.4.2.5 to see if the issue persists?
I tried again with a fresh environment, same problem.
Changed the order of installation to first try with v5.4.2.5, this worked.
Then installed v5.5.2.0 and the issue was the same again.
Don't know what's causing it, but maybe this is related to VMware. If noone else is reporting these issues, I wouldn't worry about it too much for now
It is strange that the issue only occurs in v5.5.2.0, we may need to carefully review the code changes made in v5.5.2.0.