I've used that workaround (that is, to uncheck "automatically adjust for DST" in the Region thingie), but as I posted before, it creates issues with other programs, namely Trillian, that seem to suffer from the same bug, but in a different way.

Trillian seems to set the timestamp to be "Windows Clock Minus One Hour" if that option is unchecked and DST has begun.

Go figure.