microsoft / microsoft/AzureStorageExplorer
The folder doesn't display in the destination when pasting one premium blob folder which the name is 'New Folder'
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Storage Explorer Version: 1.16.0
Build Number: 20201125.2
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 16.04/ MacOS Catalina
Architecture: ia32/x64
Regression From: Previous release(1.13.0)
Steps to Reproduce
- Expand one premium storage account (Premium StorageV2 or StorageV1)-> Blob Containers.
- Create a blob container -> Create a folder with the name 'New Folder' -> Upload one page blob to it.
- Copy the folder then paste it to any blob container.
- Check whether the folder displays in the destination.
Expected Experience
The folder displays well in the destination.
Actual Experience
The folder doesn't display in the destination.

Additional Context
- This issue doesn't reproduce when pasting one premium blob folder which the name is not 'New Folder' string.
- This issue doesn't reproduce for one regular blob folder and ADLS Gen2 blob folder.
- This issue also reproduces when cloning one premium blob folder which the name is 'New Folder'.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the copy or clone flow for a premium blob folder named “New Folder” in Azure Storage Explorer, comparing it with other folder types and names. Trace the destination refresh or display path used after the operation; done means the folder appears correctly in the destination without regressing regular or ADLS Gen2 folders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100