qBittorrent.ini settings are self changing position in ini every time !

[amdvce]

qBittorrent & operating system versions

4.6.3 win10 iot 21h2 ltsc x64 (10.0.19044) 6.4.3 2.0.9.0

What is the problem?

i md use of portable v of qb, anyway the POSITION(S) of setting(s) in the file "qBittorrent.ini" are changing every time i just open and quick close the qBittorrent.exe.

I have NEVER encounter a pro-gram that is doing that, as the matter of facts the qBittorrent is the one and only pro-gram where the position of settings within an *.ini file is changing every, every time !

BTW This is the same with ALL the qBittorrent v.

Steps to reproduce

a. open qBittorrent.exe

b. close qBittorrent

c. check the position of settings within the file "qBittorrent.ini" / make a bk by copy the file "qBittorrent.ini"

d. a

e. b

f. use winmerge to compare the bk file and the qBittorrent.ini ! The in-file POSITIONS of settings are changed !

Additional context

Fix this as is hard to debug the values of settings, since their positions are always changed Make the POSITIONS of settings in qBittorrent.ini file to be like any normal program, meaning FiXED ! So the power users, i mean US to not waste time with winmerge for looking for a value/changed.

It's annoying and un-pro ! It's like opening a book and each time you open a book page, the positions are changing every time on the same page !

Log(s) & preferences file(s)

No response

[xavier2k6]

This ticket has been closed.

---

Closure Reason: being "out-of-date", and thus either most likely resolved in recent versions or no longer applicable.

---

• If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

• Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.

• Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

• A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.

• Thank you for your contribution(s).

---

NOTE: This ticket will be locked in ~30 Days to avoid any necroing.