Dropbox Portable 1.2.51 Development Test 2

Those things are highly likely to be directly related to DropBox.

I'm looking into this and I have some ideas.

Here's how to handle the registry. Go and first delete the 2 DropboxExt dlls in the App\Dropbox folder, as these load but aren't used, and make the reg cleanup fail and start slower. After nuking those, use this as your launcher file

[Launch]
AppName=Dropbox
ProgramExecutable=Dropbox\Dropbox.exe
WorkingDirectory=%PAL:AppDir%\Dropbox

[Activate]
Registry=true

[RegistryKeys]
Dropbox=HKCU\Software\Dropbox
-=HKCU\Software\Classes\*\shellex\ContextMenuHandlers\DropboxExt
-=HKCU\Software\Classes\CLSID\{FB314ED9-A251-47B7-93E1-CDD82E34AF8B}
-=HKCU\Software\Classes\CLSID\{FB314EDA-A251-47B7-93E1-CDD82E34AF8B}
-=HKCU\Software\Classes\CLSID\{FB314EDB-A251-47B7-93E1-CDD82E34AF8B}
-=HKCU\Software\Classes\CLSID\{FB314EDC-A251-47B7-93E1-CDD82E34AF8B}
-=HKCU\Software\Classes\Directory\Background\shellex\ContextMenuHandlers\DropboxExt
-=HKCU\Software\Classes\Directory\shellex\ContextMenuHandlers\DropboxExt

[RegistryValueBackupDelete]
1=HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved\{FB314ED9-A251-47B7-93E1-CDD82E34AF8B}
2=HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved\{FB314EDA-A251-47B7-93E1-CDD82E34AF8B}
3=HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved\{FB314EDB-A251-47B7-93E1-CDD82E34AF8B}
4=HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved\{FB314EDC-A251-47B7-93E1-CDD82E34AF8B}

[FilesMove]
-=%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup\Dropbox.lnk
-=%USERPROFILE%\Desktop\Dropbox.lnk
-=%USERPROFILE%\Links\Dropbox.lnk

[DirectoriesMove]
DropboxData=%APPDATA%\Dropbox

The changes I made eliminate all registry issues, and they delete the dropbox shortcuts unless local copies existed (and those are reverted to their initial state).

Now we are going to have issues with the path. It is stored encrypted so we cannot change it. You are relying on the user taking the default path, which I guess works (because we cannot change drive letter if we tell the user to use the data folder). I have an idea to stop the copy though. We could see if we can make the launcher create a symlink to a Dropbox folder in Data (so all writes to the dropbox folder on C actually go to the portable drive and no copying is needed across drives).

I'll test that but for now that file works better. The reason I am sending APPDATA to DropboxData is for later symlink purposes.

That might be it, as the device I tried is USB HDD that is detected as "Fixed".