Microsoft

Windows 10: Fears that Microsoft is about to force updates over metered connections


windowsupdateometeredconnectionsw10cu.png

Microsoft now says on metered connections it will “automatically download only those updates required to keep Windows running smoothly”.


Image: SuperSite Windows/Microsoft

Some Windows fans are worried that the upcoming Windows 10 Creators Update could mean costly data bills.

Windows 10 currently treats Windows Updates on cellular networks differently to those over Wi-Fi because Microsoft knows these updates can be large and result in sizeable bills if they take place on a so-called metered connection, such as a cellular network.

For this reason Windows 10 only downloads ‘priority updates’.

But, as SuperSite Windows reports, the latest Windows Insider fast ring build of the Windows 10 Creators update notes a change to the language used.

In the Windows Update section of Windows Settings, Microsoft now says on metered connections it will “automatically download only those updates required to keep Windows running smoothly”.

Microsoft could allay fears by expanding on what these necessary updates are and how big might they might be.

Of course, the fast ring Insider builds aren’t necessarily what will arrive in the final release, but the Creators Update is expected to arrive in only a few weeks’ time now.

We’ve asked Microsoft to clarify what it means and will update the story if it responds.

In the longer term, Microsoft is working on a new update system that will deliver smaller updates in future, which will eventually benefit users regardless of the connection they’re on.

Source Article from http://www.zdnet.com/article/windows-10-fears-that-microsoft-is-about-to-force-updates-over-metered-connections/#ftag=RSSbaffb68


Leave a Comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>