A metered connection tells Windows to reduce or defer some data use; it is not a new speed tier imposed by your ISP. Background activity may behave differently, but the setting does not mean every app is capped to one universal Mbps value. Separate three questions: how fast the connection can transfer, what software is allowed to download and how much data your plan permits.
Microsoft’s metered-connection documentation describes changes to updates, Store activity and syncing. It also explains that Wi-Fi and Ethernet can be marked metered, while cellular connections are normally metered by default. That is a data-management policy, not a measurement of current line quality.
Identify what actually seems limited
Start with a concrete observation. Is a Store download paused? Are updates waiting? Is a cloud folder not syncing? Or is every deliberate transfer consistently slow? Those situations should not be collapsed into “Windows is throttling my internet.” Record the app, displayed message and connection type before looking for a switch to change.
A paused update is different from a transfer that starts and stays slow. A notification about data policy is different from a timeout. Copy the wording into your notes. If you have a limited plan, check the remaining allowance with the provider as well; the Windows setting and the provider’s accounting are separate pieces of information.
For the difference between a rate and an amount, see Mbps versus MBps. A monthly number in GB describes volume, while a number in Mbps describes a transfer rate. Confusing those units can make a reasonable data-saving control look like an unexplained speed cap.
Review the setting without losing the reason it exists
Inspect the active connection’s metered status in Windows Network & internet settings. Write down the original choice before changing it. If the setting is managed or unavailable, ask the administrator rather than trying to override it. An organisation may be controlling data use for a reason you cannot see from a speed-test screen.
Do not mark a capped connection unmetered merely to make an update start. First decide whether you can afford that transfer and whether a less constrained connection is available. If you choose to allow a particular update, follow the supported control for that task and check the effect on data use afterwards.
A temporary comparison can still be useful, but it should have an explicit question and a restoration plan. For example, observe whether a documented app pause changes when its permitted connection conditions are satisfied. Do not interpret a faster unrelated browser test as proof that metered status was limiting all traffic.
Delivery Optimization has its own scope
Windows Update’s bandwidth controls are another source of confusion. Microsoft’s Delivery Optimization guide describes download and upload controls for that service, including a monthly upload limit. It states that its bandwidth limits do not apply to manually initiated downloads in the same way as automatic update downloads.
Therefore, a number in Delivery Optimization is not evidence that all browsers, games and video calls have that limit. Record which control you inspected and what kind of transfer you were observing. If the problem appeared after an update, the after-update troubleshooting guide follows that symptom without assuming every update changed network capacity.
Make a short, useful data-use comparison
- Choose one task you understand, such as a known app update or an ordinary file transfer. Read its message before starting.
- Record the current network, metered choice, any relevant service-specific limit and the provider’s remaining allowance if known.
- Pause unrelated transfers you control. Do not stop system or work processes whose purpose you do not understand.
- Observe whether the task is deferred, fails or transfers at a measurable rate. Those are separate outcomes.
- Change only a supported setting relevant to the question, if you have decided the resulting data use is acceptable.
- Record the result and restore your preferred policy. A temporary diagnostic choice should not silently become the permanent data plan.
If you also run an internet speed test, budget for its traffic and label it separately. A short throughput test is active data use, not a passive inspection of an ISP plan. Repeated testing can itself complicate a complaint about unexpected consumption.
What to send to support
A useful report includes the app’s exact message, Windows version, active connection type, metered status and the relevant service control. Explain whether a transfer was paused, failed or slow. Include a before-and-after observation only if the conditions were comparable.
If everything is slow regardless of these policies, return to the one-device troubleshooting process and compare another connection or device. Do not keep toggling data-saving controls to chase a fluctuating number. The next step should follow the symptom, while preserving the user’s data budget and chosen update behaviour.
Also ask whether the complaint concerns this computer’s usage or the entire household allowance. A Windows setting on one laptop is not a record of what every other connected device transferred.