Windows 10 Redstone 4 Heads Toward the Finish Line

Posted on March 3, 2018 by Paul Thurrott in Windows 10 with 9 Comments

Windows 10 Redstone 4 Heads Toward the Finish Line

For the second time this week, Microsoft has issued a new Windows 10 Insider Preview build with no major new features, indicating that development of this version, called Redstone 4, is drawing to a close.

That makes sense since Redstone 4 will be called Windows 10 version 1803 when complete. (For the initiated, that number indicates the date of completion, as in March 2018.)

So build 17112 is now available to Windows Insiders in the Fast ring. Like the previous build, 17110, this one features a glaring Microsoft Store problem. As in there isn’t one. But the same workaround I noted before still works, so no worries there.

Worse, perhaps, this build also introduces some new problems with Windows Mixed Reality. And of them could be a first, as it will literally cause physical discomfort. (Actually, Cortana shrieking like an idiot during Windows Setup causes physical discomfort, so this isn’t a first. My mistake.)

“Windows Mixed Reality runs at a very low frame rate (8-10fps) that could result in some physical discomfort,” Microsoft’s Dona Sarkar notes. “And there are multiple crashes at startup that will cause Windows Mixed Reality to not work.”

If you’re interested in using Windows Mixed Reality, Ms. Sarkar advises not installing this build. To do so, navigate to Settings > Update & security > Windows Insider Program and select “Stop Insider Preview builds” and then “Pause updates for a bit.” Presumably, this issue will be fixed in the next build. But then I thought the Microsoft Store issue would be quickly fixed too.

As is usually the case, there are a number of other known issues and some fixes in this build. Check out Microsoft’s blog post for more info.

 

Tagged with

Join the discussion!

BECOME A THURROTT MEMBER:

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

Register
Comments (11)

11 responses to “Windows 10 Redstone 4 Heads Toward the Finish Line”

  1. Avatar

    Bart

    Like you have said before Paul. Windows Mixed Reality is just a niche product. So not many people will consider this an issue

  2. Avatar

    PeteB

    > “Windows Mixed Reality runs at a very low frame rate (8-10fps)


    Like anyone noticed. Time to put that late to the VR bandwagon non-effort out of it's misery. MS hasn't even bothered to develop content for it.


    For years MS crapped on VR, and swore Hololens-Hololens-Hololens was all that mattered. They laughed off VR like Ballmer laughing off the iPhone.


    But Hololens flopped and VR took off anyway. And VR developers never forget, which is why they'll never add native WMR support to their titles. Nevermind WMR alienates Windows 7 and 8.1 VR users.

  3. Avatar

    jimchamplin

    Oh hey.


    17112 still has the Store bug? It broke ALL OF MY UWP APPS. ALL OF THEM.


    Even the Desktop Bridge stuff.


    TOP QUALITY.


    EDIT: Restart and it's fine. Feedback sent!

    • Avatar

      hrlngrv

      In reply to jimchamplin:

      On my system all the bundled apps (Alarms & Clocks, Calculator, Calendar, Mail, Maps, etc) work, as does Store desktop Office, mobile Excel and VLC, but Code Writer, Inkscape, and Ubuntu (Windows Services for Linux) don't.

      TBH, I figure all broken would be better news than just some broken.

  4. Avatar

    SvenJ

    Again, I had no issues with the Store or UWP apps (as some have). I find it interesting how varied the experiences are and how significant the flaws that have been introduced with builds are. This one dorked up the cell service on my Surface 3. A restart fixed it, but it restarted at the end of the update. I still can't use a multi-finger swipe to clear notifications, and the clear all hot link typically doesn't. Gets some, not all. Gets more each time it is tapped. My Start Menu (in tablet mode) periodically just freezes. I can launch any app on the task bar, but everything else is non-responsive. Sometimes it comes back after several minutes. Sometimes I need to restart, force down with power button or three finger salute and power off option. I would think each successive build would move forward, get better. Often they are just sideways. MS giveth and MS taketh away.

    Yes, I report all the issues I see. That's why I run Insider builds. I have other devices on release builds and honestly they are just fine. I am just amazed at how many new issues are introduced so close to completion.

Leave a Reply