# Auto-numbering different values in MP3Tag and Windows

**URL:** https://community.mp3tag.de/t/auto-numbering-different-values-in-mp3tag-and-windows/70738
**Category:** Support
**Tags:** player
**Created:** [February 21, 2026, 8:44pm UTC](https://community.mp3tag.de/t/auto-numbering-different-values-in-mp3tag-and-windows/70738 "2026-02-21T20:44:34Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [February 21, 2026, 8:48pm UTC](https://community.mp3tag.de/t/auto-numbering-different-values-in-mp3tag-and-windows/70738/2 "2026-02-21T20:48:04Z")

</div>

> [@Harm10](#):
>
> Any idea what is happening here?

Yes: it is the leading zeros that upset the WIndows explorer which interpret the numbers now as octal values - a problem that has not been corrected for ages, see e.g. here:

> [@Padding Track Num, Scrambled.](https://community.mp3tag.de/t/padding-track-num-scrambled/11740/3):
>
> 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 …

---

_[View the full topic](https://community.mp3tag.de/t/auto-numbering-different-values-in-mp3tag-and-windows/70738)._