It just simply will not upload files. I have tried the latest version, older versions etc. Drag and drop of files as well as using the upload button specifically fails. It just simply will not load. Using the Storage SDK to upload files does work as does az copy, but the storage explorer itself fails. It simply hangs in the state "Uploading Group"

At the moment when I view Azure tables I see all the Azure "system" tables, they all appear to begin with "$", e.g. $MetricsCapacityBlob.

Personally I've never ever had need to look at those so it would de-clutter the interface if I had a way of removing them from the list. This could be as simple as an option to hide all tables beginning "$" or I guess you could go further for other scenarios.

Add the installation instructions for the Linux version of the Azure Storage Explorer as there is no .deb file nor install.sh file. A .deb file would install straight away. If you provided an obvious file name like install.sh we might have half a chance. As usual you've ignored convention and expect people to mind read.

Allow for Storage to have Read only keys that can be used in client tools like Azure Storage explorer or Cloudberry for read only access.
Often times, a client tool needs to be given to customer to access files and it is not feasible to give the shared key which has full access.

Even better would be to allow for a "user" key to be generated with granular permissions on containers that can be set from Azure portal.

This messes me up *so* much right now -- I'm alternating between Fiddler use which, depending on how I configure Storage Explorer, will block connections at times (in my case, to the Development emulator).

Hello,
my Storage Explorer on Linux stopped working. It was working some days, now the following message appears when I want to start it:

A problem caused Storage Explorer to stop working correctly (the GPU process crashed). Please close and restart the application.

Reinstalling does not change anything.
Also I'm not able to emulate the Windows version in Wine.

I'm wondering how I should access my blob storage now.
Is there a web interface?

Kind regards,
Manuel

Chocolatey makes it easy to install and upgrade programs. This should be easy to create with each deployment

Almost Japanese are not good at reading English. I have heard from my customer too.
If be OSS , I can help to localize.

Please display the created date and last modified date as a column in storage explorer.

Crash when starting up with this message
An unexpected error occurred:

Error: libgnome-keyring.so.0: cannot open shared object file: No such file or directory
at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:172:20)
at Object.Module._extensions..node (module.js:598:18)
at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:172:20)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)
at Module.require (module.js:513:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/home/mohamed/bin/AzStorageExplorer/resources/app/node_modules/keytar/lib/keytar.js:4:12)
at Object.<anonymous> (/home/mohamed/bin/AzStorageExplorer/resources/app/node_modules/keytar/lib/keytar.js:58:4)

I checked for this library using this cmd
dpkg -S $(/sbin/ldconfig -p | awk 'NR>1 { print $NF }') | grep libsecret-1.so.0
libsecret-1-0:amd64: /usr/lib/x86_64-linux-gnu/libsecret-1.so.0

Add a Move button to Storage Explorer, especially for File Shares. This functionality could move a file/folder to another location within the same share.

Right now I get "Failed to Download 'xxxx'".

1) Provide information on WHY it failed so I might be able to do something about it.
2) Allow me to easily retry - preferably by selecting one/all-some failed downloads in a download group.

To build hybrid apps, many 3rd party applications need extensive parts of the storage explorer. Thus, it was great to have it open source (deco), but now the closed source version does not apparently permit extensive UI-configuration (branding, visibility of parts etc.) to enable reasonable 3rd party use.

Simple tools like Azure Storage Explorer and AzCopy are great candidates for inclusion in the Microsoft store. For cross-platform compatibility, it makes sense not to port to UWP and to continue distributing MSIs, but for those of us with Windows 10, it makes the installation process very simple. Also, Azure Storage Explorer always seems to want to update. With the Microsoft Store, updates happen transparently and quickly.

I think it woult be useful to access multiple storage accounts from my subscription as Service Principal, without having to type in my password

We are currently using Azure Media Services which creates a new blob container for each asset. We currently have 40,000 distinct assets. When attempting to search from the blob container level using the exact container id it can take 10+ minutes. This seams to be searching for content within the containers as well. In contrast if we search Azure Media Services Explorer by id it is instant. It would be good to be able to have more control over how it searches

Azure Blob Storage doesn't really support folders, but Azure Storage Explorer implements "Virtual Folders" by using forward slashes in the name as a delimiter. Sometimes, this is really what we want, but other times it results in too many clicks when navigating a deeply nested folder structure (which is very frequent in Azure logging technologies)

See attached screenshots and imagine how many click were required to reach this file. This number of clicks could have been reduced to 0 if there had been an option to view blobs as a "flat" list (where "virtual folders" have been disabled)