Blog Post

Windows IT Pro Blog
4 MIN READ

Commercial control for continuous innovation

AriaUpdated's avatar
AriaUpdated
Icon for Microsoft rankMicrosoft
Feb 09, 2023

We are excited to be moving towards a world of continuous innovation, with consistent and regular shipping of features via the monthly latest cumulative update (LCU). This is a technology we have been building upon for years and are now taking further than ever before!

In the second half of 2019, we released Windows 10, version 1909, the first feature update shipped via an enablement package (EKB). This technology allowed us to ship a collection of new features via a monthly quality update (LCU) in an "off" state. These features were then turned on when an organization deployed the EKB package. The best part: because these features were delivered via LCU, the reboot time for these feature updates was super quick—often in less than 5 minutes!

Organizations provided a ton of positive feedback around these EKB packages, and we went on to leverage that technology for Windows 10 versions 20H2, 21H1, 21H2, and 22H2. Now, we want to take that technology one step further and deliver more features than ever via LCUs.

We are very excited to deliver continuous innovation – bringing you new value on a more frequent basis. We also understand the need for organizations to have a stable environment and control. Therefore, I'm excited to share a new client policy to control select features introduced via servicing until they are released as part of the next annual feature update. Features that may be disruptive to organizations will be off by default for all Windows update managed devices until the device enables the policy or takes the next annual feature update.

Improvements that are not behind temporary control will be rolled out through a controlled feature rollout to unmanaged devices before being included in an LCU for organizations. All features shipped in the LCU will be included in a complementary knowledge base (KB) article, which will delineate those features still in the process of being rolled out and those that are switched off by default for organizations.

Features behind the control

Not all features shipped via servicing will be behind this new control. In fact, many improvements, such as reductions in file size, performance fixes, and, as usual, any bug fixes, will be introduced in the LCU in an "on" state after being rolled out to unmanaged devices through a controlled feature rollout.

For organizations, we aspire to provide control for features that:

  • Add new experiences or user interfaces to Windows, especially for any primary control surfaces (such as the taskbar and start menu)
  • Are new in-box applications
  • Remove existing capabilities
  • Override previously configured settings (set by either IT or the end user)

We are still learning and listening to ensure that we have features behind the proper controls. Interested in helping us decide which features need what level of control? Join the Microsoft Managed Customer Connection Program (MM CCP)!

How you can configure the policy

By default, all features introduced via servicing that are behind the commercial control will be off for Windows-Update-managed devices. Windows-Update-managed devices are those that determine which Windows updates are offered by leveraging Windows Update for Business or Windows Server Update Services (WSUS).

Organizations wishing to turn on these features ahead of taking the next annual feature update can do so by enabling the new policy: "Enable features introduced via servicing that are off by default."

  • Group Policy: /Windows Components/Windows Update/Manage end user experience/Enable features introduced via servicing that are off by default
  • Configuration Service Provider (CSP) Policy: /Policy/Config/Update/AllowTemporaryEnterpriseFeatureControl

Screenshot of the policy for "Enable features introduced via servicing that are off by default"

When this policy is enabled, all the features that were on a device in an "off" state behind this control will be turned on when the device next reboots. Additionally, all new features controlled by this setting will be on when delivered as part of future LCUs.

If you choose not to enable this new control, the features behind it will be automatically turned on when a device updates to the next annual feature update.

This policy is available today, February 9, 2023, for all devices in the Windows Insider Program Dev Channel who have installed Windows 11 Insider Preview Build 25295. This policy will be coming to Windows 11, version 22H2 in the February 2023 optional, cumulative, non-security preview release.

We're listening!

As always, we are listening and learning! While we go down this path of delivering more value to you on a more regular basis, we want to continue to ensure a great experience. Therefore, please do not hesitate to reach out with questions or feedback. You can reach me directly here via the comments section, a Tech Community private message, or by reaching out to me @ariaupdated on Twitter.


Continue the conversation. Find best practices. Visit the Windows Tech Community.
Stay informed. For the latest updates on new releases, tools, and resources, stay tuned to this blog and follow us @MSWindowsITPro and @WindowsUpdate on Twitter.

Updated Feb 09, 2023
Version 3.0

38 Comments

  • Forhad_Faruqui's avatar
    Forhad_Faruqui
    Copper Contributor

    I did troubleshooting but still, the update is fine but no newer builds is available, why? Please provia solution.

  • AriaUpdated I would like to add to the previous idea. Moment Updates and changes should be linked in the Windows Release History (which is the single place as per request) table without support dates,

    These could then link to learn.microsoft.com or techcommunity.microsoft.com with verbose Information about the changes, best, pictured with pre / after screenshots per change. So IT could use this for internal updates of their guidance or training materials.

     

  • PS_Alex's avatar
    PS_Alex
    Brass Contributor

    AriaUpdatedThanks, makes sense. So enabling, then disabling/unsetting the policy would allow us to test changes, then revert to the current default behavior on a single device.

  • mhartstein that is great feedback! We will certainly attempt to ensure that our KB articles and documentation call out all of the content in each quality update and which features are behind this commercial control. Also, having a single page that shows the features behind this control is a great idea! Let me see if I can get one spun up. 🙂

     

    PS_Alex great question! If you flip this policy ON for a managed device, you will get all of the features on the device that are currently disabled for your current version and all of the future features released behind this control for that version. If you then turn this policy Off all of the features that are behind this control for your version will be turned Off at the next reboot. Once you either turn the policy ON or update to the next feature update version the features will once again be on. Does this make sense? 

     

    Forhad_Faruqui I would recommend clicking the "Troubleshoot Insider builds"   

     

     

  • Forhad_Faruqui's avatar
    Forhad_Faruqui
    Copper Contributor

    My windows is up to date but my insider build is not showing newer builds, why?

  • PS_Alex's avatar
    PS_Alex
    Brass Contributor

    AriaUpdated wrote:

    When this policy is enabled, all the features that were on a device in an "off" state behind this control will be turned on when the device next reboots. Additionally, all new features controlled by this setting will be on when delivered as part of future LCUs.


    Question: if I enable the new policy on a device, then after some time I disable/unset it, would the new features controlled by this setting be turned off at next reboot? Or would the new features enabled until the policy is disabled/unset stay on? What about new features delivered by LCU after the policy has been disabled/unset?

     

    Also, agreeing with mhartstein with having an at a glance page to list new features that would be enabled by the policy. It definitely is useful for administrators for efficiency.

  • mhartstein's avatar
    mhartstein
    Brass Contributor

    A nice compliment to this very useful control would be a central KB page (kind of like the "Windows 11 release information page") that has an up-to-date ongoing list of the commercial control gated features and which Windows versions they were added to, and, by extension, which version they will become mandatory in.

     

    This may not fly because it would require distilling the content of the "magical Moments" to a couple of boring bullet points, but, if I am an admin looking to see at a glance which features will be enabled if I turn on the policy, I'd want a clear list and to not have to hunt for a bunch of miscellaneous "Moment announcement" blog posts (not knowing who posted each one or when, or how many to look for).