dto confirms he experiences pretty much the same thing on a range of Windows versions.
If you have time to look into this, the easiest would probably be to run git bisect between 1.1.1 and 1.1.2: it's usually easier to examine a single commit that causes the regression.
dto confirms he experiences pretty much the same thing on a range of Windows versions.
If you have time to look into this, the easiest would probably be to run git bisect between 1.1.1 and 1.1.2: it's usually easier to examine a single commit that causes the regression.