I have a set of 4.x profiles on my computer. Mozilla reports some of them in its list of "unmigrated profiles" in the Profile Manager. Today I deleted some of the 4.x profiles with 4.x's Profile Manager. However Mozilla still shows them in my list of unmigrated profiles. Also, I created a new 4.x profile but it did not show up in Mozilla's list as unmigrated. Seth experienced something like this too in that he doesnt see his 4.x profiles in the list of unmigrated profiles.
I'm not sure my problem is related to bens. my guess is that ben's problem is this: he start up 5.0, it grabs all the 4.x profile info and stuffs it into the 5.0 mozilla registry 4.x obviously doesn't tinker with the 5.0 registry. perhaps we need to have 5.0 re-check the 4.x registry and validate any unmigrated profiles?
We deemed this an uncommon corner case (outside this building anyway.) Yes, we grab the 4.x info once and ignore it ever thereafter. Attempting to do otherwise turns out to be ambiguous and therefore a lot of work. Most non-developers don't create profiles on purpose and would never hit this, so we decided it was a very very low priority. Your workaround is to delete your mozregistry.dat file and try again. This will clear up our memory and we'll rediscover the current state.
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.