I'm running Shareaza 2.6 (64-bit version) under Windows 7 64-bit and seem to have shot myself in the foot. If I add a new file to be downloaded it works fine until I exit Shareaza; on restart the download is gone from the Transfers window (though vestiges are left in the Incomplete directory). Downloads that have been in progress for a long time are still there after a restart. Unfortunately I don't know quite when this started -- possibly after upgrading from 2.5.5, but just not sure.
I installed in other than the default location. I selected the Z: drive. The Downloads and Incomplete directories are EFS encrypted (even though that prevents completed downloads from being shared). That still left vestiges in C: so I tried manually setting the directories to point into Z. Suspecting that configuration to be the problem I cleaned the executables and registries out using both "Shareaza Easy Clean Install Script v1.3.bat" and manually finding and deleting entries in the registry (including the WOW6432 parts of the hierarchy,and re-installed. Still no joy.
UPDATE: Problem seems to be related to 2.6. I downgraded to 2.5.5 x64 and am once again able to add new downloads to the queue. If I re-up to 2.6 it remembers what I just added but again forgets anything added using the 2.6 client.
Any suggestions on where I should look for configuration problems that would explain why 2.6 remembers and continues old downloads but forgets new ones?