@all, what's the error when enabling debug-logging and trying open preferences and/or check deluge-debug.exe if any error displayed in cmd-prompt when trying opening preferences. I don't see this myself on Linux with 2.0.4.dev84.
@anotheruseless forum, the issues you describe are not related to this project of fmar, but deluge2 issues itself. Also, it's clearly written in first post by fmar that you should make backups first. There's code added which retains your deluge1 torrents, as otherwise missed often(if non-latin chars somewhere I believe was culprit, or alike), which have worked for about 5 reporters trying it previously(curtesy tobbez), and never heard it failed before now, unfortunetly. This is added also to stable version, and I cannot remember if merged into the dev version from upstream or not, but regardless also added to that version if not. Your port=0 issue is reported several times, also on deluge1, but mostly for deluge1 users upgrading to deluge2, mostly on linux. Possible workaround helping some, was to I believe set to random port, apply, back to port wanted, apply, and reboot, or something, sorry cannot fully remember but something of sorts, or start with fresh profile completely(can probably retain 'state' folder, to not loose torrents, but delete atleast core.conf + session.state, and it's backups).