Want to keep testing new features?
Advertisement
Last month, I warned readers that Microsoft’s Windows 10 Anniversary Update would likely be somewhat buggy and suggested consumers should wait awhile before installing it.
Addressed additional issues with certain devices that can’t transition from connected standby to sleep mode, updates not installing, and Internet Explorer 11.
“This occurred during upgrades to the Windows 10 Anniversary edition from previous versions of Windows, and during clean installations of Avast Antivirus on systems already running the Anniversary Update”.
Addressed issue in DNS Subnet Prioritization that was impacting network connectivity.
There’s been some hedging about the actual date of that release: You may recall that a now deleted Microsoft tweet claimed that Windows 10 Mobile 1067 would be “available on August 9, 2016”, though that date has passed. Some believed that would happen today, but it did not.
We wanted to send out a quick note reminding Windows Insiders to check their ring settings. Now that the Windows 10 Anniversary Update (Build 14393) has been released to our customers, it has replaced the Windows 10 November Update (Build 10586) in the Current Branch. Much like how Redstone 1 was developed, Microsoft has announced that they are focusing on under-the-hood changes first, adding new features later down the line.
Well, we know that the product is on build 10.14393.x just like other Windows 10 versions, and we can reasonably assume that Microsoft will again messily “finish” Windows 10 for phones version 1607 sometime this month. Just like just like we did after the release of the November Update, we are focusing on making some structural improvements to OneCore. It is essentially the heart of Windows. In an announcement post highlighted in the Windows 10 Feedback app, Windows 10 Insiders are warned that the Windows team will be focusing on under-the-hood refinements for now. Releasing the build simultaneously seems logical from a bug fixing point of view. As a result, these builds may include more bugs and other issues that could be slightly more painful for some people to live with.
Windows 10’s 1607 will be what enterprises begin to deploy in significant numbers, as it will coincide with the 2017-18 period during which most experts expect migrations to spike.
Advertisement
In the end, it’s very clear that Windows Phone isn’t doing very well these days, and with Microsoft not saying a single word about its plans for the platform, it’s very unlikely to see anything changing in this regard.
