Windows 10’s Next Major Updates Will Be Codenamed Vanadium, Vibranium

Posted on October 31, 2018 by Mehedi Hassan in Windows, Windows 10 with 18 Comments

Microsoft has used the “Redstone” codename scheme for multiple Windows 10 updates. The company is no longer using Redstone codenames going forward, though — in fact, the upcoming Windows 10 October 2018 Update is the last update to feature the Redstone codename.

We already know that Windows 10’s next major update is codenamed 19H1. But Microsoft is changing things up, again, according to ZDNet.

Now that Windows is in the same group as Azure, the Windows team is switching to a codenaming scheme used by the Azure team: names of elements. Windows 10 19H1 was originally meant to be codenamed Titanium, though since the Windows team had already started using 19H1 internally, they decided to stick with the name.

Going forward, though, Windows will use the same codename scheme as Azure. This means the next Windows 10 update, previously codenamed 19H2, will be called Vanadium (comes after Titanium/19H1). And the first update coming in 2020 was going to be called Chromium, but since that’s already being used by Google, the Windows team is apparently going to call it Vibranium internally. And yes — that’s the same Vibranium that’s widely used in Wakanda from Marvel’s cinematic universe.

Microsoft’s Surface team also notably uses names of elements as the codenames for their products, so it could soon become a company-wide thing at Microsoft. I personally prefer names like Vibranium and Redstone over simple schemes like 19H1 or 19H2, as they sound much cooler than just 19H1 or 20H1.

Tagged with , ,

Join the discussion!


Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Comments (18)

18 responses to “Windows 10’s Next Major Updates Will Be Codenamed Vanadium, Vibranium”

  1. jimchamplin

    Vanadium? It’s a great name. Strong, scientific, and real.

    Vibranium is all the same but not real. Or scientific. It’s still good because Stan Lee.


  2. crmguru

    Have we not learned the lesson of Metro, and Sky Drive... Don't name your stuff after other's copywrtten stuff. Hello lawsuit.....

  3. MikeGalos

    The problem with word-based names is that, like Apple's macOS naming scheme it becomes hard to remember whether Lion came before or after Tiger once they're no longer current. Hopefully Microsoft won't use those codenames for product names.

  4. hrlngrv

    I can hardly wait for Windows 10 Arsenic (24H1), but I have little doubt there'll be at least 2 naming scheme changes by then.

  5. peterlc

    How about instead of spending time thinking up catchy names, Microsoft fixes it's broken updates that don't work properly. We shouldn't have to alpha test it's mistakes.

    • MikeGalos

      In reply to peterlc:

      Well, apparently code names are important enough to get a whole topic on a significant tech board to get a full article just on a rumor of a change in naming scheme. And over a dozen comments.

  6. Zsolt Kádár

    I would have guessed Erasium or Deletium

  7. FalseAgent

    there's nothing to read much into here. It's just a codename, and the guys at Azure upended what would be been a logical codename scheme (19H1, 19H2, ...). Moving along now...

  8. shahezad738

    nice artical and so use full artical and thnaks u