microsoft / microsoft/AzureStorageExplorer

Natural Sort Order setting is not applied in Blob and ADLS Gen2 blob container explorers

Open
#9,076 1 comment 0 reactions 1 assignee View on GitHub

@craxal is already working on this.

Since Jun 22, 2026.

:beetle: regression :copilot: copilot :gear: adls gen2 :gear: blobs :gear: settings :test_tube: testing :triumph: easy
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Storage Explorer Version

1.43.0

Regression From

1.43.0

Architecture

arm64

Storage Explorer Build Number

20260518.1

Platform

All

OS Version

Windows 11 arm64/Windows11 x64/Linux Ubuntu 22.04

Bug Description

When the Natural Sort Order setting is enabled in Storage Explorer, items should be sorted using natural ordering so that numeric portions of file names are compared numerically (for example, file2.txt should come before file10.txt). However, in the Blob Container Explorer, files are still displayed in lexicographical order, causing file10.txt to come before file2.txt.

Resource Types

Blobs, ADLS Gen2 blobs

Authentication Method

None

Connection Type

None

Steps to Reproduce
  1. Open Storage Explorer.
  2. Go to Settings and enable the setting 'Natural Sort Order'.
  3. Expand one storage account -> Blob Containers.
  4. Create a new blob container -> Upload two files: file2.txt file10.txt.
  5. Close the blob container -> Reopen it.
  6. Observe the displayed order.
  7. Check whether 'file2.txt' comes before 'file10.txt'.
Actual Experience

'file10.txt' is displayed before 'file2.txt'.
Image

Expected Experience

'file2.txt' is displayed before 'file10.txt'.
Image

Additional Context

The setting description states that when enabled, file2.txt should come before file10.txt.

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.