v1.12.0

1/16/2020 (Build 20200116.10)

Welcome to the Storage Explorer version 1.12.0. This release is focused on accessibility and bug fixes.

New

• After a GPU crash, Storage Explorer will now remember if you chose to restart with GPU acceleration disabled and will always run with GPU acceleration disabled in the future. #2277
• Storage Explorer is now notarized for macOS. #2395

Fixes

• A bug has been fixed in our authentication library which was preventing authentication library processes from closing in a timely manner. #2498 #2372
• Fixed a variety of accessibility related issues. For a full list of issues fixed, see here.
• Fixed a variety of localization related issues. For a full list of issues fixed, see here.
• After upgrading, some Snap users were reporting that they could not start any long running operations, such as uploading and downloading. This has been fixed. #2320
• After opening a blob and then making and saving a change, if you chose "Ignore for now and save later", you would not be asked how to handle later saved changes to the file. This has been fixed. #2419
• In SAS attached file shares, an error related to "primaryHost" would sometimes occur while performing a clone with new name. This has been fixed. #2407
• Fixed a layout issue on the "Manage Accounts" panel. #1447
• Fixed an error message which wrongly said that Storage Explorer on Linux required .NET Core v2.1. Storage Explorer on Linux recently changed to needing .NET Core v2.2. #2322

Known Issues

• No new known issues are included in this release.

v1.11.2

12/17/2019 (Build 20191217.4)

Welcome to version 1.11.2 of Microsoft Azure Storage Explorer. The purpose of this hotfix is to decrease the chance of accidental data loss while using Rename features. We've recently become concerned that the difference in behavior between all of the currently available Rename features has increased the chance of users accidentally deleting their data.

If you have any feedback to share regarding this decision, please open an issue on GitHub.

New

• New for 1.11.2: All non-server-side Renames have been replaced with Clone with New Name.

• Operations for Blobs, ADLS Gen2 and Managed Disks now use the integrated AzCopy. More specifically, the following operations are done using AzCopy:

  • Blob Containers
    • New for 1.11.1: Copy & paste #2124
    • Blobs
    • Open for editing + Upload
    • Upload, including drag & drop
    • Download
    • Copy & paste #1249
    • Delete
  • ADLS Gen2 Blobs
    • Upload, including drag & drop
    • Download
    • Copy & paste
    • Delete, including folder delete
  • Managed Disks
    • Upload
    • Download
    • Copy & paste

  Additionally, several frequently requested features have been added to the integrated AzCopy experience:

  • Conflict resolutions - you will be prompted during transfers to resolve conflicts. #1455
  • Upload as page blobs - you can choose whether or not AzCopy uploads .vhd and .vhdx files as page blobs. #1164 and #1601
  • Configurable AzCopy parameters - Several settings have been added to tune AzCopy's performance and resource usage. See more details below.

• The integrated AzCopy has been updated to v10.3.2.

• New for 1.11.1: There is now a setting to enable a new authentication library, the Microsoft Authentication Library (MSAL). This library includes support for more robust multi-factor authentication, conditional access policies, and single sign on with Visual Studio 2019. If you've been having trouble signing in with the current authentication library then we encourage you to try using MSAL. In the near future, the current authentication library will be replaced with MSAL, so if you encounter issues using MSAL please open an issue on GitHub. You can find the MSAL setting under "Application" → "Sign-in" → "Microsoft Authentication Library (Preview)".

• To enable ADLS Gen2 and Blobs multi-protocol access and further enhance ADLS Gen2 experiences, we have added the following features for the ADLS Gen2 accounts:

  • Search using friendly names to set ACL permissions
  • View hidden containers, such as $logs and $web
  • Acquire and break container lease
  • Acquire and break Blob lease #848
  • Manage container access policies
  • Configure Blob access tiers
  • Copy & Paste Blobs

• In this release, we are previewing 17 additional languages. You can switch to a language of your choice on the settings page under "Application" → "Regional Settings" → "Language (Preview)". We are still working hard on translating additional strings and improving the translation quality. Should you have any feedback regarding a translation, or if you notice a string which is not yet translated, please open an issue on GitHub.

• In every release, we try to onboard a few settings to enable fine turning Storage Explorer. In this release, we added settings to further configure AzCopy as well as to hide service nodes:

  • AzCopy bandwidth limit - helps control how much of the network AzCopy uses. You can find this setting at "Transfers" → "AzCopy" → "Maximum transfer rate". #1099
  • AzCopy MD5 check - lets you configure if and how strictly AzCopy checks for MD5 hashes on download. You can find this setting at "Transfers" → "AzCopy" → "Check MD5".
  • AzCopy concurrency and memory buffer size - by default AzCopy will analyze your machine to determine reasonable default values for these settings. But if you run into performance problems, these advanced settings can be used to further tailor how AzCopy runs on your computer. You can find these settings under "Transfers" → "AzCopy". #994
  • Display and hide service nodes - these settings give you the options to display or hide any of the Azure services that Storage Explorer supports. You can find these settings under the "Services" section. #1877

• When creating a Snapshot of a Managed Disk, a default name is now provided. #1847

• When attaching with Azure AD, if you attach an ADLS Gen2 Blob container, then "(ADLS Gen2)" will be shown next to the node. #1861

Fixes

• New for 1.11.1: In 1.11.0, the ADLS Gen 2 multi-protocol access features were not utilizing Storage Explorer's proxy settings. This has been fixed.
• New for 1.11.1: In 1.11.0, AzCopy transfers had issues cancelling if discovery was not yet completed. This has been fixed.
• New for 1.11.1: In 1.11.0, access policies for ADLS Gen 2 containers were not being properly set. This has been fixed. #2283
• When copying, uploading, or downloading large Disks, Storage Explorer would sometimes fail to revoke access to the disks involved in the operation. This has been fixed. #2048
• Table statistics failed when viewing a partition key query. This has been fixed. #1886

Known Issues

• For Snap users, if you see any jobs which are queued forever, or if you see any error messages related to "mkdir" or "session.json", you may need to delete the folder ~/snap/storage-explorer/current/.confg/storage-explorer/sessions.

• There is a known issue with the ADLS Gen2 platform which may affect some users of Storage Explorer. If the permissions you use for accessing ADLS Gen2 data come from a group, and you are a member of a lot (roughly 200 or more) of groups, then you may receive a "resource not found" error when accessing your data. For more information, and the latest status on this issue, click here. Note: once the issue has been fixed, the issue will be removed from that page.
• Storage Explorer 1.11.0 now requires a DFS endpoint (such as "myaccount.dfs.core.windows.net") to attach to ADLS Gen2 containers. Previous versions of Storage Explorer allowed you to use a blob endpoint. These attachments may no longer work after upgrading to 1.11.0. If you encounter this problem, reattach using the DFS endpoint.
• Numeric settings are not checked for whether they lie in a valid range.#2140
• Copying blob containers from one storage account to another in the tree view may fail. We are investigating the issue.#2124
• To see all known issues, refer to the online release notes.

v1.11.1

11/20/2019 (Build 20191121.1)

Welcome to version 1.11.1 of Microsoft Azure Storage Explorer. This hotfix release resolves some new issues from 1.11.0, and also adds a new feature which was not ready in time for 1.11.0. For more details on the changes, continue reading below.

As a friendly reminder, we recommend Linux users get Storage Explorer from the Snap Store.

New

• Operations for Blobs, ADLS Gen2 and Managed Disks now use the integrated AzCopy. More specifically, the following operations are done using AzCopy:

  • Blob Containers

    • New for 1.11.1: Copy & paste #2124

    • Blobs
    • Open for editing + Upload
    • Upload, including drag & drop
    • Download
    • Copy & paste #1249
    • Delete
  • ADLS Gen2 Blobs
    • Upload, including drag & drop
    • Download
    • Copy & paste
    • Delete, including folder delete
  • Managed Disks
    • Upload
    • Download
    • Copy & paste

  Additionally, several frequently requested features have been added to the integrated AzCopy experience:

  • Conflict resolutions - you will be prompted during transfers to resolve conflicts. #1455
  • Upload as page blobs - you can choose whether or not AzCopy uploads .vhd and .vhdx files as page blobs. #1164 and #1601
  • Configurable AzCopy parameters - Several settings have been added to tune AzCopy's performance and resource usage. See more details below.

• The integrated AzCopy has been updated to v10.3.2.

• New for 1.11.1: There is now a setting to enable a new authentication library, the Microsoft Authentication Library (MSAL). This library includes support for more robust multi-factor authentication, conditional access policies, and single sign on with Visual Studio 2019. If you've been having trouble signing in with the current authentication library then we encourage you to try using MSAL. In the near future, the current authentication library will be replaced with MSAL, so if you encounter issues using MSAL please open an issue on GitHub. You can find the MSAL setting under "Application" → "Sign-in" → "Microsoft Authentication Library (Preview)".

• To enable ADLS Gen2 and Blobs multi-protocol access and further enhance ADLS Gen2 experiences, we have added the following features for the ADLS Gen2 accounts:

  • Search using friendly names to set ACL permissions
  • View hidden containers, such as $logs and $web
  • Acquire and break container lease
  • Acquire and break Blob lease #848
  • Manage container access policies
  • Configure Blob access tiers
  • Copy & Paste Blobs

• In this release, we are previewing 17 additional languages. You can switch to a language of your choice on the settings page under "Application" → "Regional Settings" → "Language (Preview)". We are still working hard on translating additional strings and improving the translation quality. Should you have any feedback regarding a translation, or if you notice a string which is not yet translated, please open an issue on GitHub.

• In every release, we try to onboard a few settings to enable fine turning Storage Explorer. In this release, we added settings to further configure AzCopy as well as to hide service nodes:

  • AzCopy bandwidth limit - helps control how much of the network AzCopy uses. You can find this setting at "Transfers" → "AzCopy" → "Maximum transfer rate". #1099
  • AzCopy MD5 check - lets you configure if and how strictly AzCopy checks for MD5 hashes on download. You can find this setting at "Transfers" → "AzCopy" → "Check MD5".
  • AzCopy concurrency and memory buffer size - by default AzCopy will analyze your machine to determine reasonable default values for these settings. But if you run into performance problems, these advanced settings can be used to further tailor how AzCopy runs on your computer. You can find these settings under "Transfers" → "AzCopy". #994
  • Display and hide service nodes - these settings give you the options to display or hide any of the Azure services that Storage Explorer supports. You can find these settings under the "Services" section. #1877

• When creating a Snapshot of a Managed Disk, a default name is now provided. #1847

• When attaching with Azure AD, if you attach an ADLS Gen2 Blob container, then "(ADLS Gen2)" will be shown next to the node. #1861

Fixes

• New for 1.11.1: In 1.11.0, the ADLS Gen 2 multi-protocol access features were not utilizing Storage Explorer's proxy settings. This has been fixed.

• New for 1.11.1: In 1.11.0, AzCopy transfers had issues cancelling if discovery was not yet completed. This has been fixed.

• New for 1.11.1: In 1.11.0, acces policies for ADLS Gen 2 containers were not being properly set. This has been fixed. #2283

• When copying, uploading, or downloading large Disks, Storage Explorer would sometimes fail to revoke access to the disks involved in the operation. This has been fixed. #2048
• Table statistics failed when viewing a partition key query. This has been fixed. #1886

Known Issues

• There is a known issue with the ADLS Gen2 platform which may affect some users of Storage Explorer. If the permissions you use for accessing ADLS Gen2 data come from a group, and you are a member of a lot (roughly 200 or more) of groups, then you may receive a "resource not found" error when accessing your data. For more information, and the latest status on this issue, click here. Note: once the issue has been fixed, the issue will be removed from that page.
• Storage Explorer 1.11.0 now requires a DFS endpoint (such as "myaccount.dfs.core.windows.net") to attach to ADLS Gen2 containers. Previous versions of Storage Explorer allowed you to use a blob endpoint. These attachments may no longer work after upgrading to 1.11.0. If you encounter this problem, reattach using the DFS endpoint.
• Numeric settings are not checked for whether they lie in a valid range.#2140
• Copying blob containers from one storage account to another in the tree view may fail. We are investigating the issue.#2124
• To see all known issues, refer to the online release notes.

v1.11.0

11/4/2019 (Build 20191105.2)

Welcome to version 1.11.0 of Microsoft Azure Storage Explorer. We are excited to bring you this new release, filled with new features and noticeable improvements in several areas. To name a few, Blob, ADLS Gen2 and Managed Disks operations now use the integrated AzCopy for stability and performance improvements. We have also fixed a few customer reported issues. In this release, we also bring some Blob specific features to ADLS Gen2 accounts through the multi-protocol access. Last but not least, we are previewing 17 additional languages for our international customers around the world. We'd like to take this opportunity to thank all of our users for your support and your valuable feedback. We really appreciate it! For more details, please continue reading below.

As a friendly reminder, we recommend Linux users get Storage Explorer from the Snap Store.

New

• Operations for Blobs, ADLS Gen2 and Managed Disks use the integrated AzCopy. More specifically, the following operations are done using AzCopy:

  • Blobs
    • Open for editing + Upload
    • Upload, including drag & drop
    • Download
    • Copy & paste #1249
    • Delete
  • ADLS Gen2 Blobs
    • Upload, including drag & drop
    • Download
    • Copy & paste
    • Delete, including folder delete
  • Managed Disks
    • Upload
    • Download
    • Copy & paste

  Additionally, several frequently requested features have been added to the integrated AzCopy experience:

  • Conflict resolutions - you will be prompted during transfers to resolve conflicts. #1455
  • Upload as page blobs - you can choose whether or not AzCopy uploads .vhd and .vhdx files as page blobs. #1164 and #1601
  • Configurable AzCopy parameters - Several settings have been added to tune AzCopy's performance and resource usage. See more details below.

• To enable ADLS Gen2 and Blobs multi-protocol access and further enhance ADLS Gen2 experiences, we have added the following features for the ADLS Gen2 accounts:

  • Search using friendly names to set ACL permissions
  • View hidden containers, such as $logs and $web
  • Acquire and break container lease
  • Acquire and break Blob lease #848
  • Manage container access policies
  • Configure Blob access tiers
  • Copy & Paste Blobs

• In this release, we are previewing 17 additional languages. You can switch to a language of your choice on the settings page under "Application" → "Regional Settings" → "Language (Preview)". We are still working hard on translating additional strings and improving the translation quality. Should you have any feedback regarding a translation, or if you notice a string which is not yet translated, please open an issue on GitHub.

• In every release, we try to onboard a few settings to enable fine turning Storage Explorer. In this release, we added settings to further configure AzCopy as well as to hide service nodes:

  • AzCopy bandwidth limit - helps control how much of the network AzCopy uses. You can find this setting at "Transfers" → "AzCopy" → "Maximum transfer rate". #1099
  • AzCopy MD5 check - lets you configure if and how strictly AzCopy checks for MD5 hashes on download. You can find this setting at "Transfers" → "AzCopy" → "Check MD5".
  • AzCopy concurrency and memory buffer size - by default AzCopy will analyze your machine to determine reasonable default values for these settings. But if you run into performance problems, these advanced settings can be used to further tailor how AzCopy runs on your computer. You can find these settings under "Transfers" → "AzCopy". #994
  • Display and hide service nodes - these settings give you the options to display or hide any of the Azure services that Storage Explorer supports. You can find these settings under the "Services" section. #1877

• When creating a Snapshot of a Managed Disk, a default name is now provided. #1847

• When attaching with Azure AD, if you attach an ADLS Gen2 Blob container, then "(ADLS Gen2)" will be shown next to the node. #1861

Fixes

• When copying, uploading, or downloading large Disks, Storage Explorer would sometimes fail to revoke access to the disks involved in the operation. This has been fixed. #2048
• Table statistics failed when viewing a partition key query. This has been fixed. #1886

Known Issues

• Storage Explorer 1.11.0 now requires a DFS endpoint (such as "myaccount.dfs.core.windows.net") to attach to ADLS Gen2 containers. Previous versions of Storage Explorer allowed you to use a blob endpoint. These attachments may no longer work after upgrading to 1.11.0. If you encounter this problem, reattach using the DFS endpoint.
• Numeric settings are not checked for whether they lie in a valid range.#2140
• Copying blob containers from one storage account to another in the tree view may fail. We are investigating the issue.#2124
• To see all known issues, refer to the online release notes.

V1.9.0

7/1/2019 (Build 20190701.8)

Welcome to version 1.9.0 of Microsoft Azure Storage Explorer. This release adds a new Attach with Azure AD feature and RBAC support for more blob operations.

New

• You can now attach Blob containers via Azure AD (RBAC or ACL permisions). This feature is intended to help users who have access to containers but not the Storage Accounts that the containers are in. See our Getting Started Guide for more information on this feature.
• Acquire and break lease now work with RBAC. #1354
• Managing access policies and setting public access level now work with RBAC. #1355
• Deleting blob folders now work with RBAC. #1450
• Changing blob access tier now work with RBAC. #1446
• You can now quickly reset Quick Access via "Help" → "Reset". #1327

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

• Fixed being unable to load more than 50 subscriptions for one account. #1416
• Fixed the "Sign in" button not working on the infobar that appears when a direct link fails. #1358
• Fixed not being to upload .app files on macOS. #1119
• Fixed "Retry All" not working for a failed blob rename. #992
• Fixed "Cancel" not working while opening a blob. #1464
• Fixed multiple spelling and tooltip isssues throughout the product. Many thanks to all who reported these issues! #1303, #1328, #1329, #1331, #1336, #1352, #1368, #1395

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.10.1

9/19/2019 (Build 20190919.2)

Welcome to version 1.10.1 of Microsoft Azure Storage Explorer. This release contains 2 new exciting features: Managed Disks and Settings. Additionally, Storage Explorer is now available for Linux via the Snap Store. For more information on these and all other changes and fixes continue reading below.

Hotfix

• Some users encountered an error in 1.10.0 while attempting to view their data in their ADLS Gen 1 accounts. This error prevented the explorer panel from rendering properly. This has been fixed. #1853 #1865

New

• Storage Explorer now has a dedicated Settings UI. You can access it either from Edit → Settings, or by clicking on the Settings icon (the gear) in the left-hand vertical toolbar. This feature is the first step we're taking towards providing a variety of user requested settings. Starting in this release the following settings are supported:
  • Theme
  • Proxy
  • Logout on exit #6
  • Enable device code flow sign-in
  • Auto refresh #1526
  • Enable AzCopy
  • AzCopy SAS duration
    If there are other setttings you would like to see added, please open an issue on GitHub describing the setting you want to see.
• Storage Explorer now supports Managed Disks. You can:
  • Upload an on-prem VHD to a new Disk
  • Download a Disk
  • Copy and paste disks across resource groups and regions
  • Delete Disks
  • Create a Snapshot of a Disk
    The uploading, downloading, and cross-region copying of disks are powered by AzCopy v10.
• Storage Explorer can now be installed via the Snap store on Linux. When you install via the Snap store, all dependencies are installed for you, including .NET Core! Currently we have verified that Storage Explorer runs well on Ubuntu and CentOS. If you encounter issues installing from the Snap store on other Linux distros, please open an issue on GitHub. To learn more about installing from the Snap store, see our getting started guide. #68
• Two major changes have been made to attach with Azure Active Directory (Azure AD) which are intended to make the feature more useful for ADLS Gen2 users:
  • You now select the tenant that the resource you are attaching is in. This means that you no longer need to have RBAC access to the resource's subscription.
  • If you are attaching an ADLS Gen2 Blob Container, you can now attach to a specific path in the container.
• When managing ACLs for ADLS Gen2 files and folders, Storage Explorer will now show the friendly names for entities in the ACL. #957
• When adding via OID to an ADLS Gen2 ACL, Storage Explorer will now validate that the OID belongs to a valid entity in your tenant. #1603
• The keyboard shortcuts for navigating between tabs now use more standard key combinations. #1018
• Middle clicking on a tab will now close it. #1348
• If an AzCopy transfer contains skips and no failures, Storage Explorer will now show a warning icon to highlight that skips occured. #1490
• The integrated AzCopy has been updated to version 10.2.1. Additionally, you can now view the version of AzCopy installed in the About dialog. #1343

Fixes

• Many users have run into various "cannot read version of undefined" or "cannot read connection of undefined" errors when working with attached Storage Accounts. Although we are still continuing to investigate the root cause of this issue, in 1.10.0 we have improved the error handling around loading attached Storage Accounts. #1626, #985, and #1532
• It was possible for the explorer tree (left-hand side) to get into a state where focus would jump to the top node repeatedly. This has been fixed. #1596
• When managing a blob's snapshots, screenreaders would not read the timestamp associated with the snapshot. This has been fixed. #1202
• Proxy setting on macOS were not being set in time for the authentication process to use them. This has been fixed. #1567
• If a Storage Account in a sovereign cloud was attached using name and key, AzCopy would not work. This has been fixed. #1544
• When attaching via a connection string, Storage Explorer will now remove trailing spaces. #1387

Known Issues

• The Auto Refresh setting does not yet affect all operations in the Blob Explorer.
• Managed Disk features are not supported in Azure Stack.
• If a Disk upload or paste fails and a new Disk was created prior to the failure, Storage Explorer will not delete the Disk for you.
• Depending on when you cancel a Disk upload or paste, it is possible to leave the new Disk in a corrupted state. If this happens, you either need to delete the new Disk, or manually call the Disk APIs to replace the contents of the Disk such that it is no longer corrupted.

To see all known issues, refer to the online release notes.

V1.10.0

9/12/2019 (Build 20190912.8)

Welcome to version 1.10.0 of Microsoft Azure Storage Explorer. This release contains 2 new exciting features: Managed Disks and Settings. Additionally, Storage Explorer is now available for Linux via the Snap Store. For more information on these and all other changes and fixes continue reading below.

New

• Storage Explorer now has a dedicated Settings UI. You can access it either from Edit → Settings, or by clicking on the Settings icon (the gear) in the left-hand vertical toolbar. This feature is the first step we're taking towards providing a variety of user requested settings. Starting in this release the following settings are supported:
  • Theme
  • Proxy
  • Logout on exit #6
  • Enable device code flow sign-in
  • Auto refresh #1526
  • Enable AzCopy
  • AzCopy SAS duration
    If there are other setttings you would like to see added, please open an issue on GitHub describing the setting you want to see.
• Storage Explorer now supports Managed Disks. You can:
  • Upload an on-prem VHD to a new Disk
  • Download a Disk
  • Copy and paste disks across resource groups and regions
  • Delete Disks
  • Create a Snapshot of a Disk
    The uploading, downloading, and cross-region copying of disks are powered by AzCopy v10.
• Storage Explorer can now be installed via the Snap store on Linux. When you install via the Snap store, all dependencies are installed for you, including .NET Core! Currently we have verified that Storage Explorer runs well on Ubuntu and CentOS. If you encounter issues installing from the Snap store on other Linux distros, please open an issue on GitHub. To learn more about installing from the Snap store, see our getting started guide. #68
• Two major changes have been made to attach with Azure Active Directory (Azure AD) which are intended to make the feature more useful for ADLS Gen2 users:
  • You now select the tenant that the resource you are attaching is in. This means that you no longer need to have RBAC access to the resource's subscription.
  • If you are attaching an ADLS Gen2 Blob Container, you can now attach to a specific path in the container.
• When managing ACLs for ADLS Gen2 files and folders, Storage Explorer will now show the friendly names for entities in the ACL. #957
• When adding via OID to an ADLS Gen2 ACL, Storage Explorer will now validate that the OID belongs to a valid entity in your tenant. #1603
• The keyboard shortcuts for navigating between tabs now use more standard key combinations. #1018
• Middle clicking on a tab will now close it. #1348
• If an AzCopy transfer contains skips and no failures, Storage Explorer will now show a warning icon to highlight that skips occured. #1490
• The integrated AzCopy has been updated to version 10.2.1. Additionally, you can now view the version of AzCopy installed in the About dialog. #1343

Fixes

• Many users have run into various "cannot read version of undefined" or "cannot read connection of undefined" errors when working with attached Storage Accounts. Although we are still continuing to investigate the root cause of this issue, in 1.10.0 we have improved the error handling around loading attached Storage Accounts. #1626, #985, and #1532
• It was possible for the explorer tree (left-hand side) to get into a state where focus would jump to the top node repeatedly. This has been fixed. #1596
• When managing a blob's snapshots, screenreaders would not read the timestamp associated with the snapshot. This has been fixed. #1202
• Proxy setting on macOS were not being set in time for the authentication process to use them. This has been fixed. #1567
• If a Storage Account in a sovereign cloud was attached using name and key, AzCopy would not work. This has been fixed. #1544
• When attaching via a connection string, Storage Explorer will now remove trailing spaces. #1387

Known Issues

• The Auto Refresh setting does not yet affect all operations in the Blob Explorer.
• Managed Disk features are not supported in Azure Stack.
• If a Disk upload or paste fails and a new Disk was created prior to the failure, Storage Explorer will not delete the Disk for you.
• Depending on when you cancel a Disk upload or paste, it is possible to leave the new Disk in a corrupted state. If this happens, you either need to delete the new Disk, or manually call the Disk APIs to replace the contents of the Disk such that it is no longer corrupted.

To see all known issues, refer to the online release notes.

V1.8.1

5/10/2019 (Build 20190510.6)

Welcome to version 1.8.1 of Microsoft Azure Storage Explorer. This is a hotfix release to fix 2 issues created in 1.8.0, and one outstanding bug which was recently found.

Hotfixes

• In some cases, clicking "Load more" at the resource level would not return the next page of resources. This has been fixed. #1359
• On Windows, AzCopy downloads would fail if a single file or folder was being downloaded and the name of the file or folder had a character which was invalid for a Windows path. This has been fixed. #1350
• In extremely rare cases, while performing a rename of a File Share or a rename in a File Share, if the copies for the rename failed, or if Storage Explore was unable to confirm the success of the copies with Azure, there was the potential for Storage Explorer to delete the original files before the copy had finished. This has been fixed.

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.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