
I read Arvid stated it could be deducted possibly if debug symbols added to release build and that it would be interesting seeing your screenshoot's with debug-symbols enabled, so I built that for you, and you can ask Arvid again if he can interpret the results of a new test-run, if wanted. I hope it works on your end, as I just last night checked my build-scripts still works, as I hadent done that in a couple months and so I just wanted to check a last time if anything needing fixing before quitting this altogether and tagging my deluge2 windows github repos as "Archived" I.e "unmaintained", which I then did, but so anyway, this "debug-symbol release" libtorrent is for python3.9, which I think you have from your screenshoot, or else give me a shout if using the py3.8 "win7" version, or if there's any other incompatibilities as built from newer components. As this is a release build, then debug-symbols supplied in external pdb file. I don't know much about such honestly, but know it has path hardcoded inside, to said pdb file, but atleast for debuggers I read quickly that it also looks in same dir as binary - this is a pyd though, so I would probably try both have the pdb next to the pyd and also maybe copy the pdb to be inside the main folder where deluge.exe is, just in case.
libtorrent-1.2.14-release_w_debug-py3.9.zip
Edit: Sorry, backup 'libtorrent.pyd' from 'Lib\site-packages' of install-dir or just rename with '-bak' ending' and then extract and copy the two files into 'Lib\site-packages' and then also copy the pdb into main install-dir as stated, just in case. You can also take a copy of your install-folder and copy it into another place and exchange the files there and run test and delete afterwards, as the folder is made pretty portable by default, though reads same profile from %appdata% unless having installed with 'Portable install' enabled during install.