Skip to content

v1.4.1

Compare
Choose a tag to compare
@jinglouMSFT jinglouMSFT released this 26 Oct 21:24
3889c35

08/28/2018

Hotfixes

  • On first launch, Storage Explorer was unable to generate the key used to encrypt sensitive data. This would cause issues when using Quick Access and attaching resources. #535
  • If your account did not require MFA for its home tenant, but did for some other tenants, Storage Explorer would be unable to list subscriptions. Now, after signing in with such an account, Storage Explorer will ask you to reenter your credentials and perform MFA. #74
  • Storage Explorer was unable to attach resources from Azure Germany and Azure US Government. #572
  • If you signed in to two accounts that had the same email address, Storage Explorer would sometimes fail to show your resources in the tree view. #580
  • On slower Windows machines, the splash screen would sometimes take a significant amount of time to appear. #586
  • The connect dialog would appear even if there were attached accounts or services. #588

New

  • External resource attachments, such as for SAS connections and emulators, has been significantly improved. Now you can:
    • Customize the display name of the resource you are attaching. #31
    • Attach to multiple local emulators using different ports. #193
    • Add attached resources to Quick Access. #392
  • Storage Explorer now supports Soft Delete. You can:
    • Configure a Soft Delete policy by right-clicking on the Blob Containers node for your Storage account.
    • View soft deleted blobs in the Blob Editor by selecting "Active and deleted blobs" in the dropdown next to the navigation bar.
    • Undelete soft deleted blobs.

Fix

  • The "Configure CORS Settings" action is no longer available on Premium Storage accounts because Premium Storage accounts do not support CORS. #142
  • There is now a Shared Access Signature property for SAS Attached Services. #184
  • The "Set Default Access Tier" action is now available For Blob and GPV2 Storage accounts that have been pinned to Quick Access. #229
  • Sometimes, Storage Explorer would fail to show Classic Storage accounts. #323

Known Issues

  • When using emulators, such as Azure Storage Emulator or Azurite, you will need to have them listen for connections on their default ports. Otherwise, Storage Explorer will not be able to connect to them.
  • 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.
  • 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.
  • Although Azure Stack doesn't currently support Files Shares, a File Shares node still appears under an attached Azure Stack storage account.
  • 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.04, 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