Hi
Misunderstanding time: I didn't ask where the profiles store data, I asked where the profiles themselves are stored (as in Preferences menu (main UI) > Options > Expert tab > top option).
Note however that it is possible to change this without migrating the existing profiles (if any), so that you have profiles in all three places (it's not recommended (we recommend migrating them) but it's possible). The program will poll all three possible storage areas (two of which are of course user-specific/dependent), though you may hit problems if the same profile (same name) exists in two or more locations: only one will be listed, but which one that would be is indeterminate (as per KB 49).
You may need to physically check where all profiles are (top option on Expert tab has an Open button to open 3 Explorer windows for you).
The final analysis remains the same: the only way we can conceive of the program kicking profiles out of a group on load-up (program-start) is if the cross-check between the name of the profile inside the Group INI and the actual profile's INI file fails, because the latter is locked. If so, that could be
- another instance of Pro running in a different context is running it (or has it Paused, as happens in a Group)
- AV or similar
- something else (no ideas right now)
It certainly seems to be peculiar to your set-up, whatever it is.
The only other thing I would consider is the Schedule frequency. Vista-and-later have a setting for 'If the Task is already running' (we recommend 'Do not start another instance') - but XP has no such settings to inhibit that, so it may indeed try to start another process/instance, so you could be getting multiple instances of Pro running if you have triggers every 3 minutes and sometimes they take 5 mins to complete (etc). It sounds possible that they may do if they find files to copy (once every 4 hours?). Bear in mind a Group running sequentially starts all member profiles, then Pauses them all, then unPauses each one in turn till it completes). That means all profiles' INI files are locked until the whole Group ends
Misunderstanding time: I didn't ask where the profiles store data, I asked where the profiles themselves are stored (as in Preferences menu (main UI) > Options > Expert tab > top option).
Note however that it is possible to change this without migrating the existing profiles (if any), so that you have profiles in all three places (it's not recommended (we recommend migrating them) but it's possible). The program will poll all three possible storage areas (two of which are of course user-specific/dependent), though you may hit problems if the same profile (same name) exists in two or more locations: only one will be listed, but which one that would be is indeterminate (as per KB 49).
You may need to physically check where all profiles are (top option on Expert tab has an Open button to open 3 Explorer windows for you).
The final analysis remains the same: the only way we can conceive of the program kicking profiles out of a group on load-up (program-start) is if the cross-check between the name of the profile inside the Group INI and the actual profile's INI file fails, because the latter is locked. If so, that could be
- another instance of Pro running in a different context is running it (or has it Paused, as happens in a Group)
- AV or similar
- something else (no ideas right now)
It certainly seems to be peculiar to your set-up, whatever it is.
The only other thing I would consider is the Schedule frequency. Vista-and-later have a setting for 'If the Task is already running' (we recommend 'Do not start another instance') - but XP has no such settings to inhibit that, so it may indeed try to start another process/instance, so you could be getting multiple instances of Pro running if you have triggers every 3 minutes and sometimes they take 5 mins to complete (etc). It sounds possible that they may do if they find files to copy (once every 4 hours?). Bear in mind a Group running sequentially starts all member profiles, then Pauses them all, then unPauses each one in turn till it completes). That means all profiles' INI files are locked until the whole Group ends