Windows 10 preview build 17133 rolls out to Insiders in the Slow ring

Microsoft is rolling out a fresh Insider preview build for those enrolled in the Slow ring today. Today's build is 17133, and it comes just three days after it first landed for Insiders in the Fast ring. Build 17133 is also expected to be the RTM build of the Windows 10 Spring Creators Update, set to roll out in April.

Microsoft cautions that it is using this release to test the engineering systems responsible for the deployment of Windows 10 updates, so it may not be available to everyone in the Slow ring right away. However, it should reach full availability for Slow ring Insiders by Monday, April 2. Here's a look at the small list of changes included in this build:

General changes, improvements, and fixes for PC

  • We fixed an issue resulting in certain devices with BitLocker enabled unexpectedly booting into BitLocker recovery in recent flights.
  • We fixed an issue resulting in not being able to change the display resolution when there were 4 or more monitors connected, due to the confirmation prompt hanging when you selected "Keep changes".
  • We fixed an issue where clicking suggested search terms when typing in the Microsoft Edge URL bar didn't do anything.

If you're currently a part of the rollout, build 17133 should be available via Windows Update now as "Feature update for Windows 10, version 1803."

Updated March 30, 2018: Windows 10 SDK preview build 17125 is also now available for developers.

Dan Thorp-Lancaster is the former Editor-in-Chief of Windows Central. He began working with Windows Central, Android Central, and iMore as a news writer in 2014 and is obsessed with tech of all sorts. You can follow Dan on Twitter @DthorpL and Instagram @heyitsdtl

  • One cannot help but wonder when (if) Microsoft will ever get rid of the engineers that are apparently running the marketing department. I mean, seriously, naming the updates by "year and month" but not even giving the public beta testers (Insiders) access to the RTM version until it is "version number plus 1 month." No wonder the public can't fully understand what Microsoft has to offer - the communication sucks. In fact, from this company it has pretty much always sucked. (And as a former developer 4x-certified by Microsoft I've seen a lot of their "communication.") I love their stuff, but their communication is just horrible.
  • Why the month, anyway? They could have chosen to number the features updates by order instead, thereby opening up for possible changes to the release schedule in the future: 2018.1 and 2018.2. Means they don't *have to* have a second one, and also that they can release a third one if necessary.
  • There are only two major feature updates per year which is why they use year and month.
  • Yeah, I know. But they're pretty consistent at missing the month in the version number... unless they mean the date when they check in the code. That would be expected from engineers - but it only confuses customers.
  • "unless they mean the date when they check in the code"
    That's exactly what they mean. "That would be expected from engineers - but it only confuses customers."
    I don't really think so because a) consumers don't really see the XXYY number scheme, they get the horrible Creators Update names instead and b) because of the staged rollout, many if not most of the users don't get the new version in the first month of availability.
  • Which would be another reason for *not* using month in the name. (And users do see the "number" if they check System Update or read articles about the update.) Frankly, the only thing a company like Apple does right is that they understand that a product is only as valuable as it appears in the eyes of the customer. Microsoft never got this right, I'm guessing because it is a company of and by engineers and not sales people and marketers. They have the superior product(s), but are just outrageously bad at communicating that fact. ("1803" is just another example of this.) Thanks for the down-votes, by the way. Makes it look like I don't know what I'm talking about. :-)
  • 99% of their customers have no idea what you're talking about, let alone are confused about it. Ask anybody on the street what version of Windows they're using, and if you're lucky you'll get 10, as in Windows 10. That or just a shrug of the shoulders. The only people who care about this stuff are nerds, and they're not confused. Man, the stuff people love to complain about...
  • Best argument / answer of the day I've to say...
  • The month is RTM month. Once it is RTM it is available to Software Assurance customers and developers.
  • Shouldn't be long before this hits the Release Preview then.
  • Another 3 days max. Possibly 5 because of the weekend.
  • I switched to the Slow Ring on my SP4 and got this build installing now but I'll switch back to Release Preview after it's finished.
  • I switched from RP to fast to get this as soon as I heard it was RTM. Installed, and back to RP. Seems to work well.
  • The only issue I noticed was with the reveal effect in certain areas but it's not a massive issue as it's cosmetic.
  • Release Preview don't exist anymore I believe, at lest not in the W10pro or it broke in my laptop after setting back to factory settings about 3 weeks ago. Getting the 17074 from January 19 for Slow ring right away while I was in RP.
  • Release ring stays on the current version 16299. until till a week or so before release than it will move to 1733. Release ring serves a different purpose than fast/slow ring
  • I'm getting an error when upgrading to this build, saying "windows could not configure one or more system components" is there a workaround this?
  • Run the Windows update troubleshooter