How to download and install the Windows 10 Anniversary Update. Виндовс 10 update


Get Windows 10 OS | Shop & Buy Windows 10 Devices

1 Games and certain content subscriptions sold separately. Ultra HD availability subject to your Netflix subscription plan, Internet service, device capabilities, and content availability. www.netflix.com/TermsOfUse to run Netflix in 4K on a PC device, it must have a 4K-capable screen and use a 7th generation (Kabylake) Intel® chipset.

2 Up to 14.5 hours of video playback. Testing conducted by Microsoft in April 2017 using Intel® Core™ i5, 256GB, 8 GB RAM devices. Testing consisted of full battery discharge during video playback. All settings were default except: Wi-Fi was associated with a network. Battery life varies significantly with settings, usage and other factors.

3 Streamlined for security and superior performance. Windows 10 S works exclusively with apps from the Microsoft Store. Some accessories and apps compatible with Windows 10 may not work, and performance may vary. Certain default settings, features, and apps cannot be changed. Easily and affordably switch to Windows 10 Pro at any time. Learn more at Microsoft.com/Windows10S.

4 Windows Hello requires specialized hardware, including fingerprint reader, illuminated IR sensor or other biometric sensors and capable devices.

5 Cortana available in select markets; experience may vary by region and device.

6 Touch capable tablet or PC required. Pen accessory may be sold separately.

7 4K display available on certain configurations.

8Dell XPS 13 Battery source

9 Up to 13.5 hours of video playback. Testing conducted by Microsoft in April 2017 using preproduction Intel® Core™ i5, 256GB, 8 GB RAM device. Testing consisted of full battery discharge during video playback. All settings were default except: Wi-Fi was associated with a network and Auto-Brightness disabled. Battery life varies significantly with settings, usage and other factors.

10 System software uses significant storage space. Available storage is subject to change based on system software updates and apps usage. 1 GB= 1 billion bytes. See Surface.com/Storage for more details.

11 Up to 17 hours of video playback. Testing conducted by Microsoft in October 2017 using preproduction Intel® Core™ i5, 256GB, 8 GB RAM device. Testing consisted of full battery discharge during video playback. All settings were default except: Wi-Fi was associated with a network and Auto-Brightness disabled. Battery life varies significantly with settings, usage and other factors.

12 The connection between the Windows Mixed Reality-ready PC and the immersive headset requires full-sized HDMI and USB 3.0 ports; separate adapters may be required.

13 Windows Mixed Reality requires a compatible Windows 10 PC and headset, plus the Windows 10 Fall Creators Update; PC requirements may vary for available apps and content.

14 Sound, Cortana and voice dictation require compatible mic-enabled headphones with a 3.5mm jack (USB not supported), plugged into the audio jack on the HMD. You can find compatible headphones by looking for the Cortana badge or Circle icon on product packaging and websites.

15 Up to 17 hours of video playback. Testing conducted by Microsoft in October 2017 using preproduction Intel® Core™ i7, 512GB, 16 GB RAM dGPU device. Testing consisted of full battery discharge during video playback. All settings were default except: Wi-Fi was associated with a network and Auto-Brightness disabled. Battery life varies significantly with settings, usage and other factors.

* Up to 16 hours of video playback. Testing conducted by Microsoft in August 2016 using preproduction Intel® Core™ i7, 1TB, 16 GB RAM device. Testing consisted of full battery discharge during video playback. All settings were default except: Wi-Fi was associated with a network and Auto-Brightness disabled. Battery life varies significantly with settings, usage, and other factors.

† Up to 9 hours of video playback. Testing conducted by Microsoft in September 2015 using preproduction Intel® Core™ i5, 256GB, 8GB RAM device. Testing consisted of full battery discharge during video playback. All settings were default except: Wi-Fi was associated with a network. Battery life varies significantly with settings, usage, and other factors.

†† If you continue to use your current version, your computer will still work, but since you won’t continue to receive new security updates, it could become more vulnerable to security risks and viruses. To learn more about end of service for Windows 10, version 1507, review the frequently asked questions.

 Displayed prices are current lowest prices offered by retailers that have been located by an automated web crawler and are subject to change. Prices are not offered by Microsoft unless stated in the window displayed after clicking shop now.

www.microsoft.com

Optimize update delivery for Windows 10 updates (Windows 10)

  • 07/27/2017
  • 5 minutes to read
  • Contributors

In this article

Applies to

Looking for consumer information? See Windows Update: FAQ

When considering your content distribution strategy for Windows 10, think about enabling a form of peer-to-peer content sharing to reduce bandwidth issues during updates. Windows 10 offers two peer-to-peer options for update content distribution: Delivery Optimization and BranchCache. These technologies can be used with several of the servicing tools for Windows 10.

Two methods of peer-to-peer content distribution are available in Windows 10.

  • Delivery Optimization is a new peer-to-peer distribution method in Windows 10. Windows 10 clients can source content from other devices on their local network that have already downloaded the updates or from peers over the internet. Using the settings available for Delivery Optimization, clients can be configured into groups, allowing organizations to identify devices that are possibly the best candidates to fulfil peer-to-peer requests.

    Windows Update, Windows Update for Business, and Windows Server Update Services (WSUS) can use Delivery Optimization. Delivery Optimization can significantly reduce the amount of network traffic to external Windows Update sources as well as the time it takes for clients to retrieve the updates.

  • BranchCache is a bandwidth optimization technology that is included in some editions of the Windows Server 2016 Technical Preview and Windows 10 operating systems, as well as in some editions of Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows 8, Windows Server 2008 R2, and Windows 7.

    Note

    Full BranchCache functionality is supported in Windows 10 Enterprise and Education; Windows 10 Pro supports some BranchCache functionality, including BITS transfers used for servicing operations.

    Windows Server Update Services (WSUS) and System Center Configuration Manager can use BranchCache to allow peers to source content from each other versus always having to contact a server. Using BranchCache, files are cached on each individual client, and other clients can retrieve them as needed. This approach distributes the cache rather than having a single point of retrieval, saving a significant amount of bandwidth while drastically reducing the time that it takes for clients to receive the requested content.

Note

System Center Configuration Manager has an additional feature called Client Peer Cache that allows peer-to-peer content sharing between clients you use System Center Configuration Manager to manage, in the same Configuration Manager boundary Group. For more information, see Client Peer Cache.

In addition to Client Peer Cache, similar functionality is available in the Windows Preinstallation Environment (Windows PE) for imaging-related content. Using this technology, clients imaging with System Center Configuration Manager task sequences can source operating system images, driver packages, boot images, packages, and programs from peers instead of distribution points. For detailed information about how Windows PE Peer Cache works and how to configure it, see Prepare Windows PE peer cache to reduce WAN traffic in System Center Configuration Manager.

Express update delivery

Windows 10 quality update downloads can be large because every package contains all previously released fixes to ensure consistency and simplicity. Windows has been able to reduce the size of Windows Update downloads with a feature called Express.

Note

Express update delivery applies to quality update downloads. Starting with Windows 10, version 1709, Express update delivery also applies to feature update downloads for clients connected to Windows Update and Windows Update for Business.

How Microsoft supports Express

  • Express on System Center Configuration Manager starting with version 1702 of Configuration Manager and Windows 10, version 1703 or 1607 with the April 2017 cumulative update.
  • Express on WSUS Standalone

    Express update delivery is available on all support versions of WSUS.

  • Express on devices directly connected to Windows Update
  • Enterprise devices managed using Windows Update for Business also get the benefit of Express update delivery support without any change in configuration.

How Express download works

For OS updates that support Express, there are two versions of the file payload stored on the service:

  1. Full-file version - essentially replacing the local versions of the update binaries.
  2. Express version - containing the deltas needed to patch the existing binaries on the device.

Both the full-file version and the Express version are referenced in the update's metadata, which has been downloaded to the client as part of the scan phase.

Express download works as follows:

The Windows Update client will try to download Express first, and under certain situations fall back to full-file if needed (for example, if going through a proxy that doesn't support byte range requests).

  1. When the Windows Update client initiates an Express download, Windows Update first downloads a stub, which is part of the Express package.
  2. The Windows Update client passes this stub to the Windows installer, which uses the stub to do a local inventory, comparing the deltas of the file on the device with what is needed to get to the latest version of the file being offered.
  3. The Windows installer then requests the Windows Update client to download the ranges, which have been determined to be required.
  4. The client downloads these ranges and passes them to the Windows Installer, which applies the ranges and then determines if additional ranges are needed. This repeats until the Windows installer tells the Windows Update client that all necessary ranges have been downloaded.

At this point, the download is complete and the update is ready to be installed.

Tip

Express will always be leveraged if your machines are updated regularly with the latest cumulative updates.

Steps to manage updates for Windows 10

docs.microsoft.com

Overview of Windows as a service (Windows 10)

  • 02/09/2018
  • 15 minutes to read
  • Contributors

In this article

Applies to

  • Windows 10
  • Windows 10 Mobile
  • Windows 10 IoT Mobile

Looking for consumer information? See Windows Update: FAQ

The Windows 10 operating system introduces a new way to build, deploy, and service Windows: Windows as a service. Microsoft has reimagined each part of the process, to simplify the lives of IT pros and maintain a consistent Windows 10 experience for its customers. These improvements focus on maximizing customer involvement in Windows development, simplifying the deployment and servicing of Windows client computers, and leveling out the resources needed to deploy and maintain Windows over time.

Click the following Microsoft Mechanics video for an overview of the release model, particularly the Semi-Annual Channel.

Building

Prior to Windows 10, Microsoft released new versions of Windows every few years. This traditional deployment schedule imposed a training burden on users because the feature revisions were often significant. That schedule also meant waiting long periods without new features — a scenario that doesn’t work in today’s rapidly changing world, a world in which new security, management, and deployment capabilities are necessary to address challenges. Windows as a service will deliver smaller feature updates two times per year, around March and September, to help address these issues.

In the past, when Microsoft developed new versions of Windows, it typically released technical previews near the end of the process, when Windows was nearly ready to ship. With Windows 10, new features will be delivered to the Windows Insider community as soon as possible — during the development cycle, through a process called flighting — so that organizations can see exactly what Microsoft is developing and start their testing as soon as possible.

Microsoft also depends on receiving feedback from organizations throughout the development process so that it can make adjustments as quickly as possible rather than waiting until after release. For more information about the Windows Insider Program and how to sign up, see the section Windows Insider.

Of course Microsoft also performs extensive internal testing, with engineering teams installing new builds daily, and larger groups of employees installing builds frequently, all before those builds are ever released to the Windows Insider Program.

Deploying

Deploying Windows 10 is simpler than with previous versions of Windows. When migrating from earlier versions of Windows, an easy in-place upgrade process can be used to automatically preserve all apps, settings, and data. And once running Windows 10, deployment of Windows 10 feature updates will be equally simple.

One of the biggest challenges for organizations when it comes to deploying a new version of Windows is compatibility testing. Whereas compatibility was previously a concern for organizations upgrading to a new version of Windows, Windows 10 is compatible with most hardware and software capable of running on Windows 7 or later. Because of this high level of compatibility, the app compatibility testing process can be greatly simplified.

Application compatibility

Application compatibility testing has historically been a burden when approaching a Windows deployment or upgrade. With Windows 10, application compatibility from the perspective of desktop applications, websites, and apps built on the Universal Windows Platform (UWP) has improved tremendously. Microsoft understands the challenges organizations experienced when they migrated from the Windows XP operating system to Windows 7 and has been working to make Windows 10 upgrades a much better experience.

Most Windows 7–compatible desktop applications will be compatible with Windows 10 straight out of the box. Windows 10 achieved such high compatibility because the changes in the existing Win32 application programming interfaces were minimal. Combined with valuable feedback via the Windows Insider Program and diagnostic data, this level of compatibility can be maintained through each feature update. As for websites, Windows 10 includes Internet Explorer 11 and its backward-compatibility modes for legacy websites. Finally, UWP apps follow a compatibility story similar to desktop applications, so most of them will be compatible with Windows 10.

For the most important business-critical applications, organizations should still perform testing on a regular basis to validate compatibility with new builds. For remaining applications, consider validating them as part of a pilot deployment process to reduce the time spent on compatibility testing. If it’s unclear whether an application is compatible with Windows 10, IT pros can either consult with the ISV or check the supported software directory at http://www.readyforwindows.com.

Device compatibility

Device compatibility in Windows 10 is also very strong; new hardware is not needed for Windows 10 as any device capable of running Windows 7 or later can run Windows 10. In fact, the minimum hardware requirements to run Windows 10 are the same as those required for Windows 7. Most hardware drivers that functioned in Windows 8.1, Windows 8, or Windows 7 will continue to function in Windows 10.

Servicing

Traditional Windows servicing has included several release types: major revisions (e.g., the Windows 8.1, Windows 8, and Windows 7 operating systems), service packs, and monthly updates. With Windows 10, there are two release types: feature updates that add new functionality twice per year, and quality updates that provide security and reliability fixes at least once a month.

With Windows 10, organizations will need to change the way they approach deploying updates. Servicing channels are the first way to separate users into deployment groups for feature and quality updates. With the introduction of servicing channels comes the concept of a deployment ring, which is simply a way to categorize the combination of a deployment group and a servicing channel to group devices for successive waves of deployment. For more information about developing a deployment strategy that leverages servicing channels and deployment rings, see Plan servicing strategy for Windows 10 updates.

For information about each servicing tool available for Windows 10, see Servicing tools.

To align with this new update delivery model, Windows 10 has three servicing channels, each of which provides different levels of flexibility over when these updates are delivered to client computers. For information about the servicing channels available in Windows 10, see Servicing channels.

Naming changes

As part of the alignment with Windows 10 and Office 365 ProPlus, we are adopting common terminology to make it as easy as possible to understand the servicing process. Going forward, these are the new terms we will be using:

  • Semi-Annual Channel - We will be referreing to Current Branch (CB) as "Semi-Annual Channel (Targeted)", while Current Branch for Business (CBB) will simply be referred to as "Semi-Annual Channel".
  • Long-Term Servicing Channel - The Long-Term Servicing Branch (LTSB) will be referred to as Long-Term Servicing Channel (LTSC).

Feature updates

With Windows 10, Microsoft will package new features into feature updates that can be deployed using existing management tools. Because feature updates are delivered more frequently than with previous Windows releases — twice per year, around March and September, rather than every 3–5 years — changes will be in bite-sized chunks rather than all at once and end user readiness time much shorter.

Tip

The feature update cadence has been aligned with Office 365 ProPlus updates. Starting with this falls' update, both Windows and Office will deliver their major updates semi-annually, around March and September. See upcoming changes to Office 365 ProPlus update management for more information about changes to Office update management.

Quality updates

Monthly updates in previous Windows versions were often overwhelming because of the sheer number of updates available each month. Many organizations selectively chose which updates they wanted to install and which they didn’t, and this created countless scenarios in which organizations deployed essential security updates but picked only a subset of non-security fixes.

In Windows 10, rather than receiving several updates each month and trying to figure out which the organization needs, which ultimately causes platform fragmentation, administrators will see one cumulative monthly update that supersedes the previous month’s update, containing both security and non-security fixes. This approach makes patching simpler and ensures that customers’ devices are more closely aligned with the testing done at Microsoft, reducing unexpected issues resulting from patching. The left side of Figure 1 provides an example of Windows 7 devices in an enterprise and what their current patch level might look like. On the right is what Microsoft’s test environment PCs contain. This drastic difference is the basis for many compatibility issues and system anomalies related to Windows updates.

Figure 1

Servicing channels

To align with the new method of delivering feature updates and quality updates in Windows 10, Microsoft introduced the concept of servicing channels to allow customers to designate how frequently their individual devices are updated. For example, an organization may have test devices that the IT department can update with new features as soon as possible, and then specialized devices that require a longer feature update cycle to ensure continuity.

With that in mind, Windows 10 offers 3 servicing channels. The Windows Insider Program provides organizations with the opportunity to test and provide feedback on features that will be shipped in the next feature update. The Semi-Annual Channel provides new functionality with twice-per-year feature update releases. Organizations can choose when to deploy updates from the Semi-Annual Channel. The Long Term Servicing Channel, which is designed to be used only for specialized devices (which typically don't run Office) such as those that control medical equipment or ATM machines, receives new feature releases every two to three years. For details about the versions in each servicing channel, see Windows 10 release information.

The concept of servicing channels is new, but organizations can use the same management tools they used to manage updates and upgrades in previous versions of Windows. For more information about the servicing tool options for Windows 10 and their capabilities, see Servicing tools.

Note

Servicing channels are not the only way to separate groups of devices when consuming updates. Each channel can contain subsets of devices, which staggers servicing even further. For information about the servicing strategy and ongoing deployment process for Windows 10, including the role of servicing channels, see Plan servicing strategy for Windows 10 updates.

Semi-Annual Channel

In the Semi-Annual servicing channel, feature updates are available as soon as Microsoft releases them. Windows 10, version 1511, had few servicing tool options to delay feature updates, limiting the use of the Semi-Annual servicing channel. Windows 10, version 1607 and onward, includes more servicing tools that can delay feature updates for up to 365 days. This servicing modal is ideal for pilot deployments and testing of Windows 10 feature updates and for users such as developers who need to work with the latest features immediately. Once the latest release went through pilot deployment and testing, you choose the timing at which it goes into broad deployment.

When Microsoft officially releases a feature update for Windows 10, it is made available to any PC not configured to defer feature updates so that those devices can immediately install it. Organizations that use Windows Server Update Services (WSUS), Microsoft System Center Configuration Manager, or Windows Update for Business, however, can defer feature updates to selective devices by withholding their approval and deployment. In this scenario, the content available for the Semi-Annual Channel will be available but not necessarily immediately mandatory, depending on the policy of the management system. For more details about Windows 10 servicing tools, see Servicing tools.

Organizations are expected to initiate targeted deployment on Semi-Annual Channel releases, while after about 4 months, we will announce broad deployment readiness, indicating that Microsoft, independent software vendors (ISVs), partners, and customers believe that the release is ready for broad deployment. Each feature update release will be supported and updated for 18 months from the time of its release

Note

Organizations can electively delay feature updates into as many phases as they wish by using one of the servicing tools mentioned in the section Servicing tools.

Long-term Servicing Channel

Specialized systems—such as PCs that control medical equipment, point-of-sale systems, and ATMs—often require a longer servicing option because of their purpose. These devices typically perform a single important task and don’t need feature updates as frequently as other devices in the organization. It’s more important that these devices be kept as stable and secure as possible than up to date with user interface changes. The LTSC servicing model prevents Windows 10 Enterprise LTSB devices from receiving the usual feature updates and provides only quality updates to ensure that device security stays up to date. With this in mind, quality updates are still immediately available to Windows 10 Enterprise LTSB clients, but customers can choose to defer them by using one of the servicing tools mentioned in the section Servicing tools.

Note

Windows 10 Enterprise LTSB is a separate Long Term Servicing Channel version.

Long-term Servicing channel is not intended for deployment on most or all the PCs in an organization; it should be used only for special-purpose devices. As a general guideline, a PC with Microsoft Office installed is a general-purpose device, typically used by an information worker, and therefore it is better suited for the Semi-Annual servicing channel.

Microsoft never publishes feature updates through Windows Update on devices that run Windows 10 Enterprise LTSB. Instead, it typically offers new LTSC releases every 2–3 years, and organizations can choose to install them as in-place upgrades or even skip releases over a 10-year life cycle.

Note

Windows 10 LTSB will support the currently released silicon at the time of release of the LTSB. As future silicon generations are released, support will be created through future Windows 10 LTSB releases that customers can deploy for those systems. For more information, see Supporting the latest processor and chipsets on Windows in Lifecycle support policy FAQ - Windows Products.

The Long-term Servicing Channel is available only in the Windows 10 Enterprise LTSB edition. This build of Windows doesn’t contain many in-box applications, such as Microsoft Edge, Microsoft Store, Cortana (limited search capabilities remain available), Microsoft Mail, Calendar, OneNote, Weather, News, Sports, Money, Photos, Camera, Music, and Clock. Therefore, it’s important to remember that Microsoft has positioned the LTSC model primarily for specialized devices.

Note

If an organization has devices currently running Windows 10 Enterprise LTSB that it would like to change to the Semi-Annual Channel, it can make the change without losing user data. Because LTSB is its own SKU, however, an upgrade is required from Windows 10 Enterprise LTSB to Windows 10 Enterprise, which supports the Semi-Annual Channel.

Windows Insider

For many IT pros, gaining visibility into feature updates early—before they’re available to the Semi-Annual Channel — can be both intriguing and valuable for future end user communications as well as provide the means to test for any issues on the next Semi-Annual Channel release. With Windows 10, feature flighting enables Windows Insiders to consume and deploy preproduction code to their test machines, gaining early visibility into the next build. Testing the early builds of Windows 10 helps both Microsoft and its customers because they have the opportunity to discover possible issues before the update is ever publicly available and can report it to Microsoft.

Microsoft recommends that all organizations have at least a few PCs enrolled in the Windows Insider Program and provide feedback on any issues they encounter. For information about the Windows Insider Program for Business, go to Windows Insider Program for Business.

Note

Microsoft recommends that all organizations have at least a few PCs enrolled in the Windows Insider Program, to include the Windows Insider Program in their deployment plans and to provide feedback on any issues they encounter to Microsoft via our Feedback Hub app.

The Windows Insider Program isn’t intended to replace Semi-Annual Channel deployments in an organization. Rather, it provides IT pros and other interested parties with pre-release Windows builds that they can test and ultimately provide feedback on to Microsoft.

There are many tools with which IT pros can service Windows as a service. Each option has its pros and cons, ranging from capabilities and control to simplicity and low administrative requirements. The following are examples of the servicing tools available to manage Windows as a service updates:

  • Windows Update (stand-alone) provides limited control over feature updates, with IT pros manually configuring the device to be in the Semi-Annual Channel. Organizations can target which devices defer updates by selecting the Defer upgrades check box in Start\Settings\Update & Security\Advanced Options on a Windows 10 client.
  • Windows Update for Business is the second option for servicing Windows as a service. This servicing tool includes control over update deferment and provides centralized management using Group Policy. Windows Update for Business can be used to defer updates by up to 365 days, depending on the version. These deployment options are available to clients in the Semi-Annual Channel. In addition to being able to use Group Policy to manage Windows Update for Business, either option can be configured without requiring any on-premises infrastructure by using Intune.
  • Windows Server Update Services (WSUS) provides extensive control over Windows 10 updates and is natively available in the Windows Server operating system. In addition to the ability to defer updates, organizations can add an approval layer for updates and choose to deploy them to specific computers or groups of computers whenever ready.
  • System Center Configuration Manager provides the greatest control over servicing Windows as a service. IT pros can defer updates, approve them, and have multiple options for targeting deployments and managing bandwidth usage and deployment times.

With all these options, which an organization chooses depends on the resources, staff, and expertise its IT organization already has. For example, if IT already uses System Center Configuration Manager to manage Windows updates, it can continue to use it. Similarly, if IT is using WSUS, it can continue to use that. For a consolidated look at the benefits of each tool, see Table 1.

Table 1

Servicing tool Can updates be deferred? Ability to approve updates Peer-to-peer option Additional features
Windows Update Yes (manual) No Delivery Optimization None
Windows Update for Business Yes No Delivery Optimization Other Group Policy objects
WSUS Yes Yes BranchCache or Delivery Optimization Upstream/downstream server scalability
Configuration Manager Yes Yes BranchCache, Client Peer Cache Distribution points, multiple deployment options

Note

Due to naming changes, older terms like CB,CBB and LTSB may still be displayed in some of our products.

Steps to manage updates for Windows 10

docs.microsoft.com

Deploy and update Windows 10 (Windows 10)

  • 12/13/2017
  • 5 minutes to read
  • Contributors

In this article

Learn about deployment in Windows 10 for IT professionals. This includes deploying the operating system, upgrading to it from previous versions and updating Windows 10. The following sections and topics are available.

Topic Description
What's new in Windows 10 deployment See this topic for a summary of new features and some recent changes related to deploying Windows 10 in your organization.
Windows 10 deployment scenarios To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the key capabilities and limitations of each, is a key task.
Windows 10 Subscription Activation Windows 10 Enterprise has traditionally been sold as on premises software, however, with Windows 10 version 1703 (also known as the Creator’s Update), both Windows 10 Enterprise E3 and Windows 10 Enterprise E5 are available as true online services via subscription. You can move from Windows 10 Pro to Windows 10 Enterprise with no keys and no reboots. If you are using a Cloud Service Providers (CSP) see the related topic: Windows 10 Enterprise E3 in CSP.
Resolve Windows 10 upgrade errors This topic provides a brief introduction to Windows 10 installation processes, and provides resolution procedures that IT administrators can use to resolve issues with Windows 10 upgrade.

Deploy Windows 10

Windows 10 upgrade options are discussed and information is provided about planning, testing, and managing your production deployment.

Topic Description
Overview of Windows AutoPilot Windows AutoPilot deployment is a new cloud service from Microsoft that provides a zero touch experience for deploying Windows 10 devices.
Windows 10 upgrade paths This topic provides information about support for upgrading directly to Windows 10 from a previous operating system.
Windows 10 edition upgrade This topic provides information about support for upgrading from one edition of Windows 10 to another.
Windows 10 volume license media This topic provides information about media available in the Microsoft Volume Licensing Service Center.
Manage Windows upgrades with Upgrade Readiness With Upgrade Readiness, enterprises now have the tools to plan and manage the upgrade process end to end, allowing them to adopt new Windows releases more quickly. With Windows diagnostic data enabled, Upgrade Readiness collects system, application, and driver data for analysis. We then identify compatibility issues that can block an upgrade and suggest fixes when they are known to Microsoft. The Upgrade Readiness workflow steps you through the discovery and rationalization process until you have a list of computers that are ready to be upgraded.
Windows 10 deployment test lab This guide contains instructions to configure a proof of concept (PoC) environment requiring a minimum amount of resources. The guide makes extensive use of Windows PowerShell and Hyper-V. Subsequent companion guides contain steps to deploy Windows 10 using the PoC environment. After completing this guide, additional guides are provided to deploy Windows 10 in the test lab using Microsoft Deployment Toolkit or System Center Configuration Manager.
Plan for Windows 10 deployment This section describes Windows 10 deployment considerations and provides information to assist in Windows 10 deployment planning.
Deploy Windows 10 with the Microsoft Deployment Toolkit This guide will walk you through the process of deploying Windows 10 in an enterprise environment using the Microsoft Deployment Toolkit (MDT).
Deploy Windows 10 with System Center 2012 R2 Configuration Manager If you have Microsoft System Center 2012 R2 Configuration Manager in your environment, you will most likely want to use it to deploy Windows 10. This topic will show you how to set up Configuration Manager for operating system deployment and how to integrate Configuration Manager with the Microsoft Deployment Toolkit (MDT) or.
Windows 10 deployment tools Learn about available tools to deploy Windows 10, such as the Windows ADK, DISM, USMT, WDS, MDT, Windows PE and more.

Update Windows 10

Information is provided about keeping Windows 10 up-to-date.

Additional topics

docs.microsoft.com

FAQ: How to manage Windows 10 updates

This article has been updated multiple times since its initial publication. The most recent update was January 16, 2018.

With Windows 10, Microsoft has completely rewritten the Windows Update rulebook. For expert users and IT pros accustomed to having fine-grained control over the update process, these changes might seem wrenching and even draconian.

You can't pick and choose which updates to install? There's no option to delay updates on PCs running Windows 10 Home? Upgrades to new versions are mandatory?

Welcome to Windows as a service.

The new update rules are designed to solve some nagging problems in the PC ecosystem. For example, if every user can choose some updates and reject others, the number of potential configurations approaches infinity; Microsoft argues that all those untested variations make effective quality assurance much more difficult.

Likewise, Microsoft's generous 10-year support lifecycle has enabled fragmentation in the installed base: Over the past decade, Microsoft's engineering staff have been required to support as many as five major versions at the same time. In a world where security challenges arrive at breakneck speed, that stretches support resources to the breaking point.

Other Windows 10 FAQs in this series:

And thus a new approach to Windows Update, whose goals are to have the majority of Windows users fully patched at all times, with only a few versions to support and an installed base that is mostly running one of the two most recent versions.

This FAQ covers the details you need to know, including important changes to the full Windows Update feature set since the initial release of Windows 10.

What kind of updates are available for Windows 10?

Microsoft provides two types of update packages for Windows 10:

  • Feature updates are the equivalent of what used to be called version upgrades. They include new features and require a multi-gigabyte download and a full setup. Each version update gets a major version number that corresponds to its date of release, in the yymm format, as well as a build number that identifies it. Version 1709, for example, was finalized in September 2017 and is identified as build 16299. Microsoft's schedule is to deliver Windows 10 feature updates twice a year.
  • Quality updates address security and reliability issues and do not include new features. These updates are cumulative, and they increment the minor version number after the major version number. The January 2018 cumulative update for version 1709, for example, is 16299.192. Even if you skip several months' worth of updates, you can install the latest cumulative update and you will be completely up to date.

All available security and reliability updates are included in a cumulative update and cannot be selected or rejected individually. That's a major change from previous versions and a big surprise to anyone upgrading to Windows 10 for the first time.

Besides these cumulative updates, you might see servicing stack updates delivered separately. These update packages fix issues in the code that Windows 10 uses to scan for and process updates. Security updates for Adobe Flash Player and definition updates for Windows Defender are also delivered separately.

Hardware drivers and firmware updates can be delivered through Windows Update. Typically, these packages are provided only when the driver fixes a bug that causes instability on targeted systems.

How are updates delivered in Windows 10?

For consumers and small businesses, both quality and feature updates are delivered via Windows Update. Organizations can use internal update management solutions, such as Windows Server Update Services, to distribute updates to computers on a corporate network.

Feature updates are delivered according to servicing channels. (In early releases of Windows 10, these were called branches. The concept is the same; only the names have changed.)

By default, all Windows 10 computers are enrolled in the Semi-Annual Channel (Targeted), which was previously known as the Current Branch. For devices assigned to this channel, updates are delivered via Windows Update shortly after they're released by Microsoft.

Because of the enormous number of machines that receive Windows updates, Microsoft "throttles" update delivery to manage the load on its servers. As a result, it may take weeks or even months for a feature update to roll out to all of the hundreds of millions of devices in each servicing channel.

After Microsoft determines that initial reliability and security issues discovered during the first few months of release have been addressed, it declares the current version ready for widespread deployment in the Semi-Annual Channel.

Quality updates are delivered at the same time to all supported branches. These cumulative updates arrive on the second Tuesday of each month, or Patch Tuesday, as it's widely known. (Microsoft officials refers to this day as Update Tuesday.)

Microsoft may deliver additional updates throughout the month, including cumulative updates and servicing stack updates. So-called out-of-band patches to address critical security issues may appear at any time, generally in response to reports that a Windows flaw is being actively exploited.

How can I tell which updates are installed?

See the list under Settings > Update & Security > Windows Update > View Installed Update History. The list is divided into three groups: Quality Updates, Driver Updates, and Other Updates. Click the entry for any update to see further details about that update, if they're available.

How do I know whether my system is up to date?

Follow this link for instructions on how to identify the build installed on your device and compare it to the master list of Windows 10 updates:

Windows 10 tip: Find and decode secret version details

When does Windows 10 install updates?

Windows 10 downloads updates in the background and installs them automatically. Using options on the Windows Update page in Settings, you can specify Active Hours (a block of up to 18 continuous hours) when you don't want to be interrupted by these installations. In theory, that prevents a large update from interfering with your workday activities, although the strategy fails if you shut your device down at the end of the day and don't restart until the next day.

Beginning with version 1709 (the Creators Update), Windows 10 offers additional notification options as well as the option to choose a specific time (during your lunch break, for example) when updates will be installed.

Can I delay the installation of updates?

If you're running Windows 10 Home, there is no supported way to delay the installation of updates. When a feature update is available, it will install in the next window outside Active Hours. You can try various workarounds, such as shutting off the Windows Update service or setting your network connection as metered, but these only briefly postpone the inevitable.

In Pro, Enterprise, and Education editions, you can defer feature updates for up to 16 months after their initial release to the Semi-Annual Channel (Targeted). In addition, you can defer quality updates, including the monthly Patch Tuesday fixes, by up to 30 days.

These deferrals use the Windows Update for Business feature set. For full instructions on how to use Windows Update for Business, see "How to take control of Windows 10 updates and upgrades (even if you don't own a business)."

After you reach the maximum deferral period for each type of update, Windows 10 installs it automatically. No further deferrals are permitted.

Can I uninstall a driver delivered through Windows Update?

Yes. Follow these instructions to remove the driver and prevent it from being installed again:

Windows 10 tip: Hide unwanted drivers in Windows Update

More update questions? Send me an email using the contact form on my bio. (Click the envelope icon.)

www.zdnet.com

Deploy Windows 10 updates using System Center Configuration Manager (Windows 10)

  • 10/16/2017
  • 14 minutes to read
  • Contributors

In this article

Applies to

  • Windows 10
  • Windows 10 Mobile

Looking for consumer information? See Windows Update: FAQ

Important

Due to naming changes, older terms like CB,CBB and LTSB may still be displayed in some of our products.

In the following settings CB refers to Semi-Annual Channel (Targeted), while CBB refers to Semi-Annual Channel.

System Center Configuration Manager provides maximum control over quality and feature updates for Windows 10. Unlike other servicing tools, Configuration Manager has capabilities that extend beyond servicing, such as application deployment, antivirus management, software metering, and reporting, and provides a secondary deployment method for LTSB clients. Configuration Manager can effectively control bandwidth usage and content distribution through a combination of BranchCache and distribution points. Microsoft encourages organizations currently using Configuration Manager for Windows update management to continue doing so for Windows 10 client computers.

You can use Configuration Manager to service Windows 10 devices in two ways. The first option is to use Windows 10 Servicing Plans to deploy Windows 10 feature updates automatically based on specific criteria, similar to an Automatic Deployment Rule for software updates. The second option is to use a task sequence to deploy feature updates, along with anything else in the installation.

Windows 10 servicing dashboard

The Windows 10 servicing dashboard gives you a quick-reference view of your active servicing plans, compliance for servicing plan deployment, and other key information about Windows 10 servicing. For details about what each tile on the servicing dashboard represents, see Manage Windows as a service using System Center Configuration Manager.

For the Windows 10 servicing dashboard to display information, you must adhere to the following requirements:

  • Heartbeat discovery. Enable heartbeat discovery for the site receiving Windows 10 servicing information. Configuration for heartbeat discovery can be found in Administration\Overview\Hierarchy Configuration\Discovery Methods.
  • Windows Server Update Service (WSUS). System Center Configuration Manager must have the Software update point site system role added and configured to receive updates from a WSUS 4.0 server with the hotfix KB3095113 installed.
  • Service connection point. Add the Service connection point site system role in Online, persistent connection mode.
  • Upgrade classification. Select Upgrade from the list of synchronized software update classifications.

    To configure Upgrade classification

    1. Go to Administration\Overview\Site Configuration\Sites, and then select your site from the list.

    2. On the Ribbon, in the Settings section, click Configure Site Components, and then click Software Update Point.

    3. In the Software Update Point Component Properties dialog box, on the Classifications tab, click Upgrades.

When you have met all these requirements and deployed a servicing plan to a collection, you’ll receive information on the Windows 10 servicing dashboard.

Create collections for deployment rings

Regardless of the method by which you deploy Windows 10 feature updates to your environment, you must start the Windows 10 servicing process by creating collections of computers that represent your deployment rings. In this example, you create two collections: Windows 10 – All Current Branch for Business and Ring 4 Broad business users. You’ll use the Windows 10 – All Current Branch for Business collection for reporting and deployments that should go to all CBB clients. You’ll use the Ring 4 Broad business users collection as a deployment ring for the first CBB users.

To create collections for deployment rings

  1. In the Configuration Manager console, go to Assets and Compliance\Overview\Device Collections.

  2. On the Ribbon, in the Create group, click Create Device Collection.

  3. In the Create Device Collection Wizard, in the name box, type Windows 10 – All Current Branch for Business.

  4. Click Browse to select the limiting collection, and then click All Systems.

  5. In Membership rules, click Add Rule, and then click Query Rule.

  6. Name the rule CBB Detection, and then click Edit Query Statement.

  7. On the Criteria tab, click the New icon.

  8. In the Criterion Properties dialog box, leave the type as Simple Value, and then click Select.

  9. In the Select Attribute dialog box, from the Attribute class list, select System Resource. From the Attribute list, select OSBranch, and then click OK.

    Note

    Configuration Manager discovers clients’ servicing branch and stores that value in the OSBranch attribute, which you will use to create collections based on servicing branch. The values in this attribute can be 0 (Current Branch), 1 (Current Branch for Business), or 2 (Long-Term Servicing Branch).

  10. Leave Operator set to is equal to; in the Value box, type 1. Click OK.

  11. Now that the OSBranch attribute is correct, verify the operating system version.

  12. On the Criteria tab, click the New icon again to add criteria.

  13. In the Criterion Properties dialog box, click Select.

  14. From the Attribute class list, select System Resource. From the Attribute list, select Operating System Name and Version, and then click OK.

  15. In the Value box, type Microsoft Windows NT Workstation 10.0, and then click OK.

  16. In the Query Statement Properties dialog box, you see two values. Click OK, and then click OK again to continue to the Create Device Collection Wizard.

  17. Click Summary, and then click Next.

  18. Close the wizard.

Important

Windows Insider PCs are discovered the same way as CB or CBB devices. If you have Windows Insider PCs that you use Configuration Manager to manage, then you should create a collection of those PCs and exclude them from this collection. You can create the membership for the Windows Insider collection either manually or by using a query where the operating system build doesn’t equal any of the current CB or CBB build numbers. You would have to update each periodically to include new devices or new operating system builds.

After you have updated the membership, this new collection will contain all managed clients on the CBB servicing branch. You will use this collection as a limiting collection for future CBB-based collections and the Ring 4 Broad broad business users collection. Complete the following steps to create the Ring 4 Broad business users device collection, which you’ll use as a CBB deployment ring for servicing plans or task sequences.

  1. In the Configuration Manager console, go to Assets and Compliance\Overview\Device Collections.

  2. On the Ribbon, in the Create group, click Create Device Collection.

  3. In the Create Device Collection Wizard, in the name box, type Ring 4 Broad business users.

  4. Click Browse to select the limiting collection, and then click Windows 10 – All Current Branch for Business.

  5. In Membership rules, click Add Rule, and then click Direct Rule.

  6. In the Create Direct Membership Rule Wizard dialog box, click Next.

  7. In the Value field, type all or part of the name of a device to add, and then click Next.

  8. Select the computer that will be part of the Ring 4 Broad business users deployment ring, and then click Next.

  9. Click Next, and then click Close.

  10. In the Create Device Collection Wizard dialog box, click Summary.

  11. Click Next, and then click Close.

Use Windows 10 servicing plans to deploy Windows 10 feature updates

There are two ways to deploy Windows 10 feature updates with System Center Configuration Manager. The first is to use servicing plans, which provide an automated method to update devices consistently in their respective deployment rings, similar to Automatic Deployment Rules for software updates.

To configure Windows feature updates for CBB clients in the Ring 4 Broad business users deployment ring using a servicing plan

  1. In the Configuration Manager console, go to Software Library\Overview\Windows 10 Servicing, and then click Servicing Plans.

  2. On the Ribbon, in the Create group, click Create Servicing Plan.

  3. Name the plan Ring 4 Broad business users Servicing Plan, and then click Next.

  4. On the Servicing Plan page, click Browse. Select the Ring 4 Broad business users collection, which you created in the Create collections for deployment rings section, click OK, and then click Next.

    Important

    Microsoft added a new protection feature to Configuration Manager that prevents accidental installation of high-risk deployments such as operating system upgrades on site systems. If you select a collection (All Systems in this example) that has a site system in it, you may receive the following message.

    For details about how to manage the settings for high-risk deployments in Configuration Manager, see Settings to manage high-risk deployments for System Center Configuration Manager.

  5. On the Deployment Ring page, select the Business Ready (Current Branch for Business) readiness state, leave the delay at 0 days, and then click Next.

    Doing so deploys CBB feature updates to the broad business users deployment ring immediately after they are released to CBB.

    On the Upgrades page, you specify filters for the feature updates to which this servicing plan is applicable. For example, if you wanted this plan to be only for Windows 10 Enterprise, you could select Title, and then type Enterprise.

  6. For this example, on the Upgrades page, click Next to leave the criterion blank.

  7. On the Deployment Schedule page, click Next to keep the default values of making the content available immediately and requiring installation by the 7-day deadline.

  8. On the User Experience page, from the Deadline behavior list, select Software Installation and System restart (if necessary). From the Device restart behavior list, select Workstations, and then click Next.

    Doing so allows installation and restarts after the 7-day deadline on workstations only.

  9. On the Deployment Package page, select Create a new deployment package. In Name, type CBB Upgrades, select a share for your package source location, and then click Next.

    In this example, \contoso-cm01\Sources\Windows 10 Feature Upgrades is a share on the Configuration Manager server that contains all the Windows 10 feature updates.

  10. On the Distribution Points page, from the Add list, select Distribution Point.

    Select the distribution points that serve the clients to which you’re deploying this servicing plan, and then click OK.

  11. Click Summary, click Next to complete the servicing plan, and then click Close.

You have now created a servicing plan for the Ring 4 Broad business users deployment ring. By default, this rule is evaluated each time the software update point is synchronized, but you can modify this schedule by viewing the service plan’s properties on the Evaluation Schedule tab.

Use a task sequence to deploy Windows 10 updates

There are times when deploying a Windows 10 feature update requires the use of a task sequence—for example:

  • LTSB feature updates. With the LTSB servicing branch, feature updates are never provided to the Windows clients themselves. Instead, feature updates must be installed like a traditional in-place upgrade.
  • Additional required tasks. When deploying a feature update requires additional steps (e.g., suspending disk encryption, updating applications), you must use task sequences to orchestrate the additional steps. Servicing plans do not have the ability to add steps to their deployments.

Each time Microsoft releases a new Windows 10 build, it releases a new .iso file containing the latest build, as well. Regardless of the scenario that requires a task sequence to deploy the Windows 10 upgrade, the base process is the same. Start by creating an Operating System Upgrade Package in the Configuration Manager console:

  1. In the Configuration Manager console, go to Software Library\Overview\Operating Systems\Operating System Upgrade Packages.

  2. On the Ribbon, in the Create group, click Add Operating System Upgrade Package.

  3. On the Data Source page, type the path of the extracted .iso file of the new version of Windows 10 you’re deploying, and then click Next.

    In this example, the Windows 10 Enterprise 1607 installation media is deployed to \contoso-cm01\Sources\Operating Systems\Windows 10 Enterprise\Windows 10 Enterprise - Version 1607.

    Note

    System Center Configuration Manager version 1606 is required to manage machines running Windows 10, version 1607.

  4. On the General page, in the Name field, type the name of the folder (Windows 10 Enterprise - Version 1607 in this example). Set the Version to 1607, and then click Next.

  5. On the Summary page, click Next to create the package.

  6. On the Completion page, click Close.

Now that the operating system upgrade package has been created, the content in that package must be distributed to the correct distribution points so that the clients can access the content. Complete the following steps to distribute the package content to distribution points:

  1. In the Configuration Manager console, go to Software Library\Overview\Operating Systems\Operating System Upgrade Packages, and then select the Windows 10 Enterprise – Version 1607 software upgrade package.

  2. On the Ribbon, in the Deployment group, click Distribute Content.

  3. In the Distribute Content Wizard, on the General page, click Next.

  4. On the Content Destination page, click Add, and then click Distribution Point.

  5. In the Add Distribution Points dialog box, select the distribution point that will serve the clients receiving this package, and then click OK.

  6. On the Content Destination page, click Next.

  7. On the Summary page, click Next to distribute the content to the selected distribution point.

  8. On the Completion page, click Close.

Now that the upgrade package has been created and its contents distributed, create the task sequence that will use it. Complete the following steps to create the task sequence, using the previously created deployment package:

  1. In the Configuration Manager console, go to Software Library\Overview\Operating Systems\Task Sequences.

  2. On the Ribbon, in the Create group, click Create Task Sequence.

  3. In the Create Task Sequence Wizard, on the Create a new task sequence page, select Upgrade an operating system from upgrade package, and then click Next.

  4. On the Task Sequence Information page, in Task sequence name, type Upgrade Windows 10 Enterprise – Version 1607, and then click Next.

  5. On the Upgrade the Windows Operating system page, click Browse, select the deployment package you created in the previous steps, and then click OK.

  6. Click Next.

  7. On the Include Updates page, select Available for installation – All software updates, and then click Next.

  8. On the Install Applications page, click Next.

  9. On the Summary page, click Next to create the task sequence.

  10. On the Completion page, click Close.

With the task sequence created, you’re ready to deploy it. If you’re using this method to deploy most of your Windows 10 feature updates, you may want to create deployment rings to stage the deployment of this task sequence, with delays appropriate for the respective deployment ring. In this example, you deploy the task sequence to the Ring 4 Broad business users collection.

Important

This process deploys a Windows 10 operating system feature update to the affected devices. If you’re testing, be sure to select the collection to which you deploy this task sequence carefully.

To deploy your task sequence

  1. In the Configuration Manager console, go to Software Library\Overview\Operating Systems\Task Sequences, and then select the Upgrade Windows 10 Enterprise – Version 1607 task sequence.

  2. On the Ribbon, in the Deployment group, click Deploy.

  3. In the Deploy Software Wizard, on the General page, click Browse. Select the target collection, click OK, and then click Next.

  4. On the Deployment Settings page, for purpose, select Required, and then click Next.

  5. On the Scheduling page, select the Schedule when this deployment will become available check box (it sets the current time by default). For Assignment schedule, click New.

  6. In the Assignment Schedule dialog box, click Schedule.

  7. In the Custom Schedule dialog box, select the desired deadline, and then click OK.

  8. In the Assignment Schedule dialog box, click OK, and then click Next.

  9. On the User Experience page, in the When the scheduled assignment time is reached, allow the following activities to be performed outside of the maintenance window section, select Software Installation and System restart (if required to complete the installation), and then click Next.

  10. Use the defaults for the remaining settings.

  11. Click Summary, and then click Next to deploy the task sequence.

  12. Click Close.

Steps to manage updates for Windows 10

See also

Manage Windows as a service using System Center Configuration Manager

docs.microsoft.com

How to download and install the Windows 10 Anniversary Update

Microsoft's Windows 10 Anniversary Edition has arrived.

Sarah Jacobsson Purewal/CNET

The first major update to Windows 10 -- the Windows 10 Anniversary Update -- started rolling out to all users on August 2. This update brings several changes to the operating system, including visual modifications, improvements to the Edge browser and new features such as Windows Ink.

See also: 15 things to look forward to in the Windows 10 Anniversary Update

You don't need to do anything to get the update. Windows 10 automatically scans for, downloads and installs new updates to your device (though the Anniversary Update will require a restart).

But maybe you've been waiting for Windows Update to automatically update your device...and it still hasn't updated. Because Microsoft is rolling out the update slowly (very slowly...), the Anniversary Update may not be available for your device yet.

Also, if you recently upgraded to Windows 10 from Windows 7 or Windows 8/8.1, the Anniversary Update will not be automatically available to you until you've had Windows 10 for at least 30 days. If you're still within this 30-day window, you can get the Anniversary Update right now by deleting the Windows.old folder with Disk Cleanup.

Once you delete the Windows.old folder, you can manually prompt Windows Update to download the Anniversary Update.

  • Open the Settings menu and go to Update & security > Windows Update.
  • Click Check for updates to prompt your PC to scan for the latest updates. The update will be downloaded and installed automatically.
  • Click Restart Now to restart your PC and complete the installation process.

If this method doesn't work for you, you can manually download the Anniversary Update ISO from Microsoft's Windows 10 update history page.

  • Go to the Windows 10 update history page.
  • Click Get the Anniversary Update now to download the ISO (an EXE file).
  • Run the file to open the Windows 10 Update Assistant, and follow the instructions to complete the installation process.

Now Playing: Watch this: Cortana gets some new tricks in Windows 10

2:30

These two other methods have also been suggested online, but right now neither of them will help you get the Anniversary Update any faster.

  • Enroll in the Windows Insider Program: Windows Insiders have had access to the features and changes present in the Anniversary Update for some time now, and anyone can enroll a device in the Windows Insider Program. But the Windows Insider Program takes several days, and sometimes weeks, to activate. So you won't receive the latest Windows Insider build immediately upon signing up for the program.
  • Manually install the update using the Windows 10 Media Creation Tool: The Windows 10 Media Creation Tool allows you to create your own Windows 10 installation media (USB, DVD or ISO) to perform a clean installation of the operating system. The Media Creation Tool doesn't yet include the Anniversary Update, so if you attempt to update your system using media created with this tool, you will simply end up reinstalling Windows 10.

    Update: The Media Creation Tool has been updated to include build 14393.0. Note that this is not the final release build of the Anniversary Update, which is build 14393.1.

Editors' note: This article was originally published on August 2, 2016, and was updated on September 15, 2016.

www.cnet.com


Смотрите также