Skip to main content

Windows 10 Redstone 4 build 17134 now rolling out for Insiders

Windows Update Insider
Windows Update Insider (Image credit: Windows Central)

As we reported last week, Microsoft has demoted build 17133 from RTM status internally, which means it has compiled another Redstone 4 build at the last minute that it is hoping will be stable enough to pass the criteria for rollout to the public. That build is now rolling out to Insiders in the Fast ring for testing as build 17134, and includes no new features.

As Build 17133 progressed through the rings, we discovered some reliability issues we wanted to fix. In certain cases, these reliability issues could have led to a higher percentage of (BSOD) on PCs for example. Instead of creating a Cumulative Update package to service these issues, we decided to create a new build with the fixes included.

Microsoft says it found reliability issues with build 17133 during testing, and sources tell Windows Central that the company found an undisclosed blocking bug just a few days before Redstone 4 was supposed to begin official rollout. This caused Microsoft to delay the public release indefinitely, and demote build 17133 from RTM status. Now, build 17134 is Microsoft's next attempt at an RTM build.

If build 17134 reaches the necessary criteria, this will be the build that rolls out to the public later this month. Build 17134 is already available on Xbox One, and will soon be available on HoloLens and IoT as well. We'll keep you updated.

Zac Bowden
Zac Bowden

Zac Bowden is a Senior Editor at Windows Central. Bringing you exclusive coverage into the world of Windows 10 on PCs, tablets, phones, and more. Also an avid collector of rare Microsoft prototype devices! Keep in touch on Twitter: @zacbowden.

32 Comments
  • So I guess this begs the question will the version now be 1804?
  • No, will still be 1803.
  • Their naming scheme is getting sillier by the day
  • They should just wait until October 2018 for public release and completely forget about 1803.
  • Why?
  • That's why they're changing it to 19H1 next year.
  • That's replacing the Redstone codename, not the version number.
  • You're not wrong here. Let's see when the time comes, my guts say it'll replace version number as well.
  • No, it will not change the version number. 19H1 is the codename for Version 1903.
  • no the version number is very necessary tells us how many build have been compiled like 10240 original release to now also let user no if there on the latest version
  • this is what happens when a company fires the quality testers so they can do it free with guinea pigs(the users who apply to the insider program) and not many of them know what they are doing either... no offense but this is the hard boiled truth, it just stinks like rotten eggs ..that's all. while i support Microsoft and how they have been going onward with windows 10 and its a good thing overall having the insider program but when you dont have professional software testers; then everything in the system comes to only a matter of time "when" will it go wrong; and in this case it has gone wrong but Microsoft has done right this time by holding back the update and working on a proper fix; as to why it takes long is quite much clear as day; that is which the insider program cannot replace = a professional group of beta testers, and that is something we cannot easily deny.
  • 1804-1.
  • a rare treat for insiders more builds😁 to test nice
  • Seriously should be 1804. Quityourbullshit microsoft
  • Does it really matter since it was originally finalized in March and this build is only one version higher
  • Use spaces. I first read your comment as "Quity our bullshit"
  • Should I change back to release ring after moving to build 17134.1??
  • Not sure you can change from FR to RP?
  • you can
  • sure you can
  • Good stuff, instead of rolling out a build which has higher % BSODs. Most users don't even know what build they run.
  • Will it fix my issues with the Dell visor
  • I can't access of these update
  • I can't access of these update
  • Why is not available for Release Preview and Slow ring?
  • Because builds always get tested on Fast Ring first, before going to the other rings.
  • 17133 working well for be, no crashes
  • that's sound good
  • Yay! 17134 fixes the maddening bitlocker-recovery-on-every-reboot issue I was having with 17133.
  • Cool, I hope this build will sort out the memory leak too or MSFT will patch 1709 again before 1803 is released in the coming weeks ahead.
  • I was on Slow Ring, and 17133.73 is really "hinky" on my machine and causing some slow downs and really bad missing graphic elements in menus at times. Switching to Fast Ring and getting 17134.xx then switching back to "just driver, app updates."
  • Aaahhh... a sigh of relief! Much better now with 17134.1 things run and act as they should!