Windows 10 Mobile is finished, stop saying otherwise

So there is something bothering me for a couple of weeks now: the attitude of the community towards build 10586 of Windows 10 Mobile. Or rather, the lack of attitude and the very weird selective behavior about updates.

Microsoft has released multiple revisions of build 10586. For desktops these where revision O, 3, 9, 11, 14, 17, 29 and 36 while Mobile has seen only 0, 11,29 and 36 so far. And that is good. That’s – in fact – amazing. However, the Mobile community has been calling Microsoft out for releasing unfinished software. Why? Because it contains bugs.

And then I’m standing there, thinking: “of course it contains bugs, which software does not?”. The answer to that question is none. For some reason it’s fine for Google to release Android 6.0.0 and then release 6.0.1 later and for Apple to release iOS 9.0.0 and then 9.0.1 later. Yet, if Microsoft does that, then it’s bad, something that shouldn’t have happened, etc. What’s up with that?

And you know what, as Windows 10 Mobile users, we shouldn’t be the ones complaining. Except for Apples iOS, there aren’t many out there that actually receive updates in the first place. Androids update policy is non existent. Sure, Nexus-devices have been able to keep up (for maximum 2 years), but beside that? Most Android users with a high-end phone never see minor bug (and security) releases, let alone major updates, or at least not before the Android development is already 2 versions ahead. Meanwhile, the low-end Lumia 520 that is about to celebrate its 3rd anniversary and will receive Windows 10 as a present.

Sure, 10586 has some rough edges, but compared to some of Apples disastrous releases (iOS 5, 6, 7 and 8 where all plagued by some major issues), we’re getting away easily. So guys, stop calling Microsoft out on releasing updates for Windows 10 Mobile and claiming that “the previous build wasn’t ready”. This is business as usual. Think of the current build as version 10.0.3 (with 10586.0 being 10.0.0, 10586.11 as 10.0.1 and 10586.29 as 10.0.2).

Which brings us to another issue: some “news”-sites out there have been claiming that because Microsoft is still working on a new version of Windows 10 Mobile build 10586 the roll out to Windows Phone 8.x devices has been delayed. The answer to that idea is: yeah… no… we don’t know that. And might be, or it might not. Again, future revisions of 10586 are just patches like every other OS has seen. Stop freaking out about it.

Lads and gents: round 3 has begun


Todays the day! Yay! Microsoft released the first preview of the third wave of Windows Insider Preview builds. 11082 is the new build you’ll receive on the fast ring. This build isn’t that interesting through. First of all, except for under the hood changes to OneCore and VP9 support in Edge, nothing has changed that much.

What did change is that the Windows Insider Fast Ring is changing its requirements for new builds. The result is that the Fast ring will be receiving more builds more quickly. That is an interesting change, through it has to be said that Microsoft has promised to push out more builds on the Fast ring more often already, however, since this is the first time – that we know of – they actually changed the requirements, it might become true. We’ll see…

Lots of Windows is about to lose support

There is just one month left for a whole lot of pieces of software that have come out of Microsoft. On January 12, 2016, Microsoft will drop support for a couple of versions of Windows (through you might consider them all different editions). But that’s not the interesting part, because next month – next year – a lot is going to change for Internet Explorer too.

So first of all, if you’re running Windows 8, Windows RT or Windows Phone 8, you might want to upgrade to Windows 8.1, Windows RT 8.1 and Windows Phone 8.1 respectively. For the first and later, you might also want considering going just straight ahead an upgrade to Windows 10 and Windows 10 Mobile (if already available for you). Windows RT-users are left out and will have to do with the 8.1-update from 2013. (By the way, Windows Home Server 2011 will follow in April 2016.)

Anyway, a while ago, Microsoft announced that it would reconsider its support schedule for Internet Explorer, and these changes are coming into effect on January 12 too. Basically, every current version of Windows will need the latest available version of Internet Explorer for that version to continue to receive updates for the browser. That means that Internet Explorer 7 and 8 will go completely out that day (as it isn’t the latest version for any version of Windows), so both Vista , 7, 2008 and 2008 R2 will lose support with that version.

Internet Explorer 9 will drop support on Windows 7 and Windows Server 2008 R2. Windows Vista, Server 2008 and Home Server 2011 will be able to continue to use IE9 and receive updates until their own end of life (which – again – for Home Server is just 3 months later). Internet Explorer 10 will also drop support for Windows 7 and Windows Server 2008 R2. Obviously, also on Windows 8, but that whole OS will be dropped that same day. The only version of Windows that will continue to use IE10 and receive updates is Windows Server 2012.

Finally, Internet Explorer 11 will… well… it won’t do anything. IE11 is the only version of Internet Explorer that isn’t affected by this change and will continue to receive support on Windows 7, 8.1, 10, Phone 8.1, Server 2012 R2 and Server 2016 for the foreseeable future. It has to be said that nothing lasts for ever, though, so in case you’re using IE11, it might be wise to upgrade to Microsoft Edge 12. Maybe you want to hold out on that until Microsoft Edge 13 or 14 as it is expected to support extentions, that’s fine, but make sure you stay save. ME12/13 are much more secure than IE11 and not a single update to IE will change that due to it’s backwards compatibility nature.

Microsoft will sign off Windows 10’s Fall update this week

So according to many people out there, Microsoft will be signing off the “Fall update” for Windows 10 later this week for a November 10 release. That’s Patch Tuesday. And that’s great, the Threshold R2 update contains a lot of nice changes, some big, some small, that make Windows 10 an even better OS to use, including Edge 13, new customization options for start and windows, a more consistent design, an updated tablet experience, a bunch of new settings, Windows Spotlight for everyone and more.

However, this update signing off means that we’ll soon get another update, this could be a soon as tomorrow. Will that be the final version? Maybe, maybe not. It might go down like the final 4 updates for Threshold R1 (10158, 10159, 10162 and 10166) that followed each other within 10 days. However, obviously, if such a thing happens, it will be less builds because there isn’t enough time if the rumor is correct, but Microsoft is very likely going to release the final update to Windows Insiders on the Fast and Slow ring prior to the public.

So here comes the speculation I talked about last time

But that’s not all! No, according to Marry Jo Folley we’ll get to see the first Redstone R1 preview build before the end of the year, too. And that is very likely as Microsoft has already started development of the first real Redstone builds a while ago. In fact, we discovered build 11040 in our logs on October 22. That means that Microsoft has at least compiled build 11051 or later today. If we consider the November 10 release and keep in mind that the first Threshold R2 build was released 20 days after the GA of Windows 10 and project that on Redstone, that means that IF Microsoft does release a Redstone R1 build 20 days after the Threshold R2 release, they have at least compiled build 11079 (but builds take at least 4 days to go from internal testing to the Windows Insider Fast Ring, and that’s a fast build in that case), so some major changes can already be included in those builds (it’s like the 9879 – 9926 gap).

Talking about that gap, will Microsoft hold another hiatus this year? Last year, after Microsoft released the third Windows 10 Technical Preview, they announced that they wouldn’t release new builds of Windows 10 until after the holidays. Build 9879 rolled out on November 12, 2014 and the next build took over 2 months to roll out: 9926 was released on January 23, 2015. However, Microsoft had an event planned and they where likely to keep some things hidden from us until the event (through a lot leaked out due to build 9901). So except for parts of the Windows team being on holidays, Microsoft doesn’t have an additional reason to not release builds during December like last year. Perhaps they will do it to get a break from the program, and that will put us up with a massive first update in 2016, on the other hand, small updates to test out before the holidays are welcome, too. Either way, we’ll have to wait and see.

A new, fancy, place to just blog

Because why not. A while ago, had it’s own, local hosted, blog based on WordPress. But well… that didn’t end well. So now, here we are, with a new blog. And it’s a blog, not a news site. So don’t expect me to cover every single news item that gets out of Microsoft. No, here, I’m just gonna bore you guys to dead with my opinion on stuff mostly surrounding the Windows Insider Program. And my theories about things that are said about it. And stats. Because I like stats and I’m expecting you guys to do the same. After all, you’re taking the time to read this blog…

Anyway, I’ll kick this off shortly. Stay tuned!