New Windows as a Service information published


As we discussed in the Windows 10 servicing guidance published on TechNet, we plan to make available new Windows 10 features via the Current Branch (CB), and declare that these features are ready for businesses by declaring a Current Branch for Business (CBB) release. We’ll also periodically release new Long-Term Servicing Branch (LTSB) releases.

To make it easy for organizations and individuals to see information about all of these releases, we have created two new web pages on TechNet that will be updated any time there are changes:

  • A new Release Notes page is available at http://windows.microsoft.com/en-us/windows-10/update-history-windows-10. This page includes details about each new update released for Windows 10, with specifics on the new security and non-security fixes included in each cumulative update.
  • A new Release Information page is available at https://aka.ms/win10releaseinfo. Included on this page is information about the current releases, as well as a full history of all the cumulative servicing updates that have been published for each one. (Remember, because these servicing updates are cumulative, you just need to install the latest one to be fully up to date.)

We hope that you find these valuable sources of information, and encourage you to provide feedback and suggestions on these pages, as well as on Windows 10 as a whole, using the Windows Feedback app.

For more information about Windows as a service, check out the Microsoft Virtual Academy sessions, and make plans to attend Microsoft Ignite later this year for more in-depth content on this and many other Windows 10 topics.


Comments (2)

  1. Anonymous says:

    Im Rahmen von „Windows as a Service“ hat Microsoft eine Webseite veröffentlicht, welche

  2. Trying to understand CB versus CBB versus LTSB says:

    I’m just trying to make sure I understand all this. So, right now, we have the original version of Windows 10, and Windows 10, 1511, which was just released on CBB. If I have machines deployed with the original version of Windows 10, the only way to get
    them up to date (or else they will no longer be supported) is to actually upgrade them to 1511 (running, either automatically or manually, the full upgrade, which I should expect to be considerably more involved than installing updates). If I am supporting
    1000 machines on the original Windows 10, I must upgrade each of them to 1511, and then again when a new feature is released to CBB.

    And, if these frequent (yearly for CBB) upgrades become disruptive, there is always Windows 10 LTSB, which is supported for 10 years.

    Have I got the right impression? Is this how it works, or am I misunderstanding something?