# Auto number track not always matching WIN 11 File Explorer

**URL:** https://community.mp3tag.de/t/auto-number-track-not-always-matching-win-11-file-explorer/65458
**Category:** Support
**Created:** [August 1, 2024, 2:21pm UTC](https://community.mp3tag.de/t/auto-number-track-not-always-matching-win-11-file-explorer/65458 "2024-08-01T14:21:41Z")
**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: [August 1, 2024, 2:26pm UTC](https://community.mp3tag.de/t/auto-number-track-not-always-matching-win-11-file-explorer/65458/2 "2024-08-01T14:26:49Z")

</div>

It's a WIndows Explorer problem, not an MP3tag problem:

> [@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 …

Workaround: do not use 3-digit-numbers with leading zeros as Windows Explorer interprets these as octal (and not decimal) values

---

_[View the full topic](https://community.mp3tag.de/t/auto-number-track-not-always-matching-win-11-file-explorer/65458)._