microsoft / microsoft/AzureStorageExplorer

Download always fails whenever bandwidth limit is set.

Open
#8,799 23 comments 0 reactions 1 assignee View on GitHub

@craxal is already working on this.

Since Jun 15, 2026.

:copilot: copilot :gear: azcopy :gear: data transfer
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Storage Explorer Version

1.39.1 (107)

Regression From

unknown

Architecture

x64

Storage Explorer Build Number

1.39.1 (107)

Platform

Windows

OS Version

Windows 11 build 26518

Bug Description

If I click "adjust bandwidth limit" on the active transfer to configure (to e.g. 20 Mbps), the active transfer will immediately fail.

If I use the "Settings" menu to configure the same for all future transfers, the active transfer ignores the setting, but all new downloads will fail quickly (within seconds).

It looks this feature is just broken.

Resource Types

No response

Authentication Method

Sign in

Connection Type

Sign in (subscription)

Steps to Reproduce

Repro A

  1. Start downloading a big file.
  2. Click "adjust bandwidth limit" on the active transfer to configure (to e.g. 20 Mbps), the active transfer will immediately fail.

Repro B

  1. Open the "Settings" menu.
  2. Configure "Maximum Transfer Rate" on the "Transfers" page (to e.g. 20 Mbps).
  3. Start downloading a file. The new download attempts will fail within seconds.
Actual Experience

Repro A: the active transfer will immediately fail.
Repro B: New download attempts will fail within seconds.

Expected Experience

A: The active download will continue but with limited speed.
B: New downloads can start successfully but with limited speed.

Additional Context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.