Microsoft accidentally let encrypted Windows 10 out into the world

Insider builds sometimes just don't work. Who knew?

Open barn door

Windows Insiders eager to get their hands on next year's Microsoft OS were reminded last night that living on the bleeding edge can have its downsides: the update consumes RAM at a prodigious rate for some before falling over.

It all began so well. Build 18237 was emitted with the usual degree of fanfare. Now given a disappointingly logical codename of 19H1 rather than the whimsy of Redstone, the code is available to Insiders who have opted to "skip ahead" past the impending October 2018 Update, and will eventually ship next year.

Among a raft of fixes was the slapping of acrylic over the Windows login screen, which the Insider team reckoned moves "the actionable controls up in the visual hierarchy while maintaining their accessibility". Vulture Central would contend it looks more like someone has smeared the display with Vaseline.

A cynic might spot more than a passing resemblance to macOS while an old gamer may reminisce about Half-Life 2 loading screens.

Windows Insider Login

The blurry world of Fluent Design

Unfortunately, the wheels quickly came off the Insider train as Microsoft's army of excited testers found themselves encountering issues ranging from a total failure to even download the thing, installs taking an age to complete, and epic memory consumption through to Green Screens of Death.

It transpired that an encrypted version of build 18237 had been put out by the Insider team, which was quickly rectified. However, users continued to encounter problems.

Fans hoping to see a fashionably blurry login screen, but instead staring at a stuck progress bar or (worse) an esoteric error code are encouraged to log the problem on Microsoft's feedback hub. Getting ready to restore from a backup might be a good idea too.

Windows Insiders have been somewhat spoiled by the stability of recent output from Microsoft. Last night's fun is a gentle reminder from Dona Sarkar and her team that sometimes things can go badly wrong when tinkering with preview code. So be careful out there. ®




Biting the hand that feeds IT © 1998–2018