Maybe.
Hmm, few days ago there was a rather similar request like yours now.
Looking at your pictures all looks fine with focus to the filenames.
When looking at the property sheet of a file resp. at the property column titled "#" there are the quirks.
For me ... it looks like ... if numbers with one leading zero will be interpreted as "octal numbers".
So that the octal number "010" will be displayed as decimal "8" or octal number "011" will be displayed as decimal "9".
I have no definite explanation for this phenomenon, but I tend to say that the property handler has a bug when reading the TRACK tag field's number string and the string looks like an octal coded number.
But that such an error, before software deployment, at least in the final inspection, has not be noticed to anyone of the programmers, that would be unbelievable.
Better you check the tag type of your files.
For compatibility with Windows they should have tag type ID3v2.3 UTF-16.
DD.20110318.0540.CET