Nice catch -- yeah, I had forgotten about those references to 1.0.6. Funny thing is, the 1.0.6 Lib folder still existed on my system, and Deluge 1.0.7 seemed to launch fine with them (I imagine not much has changed in those libs). So you're right about the changes to those paths -- basically deluge-...

Upgraded to 1.0.7, and the fix I outlined above still works for me.

Edit: @Gfree -- are you telling Firefox to run deluge32.cmd or deluge32.app? Should be deluge32.cmd

Explanation of sysnative: http://www.tipandtrick.net/2008/how-to-open-and-run-32-bit-command-prompt-in-64-bit-x64-windows/ Anyway, the following is working well for me now. First, the solution (based on apocryph's solution), and then I will explain: [EDIT: Please note that this is based on 1.0.6 -- ...

thanks, that solved it.

Deluge 1.0.6 Vista 64-bit Just upgraded to 1.0.6 from 1.0.5 and upon starting up, Deluge pops up a Connection Manager dialog, which appears to be for starting up the daemon. Is this necessary? I don't recall deluged being necessary simply to run the client, at least nothing like this happened in 1.0...