Windows 10 Redstone 4 Gets Cumulative Update for Insiders

Posted on April 10, 2018 by Mehedi Hassan in Windows 10 with 28 Comments

Microsoft was rumoured to be releasing Windows 10 Redstone 4 to the public today. The company seems to have delayed the planned rollout and is instead releasing a cumulative update to Insiders.

Windows Insiders are getting a new cumulative update (KB4100375) for build 17133, which comes with some security patches, and possibly the fix for the issue that actually caused the delay in the release. Unlike previous Windows 10 feature updates, Microsoft didn’t announce or confirm a release date for the Redstone 4 update. In fact, the company is yet to publicly announce a name for the update.

However, multiple sources previously confirmed that Redstone 4 was supposed to start rolling out today. But Microsoft likely ran into a breaking bug which prompted Redmond to push the release. We’ll let you know as we have more information.

Tagged with , ,

Join the discussion!


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

Comments (28)

28 responses to “Windows 10 Redstone 4 Gets Cumulative Update for Insiders”

  1. adamjarvis

    Patch Tuesday is not the best day to be releasing a new Windows 10 ISO unless you really want to stress test the Microsoft Datacenter capabilities.

  2. pesos

    I've been running 17133 on my nuc for a couple of weeks and I regularly get a video freeze/hang and have to unplug and replug the thunderbolt cable running to my monitor, which fixes it (although then all my app sizing gets screwed up). Hopefully this is addressed in the update.

    • JerryH

      In reply to pesos:

      I have been seeing the same issue on a Lenovo Yoga 370 using a thunderbolt dock (at work) and using a USB C dock (at home). Didn't have anyone who could reproduce it, so I wasn't able to file a bug on it yet. Hopefully this update will fix it.

  3. DavidSlade

    The update is listed as being for Windows 10 Version Next, Is this what they are going to call it "Version Next"?

  4. madthinus

    I have updated to RS4 and then exited the Insider program, my PC is not getting the update. Should I rejoin the insider program to get them?

  5. skane2600

    Am I the only one who tires of the minutia of Insider Updates instead of just reporting official deliverables.

  6. NoFlames

    Jumped back on the Release Preview to get the latest updates. Periscope TV in edge was broken (no audio), with the fix it's now working.

  7. MikeGalos

    So exactly as normal with a final cumulative update going out to the Insiders so they're up to the same version that's expected to be the actual release. Then, if no high severity bugs show up in configuration testing (the Insiders really are the source for testing millions of possible hardware/software configurations) then that build will ship. If the Insiders do find something high severity then another release candidate will be prepared and we do it again.

    • Mikhul

      In reply to MikeGalos:

      If you're a closet MSFT employee you should disclose it.

      • VancouverNinja

        In reply to Mikhul:

        Maybe he simply is not buying into the BS that is shoveled MSs way consistently.

        I happen to find his response that of someone who understands development and all of the challenges that go along with it. There is no better PC OS available today than Windows 10. Can it be better? Sure and hopefully it will continue to evolve nicely as it has been these last several years. MS has done an excellent job; relative to every other OS dev house.

  8. will

    While I am glad they fix a bug before release, everything else about this release just is just poor Microsoft management. Since they started testing this last year they have never outlined what was coming, outside of a few small items, never held any event to talk about this release, have not announced any sort of name and gave no release date.

    • hrlngrv

      In reply to will:

      Which is worse (cynical: more expected)? That MSFT lacks a clear vision for each new Windows 10 release, or that MSFT does an abysmal job communicating that vision?

      • VancouverNinja

        In reply to hrlngrv:

        How about neither?

        The updates are free. MS has an agenda that they are baking into the software. By not pre-promoting the features of the new upgrade they can release more easily and hold back any dev work they feel needs more time.

        Again more complaints about absolutely nothing. Why not be thankful that we are now in the age of free OSs? At least for the average user.

        • hrlngrv

          In reply to VancouverNinja:

          If MSFT had the flexibility to hold back any features, why would they miss any release dates?

          We're no more in the age of free Windows than we were with Windows XP and its several Service Packs. However, in the XP days one only paid once for the OEM Windows license. Today, MSFT is exploring all sorts of wonderful way to monetize Windows after first login. From that perspective, things are worse these days.

          If your response to new monetization actions is like Steve Martin in The Jerk enthusing about the new phonebooks, you have my sympathy.

  9. CyberDadIO

    Update 1:

    This seems to have fixed the continuous disconnect/reconnect I was having with the Surface Dock on my Surface Book 2.

    I updated to 1803 a couple of weeks ago by moving from the slow- to the fast-ring. Once it was updated, rather than dropping out completely, I dropped into the "Just send me early updates" ring. Read this article just now & checked my updates & waddyaknow, I've received this update (Cumulative Update for Windows 10 Version Next (10.0.17133.73)) & need to restart.

    I just got a Surface Dock off eBay having never used one before & have had nothing but connection problems with it (I had 2 1080p monitors & 3 USB devices connected & it kept disconnecting & reconnecting, with the power light on the connector going off & on). I was thinking it must be a faulty dock or that the Surface Dock is a pile of $#*%. Hopefully it's just related to this issue & will be fixed by this update.