microsoft / microsoft/AzureStorageExplorer

An error occurs when selecting a folder while importing messages or entities

Open
#8,892 5 comments 0 reactions 1 assignee View on GitHub

@craxal is already working on this.

Since Jan 20, 2026.

:computer: linux :grey_question: external :test_tube: testing
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Storage Explorer Version

1.41.0

Regression From

Not a regression

Architecture

x64

Storage Explorer Build Number

20260119.4

Platform

Linux (tar.gz)

OS Version

Linux Ubuntu 22.04

Bug Description

When importing messages into a queue / Importing entities into a table in Storage Explorer, selecting a folder instead of a file causes the operation to fail with an unclear error. After clicking Import and choosing a directory (for example, ~/Downloads), Storage Explorer displays the error:

Unable to parse import file '/home/.../Downloads'. Details: EISDIR: illegal operation on a directory, read.

This issue doesn't reproduce for snap installed storage explorer.

Resource Types

Queues, Tables

Authentication Method

None

Connection Type

Sign in (subscription)

Steps to Reproduce
  1. Download the Storage Explorer .tar package and extract it.
  2. Navigate to the extracted folder and launch Storage Explorer.
  3. Expand a storage account -> Queues.
  4. Select a queue and click -> Import.
  5. Select one Folder (.e.g., Downloads) -> Click Select.
  6. Check the result.
Actual Experience

Storage Explorer allows selecting a folder and then fails with the error:
Image

Expected Experience

Storage Explorer should prevent selecting a folder for import or display a clear validation message indicating that only files are supported.
Image

Additional Context

Here is the gif:

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.