V1.8.0

5/2/2019 (Build 20190501.8)

Welcome to version 1.8.0 of Microsoft Azure Storage Explorer.

New

• The integrated AzCopy version has been updated to version 10.1.0.
• Ctrl/Cmd+R can now be used to refresh the currently focused editor. #1097
• The Azure Stack Storage API version has been changed to 2017-04-17.
• The Manage Access Dialog for ADLS Gen2 will now keep the Mask in sync in a way similar to other POSIX permissions tools. The UI will also warn you if a change is made that causes the permissions of a user or group to exceed the bounds of the Mask. #1253
• For AzCopy uploads, the flag to calculate and set the MD5 hash is now enabled. #1223

Preview Features

• Device code flow sign in is now available to preview. To enable it, go to "Preview" → "Use Device Code Flow Sign-in". We encourage any users who have had issues with blank sign-in windows to try this feature, as it may prove to be a more reliable form of sign-in. #938
• Storage Explorer integrated with AzCopy is currently available to preview. To enable it, go to "Preview" → "Use AzCopy for Improved Blob Upload and Download". Blob transfers completed with AzCopy should be faster and more performant.

Fixes

• The Access Policies dialog will no longer set an expiry date on Storage Access Policies that do not have an expiry. #764
• Some changes have been made to the Generate SAS dialog to make sure Stored Access Policies are used correctly when generating a SAS. #1269
• When attempting to upload a non-512 byte aligned file to a page Blob, Storage Explorer will now expose a more relevant error. #1050
• Copying a Blob container which utilized a display name would fail. Now, the actual name of the Blob container is used. #1166
• Attempting to perform certain actions on an ADLS Gen2 folder which had unicode characters in its name would fail. All actions should now work. #980

Known Issues

• When performing a non-AzCopy Blob download, the MD5 for large files is not being verified. This is due to a bug in the Storage SDK. #1212
• When using RBAC, Storage Explorer requires some management layer permissions in order to access your storage resources. See the troubleshooting guide for more info.
• Attempting to access ADLS Gen2 Blobs when behind a proxy may fail.
• 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
• Running Storage Explorer on Linux requires certain dependencies to be installed first. Check the Storage Explorer troubleshooting guide for more information.

v1.7.0

3/5/2019 (Build 20190305.10)

Welcome to version 1.7.0 of Microsoft Azure Storage Explorer. Version 1.7.0 is a bug fix focused release. Additionally, for those who have been unable to sign in due to seeing a blank sign-in window, we encourage you to try a new preview feature: device code flow sign-in.

New

• You can now change the owner and owning group when managing access for an ADLS Gen2 container, file, or folder.
• On Windows, updating Storage Explorer from within the product is now an incremental install. This should result in a faster update experience. If you prefer a clean install, then you can download the installer yourself and then install manually. #1089

Preview Features

• Device code flow sign in is now available to preview. To enable it, go to "Preview" → "Use Device Code Flow Sign-in". We encourage any users who have had issues with blank sign-in windows to try this feature, as it may prove to be a more reliable form of sign-in. #938
• Storage Explorer integrated with AzCopy is currently available to preview. To enable it, go to "Preview" → "Use AzCopy for Improved Blob Upload and Download". Blob transfers completed with AzCopy should be faster and more performant.

Fixes

• You can now choose the blob type you want to upload as when AzCopy is enabled. #1111
• Previously, if you had enabled static websites for an ADLS Gen2 Storage account and then attached it with name and key, Storage Explorer would not have detected that hierarchical namespace was enabled. This has been fixed. #1081
• In the blob editor, sorting by either retention days remaining or status was broken. This has been fixed. #1106
• After 1.5.0, Storage Explorer no longer waited for server side copies to finish before reporting success during a rename or copy & paste. This has been fixed. #976
• When using the experimental AzCopy feature, the command copied after clicking "Copy command to clipboard" was not always runnable on its own. Now, all commands needed to run the transfer manually will be copied. #1079
• Previously, ADLS Gen2 blobs were not accessible if you were behind a proxy. This was due to a bug in a new networking library used by the Storage SDK. In 1.7.0, an attempt to mitigate this issue has been made, but some people may continue to see issues. A full fix will be released in a future update. #1090
• In 1.7.0, the save file dialog now correctly remembers the last location you saved a file to. #16
• In the properties panel, the SKU tier of a Storage account was being shown as the account's kind. This has been fixed. #654
• Sometimes, it was impossible to break the lease of a blob, even if you entered the name of the blob correctly. This has been fixed. #1070

Known Issues

• When using RBAC, Storage Explorer requires some management layer permissions in order to access your storage resources. See the troubleshooting guide for more info.
• Attempting to access ADLS Gen2 Blobs when behind a proxy may fail.
• 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

v1.6.2

1/8/2019 (Build 20190108.2)

Welcome to version 1.6.2 of Microsoft Azure Storage Explorer. This release fixes some outstanding bugs and several bugs that were introduced in version 1.6.0 and 1.6.1.

Hotfixes

• In v1.6.1, entities added to ADLS Gen2 ACLs by ObjectId which were not users were always added as groups. Now, only groups are added as groups, and entities such as Enterprise Applications and Service Principals are added as users. #1049
• If an ADLS Gen2 Storage account had no containers and was attached with name and key, then Storage Explorer would not detect that the Storage Account was ADLS Gen2. This has been fixed. #1048
• In v1.6.0, conflicts during copy and paste would not prompt for a resolution. Instead, the conflicted copy would simply fail. Now, on the first conflict, you will be asked how you would like it to be resolved. #1014
• Due to API limitations, all validation of ObjectIds in the Manage Access dialog have been disabled. Validation will now only occur for user UPNs. #954
• In the ADLS Gen2 Manage Access dialog, the permissions for a group could not be modified. This has been fixed. #958
• Added drag and drop upload support to the ADLS Gen2 editor. #953
• The URL property in the properties dialog for ADLS Gen2 files and folders was sometimes missing a '/'. This has been fixed. #960
• If getting the current permissions for an ADLS Gen2 container, file, or folder fails, then the error is now propertly displayed in the activity log. #965
• The temporary path created for opening files has been shortened to reduce the chance of creating a path which is longer than MAX_PATH on Windows. #93
• The Connect dialog now correctly appears when there are no signed in users and no resources have been attached. #944
• In 1.6.0, saving properties for non-HNS Blobs and Files would encode the value of every property. This resulted in unnecessary encoding of values which only contained ASCII characters. Now, values will only be encoded if they contain non-ASCII characters. #986
• Uploading a folder to a non-HNS Blob container would fail if a SAS was used and the SAS did not have read permissions. This has been fixed. #970
• Canceling an AzCopy transfer did not work. This has been fixed. #943
• AzCopy would fail when trying to download a folder from an ADLS Gen2 Blob container if the folder had spaces in its name. This has been fixed. #990
• The CosmosDB editor was broken in 1.6.0. It is now fixed. #950
• If a Blob copy resulted in many conflicts, Storage Explorer would sometimes freeze. This has been fixed.

New

• You can now use Storage Explorer to access your Blob data via RBAC. If you are signed in and Storage Explorer is unable to retrieve the keys for your Storage account, then an OAuth token will be used to authenticate when interacting with your data.
• Storage Explorer now supports ADLS Gen2 Storage accounts. When Storage Explorer detects that hierarchical namespace is enabled for a Storage account, you will see "(ADLS Gen2 Preview)" next to the name of your Storage account. Storage Explorer is able to detect whether or not hierarchical namespace is enabled when you are signed in, or if you have attached your Storage Account with name and key. For ADLS Gen2 Storage accounts, you can use Storage Explorer to:
  • Create and delete containers.
  • Manage container properties and permissions (left-hand side).
  • View and navigate data inside of containers.
  • Create new folders.
  • Upload, download, rename, and delete files and folders.
  • Manage file and folder properties and permissions (right-hand side).
    Other typical Blob features, such as Soft Delete, and Snapshots, are not currently available. Managing permissions is also only available when signed in. Additionally, when working in an ADLS Gen2 Storage account, Storage Explorer will use AzCopy for all uploads and downloads and default to using name and key credentials for all operations if available.
• After strong user feedback, break lease can once again be used to break leases on multiple blobs at once.

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

v1.6.1

12/18/2018 (Build 20181218.1)

Welcome to version 1.6.1 of Microsoft Azure Storage Explorer. This release fixes some outstanding bugs and several bugs that were introduced in version 1.6.0.

Hotfixes

• Due to API limitations, all validation of ObjectIds in the Manage Access dialog have been disabled. Validation will now only occur for user UPNs. #954
• In the ADLS Gen2 Manage Access dialog, the permissions for a group could not be modified. This has been fixed. #958
• Added drag and drop upload support to the ADLS Gen2 editor. #953
• The URL property in the properties dialog for ADLS Gen2 files and folders was sometimes missing a '/'. This has been fixed. #960
• If getting the current permissions for an ADLS Gen2 container, file, or folder fails, then the error is now propertly displayed in the activity log. #965
• The temporary path created for opening files has been shortened to reduce the chance of creating a path which is longer than MAX_PATH on Windows. #93
• The Connect dialog now correctly appears when there are no signed in users and no resources have been attached. #944
• In 1.6.0, saving properties for non-HNS Blobs and Files would encode the value of every property. This resulted in unnecessary encoding of values which only contained ASCII characters. Now, values will only be encoded if they contain non-ASCII characters. #986
• Uploading a folder to a non-HNS Blob container would fail if a SAS was used and the SAS did not have read permissions. This has been fixed. #970
• Canceling an AzCopy transfer did not work. This has been fixed. #943
• AzCopy would fail when trying to download a folder from an ADLS Gen2 Blob container if the folder had spaces in its name. This has been fixed. #990
• The CosmosDB editor was broken in 1.6.0. It is now fixed. #950
• If a Blob copy resulted in many conflicts, Storage Explorer would sometimes freeze. This has been fixed.

New

• You can now use Storage Explorer to access your Blob data via RBAC. If you are signed in and Storage Explorer is unable to retrieve the keys for your Storage account, then an OAuth token will be used to authenticate when interacting with your data.
• Storage Explorer now supports ADLS Gen2 Storage accounts. When Storage Explorer detects that hierarchical namespace is enabled for a Storage account, you will see "(ADLS Gen2 Preview)" next to the name of your Storage account. Storage Explorer is able to detect whether or not hierarchical namespace is enabled when you are signed in, or if you have attached your Storage Account with name and key. For ADLS Gen2 Storage accounts, you can use Storage Explorer to:
  • Create and delete containers.
  • Manage container properties and permissions (left-hand side).
  • View and navigate data inside of containers.
  • Create new folders.
  • Upload, download, rename, and delete files and folders.
  • Manage file and folder properties and permissions (right-hand side).
    Other typical Blob features, such as Soft Delete, and Snapshots, are not currently available. Managing permissions is also only available when signed in. Additionally, when working in an ADLS Gen2 Storage account, Storage Explorer will use AzCopy for all uploads and downloads and default to using name and key credentials for all operations if available.
• After strong user feedback, break lease can once again be used to break leases on multiple blobs at once.

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

v1.6.0

12/4/2018

Welcome to version 1.6.0 of Microsoft Azure Storage Explorer. This release focuses on supporting RBAC for Blobs and ADLS Gen2 Storage accounts.

New

• You can now use Storage Explorer to access your Blob data via RBAC. If you are signed in and Storage Explorer is unable to retrieve the keys for your Storage account, then an OAuth token will be used to authenticate when interacting with your data.

• Storage Explorer now supports ADLS Gen2 Storage accounts. When Storage Explorer detects that hierarchical namespace is enabled for a Storage account, you will see "(ADLS Gen2 Preview)" next to the name of your Storage account. Storage Explorer is able to detect whether or not hierarchical namespace is enabled when you are signed in, or if you have attached your Storage Account with name and key. For ADLS Gen2 Storage accounts, you can use Storage Explorer to:

  • Create and delete containers.
  • Manage container properties and permissions (left-hand side).
  • View and navigate data inside of containers.
  • Create new folders.
  • Upload, download, rename, and delete files and folders.
  • Manage file and folder properties and permissions (right-hand side).

  Other typical Blob features, such as Soft Delete, and Snapshots, are not currently available. Managing permissions is also only available when signed in. Additionally, when working in an ADLS Gen2 Storage account, Storage Explorer will use AzCopy for all uploads and downloads and default to using name and key credentials for all operations if available.

• After strong user feedback, break lease can once again be used to break leases on multiple blobs at once.

Known Issues

• When downloading from an ADLS Gen2 Storage account, if one of the files being transferred already exists, then AzCopy will sometimes crash. This will be fixed in an upcoming hotfix.

• 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

v1.5.0

10/29/2018

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.

• Additionally, 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

Fix

• 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. Attempting to use these features while working with Azure Stack resources may result in unexpected errors.

  • File shares
  • Access tiers
  • Soft Delete

• 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

v1.4.4

10/15/2018

Hotfixes

• The Azure Resource Management API Version has been rolled back to unblock Azure US Government users. #696
• Loading spinners are now using CSS animations to reduce the amount of GPU used by Storage Explorer. #653

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.

Fixes

• 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

v1.4.2

09/24/2018

Hotfixes

• Update Azure Resource Management Api Version to 2018-07-01 to add support for new Azure Storage Account kinds. #652

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

v1.4.1

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

v1.3.1

07/11/2018

New

• Accessing the $web containers used by Static Websites is now supported. This allows you to easily upload and manage files and folders used by your website. #223
• The app bar on macOS has been reorganized. Changes include a File menu, some shortcut key changes, and several new commands under the app menu. #99
• The authority endpoint for signing in to Azure US Government has been changed to https://login.microsoftonline.us/
• Accessibility: When a screen reader is active, keyboard navigation now works with the tables used for displaying items on the right-hand side. You can use the arrow keys to navigate rows and columns, Enter to invoke default actions, the context menu key to open up the context menu for an item, and Shift or Control to multiselect. #103

Fixes

• On some machines, child processes were taking a long time to start. When this would happen, a "child process failed to start in a timely manner" error would appear. The time allotted for a child process to start has now been increased from 20 to 90 seconds. If you are still affected by this issue, please comment on the linked GitHub issue. #281
• When using a SAS that did not have read permissions, it was not possible to upload a large blob. The logic for upload has been modified to work in this scenario. #305
• Setting the public access level for a container would remove all access policies, and vice versa. Now, public access level and access policies are preserved when setting either of the two. #197
• "AccessTierChangeTime" was truncated in the Properties dialog. This has been fixed. #145
• The "Microsoft Azure Storage Explorer -" prefix was missing from the Create New Directory dialog. This has been fixed. #299
• Accessibility: The Add Entity dialog was difficult to navigate when using VoiceOver. Improvements have been made. #206
• Accessibility: The background color of the collapse/expand button for the Actions and Properties pane was inconsistent with similar UI controls in High Contrast Black theme. The color has been changed. #123
• Accessibility: In High Contrast Black theme, the focus styling for the 'X' button in the Properties dialog was not visible. This has been fixed. #243
• Accessibility: The Actions and Properties tabs were missing several aria values which resulted in a subpar screen reader experience. The missing aria values have now been added. #316
• Accessibility: Collapsed tree nodes on the left hand side were not being given an aria-expanded value of false. This has been fixed. #352

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 this issue 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.
• 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, and attempting to use them while working with Azure Stack may result in unexpected errors:
  • File shares
  • Access tiers
  • Soft Delete
• 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