Author Topic: Windows 10 update history  (Read 2115 times)

0 Members and 1 Guest are viewing this topic.

Offline parkd1

  • Sr. Member
  • ****
  • Join Date: Jan 2013
  • Posts: 269
  • Karma: 7
    • View Profile
Windows 10 update history
« on: February 10, 2016, 08:54:41 AM »
We're committed to our customers and strive to incorporate their feedback, both in how we deliver Windows as a service and the info we provide about Windows 10. In response to this feedback, we’re providing more details about the Windows 10 updates we deliver through Windows Update. You'll see a summary of important product developments included in each update, with links to more details. This page will be regularly refreshed, as new updates are released.

We're currently delivering updates to two distinct Windows 10 branches. The July initial launch branch (build 10240), and the November update branch (build 10586). We introduced new operating system features in November after having previewed, or "flighted", them with our Windows Insiders between July and November. Most customers have already been moved automatically from the July branch to the November branch. Windows 10 Professional, Enterprise, and Education edition customers can defer the update to the November branch and stay on the July feature set longer — as long as 10 years for some Enterprise customers. For more info, see Windows 10 servicing options.

Windows 10 updates are cumulative of all previous updates. Installing the latest one makes your device current. Windows Store apps are updated through the Windows Store. Details about app updates are provided on a per app basis.

The following sections list some key improvements included in each update.

http://windows.microsoft.com/en-us/windows-10/update-history-windows-10

Offline Julian

  • "Cat and Mum Guy"
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jun 2015
  • Posts: 1320
  • Location: USA, New Mexico
  • Karma: 38
    • View Profile
Re: Windows 10 update history
« Reply #1 on: February 15, 2016, 01:24:38 PM »
omg i have to check this update to see if it fixed it!
Julian