Plus: Windows Mixed Reality sulks in kitchen while HoloLens 2 hogs limelight
Roundup While the Microsoft team were setting up shop at Barcelona’s Mobile World Congress (and frantically plugging HoloLens 2 leaks), things continued apace back in Redmond.
While the original version of Windows struggled somewhat with multitasking back in the day, today’s team seems determined to push the concept to new heights, flinging out new builds of 19H1 and 20H1 while keeping a multitude of supported versions patched.
Skip-Ahead Windows Insiders, doomed to remain on 2020’s Windows 10 unless willing to take a flamethrower to their PC, received a fresh drop of the 20H1 build, taking the version to 18841. The build continues to be light on new features, however, and the gang warned that some things « require a longer lead time ».
The more imminent 19H1 build of Windows was also updated at the end of the week, with build 18343 hot on the heels of the zombie-slaying 18342. This close to release, one doesn’t expect much in the way of new and shiny, and Friday’s fix was all about that pesky Connected Standby issue that had left the build block for some Intel-based machines (Intel64 Family 6 Models 142 and 158).
Little-used hardware that features the chippery include, er, Microsoft’s own Surface Go.
Awkward.
Still missing in action is 19H2, which Skip-Ahead users had been expecting. Those multitasking skills will be put to the test in few weeks, when the follow-up to 19H1 finally sees the light of day and Insiders find themselves spoilt for version choice.
In the same week as emitting a fresh early access build of the. NET Framework, Microsoft also reminded devs last week that its open-source replacement would not be enjoying quite such a lengthy lifespan, even in Long Term Support (LTS) guise.
Build 3745 of the venerable. NET Framework (4.8) saw tweaks to the WCF and WPF as well as a vulnerability dealt with in WorkFlow that allowed « random » code to be executed within certain XOML constructs.
