Azure Storage Explorer Version 1.5.0

October 2018 (Version 1.5.0)

Welcome to version 1.5.0 of Microsoft Azure Storage Explorer. This release contains a few bug fixes, and a new experimental feature, being able to use AzCopy for a more performant Blob upload and download experience.

New

• You can now use AzCopy v10 (Preview) for uploading and downloading Blobs. To enable this feature go to the "Experimental" menu and then click "Use AzCopy for Improved Blob Upload and Download". When enabled, AzCopy will be used in the following scenarios:Upload of folders and files to blob containers, either via the toolbar or drag and drop.
• Downloading of folders and files, either via the toolbar or context menu.
• Additonally, when using AzCopy:You can copy the AzCopy command used to execute the transfer to your clipboard. Simply click "Copy AzCopy Command to Clipboard" in the activity log.
• You will need to refresh the blob editor manually after uploading.
• Uploading files to append blobs is not supported, .vhds will be uploaded as page blobs, and all other files will be uploaded as block blobs.
• Errors and conflicts that occur during upload or download will not be surfaced until after a upload or download is finished.
• Finally, support for using AzCopy with File Shares will be coming in the future.
• Storage Explorer is now using Electron version 2.0.11.
• Breaking leases can now only be performed on one blob at a time. Additionally, you have to enter the name of the blob whose lease you are breaking. This change was made to reduce the likelihood of accidentally breaking a lease, especially in the case of .vhds for VMs. #394
• If you ever encounter sign-in issues, you can now try resetting authentication. Go to the "Help" menu and click "Reset" to access this capability. #419

Fixes

• After strong user feedback, the default emulator node has been re-enabled. You can still add additional emulator connections via the Connect dialog, but if your emulator is configured to use the default ports you can also use the "Emulator - Default Ports" node under "Local & Attached/Storage Accounts". #669
• Storage Explorer will no longer let you set blob metadata values which have leading or trailing whitespace. #760
• The "Sign In" button was always enabled on same pages of the Connect dialog. It is now disabled when appropriate. #761
• Quick Access will no longer generate an error in the console when no Quick Access items have been added.

Known Issues

• Detatching from a resource attached via SAS URI, such as a blob container, may cause an error that prevents other attachments from showing up correctly. To work around this issue, just refresh the group node. See #537 for more information.
• If you use VS for Mac and have ever created a custom AAD configuration, you may be unable to sign-in. To work around the issue, delete the contents of ~/.IdentityService/AadConfigurations. If doing so does not unblock you, please comment on this issue.
• Azurite has not yet fully implemented all Storage APIs. Because of this, there may be unexpected errors or behavior when using Azurite for development storage.
• In rare cases, the tree focus may get stuck on Quick Access. To unstick the focus, you can Refresh All.
• Uploading from your OneDrive folder does not work because of a bug in NodeJS. The bug has been fixed, but not yet integrated into Electron. To workaround this issue when uploading to or downloading from a blob container, you can use the experimental AzCopy feature.
• When targeting Azure Stack, uploading certain files as append blobs may fail.
• After clicking "Cancel" on a task, it may take a while for that task to cancel. This is because we are using the cancel filter workaround described here.
• If you choose the wrong PIN/Smartcard certificate, then you will need to restart in order to have Storage Explorer forget that decision.
• Renaming blobs (individually or inside a renamed blob container) does not preserve snapshots. All other properties and metadata for blobs, files and entities are preserved during a rename.
• Azure Stack does not support the following features:File shares
• Access tiers
• Soft Delete
• Attempting to use these features while working with Azure Stack resources may result in unexpected errors.
• The Electron shell used by Storage Explorer has trouble with some GPU (graphics processing unit) hardware acceleration. If Storage Explorer is displaying a blank (empty) main window, you can try launching Storage Explorer from the command line and disabling GPU acceleration by adding the `--disable-gpu` switch:

./StorageExplorer.exe --disable-gpu

• For Linux users, you will need to install .NET Core 2.0.
• For users on Ubuntu 14.04, you will need to ensure GCC is up to date - this can be done by running the following commands, and then restarting your machine:

sudo add-apt-repository ppa:ubuntu-toolchain-r/test

sudo apt-get update

sudo apt-get upgrade

sudo apt-get dist-upgrade

• For users on Ubuntu 17.10, you will need to install GConf - this can be done by running the following commands, and then restarting your machine:

sudo apt-get install libgconf-2-4

Download