Skip to content
  • v1.14.0
  • 64ca6ba
  • Compare
    Choose a tag to compare
    Search for a tag
  • v1.14.0
  • 64ca6ba
  • Compare
    Choose a tag to compare
    Search for a tag

@jinglouMSFT jinglouMSFT released this Jun 24, 2020

6/24/2020 (Version 1.14.0 / Build 20200624.3)

Welcome to Storage Explorer version 1.14.0.

New

AzCopy

  • There is now a setting to turn on AzCopy's --decompress flag. Enabling this flag will tell AzCopy to decompress files during download. Supported compression formats are gzip and deflate. You can find more information about this setting under: Settings → Transfers → AzCopy → Decompress Files. #758 #2359
  • There is now a setting to turn on AzCopy's --preserve-smb-info flag. Enabling this flag will tell AzCopy to preserve SMB information when transferring data between File Shares and other SMB aware resources. You can find more information about this setting under: Settings → Transfers → AzCopy → Preserve SMB information. #2969

Blobs

  • If you have a custom domain for a Storage Account, you can now choose to use your custom domain instead of the Blob service endpoint when copying Blob URLs. #1153
  • When uploading Blobs with a SAS whose permissions come from an Access Policy, you will now be asked how you would like to handle overwrites and other features which require read permission. #2336
  • Support has been added for properly browsing files and folders with no name. Some operations are disabled for such files and folders though. For more information see the linked issue. #1512
  • You can now double click to open files in ADLS Gen2 Blob containers. #3044
  • Files put onto the clipboard from your operating system's file system can now be pasted into Blob containers. #1203

Queues

  • Storage Explorer now supports accessing Queue resources via RBAC. #975
  • Possible values for time to live (TTL) have been expanded when adding a message. You can now specify any positive TTL or even no TTL. #314
  • You can now specify a visibility delay when adding a message to a queue. #2738

Linux Requirements

  • Storage Explorer now requires .NET Core version 2.1 or 2.2 on Linux. Previously, only version 2.2 was compatible. #2752
  • The Linux dependencies section in the troubleshooting guide has been updated with new information.

Other

  • Storage Explorer is now using Electron 8.2.4.
  • For most text input dialogs, the default text in the text input box is now highlighted. #2071
  • When computing statistics in a Blob container or File Share, a timestamp is now added to the final results in the Activity Log. #222

Fixes

  • Disk copies would fail if the copy was from one tenant to another. This has been fixed. #2722
  • Certain queue messages would be mistakenly identified as Base64 encoded and thus be Base64 decoded. Now, you can toggle between viewing queue messages as Base64 encoded or UTF-8 encoded. #1338
  • For certain dates, the date picker in the Manage Access Policies dialog would become buggy. This has been fixed. #2812
  • The validation for Blob metadata keys was not correctly identifying all invalid strings. This has been fixed. #2567
  • The save file dialog would freeze for certain locales on macOS. This was fixed by the Electron upgrade. #2794
  • After searching by prefix in a Blob container, if a folder was returned and you navigated into that folder, the prefix to search would be lost and the navigation would fail. This has been fixed. #541 #2667

A full list of issues closed in 1.14.0 can be found here.

Known Issues

  • If you are on Windows 10, version 1909 or older, and you try to open a file without a file extension, you will be unable to select what application you would like to use to open the file. This issue is fixed in Windows 10 version 2004. #1531
  • Messages with no time to live may cause issues when working with the .NET Storage Emulator or Azure Stack. #3124

A full list of currently open issues can be found here.

Assets 5
  • v1.13.1
  • 64ca6ba
  • Compare
    Choose a tag to compare
    Search for a tag
  • v1.13.1
  • 64ca6ba
  • Compare
    Choose a tag to compare
    Search for a tag

@jinglouMSFT jinglouMSFT released this May 18, 2020

5/18/2020 (Version 1.13.1 / Build 20200515.1)

Welcome to Storage Explorer version 1.13.1. This is a hotfix release of version 1.13.0. For more details, continue reading below.

Hotfixes

  • Forward slashes ("/") in Blob URLs for Copy URL and the Properties dialog were being encoded. They are now back to being not encoded. #2939
  • For Blob snapshot URLs, the snapshot ID is now present both for Copy URL and in the Properties dialog. #2788
  • Several properties were missing from the Properties dialog for Blobs. All missing properties have been restored. #2940
  • When generating a SAS for an emulator Blob or container, the emulator account name was missing. This has been fixed. #2948
  • If you used a stored access policy while creating a Blob SAS, the SAS would incorrectly be a container SAS. This has been fixed. #2981

New

AzCopy

  • File Share transfers now use AzCopy. This includes:
    • Clone with new name
    • Upload & download
    • Copy & paste
    • Delete
  • The integrated AzCopy version is now v10.4.2.
  • When attaching via SAS, AzCopy features are now able to work with a wider variety of SAS permissions. #2336
  • When deleting a Blob with snapshots, you can now choose to delete all snapshots on retry. #2202 #1286

Settings

  • You can now disable the usage of Storage Account keys for all Blob actions. To do so, go to Settings → Services → Storage Accounts → Disable Usage of Keys.
  • You can now configure what file extensions Storage Explorer considers safe when opening a file. To view and modify trusted file extensions, go to Settings → Transfers → File Open → Trusted File Extensions. #164
  • You can now configure whether or not Storage Explorer shows metrics tables. This setting can be found under Settings → Services → Storage Accounts → Show metrics tables. #3
  • You can now choose whether or not Storage Explorer includes type annotations when exporting from a table. To configure this, go to Settings → Transfers → Table Import/Export → Export Type Annotations. #2104

Other

  • On Windows, the Storage Explorer installer no longer requires you to have administrator permissions. #1108
  • You can now "requeue" a message in a queue. When you requeue a message, a new message with the same contents and lifespan as the original message will be added to the queue. #1064
  • You can now add or edit binary values in tables. #554
  • On Windows, Storage Explorer now requires .NET 4.7.2 at a minimum.

Fixes

  • Downloading blobs with ":" in their names is now fixed. #2297
  • In the table explorer, when editing a query, shortcut keys would sometimes trigger actions in the table view. This has been fixed. #2741 #2631
  • Deleting Blob folders with * characters in their name would result in an error. This has been fixed. #2651
  • Storage Explorer now prevents you from adding too many entities to an ADLS Gen2 access control list. #2650
  • Storage Explorer will no longer check the value of a Disk's MD5 hash. The underlying blobs for Disks should not have an MD5 hash. Therefore any attempt to check the hash could result in a false alarm. #2588
  • On macOS, if you made Storage Explorer full screen and then did something that opened a dialog, the main Storage Explorer window would become unusable. This has been fixed. #2302
  • When creating access policies for containers with very long names, Storage Explorer would generate IDs which were too long. This has been fixed. #2191
  • Fixed accessibility bugs. A full list can be found here.
  • Fixed localization bugs. A full list can be found here.

A full list of issues closed in 1.13.0 can be found here.

Known Issues

  • If any of your blobs have the metadata hdi_isfolder=true, there may be issues deleting those blobs or their corresponding virtual folder. #2665
  • When MSAL is enabled you might see duplicate accounts.
  • Copying data between file shares in different storage accounts might fail if you have Storage Firewall enabled for either account. A server side fix for this issue is being rolled out. If you encounter this issue prior to the fix’s deployment, you can use Storage Explorer v1.12.0. To see the status of the service roll out, please see #2845.
  • Copying data from a file share snapshot may fail. To restore data from a file share snapshot to its root, please use the Restore Snapshot command. #964
  • When uploading from Windows to Azure Files or downloading from Azure Files to Windows, the SMB access control list will not be preserved.

To see all open issues, refer to our issues page.

Assets 5
  • v1.13.0
  • 64ca6ba
  • Compare
    Choose a tag to compare
    Search for a tag
  • v1.13.0
  • 64ca6ba
  • Compare
    Choose a tag to compare
    Search for a tag

@jinglouMSFT jinglouMSFT released this May 1, 2020

5/1/2020 (Build 20200430.5)

Welcome to Storage Explorer version 1.13.0. This release contains a significant number of new features, including no longer requiring administrator permissions when installing on Windows, and an assortment of bug fixes. For more details, continue reading below.

New

AzCopy

  • File Share transfers now use AzCopy. This includes:
    • Clone with new name
    • Upload & download
    • Copy & paste
    • Delete
  • The integrated AzCopy version is now v10.4.2.
  • When attaching via SAS, AzCopy features are now able to work with a wider variety of SAS permissions. #2336
  • When deleting a Blob with snapshots, you can now choose to delete all snapshots on retry. #2202 #1286

Settings

  • You can now disable the usage of Storage Account keys for all Blob actions. To do so, go to Settings → Services → Storage Accounts → Disable Usage of Keys.
  • You can now configure what file extensions Storage Explorer considers safe when opening a file. To view and modify trusted file extensions, go to Settings → Transfers → File Open → Trusted File Extensions. #164
  • You can now configure whether or not Storage Explorer shows metrics tables. This setting can be found under Settings → Services → Storage Accounts → Show metrics tables. #3
  • You can now choose whether or not Storage Explorer includes type annotations when exporting from a table. To configure this, go to Settings → Transfers → Table Import/Export → Export Type Annotations. #2104

Other

  • On Windows, the Storage Explorer installer no longer requires you to have administrator permissions. #1108
  • You can now "requeue" a message in a queue. When you requeue a message, a new message with the same contents and lifespan as the original message will be added to the queue. #1064
  • You can now add or edit binary values in tables. #554
  • On Windows, Storage Explorer now requires .NET 4.7.2 at a minimum.

Fixes

  • Downloading blobs with ":" in their names is now fixed. #2297
  • In the table explorer, when editing a query, shortcut keys would sometimes trigger actions in the table view. This has been fixed. #2741 #2631
  • Deleting Blob folders with * characters in their name would result in an error. This has been fixed. #2651
  • Storage Explorer now prevents you from adding too many entities to an ADLS Gen2 access control list. #2650
  • Storage Explorer will no longer check the value of a Disk's MD5 hash. The underlying blobs for Disks should not have an MD5 hash. Therefore any attempt to check the hash could result in a false alarm. #2588
  • On macOS, if you made Storage Explorer full screen and then did something that opened a dialog, the main Storage Explorer window would become unusable. This has been fixed. #2302
  • When creating access policies for containers with very long names, Storage Explorer would generate IDs which were too long. This has been fixed. #2191
  • Fixed accessibility bugs. A full list can be found here.
  • Fixed localization bugs. A full list can be found here.

A full list of issues closed in 1.13.0 can be found here.

Known Issues

  • If any of your blobs have the metadata hdi_isfolder=true, there may be issues deleting those blobs or their corresponding virtual folder. #2665
  • When MSAL is enabled you might see duplicate accounts.
  • Copying data between file shares in different storage accounts might fail if you have Storage Firewall enabled for either account. A server side fix for this issue is being rolled out. If you encounter this issue prior to the fix’s deployment, you can use Storage Explorer v1.12.0. To see the status of the service roll out, please see #2845.
  • Copying data from a file share snapshot may fail. To restore data from a file share snapshot to its root, please use the Restore Snapshot command. #964
  • When uploading from Windows to Azure Files or downloading from Azure Files to Windows, the SMB access control list will not be preserved.

To see all open issues, refer to our issues page.

Assets 5

@jinglouMSFT jinglouMSFT released this Jan 17, 2020 · 1 commit to master since this release

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

@jinglouMSFT jinglouMSFT released this Dec 19, 2019 · 1 commit to master since this release

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

@jinglouMSFT jinglouMSFT released this Nov 23, 2019 · 1 commit to master since this release

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

@jinglouMSFT jinglouMSFT released this Nov 5, 2019 · 1 commit to master since this release

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

@jinglouMSFT jinglouMSFT released this Sep 19, 2019 · 1 commit to master since this release

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.

Assets 5

@jinglouMSFT jinglouMSFT released this Sep 13, 2019 · 1 commit to master since this release

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.

Assets 5

@jinglouMSFT jinglouMSFT released this Jul 2, 2019 · 1 commit to master since this release

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.
Assets 5
You can’t perform that action at this time.