After quite a few years, I finally resolved to come up with a stronger, more flexible key for everyday use. Once it was generated, I proceeded to edit it's preferences, minded to allow every cipher, digest and compression available, only sorted out by strength.
The problem I've encounter is the following: it all works fine so long as every preference is set at once. E.g.
setpref TWOFISH AES256 CAMELLIA256 AES192 CAMELLIA192 AES CAMELLIA128 BLOWFISH IDEA CAST5 3DES SHA512 SHA384 SHA256 SHA224 RIPEMD160 SHA1 BZIP2 ZLIB ZIP Uncompressed (don't mind the order)
Howbeit, if I were to set one after the other (say all ciphers first, then all digests and finally all compressions) then the preferences set for the later will cause the others to reset back to "none" (SHA1, ZIP/Uncompressed)
Basically there's nothing in the standard that should keep a user from being able to make use of every preference by setting them at different times (neither is there anything in the official manual that would hint me to believe otherwise), so it's possible that this is an oversight and therefore do I report it today.
2.1.23 tested on 32-Bit WinXP SP3.