Valentina,
This seems to be caused by some of the internal workings of the UltraExpandableGroupBox in terms of its serialization and when it can safely assign the expanded size; I do feel that this is a bug, though, and you should be able to set the value in code immediately after the InitializeComponent call so you should submit this to Developer Support.
As a workaround, using the form's Load event seems to be ok for me, and should still allow you to assign the expanded state of the control based on your condition. If that cannot work for some reason, you could created a control that derives from UltraExpandableGroupBox and override the OnCreateControl method; you would call the base implementation and then set the Expanded state accordingly.
-Matt
If you do end up being able to reproduce it again, you should submit the sample project to developer support so that it can be looked into and possible be prevented from happening in the future.
It's hard to say what's going on here; the Expanded property should certainly not always be showing true if it's collapsed. I just tested this in my application where the group box starts off collapsed and clicking a button expands it, and it worked fine. What is being serialized in the designer code for the ExpandedSize property? I know that there have been bugs in the past regarding the serialization of these properties, so you may want to ensure that you have the latest hotfix.