Warning before installing Windows 10 Creators Update

Microsoft have issued a warning for those thinking of manually upgrading Windows 10 to the Creators Update [a.k.a. v1703, a.k.a. Redstone 2, a.k.a. build 15063]: Don’t.

The big update has already run into problems with some types of Broadcom Bluetooth LE radios: the code was killing connections with accessories, apparently. So Microsoft stopped pushing automatic downloads to computers carrying that hardware. There may also be others hardware issues.

When an issue such as this happens, they issue a “block” which will stop the computer from getting the update. It doesn’t stop, however, a person from upgrading manually on their own with an ISO or other ways. Once the issue has been corrected, the block is removed.

That’s why Microsoft started with newer hardware first. It will give them time to correct the problem.

So far maybe 10 per cent of Windows machines are running the Creators Update. Microsoft’s own recent hardware are leading the pack in upgrades.

Unsure how they release CU with this issue – except maybe because they gave themselves a deadline. But this is v1703. At one point, it looked like it would be called v1704. An extra month [or at least a week or so] wouldn’t have caused these problems.

 

Windows 10 v1703 goes RTM?

According to some reports, Windows 10 [a.k.a. v1703 (not v1704), a.k.a. Redstone 2, a.k.a. Creators Update] may have been RTMed [“release to manufacturing”] this past week with a rumored/leaked release date of April 11th – the same day the dreaded Vista gets its last updates and goes unsupported. Build number is 15063.

There are probably good indications of both as there hasn’t been any builds since 15063 was released over a week ago and Microsoft has started to release builds for “Redstone 3” [due on November].

In addition, “RTM” was mentioned in various XML files as part of the 15063 build.

As for the actual release date, Microsoft tends to prefer Patch Tuesdays. In addition a leaked and later pulled file mentioned April 11th.

Those part of the windows Insiders program [or have connections!] should be able to get the bits. Others will wait until they get notified sometime on or after April 11th.

Note that any systems upgraded to v1607 build within the past 30 days will not get the upgrade notice at least until after the 30 days are up.

Of course domain and enterprise level systems will not get the upgrade until the administrators approve.