Makes sense to continue the naming strategy introduce in the April 2018 Update - if only to stop having to think up silly names with unfortunate acronyms (Fall Creators Update, for instance).

However, naming the release after a month adds its own pressures. Remember how 17133 was all set to be the release build of 1803, the April 2018 Update? All the way through to mid April when it was pulled due to a mysterious 'blocking bug'? Build 17134 was released in a mad rush in the last few days of April, to the Fast Ring on 20th, the Slow Ring on 27th and the public release on the 30th - all to justify that 'April' name tag.

Unsurprising then that it was released in an 'unpolished' state and had some Insider 'leftovers' in the public build....

'Privacy > Diagnostics & feedback > Feedback frequency' still says 'Windows Insider Program manages this option' and is greyed out.

Cumulative Update KB4103721 Windows 10 v1803 Build 17134.48 - May 8 - Page 8 - Windows 10 Forums

IMHO 1803 was one of the least well prepared release builds (and I've installed them all on day 1) mainly due to rushing it out on the 30th to meet the self-imposed 'April' deadline. It wasn't really ready until build 17134.112, the build you now get from the MCT.

Let's hope the 'October Update' doesn't suffer similar last minute upsets, or it may also end up as a 'rough diamond'.

Well the version sould be 1810 not 1809. Still it's not too far out

DooGie said:

Well the version sould be 1810 not 1809. Still it's not too far out

We had the same arguments about the April Update, that was 1803 (not 04). The YYMM number is supposed to be the date the build was finalised for release, that will be some time in September. Any last minute changes are normally be done by a CU, tested in the Release Ring before the rollout begins and released simultaneously with the public RTM.