ok, I was off by twelve hours, sorry for that.
It looked as if this was one of those hit 'n run questions where someone gets frustrated if not properly answered within the hour. So my original post may be a bit harse due to that mistake.
However, i'll stay with my original statement that this is an insignificant issue if any exists at all.
First: saying default.xbe does not necessarily mean default.xbe.
Topicstarter may just as well be one of those thousands of people who say one thing while the other is true.
(i.e. people who type www.192.168.0.1 when I say 192.168.0.1 and fail to ever mention the www which they just made up themselves whilst asking me for help)
If I were having this problem I would have easily solved it within the 13 hours time by either clearing the cache (may be a bit more advanced) or just removing \apps\xbmc and ftp it over again.
Maybe the way I said it was a bit misleading but what I meant with non-existant problem is not that he is making it up but that this is just a random, weird 'problem' which is not directly related to Avalaunch or XBMC but rather just some freaky coincidence which can be resolved by just resetting / reinstalling (ok, basic copy files instead of install
) / ignored (it's purely cosmetic, how often do you launch Avalaunch anyway?) etc.
This is not a(n) (un)known bug or feature. There is no alternative setting or option for this and for the hundreds of xbox's fitted with numerous versions of xbmc and alternate settings I have never encountered anything like this. In other words: It's a user-error and not a software-error.