mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
author change
This commit is contained in:
Greg Lindsay
parent
2ceb52e68f
commit
cd9dfebd75
@ -1,206 +1,207 @@
|
|||||||
---
|
---
|
||||||
title: Windows Updates using forward and reverse differentials
|
title: Windows Updates using forward and reverse differentials
|
||||||
description: A technique to produce compact software updates optimized for any origin and destination revision pair
|
description: A technique to produce compact software updates optimized for any origin and destination revision pair
|
||||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.author: greglin
|
ms.localizationpriority: medium
|
||||||
ms.date: 10/18/2018
|
ms.author: jaimeo
|
||||||
ms.reviewer:
|
ms.date: 10/18/2018
|
||||||
manager: laurawi
|
ms.reviewer:
|
||||||
ms.topic: article
|
manager: laurawi
|
||||||
---
|
ms.topic: article
|
||||||
|
---
|
||||||
# Windows Updates using forward and reverse differentials
|
|
||||||
|
# Windows Updates using forward and reverse differentials
|
||||||
|
|
||||||
Windows 10 monthly quality updates are cumulative, containing all previously
|
|
||||||
released fixes to ensure consistency and simplicity. For an operating system
|
Windows 10 monthly quality updates are cumulative, containing all previously
|
||||||
platform like Windows 10, which stays in support for multiple years, the size of
|
released fixes to ensure consistency and simplicity. For an operating system
|
||||||
monthly quality updates can quickly grow large, thus directly impacting network
|
platform like Windows 10, which stays in support for multiple years, the size of
|
||||||
bandwidth consumption.
|
monthly quality updates can quickly grow large, thus directly impacting network
|
||||||
|
bandwidth consumption.
|
||||||
Today, this problem is addressed by using express downloads, where differential
|
|
||||||
downloads for every changed file in the update are generated based on selected
|
Today, this problem is addressed by using express downloads, where differential
|
||||||
historical revisions plus the base version. In this paper, we introduce a new
|
downloads for every changed file in the update are generated based on selected
|
||||||
technique to build compact software update packages that are applicable to any
|
historical revisions plus the base version. In this paper, we introduce a new
|
||||||
revision of the base version, and then describe how Windows 10 quality updates
|
technique to build compact software update packages that are applicable to any
|
||||||
uses this technique.
|
revision of the base version, and then describe how Windows 10 quality updates
|
||||||
|
uses this technique.
|
||||||
## General Terms
|
|
||||||
|
## General Terms
|
||||||
The following general terms apply throughout this document:
|
|
||||||
|
The following general terms apply throughout this document:
|
||||||
- *Base version*: A major software release with significant changes, such as
|
|
||||||
Windows 10, version 1809 (Windows 10 Build 17763.1)
|
- *Base version*: A major software release with significant changes, such as
|
||||||
|
Windows 10, version 1809 (Windows 10 Build 17763.1)
|
||||||
- *Revision*: Minor releases in between the major version releases, such as
|
|
||||||
KB4464330 (Windows 10 Build 17763.55)
|
- *Revision*: Minor releases in between the major version releases, such as
|
||||||
|
KB4464330 (Windows 10 Build 17763.55)
|
||||||
- *Baseless Patch Storage Files (Baseless PSF)*: Patch storage files that
|
|
||||||
contain full binaries or files
|
- *Baseless Patch Storage Files (Baseless PSF)*: Patch storage files that
|
||||||
|
contain full binaries or files
|
||||||
## Introduction
|
|
||||||
|
## Introduction
|
||||||
In this paper, we introduce a new technique that can produce compact software
|
|
||||||
updates optimized for any origin/destination revision pair. It does this by
|
In this paper, we introduce a new technique that can produce compact software
|
||||||
calculating forward the differential of a changed file from the base version and
|
updates optimized for any origin/destination revision pair. It does this by
|
||||||
its reverse differential back to the base version. Both forward and reverse
|
calculating forward the differential of a changed file from the base version and
|
||||||
differentials are then packaged as an update and distributed to the endpoints
|
its reverse differential back to the base version. Both forward and reverse
|
||||||
running the software to be updated. The update package contents can be symbolized as follows:
|
differentials are then packaged as an update and distributed to the endpoints
|
||||||
|
running the software to be updated. The update package contents can be symbolized as follows:
|
||||||
|
|
||||||
|
|
||||||
The endpoints that have the base version of the file (V<sub>0</sub>) hydrate the target
|
|
||||||
revision (V<sub>N</sub>) by applying a simple transformation:
|
The endpoints that have the base version of the file (V<sub>0</sub>) hydrate the target
|
||||||
|
revision (V<sub>N</sub>) by applying a simple transformation:
|
||||||
|
|
||||||
|
|
||||||
The endpoints that have revision N of the file (V<sub>N</sub>), hydrate the target revision
|
|
||||||
(V<sub>R</sub>) by applying the following set of transformations:
|
The endpoints that have revision N of the file (V<sub>N</sub>), hydrate the target revision
|
||||||
|
(V<sub>R</sub>) by applying the following set of transformations:
|
||||||
|
|
||||||
|
|
||||||
The endpoints retain the reverse differentials for the software revision they
|
|
||||||
are on, so that it can be used for hydrating and applying next revision update.
|
The endpoints retain the reverse differentials for the software revision they
|
||||||
|
are on, so that it can be used for hydrating and applying next revision update.
|
||||||
By using a common baseline, this technique produces a single update package with
|
|
||||||
numerous advantages:
|
By using a common baseline, this technique produces a single update package with
|
||||||
|
numerous advantages:
|
||||||
- Compact in size
|
|
||||||
|
- Compact in size
|
||||||
- Applicable to all baselines
|
|
||||||
|
- Applicable to all baselines
|
||||||
- Simple to build
|
|
||||||
|
- Simple to build
|
||||||
- Efficient to install
|
|
||||||
|
- Efficient to install
|
||||||
- Redistributable
|
|
||||||
|
- Redistributable
|
||||||
Historically, download sizes of Windows 10 quality updates (Windows 10, version
|
|
||||||
1803 and older supported versions of Windows 10) are optimized by using express
|
Historically, download sizes of Windows 10 quality updates (Windows 10, version
|
||||||
download. Express download is optimized such that updating Windows 10 systems
|
1803 and older supported versions of Windows 10) are optimized by using express
|
||||||
will download the minimum number of bytes. This is achieved by generating
|
download. Express download is optimized such that updating Windows 10 systems
|
||||||
differentials for every updated file based on selected historical base revisions
|
will download the minimum number of bytes. This is achieved by generating
|
||||||
of the same file + its base or RTM version.
|
differentials for every updated file based on selected historical base revisions
|
||||||
|
of the same file + its base or RTM version.
|
||||||
For example, if the October monthly quality update has updated Notepad.exe,
|
|
||||||
differentials for Notepad.exe file changes from September to October, August to
|
For example, if the October monthly quality update has updated Notepad.exe,
|
||||||
October, July to October, June to October, and from the original feature release
|
differentials for Notepad.exe file changes from September to October, August to
|
||||||
to October are generated. All these differentials are stored in a Patch Storage
|
October, July to October, June to October, and from the original feature release
|
||||||
File (PSF, also referred to as “express download files”) and hosted or cached on
|
to October are generated. All these differentials are stored in a Patch Storage
|
||||||
Windows Update or other update management or distribution servers (for example,
|
File (PSF, also referred to as “express download files”) and hosted or cached on
|
||||||
Windows Server Update Services (WSUS), System Center Configuration Manager, or a
|
Windows Update or other update management or distribution servers (for example,
|
||||||
non-Microsoft update management or distribution server that supports express
|
Windows Server Update Services (WSUS), System Center Configuration Manager, or a
|
||||||
updates). A device leveraging express updates uses network protocol to determine
|
non-Microsoft update management or distribution server that supports express
|
||||||
optimal differentials, then downloads only what is needed from the update
|
updates). A device leveraging express updates uses network protocol to determine
|
||||||
distribution endpoints.
|
optimal differentials, then downloads only what is needed from the update
|
||||||
|
distribution endpoints.
|
||||||
The flipside of express download is that the size of PSF files can be very large
|
|
||||||
depending on the number of historical baselines against which differentials were
|
The flipside of express download is that the size of PSF files can be very large
|
||||||
calculated. Downloading and caching large PSF files to on-premises or remote
|
depending on the number of historical baselines against which differentials were
|
||||||
update distribution servers is problematic for most organizations, hence they
|
calculated. Downloading and caching large PSF files to on-premises or remote
|
||||||
are unable to leverage express updates to keep their fleet of devices running
|
update distribution servers is problematic for most organizations, hence they
|
||||||
Windows 10 up to date. Secondly, due to the complexity of generating
|
are unable to leverage express updates to keep their fleet of devices running
|
||||||
differentials and size of the express files that need to be cached on update
|
Windows 10 up to date. Secondly, due to the complexity of generating
|
||||||
distribution servers, it is only feasible to generate express download files for
|
differentials and size of the express files that need to be cached on update
|
||||||
the most common baselines, thus express updates are only applicable to selected
|
distribution servers, it is only feasible to generate express download files for
|
||||||
baselines. Finally, calculation of optimal differentials is expensive in terms
|
the most common baselines, thus express updates are only applicable to selected
|
||||||
of system memory utilization, especially for low-cost systems, impacting their
|
baselines. Finally, calculation of optimal differentials is expensive in terms
|
||||||
ability to download and apply an update seamlessly.
|
of system memory utilization, especially for low-cost systems, impacting their
|
||||||
|
ability to download and apply an update seamlessly.
|
||||||
In the following sections, we describe how Windows 10 quality updates will
|
|
||||||
leverage this technique based on forward and reverse differentials for newer
|
In the following sections, we describe how Windows 10 quality updates will
|
||||||
releases of Windows 10 and Windows Server to overcome the challenges with
|
leverage this technique based on forward and reverse differentials for newer
|
||||||
express downloads.
|
releases of Windows 10 and Windows Server to overcome the challenges with
|
||||||
|
express downloads.
|
||||||
## High-level Design
|
|
||||||
|
## High-level Design
|
||||||
### Update packaging
|
|
||||||
|
### Update packaging
|
||||||
Windows 10 quality update packages will contain forward differentials from
|
|
||||||
quality update RTM baselines (∆RTM→N) and reverse differentials back to RTM
|
Windows 10 quality update packages will contain forward differentials from
|
||||||
(∆N→RTM) for each file that has changed since RTM. By using the RTM version as
|
quality update RTM baselines (∆RTM→N) and reverse differentials back to RTM
|
||||||
the baseline, we ensure that all devices will have an identical payload. Update
|
(∆N→RTM) for each file that has changed since RTM. By using the RTM version as
|
||||||
package metadata, content manifests, and forward and reverse differentials will
|
the baseline, we ensure that all devices will have an identical payload. Update
|
||||||
be packaged into a cabinet file (.cab). This .cab file, and the applicability
|
package metadata, content manifests, and forward and reverse differentials will
|
||||||
logic, will also be wrapped in Microsoft Standalone Update (.msu) format.
|
be packaged into a cabinet file (.cab). This .cab file, and the applicability
|
||||||
|
logic, will also be wrapped in Microsoft Standalone Update (.msu) format.
|
||||||
There can be cases where new files are added to the system during servicing.
|
|
||||||
These files will not have RTM baselines, thus forward and reverse differentials
|
There can be cases where new files are added to the system during servicing.
|
||||||
cannot be used. In these scenarios, null differentials will be used to handle
|
These files will not have RTM baselines, thus forward and reverse differentials
|
||||||
servicing. Null differentials are the slightly compressed and optimized version
|
cannot be used. In these scenarios, null differentials will be used to handle
|
||||||
of the full binaries. Update packages can have either
|
servicing. Null differentials are the slightly compressed and optimized version
|
||||||
forward or reverse differentials, or null differential of any given binary in
|
of the full binaries. Update packages can have either
|
||||||
them. The following image symbolizes the content of a Windows 10 quality update installer:
|
forward or reverse differentials, or null differential of any given binary in
|
||||||
|
them. The following image symbolizes the content of a Windows 10 quality update installer:
|
||||||
|
|
||||||
|
|
||||||
### Hydration and installation
|
|
||||||
|
### Hydration and installation
|
||||||
Once the usual applicability checks are performed on the update package and are
|
|
||||||
determined to be applicable, the Windows component servicing infrastructure will
|
Once the usual applicability checks are performed on the update package and are
|
||||||
hydrate the full files during pre-installation and then proceed with the usual
|
determined to be applicable, the Windows component servicing infrastructure will
|
||||||
installation process.
|
hydrate the full files during pre-installation and then proceed with the usual
|
||||||
|
installation process.
|
||||||
Below is a high-level sequence of activities that the component servicing
|
|
||||||
infrastructure will run in a transaction to complete installation of the update:
|
Below is a high-level sequence of activities that the component servicing
|
||||||
|
infrastructure will run in a transaction to complete installation of the update:
|
||||||
- Identify all files that are required to install the update.
|
|
||||||
|
- Identify all files that are required to install the update.
|
||||||
- Hydrate each of necessary files using current version (V<sub>N</sub>) of the file,
|
|
||||||
reverse differential (V<sub>N</sub>--->RTM) of the file back to quality update RTM/base
|
- Hydrate each of necessary files using current version (V<sub>N</sub>) of the file,
|
||||||
version and forward differential (V<sub>RTM</sub>--->R) from feature update RTM/base
|
reverse differential (V<sub>N</sub>--->RTM) of the file back to quality update RTM/base
|
||||||
version to the target version. Also, use null differential hydration to
|
version and forward differential (V<sub>RTM</sub>--->R) from feature update RTM/base
|
||||||
hydrate null compressed files.
|
version to the target version. Also, use null differential hydration to
|
||||||
|
hydrate null compressed files.
|
||||||
- Stage the hydrated files (full file), forward differentials (under ‘f’
|
|
||||||
folder) and reverse differentials (under ‘r’ folder) or null compressed
|
- Stage the hydrated files (full file), forward differentials (under ‘f’
|
||||||
files (under ‘n’ folder) in the component store (%windir%\\WinSxS folder).
|
folder) and reverse differentials (under ‘r’ folder) or null compressed
|
||||||
|
files (under ‘n’ folder) in the component store (%windir%\\WinSxS folder).
|
||||||
- Resolve any dependencies and install components.
|
|
||||||
|
- Resolve any dependencies and install components.
|
||||||
- Clean up older state (V<sub>N-1</sub>); the previous state V<sub>N</sub> is retained for
|
|
||||||
uninstallation and restoration or repair.
|
- Clean up older state (V<sub>N-1</sub>); the previous state V<sub>N</sub> is retained for
|
||||||
|
uninstallation and restoration or repair.
|
||||||
### **Resilient Hydration**
|
|
||||||
|
### **Resilient Hydration**
|
||||||
To ensure resiliency against component store corruption or missing files that
|
|
||||||
could occur due to susceptibility of certain types of hardware to file system
|
To ensure resiliency against component store corruption or missing files that
|
||||||
corruption, a corruption repair service has been traditionally used to recover
|
could occur due to susceptibility of certain types of hardware to file system
|
||||||
the component store automatically (“automatic corruption repair”) or on demand
|
corruption, a corruption repair service has been traditionally used to recover
|
||||||
(“manual corruption repair”) using an online or local repair source. This
|
the component store automatically (“automatic corruption repair”) or on demand
|
||||||
service will continue to offer the ability to repair and recover content for
|
(“manual corruption repair”) using an online or local repair source. This
|
||||||
hydration and successfully install an update, if needed.
|
service will continue to offer the ability to repair and recover content for
|
||||||
|
hydration and successfully install an update, if needed.
|
||||||
When corruption is detected during update operations, automatic corruption
|
|
||||||
repair will start as usual and use the Baseless Patch Storage File published to
|
When corruption is detected during update operations, automatic corruption
|
||||||
Windows Update for each update to fix corrupted manifests, binary differentials,
|
repair will start as usual and use the Baseless Patch Storage File published to
|
||||||
or hydrated or full files. Baseless patch storage files will contain reverse and
|
Windows Update for each update to fix corrupted manifests, binary differentials,
|
||||||
forward differentials and full files for each updated component. Integrity of
|
or hydrated or full files. Baseless patch storage files will contain reverse and
|
||||||
the repair files will be hash verified.
|
forward differentials and full files for each updated component. Integrity of
|
||||||
|
the repair files will be hash verified.
|
||||||
Corruption repair will use the component manifest to detect missing files and
|
|
||||||
get hashes for corruption detection. During update installation, new registry
|
Corruption repair will use the component manifest to detect missing files and
|
||||||
flags for each differential staged on the machine will be set. When automatic
|
get hashes for corruption detection. During update installation, new registry
|
||||||
corruption repair runs, it will scan hydrated files using the manifest and
|
flags for each differential staged on the machine will be set. When automatic
|
||||||
differential files using the flags. If the differential cannot be found or
|
corruption repair runs, it will scan hydrated files using the manifest and
|
||||||
verified, it will be added to the list of corruptions to repair.
|
differential files using the flags. If the differential cannot be found or
|
||||||
|
verified, it will be added to the list of corruptions to repair.
|
||||||
### Lazy automatic corruption repair
|
|
||||||
|
### Lazy automatic corruption repair
|
||||||
“Lazy automatic corruption repair” runs during update operations to detect
|
|
||||||
corrupted binaries and differentials. While applying an update, if hydration of
|
“Lazy automatic corruption repair” runs during update operations to detect
|
||||||
any file fails, "lazy" automatic corruption repair automatically starts,
|
corrupted binaries and differentials. While applying an update, if hydration of
|
||||||
identifies the corrupted binary or differential file, and then adds it to the
|
any file fails, "lazy" automatic corruption repair automatically starts,
|
||||||
corruption list. Later, the update operation continues as far as it can go, so
|
identifies the corrupted binary or differential file, and then adds it to the
|
||||||
that "lazy" automatic corruption repair can collect as many corrupted files to fix
|
corruption list. Later, the update operation continues as far as it can go, so
|
||||||
as possible. At the end of the hydration section, the update fails, and
|
that "lazy" automatic corruption repair can collect as many corrupted files to fix
|
||||||
automatic corruption repair starts. Automatic corruption repair runs as usual
|
as possible. At the end of the hydration section, the update fails, and
|
||||||
and at the end of its operation, adds the corruption list generated by "lazy"
|
automatic corruption repair starts. Automatic corruption repair runs as usual
|
||||||
automatic corruption repair on top of the new list to repair. Automatic
|
and at the end of its operation, adds the corruption list generated by "lazy"
|
||||||
corruption repair then repairs the files on the corruption list and installation
|
automatic corruption repair on top of the new list to repair. Automatic
|
||||||
of the update will succeed on the next attempt.
|
corruption repair then repairs the files on the corruption list and installation
|
||||||
|
of the update will succeed on the next attempt.
|
||||||
|
|||||||
@ -1,74 +1,76 @@
|
|||||||
---
|
---
|
||||||
title: Introduction to the Windows Insider Program for Business
|
title: Introduction to the Windows Insider Program for Business
|
||||||
description: Introduction to the Windows Insider Program for Business and why IT Pros should join it
|
description: Introduction to the Windows Insider Program for Business and why IT Pros should join it
|
||||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, WiP4Biz, enterprise, rings, flight
|
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, WiP4Biz, enterprise, rings, flight
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.audience: itpro
author: greg-lindsay
|
ms.localizationprioauthor: jaimeo
|
||||||
ms.date: 03/01/2018
|
ms.audience: itpro
|
||||||
ms.reviewer:
|
author: jaimeo
|
||||||
manager: laurawi
|
ms.date: 03/01/2018
|
||||||
ms.topic: article
|
ms.reviewer:
|
||||||
---
|
manager: laurawi
|
||||||
|
ms.topic: article
|
||||||
# Introduction to the Windows Insider Program for Business
|
---
|
||||||
|
|
||||||
|
# Introduction to the Windows Insider Program for Business
|
||||||
**Applies to**
|
|
||||||
|
|
||||||
- Windows 10
|
**Applies to**
|
||||||
|
|
||||||
> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
- Windows 10
|
||||||
|
|
||||||
For many IT Pros, it's valuable to have visibility into feature updates early--before they’re available in the Semi-Annual Channel. With Windows 10, feature flighting enables participants in the Windows Insider Preview program can consume and deploy preproduction code to test devices, gaining early visibility into the next build. This is better for your organization because you can test the early builds of Windows 10 to discover possible issues with the code or with device and app compatibility in your organization before the update is ever publicly available. We at Microsoft also appreciate it because Insiders can report issues back to us in time for us to make improvements in a release before it is more generally available.
|
> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||||
|
|
||||||
The Windows Insider Program for Business gives you the opportunity to:
|
For many IT Pros, it's valuable to have visibility into feature updates early--before they’re available in the Semi-Annual Channel. With Windows 10, feature flighting enables participants in the Windows Insider Preview program can consume and deploy preproduction code to test devices, gaining early visibility into the next build. This is better for your organization because you can test the early builds of Windows 10 to discover possible issues with the code or with device and app compatibility in your organization before the update is ever publicly available. We at Microsoft also appreciate it because Insiders can report issues back to us in time for us to make improvements in a release before it is more generally available.
|
||||||
|
|
||||||
* Get early access to Windows Insider Preview Builds.
|
The Windows Insider Program for Business gives you the opportunity to:
|
||||||
* Provide feedback to Microsoft in real time by using the Feedback Hub app.
|
|
||||||
* Sign in with corporate credentials (Azure Active Directory) and increase the visibility of your organization's feedback with Microsoft – especially on features that support your productivity and business needs.
|
* Get early access to Windows Insider Preview Builds.
|
||||||
* Register your Azure Active Directory domain in the program, allowing you to cover all users within your organization with just one registration.
|
* Provide feedback to Microsoft in real time by using the Feedback Hub app.
|
||||||
* Starting with Windows 10, version 1709, enable, disable, defer, and pause the installation of preview builds through policies.
|
* Sign in with corporate credentials (Azure Active Directory) and increase the visibility of your organization's feedback with Microsoft – especially on features that support your productivity and business needs.
|
||||||
* Track feedback provided through the Feedback Hub App across your organization.
|
* Register your Azure Active Directory domain in the program, allowing you to cover all users within your organization with just one registration.
|
||||||
|
* Starting with Windows 10, version 1709, enable, disable, defer, and pause the installation of preview builds through policies.
|
||||||
Microsoft recommends that all organizations have at least a few devices 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.
|
* Track feedback provided through the Feedback Hub App across your organization.
|
||||||
|
|
||||||
The Windows Insider Program doesn't 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.
|
Microsoft recommends that all organizations have at least a few devices 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 doesn't 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.
|
||||||
[](images/WIP4Biz_deployment.png)<br>
|
|
||||||
Windows 10 Insider Preview builds enable organizations to prepare sooner for Windows Semi-Annual releases and reduce the overall validation effort required with traditional deployments.
|
|
||||||
|
[](images/WIP4Biz_deployment.png)<br>
|
||||||
|
Windows 10 Insider Preview builds enable organizations to prepare sooner for Windows Semi-Annual releases and reduce the overall validation effort required with traditional deployments.
|
||||||
## Explore new Windows 10 features in Insider Previews
|
|
||||||
Windows 10 Insider Preview builds offer organizations a valuable and exciting opportunity to evaluate new Windows features well before general release. What’s more, by providing feedback to Microsoft on these features, you and other Insiders in your organization can help shape Windows for your specific business needs. Here’s how to get the most out of your feature exploration:
|
|
||||||
|
## Explore new Windows 10 features in Insider Previews
|
||||||
|Objective |Feature exploration|
|
Windows 10 Insider Preview builds offer organizations a valuable and exciting opportunity to evaluate new Windows features well before general release. What’s more, by providing feedback to Microsoft on these features, you and other Insiders in your organization can help shape Windows for your specific business needs. Here’s how to get the most out of your feature exploration:
|
||||||
|---------|---------|
|
|
||||||
|Release channel |**Fast Ring:** Insider Preview builds in the Fast Ring are released approximately once a week and contain the very latest features. This makes them ideal for feature exploration.|
|
|Objective |Feature exploration|
|
||||||
|Users | Because Fast Ring builds are released so early in the development cycle, we recommend limiting feature exploration in your organization to IT administrators and developers running Insider Preview builds on secondary devices. |
|
|---------|---------|
|
||||||
|Tasks | - Install and manage Insider Preview builds on devices (per device or centrally across multiple devices)<br> - Explore new features in Windows designed for organizations, including new features related to current and planned line of business applications<br> - Before running an Insider Preview build, check our [Windows Insider blog](https://blogs.windows.com/windowsexperience/tag/windows-insider-program/#k3WWwxKCTWHCO82H.97) for a summary of current features. |
|
|Release channel |**Fast Ring:** Insider Preview builds in the Fast Ring are released approximately once a week and contain the very latest features. This makes them ideal for feature exploration.|
|
||||||
|Feedback | - Provide feedback via [Feedback Hub app](insiderhub://home/). This helps us make adjustments to features as quickly as possible.<br> - Encourage users to sign into the Feedback Hub using their AAD work accounts. This enables both you and Microsoft to track feedback submitted by users within your specific organization. (Note: This tracking is only visible to Microsoft and registered Insiders within your organization’s domain.)<br> - [Learn how to provide effective feedback in the Feedback Hub](https://insider.windows.com/en-us/how-to-feedback/) |
|
|Users | Because Fast Ring builds are released so early in the development cycle, we recommend limiting feature exploration in your organization to IT administrators and developers running Insider Preview builds on secondary devices. |
|
||||||
|
|Tasks | - Install and manage Insider Preview builds on devices (per device or centrally across multiple devices)<br> - Explore new features in Windows designed for organizations, including new features related to current and planned line of business applications<br> - Before running an Insider Preview build, check our [Windows Insider blog](https://blogs.windows.com/windowsexperience/tag/windows-insider-program/#k3WWwxKCTWHCO82H.97) for a summary of current features. |
|
||||||
## Validate Insider Preview builds
|
|Feedback | - Provide feedback via [Feedback Hub app](insiderhub://home/). This helps us make adjustments to features as quickly as possible.<br> - Encourage users to sign into the Feedback Hub using their AAD work accounts. This enables both you and Microsoft to track feedback submitted by users within your specific organization. (Note: This tracking is only visible to Microsoft and registered Insiders within your organization’s domain.)<br> - [Learn how to provide effective feedback in the Feedback Hub](https://insider.windows.com/en-us/how-to-feedback/) |
|
||||||
Along with exploring new features, you also have the option to validate your apps and infrastructure on Insider Preview builds. This activity can play an important role in your [Windows 10 deployment strategy](https://docs.microsoft.com/windows/deployment/update/waas-windows-insider-for-business). Early validation has several benefits:
|
|
||||||
|
## Validate Insider Preview builds
|
||||||
- Get a head start on your Windows validation process
|
Along with exploring new features, you also have the option to validate your apps and infrastructure on Insider Preview builds. This activity can play an important role in your [Windows 10 deployment strategy](https://docs.microsoft.com/windows/deployment/update/waas-windows-insider-for-business). Early validation has several benefits:
|
||||||
- Identify issues sooner to accelerate your Windows deployment
|
|
||||||
- Engage Microsoft earlier for help with potential compatibility issues
|
- Get a head start on your Windows validation process
|
||||||
- Deploy Windows 10 Semi-Annual releases faster and more confidently
|
- Identify issues sooner to accelerate your Windows deployment
|
||||||
- Maximize the 18-month support Window that comes with each Semi-Annual release.
|
- Engage Microsoft earlier for help with potential compatibility issues
|
||||||
|
- Deploy Windows 10 Semi-Annual releases faster and more confidently
|
||||||
|
- Maximize the 18-month support Window that comes with each Semi-Annual release.
|
||||||
|
|
||||||
|Objective |Feature exploration|
|
|
||||||
|---------|---------|
|
|
||||||
|Release channel |**Slow Ring:** Insider Preview builds in the Slow Ring are released approximately once a month. They are more stable than Fast Ring releases, making them better suited for validation purposes. Slow Ring releases can be run on either secondary or primary production devices by skilled users.|
|
|Objective |Feature exploration|
|
||||||
|Users | Application and infrastructure validation: In addition to Insiders who might have participated in feature exploration, we also recommend including a small group of application users from each business department to ensure a representative sample.|
|
|---------|---------|
|
||||||
|Tasks | Application and infrastructure validation: Before running an Insider Preview build, check our [Windows Insider blog](https://blogs.windows.com/windowsexperience/tag/windows-insider-program/#k3WWwxKCTWHCO82H.97) and [Windows Insider Tech Community](https://techcommunity.microsoft.com/t5/Windows-Insider-Program/bd-p/WindowsInsiderProgram) pages for updates on current issues and fixes. |
|
|Release channel |**Slow Ring:** Insider Preview builds in the Slow Ring are released approximately once a month. They are more stable than Fast Ring releases, making them better suited for validation purposes. Slow Ring releases can be run on either secondary or primary production devices by skilled users.|
|
||||||
|Feedback | Application and infrastructure validation:Provide feedback in the Feedback Hub app and also inform app vendors of any significant issues. |
|
|Users | Application and infrastructure validation: In addition to Insiders who might have participated in feature exploration, we also recommend including a small group of application users from each business department to ensure a representative sample.|
|
||||||
|Guidance | Application and infrastructure validation:<br>- [Use Upgrade Readiness to create an app inventory and identify mission-critical apps](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-identify-apps)<br>- [Use Device Health to identify problem devices and device drivers](https://docs.microsoft.com/windows/deployment/update/device-health-monitor)<br> - [Windows 10 application compatibility](https://technet.microsoft.com/windows/mt703793)|
|
|Tasks | Application and infrastructure validation: Before running an Insider Preview build, check our [Windows Insider blog](https://blogs.windows.com/windowsexperience/tag/windows-insider-program/#k3WWwxKCTWHCO82H.97) and [Windows Insider Tech Community](https://techcommunity.microsoft.com/t5/Windows-Insider-Program/bd-p/WindowsInsiderProgram) pages for updates on current issues and fixes. |
|
||||||
|
|Feedback | Application and infrastructure validation:Provide feedback in the Feedback Hub app and also inform app vendors of any significant issues. |
|
||||||
|
|Guidance | Application and infrastructure validation:<br>- [Use Upgrade Readiness to create an app inventory and identify mission-critical apps](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-identify-apps)<br>- [Use Device Health to identify problem devices and device drivers](https://docs.microsoft.com/windows/deployment/update/device-health-monitor)<br> - [Windows 10 application compatibility](https://technet.microsoft.com/windows/mt703793)|
|
||||||
|
|
||||||
|
|||||||
@ -1,52 +1,52 @@
|
|||||||
---
|
---
|
||||||
title: Change history for Update Windows 10 (Windows 10)
|
title: Change history for Update Windows 10 (Windows 10)
|
||||||
description: This topic lists new and updated topics in the Update Windows 10 documentation for Windows 10 and Windows 10 Mobile.
|
description: This topic lists new and updated topics in the Update Windows 10 documentation for Windows 10 and Windows 10 Mobile.
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.author: greglin
|
author: jaimeo
|
||||||
ms.date: 09/18/2018
|
ms.author: jaimeo
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
---
|
---
|
||||||
|
|
||||||
# Change history for Update Windows 10
|
# Change history for Update Windows 10
|
||||||
|
|
||||||
This topic lists new and updated topics in the [Update Windows 10](index.md) documentation for [Deploy and Update Windows 10](https://docs.microsoft.com/windows/deployment).
|
This topic lists new and updated topics in the [Update Windows 10](index.md) documentation for [Deploy and Update Windows 10](https://docs.microsoft.com/windows/deployment).
|
||||||
|
|
||||||
>If you're looking for **update history** for Windows 10, see [Windows 10 and Windows Server 2016 update history](https://support.microsoft.com/help/12387/windows-10-update-history).
|
>If you're looking for **update history** for Windows 10, see [Windows 10 and Windows Server 2016 update history](https://support.microsoft.com/help/12387/windows-10-update-history).
|
||||||
|
|
||||||
## September 2018
|
## September 2018
|
||||||
|
|
||||||
| New or changed topic | Description |
|
| New or changed topic | Description |
|
||||||
| --- | --- |
|
| --- | --- |
|
||||||
| [Get started with Windows Update](windows-update-overview.md) | New |
|
| [Get started with Windows Update](windows-update-overview.md) | New |
|
||||||
|
|
||||||
|
|
||||||
## RELEASE: Windows 10, version 1709
|
## RELEASE: Windows 10, version 1709
|
||||||
|
|
||||||
The topics in this library have been updated for Windows 10, version 1709 (also known as the Fall Creators Update).
|
The topics in this library have been updated for Windows 10, version 1709 (also known as the Fall Creators Update).
|
||||||
|
|
||||||
## September 2017
|
## September 2017
|
||||||
|
|
||||||
| New or changed topic | Description |
|
| New or changed topic | Description |
|
||||||
| --- | --- |
|
| --- | --- |
|
||||||
| [Olympia Corp](olympia/olympia-enrollment-guidelines.md) | New |
|
| [Olympia Corp](olympia/olympia-enrollment-guidelines.md) | New |
|
||||||
|
|
||||||
## July 2017
|
## July 2017
|
||||||
|
|
||||||
All topics were updated to reflect the new [naming changes](waas-overview.md#naming-changes).
|
All topics were updated to reflect the new [naming changes](waas-overview.md#naming-changes).
|
||||||
|
|
||||||
## May 2017
|
## May 2017
|
||||||
|
|
||||||
| New or changed topic | Description |
|
| New or changed topic | Description |
|
||||||
| --- | --- |
|
| --- | --- |
|
||||||
| [Manage additional Windows Update settings](waas-wu-settings.md) | New |
|
| [Manage additional Windows Update settings](waas-wu-settings.md) | New |
|
||||||
|
|
||||||
## RELEASE: Windows 10, version 1703
|
## RELEASE: Windows 10, version 1703
|
||||||
|
|
||||||
The topics in this library have been updated for Windows 10, version 1703 (also known as the Creators Update). The following new topics have been added:
|
The topics in this library have been updated for Windows 10, version 1703 (also known as the Creators Update). The following new topics have been added:
|
||||||
* [Windows Insider Program for Business](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-get-started)
|
* [Windows Insider Program for Business](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-get-started)
|
||||||
* [Windows Insider Program for Business](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-register)
|
* [Windows Insider Program for Business](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-register)
|
||||||
|
|||||||
@ -1,24 +1,25 @@
|
|||||||
---
|
---
|
||||||
title: Best practices for feature updates - conclusion
|
title: Best practices for feature updates - conclusion
|
||||||
description: Final thoughts about how to deploy feature updates
|
description: Final thoughts about how to deploy feature updates
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.author: greglin
|
ms.localizationpriority: medium
|
||||||
ms.date: 07/09/2018
|
ms.author: jaimeo
|
||||||
ms.reviewer:
|
ms.date: 07/09/2018
|
||||||
manager: laurawi
|
ms.reviewer:
|
||||||
ms.collection: M365-modern-desktop
|
manager: laurawi
|
||||||
ms.topic: article
|
ms.collection: M365-modern-desktop
|
||||||
---
|
ms.topic: article
|
||||||
|
---
|
||||||
# Conclusion
|
|
||||||
|
# Conclusion
|
||||||
**Applies to**: Windows 10
|
|
||||||
|
**Applies to**: Windows 10
|
||||||
Mission critical devices that need to be online 24x7 pose unique challenges for the IT Pro looking to stay current with the latest Windows 10 feature update. Because these devices are online continually, providing mission critical services, with only a small window of time available to apply feature updates, specific procedures are required to effectively keep these devices current, with as little downtime as possible.
|
|
||||||
|
Mission critical devices that need to be online 24x7 pose unique challenges for the IT Pro looking to stay current with the latest Windows 10 feature update. Because these devices are online continually, providing mission critical services, with only a small window of time available to apply feature updates, specific procedures are required to effectively keep these devices current, with as little downtime as possible.
|
||||||
Whether you have defined servicing windows at your disposal where feature updates can be installed automatically, or you require user initiated installs by a technician, this whitepaper provides guidelines for either approach. Improvements are continually being made to Windows 10 setup to reduce device offline time for feature updates. This whitepaper will be updated as enhancements become available to improve the overall servicing approach and experience.
|
|
||||||
|
Whether you have defined servicing windows at your disposal where feature updates can be installed automatically, or you require user initiated installs by a technician, this whitepaper provides guidelines for either approach. Improvements are continually being made to Windows 10 setup to reduce device offline time for feature updates. This whitepaper will be updated as enhancements become available to improve the overall servicing approach and experience.
|
||||||
|
|
||||||
|
|||||||
@ -1,261 +1,262 @@
|
|||||||
---
|
---
|
||||||
title: Best practices - deploy feature updates during maintenance windows
|
title: Best practices - deploy feature updates during maintenance windows
|
||||||
description: Learn how to deploy feature updates during a maintenance window
|
description: Learn how to deploy feature updates during a maintenance window
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.author: greglin
|
ms.localizationpriority: medium
|
||||||
ms.date: 07/09/2018
|
ms.author: jaimeo
|
||||||
ms.reviewer:
|
ms.date: 07/09/2018
|
||||||
manager: laurawi
|
ms.reviewer:
|
||||||
ms.collection: M365-modern-desktop
|
manager: laurawi
|
||||||
ms.topic: article
|
ms.collection: M365-modern-desktop
|
||||||
---
|
ms.topic: article
|
||||||
|
---
|
||||||
# Deploy feature updates during maintenance windows
|
|
||||||
|
# Deploy feature updates during maintenance windows
|
||||||
**Applies to**: Windows 10
|
|
||||||
|
**Applies to**: Windows 10
|
||||||
Use the following information to deploy feature updates during a maintenance window.
|
|
||||||
|
Use the following information to deploy feature updates during a maintenance window.
|
||||||
## Get ready to deploy feature updates
|
|
||||||
|
## Get ready to deploy feature updates
|
||||||
### Step 1: Configure maintenance windows
|
|
||||||
|
### Step 1: Configure maintenance windows
|
||||||
1. In the Configuration Manager console, choose **Assets and Compliance> Device Collections**.
|
|
||||||
2. In the **Device Collections** list, select the collection for which you intended to deploy the feature update(s).
|
1. In the Configuration Manager console, choose **Assets and Compliance> Device Collections**.
|
||||||
3. On the **Home** tab, in the **Properties** group, choose **Properties**.
|
2. In the **Device Collections** list, select the collection for which you intended to deploy the feature update(s).
|
||||||
4. In the **Maintenance Windows** tab of the `<collection name>` Properties dialog box, choose the New icon.
|
3. On the **Home** tab, in the **Properties** group, choose **Properties**.
|
||||||
5. Complete the `<new>` Schedule dialog.
|
4. In the **Maintenance Windows** tab of the `<collection name>` Properties dialog box, choose the New icon.
|
||||||
6. Select from the Apply this schedule to drop-down list.
|
5. Complete the `<new>` Schedule dialog.
|
||||||
7. Choose **OK** and then close the **\<collection name\> Properties** dialog box.
|
6. Select from the Apply this schedule to drop-down list.
|
||||||
|
7. Choose **OK** and then close the **\<collection name\> Properties** dialog box.
|
||||||
### Step 2: Review computer restart device settings
|
|
||||||
|
### Step 2: Review computer restart device settings
|
||||||
If you’re not suppressing computer restarts and the feature update will be installed when no users are present, consider deploying a custom client settings policy to your feature update target collection to shorten the settings below or consider the total duration of these settings when defining your maintenance window duration.
|
|
||||||
|
If you’re not suppressing computer restarts and the feature update will be installed when no users are present, consider deploying a custom client settings policy to your feature update target collection to shorten the settings below or consider the total duration of these settings when defining your maintenance window duration.
|
||||||
For example, by default, 90 minutes will be honored before the system is rebooted after the feature update install. If users will not be impacted by the user logoff or restart, there is no need to wait a full 90 minutes before rebooting the computer. If a delay and notification is needed, ensure that the maintenance window takes this into account along with the total time needed to install the feature update.
|
|
||||||
|
For example, by default, 90 minutes will be honored before the system is rebooted after the feature update install. If users will not be impacted by the user logoff or restart, there is no need to wait a full 90 minutes before rebooting the computer. If a delay and notification is needed, ensure that the maintenance window takes this into account along with the total time needed to install the feature update.
|
||||||
>[!NOTE]
|
|
||||||
> The following settings must be shorter in duration than the shortest maintenance window applied to the computer.
|
>[!NOTE]
|
||||||
>- **Display a temporary notification to the user that indicates the interval before the user is logged off or the computer restarts (minutes).**
|
> The following settings must be shorter in duration than the shortest maintenance window applied to the computer.
|
||||||
>- **Display a dialog box that the user cannot close, which displays the countdown interval before the user is logged off or the computer restarts (minutes).**
|
>- **Display a temporary notification to the user that indicates the interval before the user is logged off or the computer restarts (minutes).**
|
||||||
|
>- **Display a dialog box that the user cannot close, which displays the countdown interval before the user is logged off or the computer restarts (minutes).**
|
||||||
### Step 3: Enable Peer Cache
|
|
||||||
|
### Step 3: Enable Peer Cache
|
||||||
Use **Peer Cache** to help manage deployment of content to clients in remote locations. Peer Cache is a built-in Configuration Manager solution that enables clients to share content with other clients directly from their local cache.
|
|
||||||
|
Use **Peer Cache** to help manage deployment of content to clients in remote locations. Peer Cache is a built-in Configuration Manager solution that enables clients to share content with other clients directly from their local cache.
|
||||||
[Enable Configuration Manager client in full OS to share content](https://docs.microsoft.com/sccm/core/clients/deploy/about-client-settings#enable-configuration-manager-client-in-full-os-to-share-content) if you have clients in remote locations that would benefit from downloading feature update content from a peer instead of downloading it from a distribution point (or Microsoft Update).
|
|
||||||
|
[Enable Configuration Manager client in full OS to share content](https://docs.microsoft.com/sccm/core/clients/deploy/about-client-settings#enable-configuration-manager-client-in-full-os-to-share-content) if you have clients in remote locations that would benefit from downloading feature update content from a peer instead of downloading it from a distribution point (or Microsoft Update).
|
||||||
### Step 4: Override the default Windows setup priority (Windows 10, version 1709 and later)
|
|
||||||
|
### Step 4: Override the default Windows setup priority (Windows 10, version 1709 and later)
|
||||||
If you’re deploying **Feature update to Windows 10, version 1709** or later, by default, portions of setup are configured to run at a lower priority. This can result in a longer total install time for the feature update. When deploying within a maintenance window, we recommend that you override this default behavior to benefit from faster total install times. To override the default priority, create a file called SetupConfig.ini on each machine to be upgraded in the below location containing the single section noted.
|
|
||||||
|
If you’re deploying **Feature update to Windows 10, version 1709** or later, by default, portions of setup are configured to run at a lower priority. This can result in a longer total install time for the feature update. When deploying within a maintenance window, we recommend that you override this default behavior to benefit from faster total install times. To override the default priority, create a file called SetupConfig.ini on each machine to be upgraded in the below location containing the single section noted.
|
||||||
%systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini
|
|
||||||
|
%systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini
|
||||||
```
|
|
||||||
[SetupConfig]
|
```
|
||||||
Priority=Normal
|
[SetupConfig]
|
||||||
```
|
Priority=Normal
|
||||||
|
```
|
||||||
You can use the new [Run Scripts](https://docs.microsoft.com/sccm/apps/deploy-use/create-deploy-scripts) feature to run a PowerShell script like the sample below to create the SetupConfig.ini on target devices.
|
|
||||||
|
You can use the new [Run Scripts](https://docs.microsoft.com/sccm/apps/deploy-use/create-deploy-scripts) feature to run a PowerShell script like the sample below to create the SetupConfig.ini on target devices.
|
||||||
```
|
|
||||||
#Parameters
|
```
|
||||||
Param(
|
#Parameters
|
||||||
[string] $PriorityValue = "Normal"
|
Param(
|
||||||
)
|
[string] $PriorityValue = "Normal"
|
||||||
|
)
|
||||||
#Variable for ini file path
|
|
||||||
$iniFilePath = "$env:SystemDrive\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini"
|
#Variable for ini file path
|
||||||
|
$iniFilePath = "$env:SystemDrive\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini"
|
||||||
#Variables for SetupConfig
|
|
||||||
$iniSetupConfigSlogan = "[SetupConfig]"
|
#Variables for SetupConfig
|
||||||
$iniSetupConfigKeyValuePair =@{"Priority"=$PriorityValue;}
|
$iniSetupConfigSlogan = "[SetupConfig]"
|
||||||
|
$iniSetupConfigKeyValuePair =@{"Priority"=$PriorityValue;}
|
||||||
#Init SetupConfig content
|
|
||||||
$iniSetupConfigContent = @"
|
#Init SetupConfig content
|
||||||
$iniSetupConfigSlogan
|
$iniSetupConfigContent = @"
|
||||||
"@
|
$iniSetupConfigSlogan
|
||||||
|
"@
|
||||||
#Build SetupConfig content with settings
|
|
||||||
foreach ($k in $iniSetupConfigKeyValuePair.Keys)
|
#Build SetupConfig content with settings
|
||||||
{
|
foreach ($k in $iniSetupConfigKeyValuePair.Keys)
|
||||||
$val = $iniSetupConfigKeyValuePair[$k]
|
{
|
||||||
|
$val = $iniSetupConfigKeyValuePair[$k]
|
||||||
$iniSetupConfigContent = $iniSetupConfigContent.Insert($iniSetupConfigContent.Length, "`r`n$k=$val")
|
|
||||||
}
|
$iniSetupConfigContent = $iniSetupConfigContent.Insert($iniSetupConfigContent.Length, "`r`n$k=$val")
|
||||||
|
}
|
||||||
#Write content to file
|
|
||||||
New-Item $iniFilePath -ItemType File -Value $iniSetupConfigContent -Force
|
#Write content to file
|
||||||
|
New-Item $iniFilePath -ItemType File -Value $iniSetupConfigContent -Force
|
||||||
Disclaimer
|
|
||||||
Sample scripts are not supported under any Microsoft standard support program or service. The sample scripts is
|
Disclaimer
|
||||||
provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without
|
Sample scripts are not supported under any Microsoft standard support program or service. The sample scripts is
|
||||||
limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk
|
provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without
|
||||||
arising out of the use or performance of the sample script and documentation remains with you. In no event shall
|
limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk
|
||||||
Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable
|
arising out of the use or performance of the sample script and documentation remains with you. In no event shall
|
||||||
for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption,
|
Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable
|
||||||
loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample script
|
for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption,
|
||||||
or documentation, even if Microsoft has been advised of the possibility of such damages.
|
loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample script
|
||||||
```
|
or documentation, even if Microsoft has been advised of the possibility of such damages.
|
||||||
|
```
|
||||||
>[!NOTE]
|
|
||||||
>If you elect not to override the default setup priority, you will need to increase the [maximum run time](https://docs.microsoft.com/sccm/sum/get-started/manage-settings-for-software-updates#BKMK_SetMaxRunTime) value for Feature Update to Windows 10, version 1709 or higher from the default of 60 minutes. A value of 240 minutes may be required. Remember to ensure that your maintenance window duration is larger than your defined maximum run time value.
|
>[!NOTE]
|
||||||
|
>If you elect not to override the default setup priority, you will need to increase the [maximum run time](https://docs.microsoft.com/sccm/sum/get-started/manage-settings-for-software-updates#BKMK_SetMaxRunTime) value for Feature Update to Windows 10, version 1709 or higher from the default of 60 minutes. A value of 240 minutes may be required. Remember to ensure that your maintenance window duration is larger than your defined maximum run time value.
|
||||||
## Manually deploy feature updates
|
|
||||||
|
## Manually deploy feature updates
|
||||||
The following sections provide the steps to manually deploy a feature update.
|
|
||||||
|
The following sections provide the steps to manually deploy a feature update.
|
||||||
### Step 1: Specify search criteria for feature updates
|
|
||||||
There are potentially a thousand or more feature updates displayed in the Configuration Manager console. The first step in the workflow for manually deploying feature updates is to identify the feature updates that you want to deploy.
|
### Step 1: Specify search criteria for feature updates
|
||||||
|
There are potentially a thousand or more feature updates displayed in the Configuration Manager console. The first step in the workflow for manually deploying feature updates is to identify the feature updates that you want to deploy.
|
||||||
1. In the Configuration Manager console, click **Software Library**.
|
|
||||||
2. In the Software Library workspace, expand **Windows 10 Servicing**, and click **All Windows 10 Updates**. The synchronized feature updates are displayed.
|
1. In the Configuration Manager console, click **Software Library**.
|
||||||
3. In the search pane, filter to identify the feature updates that you need by using one or both of the following steps:
|
2. In the Software Library workspace, expand **Windows 10 Servicing**, and click **All Windows 10 Updates**. The synchronized feature updates are displayed.
|
||||||
- In the search text box, type a search string that will filter the feature updates. For example, type the version number for a specific feature update, or enter a string that would appear in the title of the feature update.
|
3. In the search pane, filter to identify the feature updates that you need by using one or both of the following steps:
|
||||||
- Click **Add Criteria**, select the criteria that you want to use to filter software updates, click **Add**, and then provide the values for the criteria. For example, Title contains 1803, Required is greater than or equal to 1, and Language equals English.
|
- In the search text box, type a search string that will filter the feature updates. For example, type the version number for a specific feature update, or enter a string that would appear in the title of the feature update.
|
||||||
|
- Click **Add Criteria**, select the criteria that you want to use to filter software updates, click **Add**, and then provide the values for the criteria. For example, Title contains 1803, Required is greater than or equal to 1, and Language equals English.
|
||||||
4. Save the search for future use.
|
|
||||||
|
4. Save the search for future use.
|
||||||
### Step 2: Download the content for the feature update(s)
|
|
||||||
Before you deploy the feature updates, you can download the content as a separate step. Do this so you can verify that the content is available on the distribution points before you deploy the feature updates. This will help you to avoid any unexpected issues with the content delivery. Use the following procedure to download the content for feature updates before creating the deployment.
|
### Step 2: Download the content for the feature update(s)
|
||||||
|
Before you deploy the feature updates, you can download the content as a separate step. Do this so you can verify that the content is available on the distribution points before you deploy the feature updates. This will help you to avoid any unexpected issues with the content delivery. Use the following procedure to download the content for feature updates before creating the deployment.
|
||||||
1. In the Configuration Manager console, navigate to **Software Library > Windows 10 Servicing**.
|
|
||||||
2. Choose the feature update(s) to download by using your saved search criteria. Select one or more of the feature updates returned, right click, and select Download.
|
1. In the Configuration Manager console, navigate to **Software Library > Windows 10 Servicing**.
|
||||||
|
2. Choose the feature update(s) to download by using your saved search criteria. Select one or more of the feature updates returned, right click, and select Download.
|
||||||
The **Download Software Updates Wizard** opens.
|
|
||||||
3. On the **Deployment Package** page, configure the following settings:
|
The **Download Software Updates Wizard** opens.
|
||||||
**Create a new deployment package**: Select this setting to create a new deployment package for the software updates that are in the deployment. Configure the following settings:
|
3. On the **Deployment Package** page, configure the following settings:
|
||||||
- **Name**: Specifies the name of the deployment package. The package must have a unique name that briefly describes the package content. It is limited to 50 characters.
|
**Create a new deployment package**: Select this setting to create a new deployment package for the software updates that are in the deployment. Configure the following settings:
|
||||||
- **Description**: Specifies the description of the deployment package. The package description provides information about the package contents and is limited to 127 characters.
|
- **Name**: Specifies the name of the deployment package. The package must have a unique name that briefly describes the package content. It is limited to 50 characters.
|
||||||
- **Package source**: Specifies the location of the feature update source files. Type a network path for the source location, for example, \\server\sharename\path, or click **Browse** to find the network location. You must create the shared folder for the deployment package source files before you proceed to the next page.
|
- **Description**: Specifies the description of the deployment package. The package description provides information about the package contents and is limited to 127 characters.
|
||||||
|
- **Package source**: Specifies the location of the feature update source files. Type a network path for the source location, for example, \\server\sharename\path, or click **Browse** to find the network location. You must create the shared folder for the deployment package source files before you proceed to the next page.
|
||||||
>[!NOTE]
|
|
||||||
>The deployment package source location that you specify cannot be used by another software deployment package.
|
>[!NOTE]
|
||||||
|
>The deployment package source location that you specify cannot be used by another software deployment package.
|
||||||
>[!IMPORTANT]
|
|
||||||
>The SMS Provider computer account and the user that is running the wizard to download the feature updates must both have Write NTFS permissions on the download location. You should carefully restrict access to the download location to reduce the risk of attackers tampering with the feature update source files.
|
>[!IMPORTANT]
|
||||||
|
>The SMS Provider computer account and the user that is running the wizard to download the feature updates must both have Write NTFS permissions on the download location. You should carefully restrict access to the download location to reduce the risk of attackers tampering with the feature update source files.
|
||||||
>[!IMPORTANT]
|
|
||||||
>You can change the package source location in the deployment package properties after Configuration Manager creates the deployment package. But if you do so, you must first copy the content from the original package source to the new package source location.
|
>[!IMPORTANT]
|
||||||
|
>You can change the package source location in the deployment package properties after Configuration Manager creates the deployment package. But if you do so, you must first copy the content from the original package source to the new package source location.
|
||||||
Click **Next**.
|
|
||||||
4. On the **Distribution Points** page, specify the distribution points or distribution point groups that will host the feature update files, and then click **Next**. For more information about distribution points, see [Distribution point configurations](https://docs.microsoft.com/sccm/core/servers/deploy/configure/install-and-configure-distribution-points#bkmk_configs).
|
Click **Next**.
|
||||||
|
4. On the **Distribution Points** page, specify the distribution points or distribution point groups that will host the feature update files, and then click **Next**. For more information about distribution points, see [Distribution point configurations](https://docs.microsoft.com/sccm/core/servers/deploy/configure/install-and-configure-distribution-points#bkmk_configs).
|
||||||
>[!NOTE]
|
|
||||||
>The Distribution Points page is available only when you create a new software update deployment package.
|
>[!NOTE]
|
||||||
5. On the **Distribution Settings** page, specify the following settings:
|
>The Distribution Points page is available only when you create a new software update deployment package.
|
||||||
|
5. On the **Distribution Settings** page, specify the following settings:
|
||||||
- **Distribution priority**: Use this setting to specify the distribution priority for the deployment package. The distribution priority applies when the deployment package is sent to distribution points at child sites. Deployment packages are sent in priority order: High, Medium, or Low. Packages with identical priorities are sent in the order in which they were created. If there is no backlog, the package will process immediately regardless of its priority. By default, packages are sent using Medium priority.
|
|
||||||
- **Enable for on-demand distribution**: Use this setting to enable on-demand content distribution to preferred distribution points. When this setting is enabled, the management point creates a trigger for the distribution manager to distribute the content to all preferred distribution points when a client requests the content for the package and the content is not available on any preferred distribution points. For more information about preferred distribution points and on-demand content, see [Content source location scenarios](https://docs.microsoft.com/sccm/core/plan-design/hierarchy/content-source-location-scenarios).
|
- **Distribution priority**: Use this setting to specify the distribution priority for the deployment package. The distribution priority applies when the deployment package is sent to distribution points at child sites. Deployment packages are sent in priority order: High, Medium, or Low. Packages with identical priorities are sent in the order in which they were created. If there is no backlog, the package will process immediately regardless of its priority. By default, packages are sent using Medium priority.
|
||||||
- **Prestaged distribution point settings**: Use this setting to specify how you want to distribute content to prestaged distribution points. Choose one of the following options:
|
- **Enable for on-demand distribution**: Use this setting to enable on-demand content distribution to preferred distribution points. When this setting is enabled, the management point creates a trigger for the distribution manager to distribute the content to all preferred distribution points when a client requests the content for the package and the content is not available on any preferred distribution points. For more information about preferred distribution points and on-demand content, see [Content source location scenarios](https://docs.microsoft.com/sccm/core/plan-design/hierarchy/content-source-location-scenarios).
|
||||||
- **Automatically download content when packages are assigned to distribution points**: Use this setting to ignore the prestage settings and distribute content to the distribution point.
|
- **Prestaged distribution point settings**: Use this setting to specify how you want to distribute content to prestaged distribution points. Choose one of the following options:
|
||||||
- **Download only content changes to the distribution point**: Use this setting to prestage the initial content to the distribution point, and then distribute content changes to the distribution point.
|
- **Automatically download content when packages are assigned to distribution points**: Use this setting to ignore the prestage settings and distribute content to the distribution point.
|
||||||
- **Manually copy the content in this package to the distribution point**: Use this setting to always prestage content on the distribution point. This is the default setting.
|
- **Download only content changes to the distribution point**: Use this setting to prestage the initial content to the distribution point, and then distribute content changes to the distribution point.
|
||||||
|
- **Manually copy the content in this package to the distribution point**: Use this setting to always prestage content on the distribution point. This is the default setting.
|
||||||
For more information about prestaging content to distribution points, see [Use Prestaged content](https://docs.microsoft.com/sccm/core/servers/deploy/configure/deploy-and-manage-content#bkmk_prestage).
|
|
||||||
Click **Next**.
|
For more information about prestaging content to distribution points, see [Use Prestaged content](https://docs.microsoft.com/sccm/core/servers/deploy/configure/deploy-and-manage-content#bkmk_prestage).
|
||||||
6. On the **Download Location** page, specify location that Configuration Manager will use to download the software update source files. As needed, use the following options:
|
Click **Next**.
|
||||||
|
6. On the **Download Location** page, specify location that Configuration Manager will use to download the software update source files. As needed, use the following options:
|
||||||
- **Download software updates from the Internet**: Select this setting to download the software updates from the location on the Internet. This is the default setting.
|
|
||||||
- **Download software updates from a location on the local network**: Select this setting to download software updates from a local folder or shared network folder. Use this setting when the computer running the wizard does not have Internet access.
|
- **Download software updates from the Internet**: Select this setting to download the software updates from the location on the Internet. This is the default setting.
|
||||||
|
- **Download software updates from a location on the local network**: Select this setting to download software updates from a local folder or shared network folder. Use this setting when the computer running the wizard does not have Internet access.
|
||||||
>[!NOTE]
|
|
||||||
>When you use this setting, download the software updates from any computer with Internet access, and then copy the software updates to a location on the local network that is accessible from the computer running the wizard.
|
>[!NOTE]
|
||||||
|
>When you use this setting, download the software updates from any computer with Internet access, and then copy the software updates to a location on the local network that is accessible from the computer running the wizard.
|
||||||
Click **Next**.
|
|
||||||
7. On the **Language Selection** page, specify the languages for which the selected feature updates are to be downloaded, and then click **Next**. Ensure that your language selection matches the language(s) of the feature updates selected for download. For example, if you selected English and German based feature updates for download, select those same languages on the language selection page.
|
Click **Next**.
|
||||||
8. On the **Summary** page, verify the settings that you selected in the wizard, and then click Next to download the software updates.
|
7. On the **Language Selection** page, specify the languages for which the selected feature updates are to be downloaded, and then click **Next**. Ensure that your language selection matches the language(s) of the feature updates selected for download. For example, if you selected English and German based feature updates for download, select those same languages on the language selection page.
|
||||||
9. On the **Completion** page, verify that the software updates were successfully downloaded, and then click Close.
|
8. On the **Summary** page, verify the settings that you selected in the wizard, and then click Next to download the software updates.
|
||||||
|
9. On the **Completion** page, verify that the software updates were successfully downloaded, and then click Close.
|
||||||
#### To monitor content status
|
|
||||||
1. To monitor the content status for the feature updates, click **Monitoring** in the Configuration Manager console.
|
#### To monitor content status
|
||||||
2. In the Monitoring workspace, expand **Distribution Status**, and then click **Content Status**.
|
1. To monitor the content status for the feature updates, click **Monitoring** in the Configuration Manager console.
|
||||||
3. Select the feature update package that you previously identified to download the feature updates.
|
2. In the Monitoring workspace, expand **Distribution Status**, and then click **Content Status**.
|
||||||
4. On the **Home** tab, in the Content group, click **View Status**.
|
3. Select the feature update package that you previously identified to download the feature updates.
|
||||||
|
4. On the **Home** tab, in the Content group, click **View Status**.
|
||||||
### Step 3: Deploy the feature update(s)
|
|
||||||
After you determine which feature updates you intend to deploy, you can manually deploy the feature update(s). Use the following procedure to manually deploy the feature update(s).
|
### Step 3: Deploy the feature update(s)
|
||||||
|
After you determine which feature updates you intend to deploy, you can manually deploy the feature update(s). Use the following procedure to manually deploy the feature update(s).
|
||||||
1. In the Configuration Manager console, click **Software Library**.
|
|
||||||
2. In the Software Library workspace, expand **Windows 10 Servicing**, and click **All Windows 10 Updates**.
|
1. In the Configuration Manager console, click **Software Library**.
|
||||||
3. Choose the feature update(s) to deploy by using your saved search criteria. Select one or more of the feature updates returned, right click, and select **Deploy**.
|
2. In the Software Library workspace, expand **Windows 10 Servicing**, and click **All Windows 10 Updates**.
|
||||||
|
3. Choose the feature update(s) to deploy by using your saved search criteria. Select one or more of the feature updates returned, right click, and select **Deploy**.
|
||||||
The **Deploy Software Updates Wizard** opens.
|
|
||||||
4. On the General page, configure the following settings:
|
The **Deploy Software Updates Wizard** opens.
|
||||||
- **Name**: Specify the name for the deployment. The deployment must have a unique name that describes the purpose of the deployment and differentiates it from other deployments in the Configuration Manager site. By default, Configuration Manager automatically provides a name for the deployment in the following format: **Microsoft Software Updates - \<date\>\<time\>**
|
4. On the General page, configure the following settings:
|
||||||
- **Description**: Specify a description for the deployment. The description provides an overview of the deployment and any other relevant information that helps to identify and differentiate the deployment among others in Configuration Manager site. The description field is optional, has a limit of 256 characters, and has a blank value by default.
|
- **Name**: Specify the name for the deployment. The deployment must have a unique name that describes the purpose of the deployment and differentiates it from other deployments in the Configuration Manager site. By default, Configuration Manager automatically provides a name for the deployment in the following format: **Microsoft Software Updates - \<date\>\<time\>**
|
||||||
- **Software Update/Software Update Group**: Verify that the displayed software update group, or software update, is correct.
|
- **Description**: Specify a description for the deployment. The description provides an overview of the deployment and any other relevant information that helps to identify and differentiate the deployment among others in Configuration Manager site. The description field is optional, has a limit of 256 characters, and has a blank value by default.
|
||||||
- **Select Deployment Template**: Specify whether to apply a previously saved deployment template. You can configure a deployment template to contain multiple common software update deployment properties and then apply the template when you deploy subsequent software updates to ensure consistency across similar deployments and to save time.
|
- **Software Update/Software Update Group**: Verify that the displayed software update group, or software update, is correct.
|
||||||
- **Collection**: Specify the collection for the deployment, as applicable. Members of the collection receive the feature updates that are defined in the deployment.
|
- **Select Deployment Template**: Specify whether to apply a previously saved deployment template. You can configure a deployment template to contain multiple common software update deployment properties and then apply the template when you deploy subsequent software updates to ensure consistency across similar deployments and to save time.
|
||||||
5. On the Deployment Settings page, configure the following settings:
|
- **Collection**: Specify the collection for the deployment, as applicable. Members of the collection receive the feature updates that are defined in the deployment.
|
||||||
|
5. On the Deployment Settings page, configure the following settings:
|
||||||
- **Type of deployment**: Specify the deployment type for the software update deployment. Select **Required** to create a mandatory software update deployment in which the feature updates are automatically installed on clients before a configured installation deadline.
|
|
||||||
|
- **Type of deployment**: Specify the deployment type for the software update deployment. Select **Required** to create a mandatory software update deployment in which the feature updates are automatically installed on clients before a configured installation deadline.
|
||||||
>[!IMPORTANT]
|
|
||||||
> After you create the software update deployment, you cannot later change the type of deployment.
|
>[!IMPORTANT]
|
||||||
|
> After you create the software update deployment, you cannot later change the type of deployment.
|
||||||
>[!NOTE]
|
|
||||||
>A software update group deployed as Required will be downloaded in background and honor BITS settings, if configured.
|
>[!NOTE]
|
||||||
|
>A software update group deployed as Required will be downloaded in background and honor BITS settings, if configured.
|
||||||
- **Use Wake-on-LAN to wake up clients for required deployments**: Specify whether to enable Wake On LAN at the deadline to send wake-up packets to computers that require one or more software updates in the deployment. Any computers that are in sleep mode at the installation deadline time will be awakened so the software update installation can initiate. Clients that are in sleep mode that do not require any software updates in the deployment are not started. By default, this setting is not enabled and is available only when Type of deployment is set to Required.
|
|
||||||
|
- **Use Wake-on-LAN to wake up clients for required deployments**: Specify whether to enable Wake On LAN at the deadline to send wake-up packets to computers that require one or more software updates in the deployment. Any computers that are in sleep mode at the installation deadline time will be awakened so the software update installation can initiate. Clients that are in sleep mode that do not require any software updates in the deployment are not started. By default, this setting is not enabled and is available only when Type of deployment is set to Required.
|
||||||
>[!WARNING]
|
|
||||||
>Before you can use this option, computers and networks must be configured for Wake On LAN.
|
>[!WARNING]
|
||||||
|
>Before you can use this option, computers and networks must be configured for Wake On LAN.
|
||||||
- **Detail level**: Specify the level of detail for the state messages that are reported by client computers.
|
|
||||||
6. On the Scheduling page, configure the following settings:
|
- **Detail level**: Specify the level of detail for the state messages that are reported by client computers.
|
||||||
|
6. On the Scheduling page, configure the following settings:
|
||||||
- **Schedule evaluation**: Specify whether the available time and installation deadline times are evaluated according to UTC or the local time of the computer running the Configuration Manager console.
|
|
||||||
|
- **Schedule evaluation**: Specify whether the available time and installation deadline times are evaluated according to UTC or the local time of the computer running the Configuration Manager console.
|
||||||
>[!NOTE]
|
|
||||||
>When you select local time, and then select **As soon as possible** for the **Software available time** or **Installation deadline**, the current time on the computer running the Configuration Manager console is used to evaluate when updates are available or when they are installed on a client. If the client is in a different time zone, these actions will occur when the client's time reaches the evaluation time.
|
>[!NOTE]
|
||||||
|
>When you select local time, and then select **As soon as possible** for the **Software available time** or **Installation deadline**, the current time on the computer running the Configuration Manager console is used to evaluate when updates are available or when they are installed on a client. If the client is in a different time zone, these actions will occur when the client's time reaches the evaluation time.
|
||||||
- **Software available time**: Select **As soon as possible** to specify when the software updates will be available to clients:
|
|
||||||
- **As soon as possible**: Select this setting to make the software updates in the deployment available to clients as soon as possible. When the deployment is created, the client policy is updated, the clients are made aware of the deployment at their next client policy polling cycle, and then the software updates are available for installation.
|
- **Software available time**: Select **As soon as possible** to specify when the software updates will be available to clients:
|
||||||
- **Installation deadline**: Select **Specific time** to specify the installation deadline for the software updates in the deployment.
|
- **As soon as possible**: Select this setting to make the software updates in the deployment available to clients as soon as possible. When the deployment is created, the client policy is updated, the clients are made aware of the deployment at their next client policy polling cycle, and then the software updates are available for installation.
|
||||||
|
- **Installation deadline**: Select **Specific time** to specify the installation deadline for the software updates in the deployment.
|
||||||
>[!NOTE]
|
|
||||||
>You can configure the installation deadline setting only when **Type of deployment** is set to **Required** on the Deployment Settings page.
|
>[!NOTE]
|
||||||
|
>You can configure the installation deadline setting only when **Type of deployment** is set to **Required** on the Deployment Settings page.
|
||||||
- **Specific time**: Select this setting to automatically install the software updates in the deployment at a specific date and time. Set the date and time value to correspond with your defined maintenance window for the target collection. Allow sufficient time for clients to download the content in advance of the deadline. Adjust accordingly if clients in your environment will need additional download time. E.g., slow or unreliable network links.
|
|
||||||
|
- **Specific time**: Select this setting to automatically install the software updates in the deployment at a specific date and time. Set the date and time value to correspond with your defined maintenance window for the target collection. Allow sufficient time for clients to download the content in advance of the deadline. Adjust accordingly if clients in your environment will need additional download time. E.g., slow or unreliable network links.
|
||||||
>[!NOTE]
|
|
||||||
>The actual installation deadline time is the specific time that you configure plus a random amount of time up to 2 hours. This reduces the potential impact of all client computers in the destination collection installing the software updates in the deployment at the same time. Configure the Computer Agent client setting, Disable deadline randomization to disable the installation randomization delay for the required software updates to allow a greater chance for the installation to start and complete within your defined maintenance window. For more information, see [Computer Agent](https://docs.microsoft.com/sccm/core/clients/deploy/about-client-settings#computer-agent).
|
>[!NOTE]
|
||||||
7. On the User Experience page, configure the following settings:
|
>The actual installation deadline time is the specific time that you configure plus a random amount of time up to 2 hours. This reduces the potential impact of all client computers in the destination collection installing the software updates in the deployment at the same time. Configure the Computer Agent client setting, Disable deadline randomization to disable the installation randomization delay for the required software updates to allow a greater chance for the installation to start and complete within your defined maintenance window. For more information, see [Computer Agent](https://docs.microsoft.com/sccm/core/clients/deploy/about-client-settings#computer-agent).
|
||||||
- **User notifications**: Specify whether to display notification of the software updates in Software Center on the client computer at the configured **Software available time** and whether to display user notifications on the client computers. When **Type of deployment** is set to **Available** on the Deployment Settings page, you cannot select **Hide in Software Center and all notifications**.
|
7. On the User Experience page, configure the following settings:
|
||||||
- **Deadline behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify the behavior that is to occur when the deadline is reached for the software update deployment. Specify whether to install the software updates in the deployment. Also specify whether to perform a system restart after software update installation regardless of a configured maintenance window. For more information about maintenance windows, see [How to use maintenance windows](https://docs.microsoft.com/sccm/core/clients/manage/collections/use-maintenance-windows).
|
- **User notifications**: Specify whether to display notification of the software updates in Software Center on the client computer at the configured **Software available time** and whether to display user notifications on the client computers. When **Type of deployment** is set to **Available** on the Deployment Settings page, you cannot select **Hide in Software Center and all notifications**.
|
||||||
- **Device restart behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify whether to suppress a system restart on servers and workstations after software updates are installed and a system restart is required to complete the installation.
|
- **Deadline behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify the behavior that is to occur when the deadline is reached for the software update deployment. Specify whether to install the software updates in the deployment. Also specify whether to perform a system restart after software update installation regardless of a configured maintenance window. For more information about maintenance windows, see [How to use maintenance windows](https://docs.microsoft.com/sccm/core/clients/manage/collections/use-maintenance-windows).
|
||||||
|
- **Device restart behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify whether to suppress a system restart on servers and workstations after software updates are installed and a system restart is required to complete the installation.
|
||||||
>[!IMPORTANT]
|
|
||||||
>Suppressing system restarts can be useful in server environments or for cases in which you do not want the computers that are installing the software updates to restart by default. However, doing so can leave computers in an insecure state, whereas allowing a forced restart helps to ensure immediate completion of the software update installation.
|
>[!IMPORTANT]
|
||||||
- **Write filter handling for Windows Embedded devices**: When you deploy software updates to Windows Embedded devices that are write filter enabled, you can specify to install the software update on the temporary overlay and either commit changes later or commit the changes at the installation deadline or during a maintenance window. When you commit changes at the installation deadline or during a maintenance window, a restart is required and the changes persist on the device.
|
>Suppressing system restarts can be useful in server environments or for cases in which you do not want the computers that are installing the software updates to restart by default. However, doing so can leave computers in an insecure state, whereas allowing a forced restart helps to ensure immediate completion of the software update installation.
|
||||||
|
- **Write filter handling for Windows Embedded devices**: When you deploy software updates to Windows Embedded devices that are write filter enabled, you can specify to install the software update on the temporary overlay and either commit changes later or commit the changes at the installation deadline or during a maintenance window. When you commit changes at the installation deadline or during a maintenance window, a restart is required and the changes persist on the device.
|
||||||
>[!NOTE]
|
|
||||||
>When you deploy a software update to a Windows Embedded device, make sure that the device is a member of a collection that has a configured maintenance window.
|
>[!NOTE]
|
||||||
- **Software updates deployment re-evaluation behavior upon restart**: Starting in Configuration Manager version 1606, select this setting to configure software updates deployments to have clients run a software updates compliance scan immediately after a client installs software updates and restarts. This enables the client to check for additional software updates that become applicable after the client restarts, and to then install them (and become compliant) during the same maintenance window.
|
>When you deploy a software update to a Windows Embedded device, make sure that the device is a member of a collection that has a configured maintenance window.
|
||||||
8. On the Alerts page, configure how Configuration Manager and System Center Operations Manager will generate alerts for this deployment. You can configure alerts only when **Type of deployment** is set to **Required** on the Deployment Settings page.
|
- **Software updates deployment re-evaluation behavior upon restart**: Starting in Configuration Manager version 1606, select this setting to configure software updates deployments to have clients run a software updates compliance scan immediately after a client installs software updates and restarts. This enables the client to check for additional software updates that become applicable after the client restarts, and to then install them (and become compliant) during the same maintenance window.
|
||||||
|
8. On the Alerts page, configure how Configuration Manager and System Center Operations Manager will generate alerts for this deployment. You can configure alerts only when **Type of deployment** is set to **Required** on the Deployment Settings page.
|
||||||
>[!NOTE]
|
|
||||||
>You can review recent software updates alerts from the Software Updates node in the Software Library workspace.
|
>[!NOTE]
|
||||||
9. On the Download Settings page, configure the following settings:
|
>You can review recent software updates alerts from the Software Updates node in the Software Library workspace.
|
||||||
- Specify whether the client will download and install the software updates when a client is connected to a slow network or is using a fallback content location.
|
9. On the Download Settings page, configure the following settings:
|
||||||
- Specify whether to have the client download and install the software updates from a fallback distribution point when the content for the software updates is not available on a preferred distribution point.
|
- Specify whether the client will download and install the software updates when a client is connected to a slow network or is using a fallback content location.
|
||||||
- **Allow clients to share content with other clients on the same subnet**: Specify whether to enable the use of BranchCache for content downloads. For more information about BranchCache, see [Fundamental concepts for content management](https://docs.microsoft.com/sccm/core/plan-design/hierarchy/fundamental-concepts-for-content-management#branchcache).
|
- Specify whether to have the client download and install the software updates from a fallback distribution point when the content for the software updates is not available on a preferred distribution point.
|
||||||
- **If software updates are not available on distribution point in current, neighbor or site groups, download content from Microsoft Updates**: Select this setting to have clients that are connected to the intranet download software updates from Microsoft Update if software updates are not available on distribution points. Internet-based clients can always go to Microsoft Update for software updates content.
|
- **Allow clients to share content with other clients on the same subnet**: Specify whether to enable the use of BranchCache for content downloads. For more information about BranchCache, see [Fundamental concepts for content management](https://docs.microsoft.com/sccm/core/plan-design/hierarchy/fundamental-concepts-for-content-management#branchcache).
|
||||||
- Specify whether to allow clients to download after an installation deadline when they use metered Internet connections. Internet providers sometimes charge by the amount of data that you send and receive when you are on a metered Internet connection.
|
- **If software updates are not available on distribution point in current, neighbor or site groups, download content from Microsoft Updates**: Select this setting to have clients that are connected to the intranet download software updates from Microsoft Update if software updates are not available on distribution points. Internet-based clients can always go to Microsoft Update for software updates content.
|
||||||
|
- Specify whether to allow clients to download after an installation deadline when they use metered Internet connections. Internet providers sometimes charge by the amount of data that you send and receive when you are on a metered Internet connection.
|
||||||
>[!NOTE]
|
|
||||||
>Clients request the content location from a management point for the software updates in a deployment. The download behavior depends upon how you have configured the distribution point, the deployment package, and the settings on this page. For more information, see [Content source location scenarios](https://docs.microsoft.com/sccm/core/plan-design/hierarchy/content-source-location-scenarios).
|
>[!NOTE]
|
||||||
10. On the Summary page, review the settings. To save the settings to a deployment template, click **Save As Template**, enter a name and select the settings that you want to include in the template, and then click **Save**. To change a configured setting, click the associated wizard page and change the setting.
|
>Clients request the content location from a management point for the software updates in a deployment. The download behavior depends upon how you have configured the distribution point, the deployment package, and the settings on this page. For more information, see [Content source location scenarios](https://docs.microsoft.com/sccm/core/plan-design/hierarchy/content-source-location-scenarios).
|
||||||
11. Click **Next** to deploy the feature update(s).
|
10. On the Summary page, review the settings. To save the settings to a deployment template, click **Save As Template**, enter a name and select the settings that you want to include in the template, and then click **Save**. To change a configured setting, click the associated wizard page and change the setting.
|
||||||
|
11. Click **Next** to deploy the feature update(s).
|
||||||
### Step 4: Monitor the deployment status
|
|
||||||
After you deploy the feature update(s), you can monitor the deployment status. Use the following procedure to monitor the deployment status:
|
### Step 4: Monitor the deployment status
|
||||||
|
After you deploy the feature update(s), you can monitor the deployment status. Use the following procedure to monitor the deployment status:
|
||||||
1. In the Configuration Manager console, navigate to **Monitoring > Overview > Deployments**.
|
|
||||||
2. Click the software update group or software update for which you want to monitor the deployment status.
|
1. In the Configuration Manager console, navigate to **Monitoring > Overview > Deployments**.
|
||||||
3. On the **Home** tab, in the **Deployment** group, click **View Status**.
|
2. Click the software update group or software update for which you want to monitor the deployment status.
|
||||||
|
3. On the **Home** tab, in the **Deployment** group, click **View Status**.
|
||||||
|
|||||||
@ -1,43 +1,44 @@
|
|||||||
---
|
---
|
||||||
title: Best practices and recommendations for deploying Windows 10 Feature updates to mission critical devices
|
title: Best practices and recommendations for deploying Windows 10 Feature updates to mission critical devices
|
||||||
description: Learn how to deploy feature updates to your mission critical devices
|
description: Learn how to deploy feature updates to your mission critical devices
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.author: greglin
|
ms.localizationpriority: medium
|
||||||
ms.date: 07/10/2018
|
ms.author: jaimeo
|
||||||
ms.reviewer:
|
ms.date: 07/10/2018
|
||||||
manager: laurawi
|
ms.reviewer:
|
||||||
ms.collection: M365-modern-desktop
|
manager: laurawi
|
||||||
ms.topic: article
|
ms.collection: M365-modern-desktop
|
||||||
---
|
ms.topic: article
|
||||||
|
---
|
||||||
# Best practices and recommendations for deploying Windows 10 Feature updates to mission critical devices
|
|
||||||
|
# Best practices and recommendations for deploying Windows 10 Feature updates to mission critical devices
|
||||||
**Applies to**: Windows 10
|
|
||||||
|
**Applies to**: Windows 10
|
||||||
Managing an environment with devices that provide mission critical services 24 hours a day, 7 days a week, can present challenges in keeping these devices current with Windows 10 feature updates. The processes that you use to keep regular devices current with Windows 10 feature updates, often aren’t the most effective to service mission critical devices. This whitepaper will focus on the recommended approach of using the System Center Configuration Manager (current branch) software updates feature to deploy Windows 10 semi-annual feature updates.
|
|
||||||
|
Managing an environment with devices that provide mission critical services 24 hours a day, 7 days a week, can present challenges in keeping these devices current with Windows 10 feature updates. The processes that you use to keep regular devices current with Windows 10 feature updates, often aren’t the most effective to service mission critical devices. This whitepaper will focus on the recommended approach of using the System Center Configuration Manager (current branch) software updates feature to deploy Windows 10 semi-annual feature updates.
|
||||||
For simplicity, we will outline the steps to deploy a feature update manually. If you prefer an automated approach, please see [Using Windows 10 servicing plans to deploy Windows 10 feature updates](waas-manage-updates-configuration-manager.md#use-windows-10-servicing-plans-to-deploy-windows-10-feature-updates).
|
|
||||||
|
For simplicity, we will outline the steps to deploy a feature update manually. If you prefer an automated approach, please see [Using Windows 10 servicing plans to deploy Windows 10 feature updates](waas-manage-updates-configuration-manager.md#use-windows-10-servicing-plans-to-deploy-windows-10-feature-updates).
|
||||||
Devices and shared workstations that are online and available 24 hours a day, 7 days a week, can be serviced via one of two primary methods:
|
|
||||||
|
Devices and shared workstations that are online and available 24 hours a day, 7 days a week, can be serviced via one of two primary methods:
|
||||||
- **Service during maintenance windows** – Devices that have established maintenance windows will need to have feature updates scheduled to fit within these windows.
|
|
||||||
- **Service only when manually initiated** – Devices that need physical verification of the availability to update will need to have updates manually initiated by a technician.
|
- **Service during maintenance windows** – Devices that have established maintenance windows will need to have feature updates scheduled to fit within these windows.
|
||||||
|
- **Service only when manually initiated** – Devices that need physical verification of the availability to update will need to have updates manually initiated by a technician.
|
||||||
You can use Configuration Manager to deploy feature updates to Windows 10 devices in two ways. The first option is to use the software updates feature. The second option is to use a task sequence to deploy feature updates. There are times when deploying a Windows 10 feature update requires the use of a task sequence—for example:
|
|
||||||
|
You can use Configuration Manager to deploy feature updates to Windows 10 devices in two ways. The first option is to use the software updates feature. The second option is to use a task sequence to deploy feature updates. There are times when deploying a Windows 10 feature update requires the use of a task sequence—for example:
|
||||||
- **Upgrade to the next LTSC release.** With the LTSC 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 can use task sequences to orchestrate the additional steps. Software updates do not have the ability to add steps to their deployments.
|
- **Upgrade to the next LTSC release.** With the LTSC servicing branch, feature updates are never provided to the Windows clients themselves. Instead, feature updates must be installed like a traditional in-place upgrade.
|
||||||
- **Language pack installs.** When deploying a feature update requires the installation of additional language packs, you can use task sequences to orchestrate the installation. Software updates do not have the ability to natively install language packs.
|
- **Additional required tasks.** When deploying a feature update requires additional steps (e.g., suspending disk encryption, updating applications), you can use task sequences to orchestrate the additional steps. Software updates do not have the ability to add steps to their deployments.
|
||||||
|
- **Language pack installs.** When deploying a feature update requires the installation of additional language packs, you can use task sequences to orchestrate the installation. Software updates do not have the ability to natively install language packs.
|
||||||
If you need to leverage a task sequence to deploy feature updates, please see [Using a task sequence to deploy Windows 10 updates](waas-manage-updates-configuration-manager.md#use-a-task-sequence-to-deploy-windows-10-updates) for more information. If you find that your requirement for a task sequence is based solely on the need to run additional tasks preformed pre-install or pre-commit, please see the new [run custom actions](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-setup-enable-custom-actions) functionality first introduced with Windows 10, version 1803. You may be able to leverage this functionality with the software updates deployment method.
|
|
||||||
|
If you need to leverage a task sequence to deploy feature updates, please see [Using a task sequence to deploy Windows 10 updates](waas-manage-updates-configuration-manager.md#use-a-task-sequence-to-deploy-windows-10-updates) for more information. If you find that your requirement for a task sequence is based solely on the need to run additional tasks preformed pre-install or pre-commit, please see the new [run custom actions](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-setup-enable-custom-actions) functionality first introduced with Windows 10, version 1803. You may be able to leverage this functionality with the software updates deployment method.
|
||||||
Use the following information:
|
|
||||||
|
Use the following information:
|
||||||
|
|
||||||
- [Deploy feature updates during maintenance windows](feature-update-maintenance-window.md)
|
|
||||||
- [Deploy feature updates for user-initiated installations](feature-update-user-install.md)
|
- [Deploy feature updates during maintenance windows](feature-update-maintenance-window.md)
|
||||||
- [Conclusion](feature-update-conclusion.md)
|
- [Deploy feature updates for user-initiated installations](feature-update-user-install.md)
|
||||||
|
- [Conclusion](feature-update-conclusion.md)
|
||||||
|
|||||||
@ -5,9 +5,9 @@ ms.prod: w10
|
|||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: jaimeo
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.author: greglin
|
ms.author: jaimeo
|
||||||
ms.date: 07/10/2018
|
ms.date: 07/10/2018
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
|
|||||||
@ -5,9 +5,9 @@ ms.prod: w10
|
|||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.pagetype: article
|
ms.pagetype: article
|
||||||
ms.author: greglin
|
ms.author: jaimeo
|
||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: jaimeo
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.date: 03/13/2019
|
ms.date: 03/13/2019
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
|
|||||||
@ -1,146 +1,147 @@
|
|||||||
---
|
---
|
||||||
title: How Windows Update works
|
title: How Windows Update works
|
||||||
description: Learn how Windows Update works, including architecture and troubleshooting
|
description: Learn how Windows Update works, including architecture and troubleshooting
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl:
|
ms.mktglfcycl:
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.author: greglin
|
ms.localizationpriority: medium
|
||||||
ms.date: 09/18/2018
|
ms.author: jaimeo
|
||||||
ms.reviewer:
|
ms.date: 09/18/2018
|
||||||
manager: laurawi
|
ms.reviewer:
|
||||||
ms.collection: M365-modern-desktop
|
manager: laurawi
|
||||||
ms.topic: article
|
ms.collection: M365-modern-desktop
|
||||||
---
|
ms.topic: article
|
||||||
|
---
|
||||||
# How does Windows Update work?
|
|
||||||
|
# How does Windows Update work?
|
||||||
> Applies to: Windows 10
|
|
||||||
|
> Applies to: Windows 10
|
||||||
The Windows Update workflow has four core areas of functionality:
|
|
||||||
|
The Windows Update workflow has four core areas of functionality:
|
||||||
### Scan
|
|
||||||
|
### Scan
|
||||||
1. Orchestrator schedules the scan.
|
|
||||||
2. Orchestrator verifies admin approvals and policies for download.
|
1. Orchestrator schedules the scan.
|
||||||
|
2. Orchestrator verifies admin approvals and policies for download.
|
||||||
|
|
||||||
### Download
|
|
||||||
1. Orchestrator initiates downloads.
|
### Download
|
||||||
2. Windows Update downloads manifest files and provides them to the arbiter.
|
1. Orchestrator initiates downloads.
|
||||||
3. The arbiter evaluates the manifest and tells the Windows Update client to download files.
|
2. Windows Update downloads manifest files and provides them to the arbiter.
|
||||||
4. Windows Update client downloads files in a temporary folder.
|
3. The arbiter evaluates the manifest and tells the Windows Update client to download files.
|
||||||
5. The arbiter stages the downloaded files.
|
4. Windows Update client downloads files in a temporary folder.
|
||||||
|
5. The arbiter stages the downloaded files.
|
||||||
|
|
||||||
### Install
|
|
||||||
1. Orchestrator initiates the installation.
|
### Install
|
||||||
2. The arbiter calls the installer to install the package.
|
1. Orchestrator initiates the installation.
|
||||||
|
2. The arbiter calls the installer to install the package.
|
||||||
|
|
||||||
### Commit
|
|
||||||
1. Orchestrator initiates a restart.
|
### Commit
|
||||||
2. The arbiter finalizes before the restart.
|
1. Orchestrator initiates a restart.
|
||||||
|
2. The arbiter finalizes before the restart.
|
||||||
|
|
||||||
## How updating works
|
|
||||||
During the updating process, the Windows Update Orchestrator operates in the background to scan, download, and install updates. It does this automatically, according to your settings, and in a silent manner that doesn’t disrupt your computer usage.
|
## How updating works
|
||||||
|
During the updating process, the Windows Update Orchestrator operates in the background to scan, download, and install updates. It does this automatically, according to your settings, and in a silent manner that doesn’t disrupt your computer usage.
|
||||||
## Scanning updates
|
|
||||||
|
## Scanning updates
|
||||||
|
|
||||||
The Windows Update Orchestrator on your PC checks the Microsoft Update server or your WSUS endpoint for new updates at random intervals. The randomization ensures that the Windows Update server isn't overloaded with requests all at the same time. The Update Orchestrator searches only for updates that have been added since the last time updates were searched, allowing it to find updates quickly and efficiently.
|
|
||||||
|
The Windows Update Orchestrator on your PC checks the Microsoft Update server or your WSUS endpoint for new updates at random intervals. The randomization ensures that the Windows Update server isn't overloaded with requests all at the same time. The Update Orchestrator searches only for updates that have been added since the last time updates were searched, allowing it to find updates quickly and efficiently.
|
||||||
When checking for updates, the Windows Update Orchestrator evaluates whether the update is appropriate for your computer using guidelines defined by the publisher of the update, for example, Microsoft Office including enterprise group policies.
|
|
||||||
|
When checking for updates, the Windows Update Orchestrator evaluates whether the update is appropriate for your computer using guidelines defined by the publisher of the update, for example, Microsoft Office including enterprise group policies.
|
||||||
Make sure you're familiar with the following terminology related to Windows Update scan:
|
|
||||||
|
Make sure you're familiar with the following terminology related to Windows Update scan:
|
||||||
|Term|Definition|
|
|
||||||
|----|----------|
|
|Term|Definition|
|
||||||
|Update|We use this term to mean a lot of different things, but in this context it's the actual patch or change.|
|
|----|----------|
|
||||||
|Bundle update|An update that contains 1-N child updates; doesn't contain payload itself.|
|
|Update|We use this term to mean a lot of different things, but in this context it's the actual patch or change.|
|
||||||
|Child update|Leaf update that's bundled by another update; contains payload.|
|
|Bundle update|An update that contains 1-N child updates; doesn't contain payload itself.|
|
||||||
|Detectoid update|A special 'update' that contains "IsInstalled" applicability rule only and no payload. Used for prereq evaluation.|
|
|Child update|Leaf update that's bundled by another update; contains payload.|
|
||||||
|Category update|A special 'detectoid' that has always true IsInstalled rule. Used for grouping updates and for client to filter updates. |
|
|Detectoid update|A special 'update' that contains "IsInstalled" applicability rule only and no payload. Used for prereq evaluation.|
|
||||||
|Full scan|Scan with empty datastore.|
|
|Category update|A special 'detectoid' that has always true IsInstalled rule. Used for grouping updates and for client to filter updates. |
|
||||||
|Delta scan|Scan with updates from previous scan already cached in datastore.|
|
|Full scan|Scan with empty datastore.|
|
||||||
|Online scan|Scan that hits network and goes against server on cloud. |
|
|Delta scan|Scan with updates from previous scan already cached in datastore.|
|
||||||
|Offline scan|Scan that doesn't hit network and goes against local datastore. Only useful if online scan has been performed before. |
|
|Online scan|Scan that hits network and goes against server on cloud. |
|
||||||
|CatScan|Category scan where caller can specify a categoryId to get updates published under the categoryId.|
|
|Offline scan|Scan that doesn't hit network and goes against local datastore. Only useful if online scan has been performed before. |
|
||||||
|AppCatScan|Category scan where caller can specify an AppCategoryId to get apps published under the appCategoryId.|
|
|CatScan|Category scan where caller can specify a categoryId to get updates published under the categoryId.|
|
||||||
|Software sync|Part of the scan that looks at software updates only (OS and apps).|
|
|AppCatScan|Category scan where caller can specify an AppCategoryId to get apps published under the appCategoryId.|
|
||||||
|Driver sync|Part of the scan that looks at Driver updates only. This is run after Software sync and is optional.|
|
|Software sync|Part of the scan that looks at software updates only (OS and apps).|
|
||||||
|ProductSync|Attributes based sync, where client provides a list of device, product and caller attributes ahead of time to allow service to evaluate applicability in the cloud. |
|
|Driver sync|Part of the scan that looks at Driver updates only. This is run after Software sync and is optional.|
|
||||||
|
|ProductSync|Attributes based sync, where client provides a list of device, product and caller attributes ahead of time to allow service to evaluate applicability in the cloud. |
|
||||||
### How Windows Update scanning works
|
|
||||||
|
### How Windows Update scanning works
|
||||||
Windows Update takes the following sets of actions when it runs a scan.
|
|
||||||
|
Windows Update takes the following sets of actions when it runs a scan.
|
||||||
#### Starts the scan for updates
|
|
||||||
When users start scanning in Windows Update through the Settings panel, the following occurs:
|
#### Starts the scan for updates
|
||||||
|
When users start scanning in Windows Update through the Settings panel, the following occurs:
|
||||||
- The scan first generates a “ComApi” message. The caller (Windows Defender Antivirus) tells the WU engine to scan for updates.
|
|
||||||
- "Agent" messages: queueing the scan, then actually starting the work:
|
- The scan first generates a “ComApi” message. The caller (Windows Defender Antivirus) tells the WU engine to scan for updates.
|
||||||
- Updates are identified by the different IDs ("Id = 10", "Id = 11") and from the different thread ID numbers.
|
- "Agent" messages: queueing the scan, then actually starting the work:
|
||||||
- Windows Update uses the thread ID filtering to concentrate on one particular task.
|
- Updates are identified by the different IDs ("Id = 10", "Id = 11") and from the different thread ID numbers.
|
||||||
|
- Windows Update uses the thread ID filtering to concentrate on one particular task.
|
||||||
|
|
||||||
|
|
||||||
#### Identifies service IDs
|
|
||||||
|
#### Identifies service IDs
|
||||||
- Service IDs indicate which update source is being scanned.
|
|
||||||
Note The next screen shot shows Microsoft Update and the Flighting service.
|
- Service IDs indicate which update source is being scanned.
|
||||||
|
Note The next screen shot shows Microsoft Update and the Flighting service.
|
||||||
- The Windows Update engine treats every service as a separate entity, even though multiple services may contain the same updates.
|
|
||||||
|
- The Windows Update engine treats every service as a separate entity, even though multiple services may contain the same updates.
|
||||||
- Common service IDs
|
|
||||||
|
- Common service IDs
|
||||||
> [!IMPORTANT]
|
|
||||||
> ServiceId here identifies a client abstraction, not any specific service in the cloud. No assumption should be made of which server a serviceId is pointing to, it's totally controlled by the SLS responses.
|
> [!IMPORTANT]
|
||||||
|
> ServiceId here identifies a client abstraction, not any specific service in the cloud. No assumption should be made of which server a serviceId is pointing to, it's totally controlled by the SLS responses.
|
||||||
|Service|ServiceId|
|
|
||||||
|-------|---------|
|
|Service|ServiceId|
|
||||||
|Unspecified / Default|WU, MU or WSUS <br>00000000-0000-0000-0000-000000000000 |
|
|-------|---------|
|
||||||
|WU|9482F4B4-E343-43B6-B170-9A65BC822C77|
|
|Unspecified / Default|WU, MU or WSUS <br>00000000-0000-0000-0000-000000000000 |
|
||||||
|MU|7971f918-a847-4430-9279-4a52d1efe18d|
|
|WU|9482F4B4-E343-43B6-B170-9A65BC822C77|
|
||||||
|Store|855E8A7C-ECB4-4CA3-B045-1DFA50104289|
|
|MU|7971f918-a847-4430-9279-4a52d1efe18d|
|
||||||
|OS Flighting|8B24B027-1DEE-BABB-9A95-3517DFB9C552|
|
|Store|855E8A7C-ECB4-4CA3-B045-1DFA50104289|
|
||||||
|WSUS or SCCM|Via ServerSelection::ssManagedServer <br>3DA21691-E39D-4da6-8A4B-B43877BCB1B7 |
|
|OS Flighting|8B24B027-1DEE-BABB-9A95-3517DFB9C552|
|
||||||
|Offline scan service|Via IUpdateServiceManager::AddScanPackageService|
|
|WSUS or SCCM|Via ServerSelection::ssManagedServer <br>3DA21691-E39D-4da6-8A4B-B43877BCB1B7 |
|
||||||
|
|Offline scan service|Via IUpdateServiceManager::AddScanPackageService|
|
||||||
#### Finds network faults
|
|
||||||
Common update failure is caused due to network issues. To find the root of the issue:
|
#### Finds network faults
|
||||||
|
Common update failure is caused due to network issues. To find the root of the issue:
|
||||||
- Look for "ProtocolTalker" messages to see client-server sync network traffic.
|
|
||||||
- "SOAP faults" can be either client- or server-side issues; read the message.
|
- Look for "ProtocolTalker" messages to see client-server sync network traffic.
|
||||||
- The WU client uses SLS (Service Locator Service) to discover the configurations and endpoints of Microsoft network update sources – WU, MU, Flighting.
|
- "SOAP faults" can be either client- or server-side issues; read the message.
|
||||||
|
- The WU client uses SLS (Service Locator Service) to discover the configurations and endpoints of Microsoft network update sources – WU, MU, Flighting.
|
||||||
> [!NOTE]
|
|
||||||
> Warning messages for SLS can be ignored if the search is against WSUS/SCCM.
|
> [!NOTE]
|
||||||
|
> Warning messages for SLS can be ignored if the search is against WSUS/SCCM.
|
||||||
- On sites that only use WSUS/SCCM, the SLS may be blocked at the firewall. In this case the SLS request will fail, and can’t scan against Windows Update or Microsoft Update but can still scan against WSUS/SCCM, since it’s locally configured.
|
|
||||||
|
- On sites that only use WSUS/SCCM, the SLS may be blocked at the firewall. In this case the SLS request will fail, and can’t scan against Windows Update or Microsoft Update but can still scan against WSUS/SCCM, since it’s locally configured.
|
||||||
|
|
||||||
## Downloading updates
|
|
||||||
|
## Downloading updates
|
||||||
|
|
||||||
Once the Windows Update Orchestrator determines which updates apply to your computer, it will begin downloading the updates, if you have selected the option to automatically download updates. It does this in the background without interrupting your normal use of the computer.
|
|
||||||
|
Once the Windows Update Orchestrator determines which updates apply to your computer, it will begin downloading the updates, if you have selected the option to automatically download updates. It does this in the background without interrupting your normal use of the computer.
|
||||||
To ensure that your other downloads aren’t affected or slowed down because updates are downloading, Windows Update uses the Delivery Optimization (DO) technology which downloads updates and reduces bandwidth consumption.
|
|
||||||
|
To ensure that your other downloads aren’t affected or slowed down because updates are downloading, Windows Update uses the Delivery Optimization (DO) technology which downloads updates and reduces bandwidth consumption.
|
||||||
For more information see [Configure Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md).
|
|
||||||
|
For more information see [Configure Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md).
|
||||||
## Installing updates
|
|
||||||
|
## Installing updates
|
||||||
|
|
||||||
When an update is applicable, the "Arbiter" and metadata are downloaded. Depending on your Windows Update settings, when downloading is complete, the Arbiter will gather details from the device, and compare that with the downloaded metadata to create an "action list".
|
|
||||||
|
When an update is applicable, the "Arbiter" and metadata are downloaded. Depending on your Windows Update settings, when downloading is complete, the Arbiter will gather details from the device, and compare that with the downloaded metadata to create an "action list".
|
||||||
The action list describes all the files needed from WU, and what the install agent (such as CBS or Setup) should do with them. The action list is provided to the install agent along with the payload to begin the installation.
|
|
||||||
|
The action list describes all the files needed from WU, and what the install agent (such as CBS or Setup) should do with them. The action list is provided to the install agent along with the payload to begin the installation.
|
||||||
## Committing Updates
|
|
||||||
|
## Committing Updates
|
||||||
|
|
||||||
When the option to automatically install updates is configured, the Windows Update Orchestrator, in most cases, automatically restarts the PC for you after installing the updates. This is necessary because your PC may be insecure, or not fully updated, until a restart is completed. You can use Group Policy settings, mobile device management (MDM), or the registry (not recommended) to configure when devices will restart after a Windows 10 update is installed.
|
|
||||||
|
When the option to automatically install updates is configured, the Windows Update Orchestrator, in most cases, automatically restarts the PC for you after installing the updates. This is necessary because your PC may be insecure, or not fully updated, until a restart is completed. You can use Group Policy settings, mobile device management (MDM), or the registry (not recommended) to configure when devices will restart after a Windows 10 update is installed.
|
||||||
For more information see [Manage device restarts after updates](waas-restart.md).
|
|
||||||
|
For more information see [Manage device restarts after updates](waas-restart.md).
|
||||||
|
|||||||
@ -1,131 +1,132 @@
|
|||||||
---
|
---
|
||||||
title: Olympia Corp enrollment guidelines
|
title: Olympia Corp enrollment guidelines
|
||||||
description: Olympia Corp enrollment guidelines
|
description: Olympia Corp enrollment guidelines
|
||||||
ms.author: greglin
|
ms.author: jaimeo
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.technology: windows
|
ms.technology: windows
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.reviewer:
|
author: jaimeo
|
||||||
manager: laurawi
|
ms.reviewer:
|
||||||
keywords: insider, trial, enterprise, lab, corporation, test
|
manager: laurawi
|
||||||
---
|
keywords: insider, trial, enterprise, lab, corporation, test
|
||||||
|
---
|
||||||
# Olympia Corp
|
|
||||||
|
# Olympia Corp
|
||||||
## What is Windows Insider Lab for Enterprise and Olympia Corp?
|
|
||||||
|
## What is Windows Insider Lab for Enterprise and Olympia Corp?
|
||||||
Windows Insider Lab for Enterprise is intended for Windows Insiders who want to try new experimental and pre-release enterprise privacy and security features. To get the complete experience of these enterprise features, Olympia Corp, a virtual corporation has been set up to reflect the IT infrastructure of real world business. Selected customers are invited to join Olympia Corp and try these features.
|
|
||||||
|
Windows Insider Lab for Enterprise is intended for Windows Insiders who want to try new experimental and pre-release enterprise privacy and security features. To get the complete experience of these enterprise features, Olympia Corp, a virtual corporation has been set up to reflect the IT infrastructure of real world business. Selected customers are invited to join Olympia Corp and try these features.
|
||||||
As an Olympia user, you will have an opportunity to:
|
|
||||||
|
As an Olympia user, you will have an opportunity to:
|
||||||
- Use various enterprise features like Windows Information Protection (WIP), Advanced Threat Protection (ATP), windows Defender Application Guard (WDAG), and Application Virtualization (APP-V).
|
|
||||||
- Learn how Microsoft is preparing for GDPR, as well as enabling enterprise customers to prepare for their own readiness.
|
- Use various enterprise features like Windows Information Protection (WIP), Advanced Threat Protection (ATP), windows Defender Application Guard (WDAG), and Application Virtualization (APP-V).
|
||||||
- Validate and test pre-release software in your environment.
|
- Learn how Microsoft is preparing for GDPR, as well as enabling enterprise customers to prepare for their own readiness.
|
||||||
- Provide feedback.
|
- Validate and test pre-release software in your environment.
|
||||||
- Interact with engineering team members through a variety of communication channels.
|
- Provide feedback.
|
||||||
|
- Interact with engineering team members through a variety of communication channels.
|
||||||
>[!Note]
|
|
||||||
>Enterprise features might have reduced or different security, privacy, accessibility, availability, and reliability standards relative to commercially provided services and software. We may change or discontinue any of the enterprise features at any time without notice.
|
>[!Note]
|
||||||
|
>Enterprise features might have reduced or different security, privacy, accessibility, availability, and reliability standards relative to commercially provided services and software. We may change or discontinue any of the enterprise features at any time without notice.
|
||||||
For more information about Olympia Corp, see [https://olympia.windows.com/Info/FAQ](https://olympia.windows.com/Info/FAQ).
|
|
||||||
|
For more information about Olympia Corp, see [https://olympia.windows.com/Info/FAQ](https://olympia.windows.com/Info/FAQ).
|
||||||
To request an Olympia Corp account, fill out the survey at [https://aka.ms/RegisterOlympia](https://aka.ms/RegisterOlympia).
|
|
||||||
|
To request an Olympia Corp account, fill out the survey at [https://aka.ms/RegisterOlympia](https://aka.ms/RegisterOlympia).
|
||||||
## Enrollment guidelines
|
|
||||||
|
## Enrollment guidelines
|
||||||
Welcome to Olympia Corp. Here are the steps needed to enroll.
|
|
||||||
|
Welcome to Olympia Corp. Here are the steps needed to enroll.
|
||||||
As part of Windows Insider Lab for Enterprise, you can upgrade to Windows 10 Enterprise from Windows 10 Pro. This upgrade is optional. Since certain features such as Windows Defender Application Guard are only available on Windows 10 Enterprise, we recommend you to upgrade.
|
|
||||||
|
As part of Windows Insider Lab for Enterprise, you can upgrade to Windows 10 Enterprise from Windows 10 Pro. This upgrade is optional. Since certain features such as Windows Defender Application Guard are only available on Windows 10 Enterprise, we recommend you to upgrade.
|
||||||
Choose one of the following two enrollment options:
|
|
||||||
|
Choose one of the following two enrollment options:
|
||||||
- To set up an AAD-registered device, [follow these steps](#enrollment-keep-current-edition). In this case, you log onto the device by using an existing (non-Olympia) account.
|
|
||||||
|
- To set up an AAD-registered device, [follow these steps](#enrollment-keep-current-edition). In this case, you log onto the device by using an existing (non-Olympia) account.
|
||||||
- If you are running Windows 10 Pro, we recommend that you upgrade to Windows 10 Enterprise by following these steps to [set up an Azure Active Directory-joined device](#enrollment-upgrade-to-enterprise). In this case, you will be able to log on to the device with your Olympia account.
|
|
||||||
|
- If you are running Windows 10 Pro, we recommend that you upgrade to Windows 10 Enterprise by following these steps to [set up an Azure Active Directory-joined device](#enrollment-upgrade-to-enterprise). In this case, you will be able to log on to the device with your Olympia account.
|
||||||
<a id="enrollment-keep-current-edition"></a>
|
|
||||||
|
<a id="enrollment-keep-current-edition"></a>
|
||||||
### Set up an Azure Active Directory-REGISTERED Windows 10 device
|
|
||||||
|
### Set up an Azure Active Directory-REGISTERED Windows 10 device
|
||||||
This is the Bring Your Own Device (BYOD) method--your device will receive Olympia policies and features, but a new account will not be created. See [Set up Azure Active Directory registered Windows 10 devices](https://docs.microsoft.com/azure/active-directory/device-management-azuread-registered-devices-windows10-setup) for additional information.
|
|
||||||
|
This is the Bring Your Own Device (BYOD) method--your device will receive Olympia policies and features, but a new account will not be created. See [Set up Azure Active Directory registered Windows 10 devices](https://docs.microsoft.com/azure/active-directory/device-management-azuread-registered-devices-windows10-setup) for additional information.
|
||||||
1. Go to **Start > Settings > Accounts > Access work or school**. To see this setting, you need to have administrator rights to your device (see [local administrator](https://support.microsoft.com/instantanswers/5de907f1-f8ba-4fd9-a89d-efd23fee918c/create-a-local-user-or-administrator-account-in-windows-10)).
|
|
||||||
|
1. Go to **Start > Settings > Accounts > Access work or school**. To see this setting, you need to have administrator rights to your device (see [local administrator](https://support.microsoft.com/instantanswers/5de907f1-f8ba-4fd9-a89d-efd23fee918c/create-a-local-user-or-administrator-account-in-windows-10)).
|
||||||
|
|
||||||
|
|
||||||
2. If you are already connected to a domain, click the existing account and then click **Disconnect**. Click **Restart Later**.
|
|
||||||
|
2. If you are already connected to a domain, click the existing account and then click **Disconnect**. Click **Restart Later**.
|
||||||
3. Click **Connect** and enter your **Olympia corporate account** (e.g., username@olympia.windows.com). Click **Next**.
|
|
||||||
|
3. Click **Connect** and enter your **Olympia corporate account** (e.g., username@olympia.windows.com). Click **Next**.
|
||||||
|
|
||||||
|
|
||||||
4. Enter the temporary password that was sent to you. Click **Sign in**. Follow the instructions to set a new password.
|
|
||||||
|
4. Enter the temporary password that was sent to you. Click **Sign in**. Follow the instructions to set a new password.
|
||||||
> [!NOTE]
|
|
||||||
> Passwords should contain 8-16 characters, including at least one special character or number.
|
> [!NOTE]
|
||||||
|
> Passwords should contain 8-16 characters, including at least one special character or number.
|
||||||
|
|
||||||
|
|
||||||
5. Read the **Terms and Conditions**. Click **Accept** to participate in the program.
|
|
||||||
|
5. Read the **Terms and Conditions**. Click **Accept** to participate in the program.
|
||||||
6. If this is the first time you are logging in, fill in the additional information to help you retrieve your account details.
|
|
||||||
|
6. If this is the first time you are logging in, fill in the additional information to help you retrieve your account details.
|
||||||
7. Create a PIN for signing into your Olympia corporate account.
|
|
||||||
|
7. Create a PIN for signing into your Olympia corporate account.
|
||||||
8. Go to **Start > Settings > Update & Security > Windows Insider Program**. Click on the current Windows Insider account, and click **Change**. Sign in with your **Olympia corporate account**.
|
|
||||||
|
8. Go to **Start > Settings > Update & Security > Windows Insider Program**. Click on the current Windows Insider account, and click **Change**. Sign in with your **Olympia corporate account**.
|
||||||
> [!NOTE]
|
|
||||||
> To complete this step, you will need to register your account with the [Windows Insider Program for Business](https://insider.windows.com/ForBusiness).
|
> [!NOTE]
|
||||||
|
> To complete this step, you will need to register your account with the [Windows Insider Program for Business](https://insider.windows.com/ForBusiness).
|
||||||
9. Open the **Feedback Hub**, and sign in with your **Olympia corporate account**.
|
|
||||||
|
9. Open the **Feedback Hub**, and sign in with your **Olympia corporate account**.
|
||||||
<a id="enrollment-upgrade-to-enterprise"></a>
|
|
||||||
|
<a id="enrollment-upgrade-to-enterprise"></a>
|
||||||
### Set up Azure Active Directory-JOINED Windows 10 device
|
|
||||||
|
### Set up Azure Active Directory-JOINED Windows 10 device
|
||||||
- This method will upgrade your Windows 10 Pro license to Enterprise and create a new account. See [Set up Azure Active Directory joined devices](https://docs.microsoft.com/azure/active-directory/device-management-azuread-joined-devices-setup) for more information.
|
|
||||||
|
- This method will upgrade your Windows 10 Pro license to Enterprise and create a new account. See [Set up Azure Active Directory joined devices](https://docs.microsoft.com/azure/active-directory/device-management-azuread-joined-devices-setup) for more information.
|
||||||
1. Go to **Start > Settings > Accounts > Access work or school**. To see this setting, you need to have administrator rights to your device (see [local administrator](https://support.microsoft.com/instantanswers/5de907f1-f8ba-4fd9-a89d-efd23fee918c/create-a-local-user-or-administrator-account-in-windows-10)).
|
|
||||||
|
1. Go to **Start > Settings > Accounts > Access work or school**. To see this setting, you need to have administrator rights to your device (see [local administrator](https://support.microsoft.com/instantanswers/5de907f1-f8ba-4fd9-a89d-efd23fee918c/create-a-local-user-or-administrator-account-in-windows-10)).
|
||||||
|
|
||||||
|
|
||||||
2. If you are already connected to a domain, click the existing account and then click **Disconnect**. Click **Restart Later**.
|
|
||||||
|
2. If you are already connected to a domain, click the existing account and then click **Disconnect**. Click **Restart Later**.
|
||||||
3. Click **Connect**, then click **Join this device to Azure Active Directory**.
|
|
||||||
|
3. Click **Connect**, then click **Join this device to Azure Active Directory**.
|
||||||
|
|
||||||
|
|
||||||
4. Enter your **Olympia corporate account** (e.g., username@olympia.windows.com). Click **Next**.
|
|
||||||
|
4. Enter your **Olympia corporate account** (e.g., username@olympia.windows.com). Click **Next**.
|
||||||
|
|
||||||
|
|
||||||
5. Enter the temporary password that was sent to you. Click **Sign in**. Follow the instructions to set a new password.
|
|
||||||
|
5. Enter the temporary password that was sent to you. Click **Sign in**. Follow the instructions to set a new password.
|
||||||
> [!NOTE]
|
|
||||||
> Passwords should contain 8-16 characters, including at least one special character or number.
|
> [!NOTE]
|
||||||
|
> Passwords should contain 8-16 characters, including at least one special character or number.
|
||||||
|
|
||||||
|
|
||||||
6. When asked to make sure this is your organization, verify that the information is correct. If so, click **Join**.
|
|
||||||
|
6. When asked to make sure this is your organization, verify that the information is correct. If so, click **Join**.
|
||||||
7. If this is the first time you are signing in, fill in the additional information to help you retrieve your account details.
|
|
||||||
|
7. If this is the first time you are signing in, fill in the additional information to help you retrieve your account details.
|
||||||
8. Create a PIN for signing into your Olympia corporate account.
|
|
||||||
|
8. Create a PIN for signing into your Olympia corporate account.
|
||||||
9. When asked to make sure this is your organization, verify that the information is correct. If so, click **Join**.
|
|
||||||
|
9. When asked to make sure this is your organization, verify that the information is correct. If so, click **Join**.
|
||||||
10. Restart your device.
|
|
||||||
|
10. Restart your device.
|
||||||
11. In the sign-in screen, choose **Other User** and sign in with your **Olympia corporate account**. Your device will upgrade to Windows 10 Enterprise.
|
|
||||||
|
11. In the sign-in screen, choose **Other User** and sign in with your **Olympia corporate account**. Your device will upgrade to Windows 10 Enterprise.
|
||||||
12. Go to **Start > Settings > Update & Security > Windows Insider Program**. Click on the current Windows Insider account, and click **Change**. Sign in with your **Olympia corporate account**.
|
|
||||||
|
12. Go to **Start > Settings > Update & Security > Windows Insider Program**. Click on the current Windows Insider account, and click **Change**. Sign in with your **Olympia corporate account**.
|
||||||
> [!NOTE]
|
|
||||||
> To complete this step, you will need to register your account with the [Windows Insider Program for Business](https://insider.windows.com/ForBusiness).
|
> [!NOTE]
|
||||||
|
> To complete this step, you will need to register your account with the [Windows Insider Program for Business](https://insider.windows.com/ForBusiness).
|
||||||
13. Open the **Feedback Hub**, and sign in with your **Olympia corporate account**.
|
|
||||||
|
13. Open the **Feedback Hub**, and sign in with your **Olympia corporate account**.
|
||||||
>[!NOTE]
|
|
||||||
> Your Windows 10 Enterprise license will not be renewed if your device is not connected to Olympia.
|
>[!NOTE]
|
||||||
|
> Your Windows 10 Enterprise license will not be renewed if your device is not connected to Olympia.
|
||||||
|
|
||||||
|
|||||||
@ -1,56 +1,57 @@
|
|||||||
---
|
---
|
||||||
title: Servicing stack updates (Windows 10)
|
title: Servicing stack updates (Windows 10)
|
||||||
description: Servicing stack updates improve the code that installs the other updates.
|
description: Servicing stack updates improve the code that installs the other updates.
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.author: greglin
|
ms.localizationpriority: medium
|
||||||
ms.date: 11/29/2018
|
ms.author: jaimeo
|
||||||
ms.reviewer:
|
ms.date: 11/29/2018
|
||||||
manager: laurawi
|
ms.reviewer:
|
||||||
ms.collection: M365-modern-desktop
|
manager: laurawi
|
||||||
ms.topic: article
|
ms.collection: M365-modern-desktop
|
||||||
---
|
ms.topic: article
|
||||||
|
---
|
||||||
# Servicing stack updates
|
|
||||||
|
# Servicing stack updates
|
||||||
|
|
||||||
**Applies to**
|
|
||||||
|
**Applies to**
|
||||||
- Windows 10, Windows 8.1, Windows 8, Windows 7
|
|
||||||
|
- Windows 10, Windows 8.1, Windows 8, Windows 7
|
||||||
## What is a servicing stack update?
|
|
||||||
Servicing stack updates provide fixes to the servicing stack, the component that installs Windows updates. Additionally, it contains the "component-based servicing stack" (CBS), which is a key underlying component for several elements of Windows deployment, such as DISM, SFC, changing Windows features or roles, and repairing components. The CBS is a small component that typically does not have updates released every month.
|
## What is a servicing stack update?
|
||||||
|
Servicing stack updates provide fixes to the servicing stack, the component that installs Windows updates. Additionally, it contains the "component-based servicing stack" (CBS), which is a key underlying component for several elements of Windows deployment, such as DISM, SFC, changing Windows features or roles, and repairing components. The CBS is a small component that typically does not have updates released every month.
|
||||||
## Why should servicing stack updates be installed and kept up to date?
|
|
||||||
|
## Why should servicing stack updates be installed and kept up to date?
|
||||||
Servicing stack updates improve the reliability of the update process to mitigate potential issues while installing the latest quality updates and feature updates. If you don't install the latest servicing stack update, there's a risk that your device can't be updated with the latest Microsoft security fixes.
|
|
||||||
|
Servicing stack updates improve the reliability of the update process to mitigate potential issues while installing the latest quality updates and feature updates. If you don't install the latest servicing stack update, there's a risk that your device can't be updated with the latest Microsoft security fixes.
|
||||||
## When are they released?
|
|
||||||
|
## When are they released?
|
||||||
Servicing stack update are released depending on new issues or vulnerabilities. In rare occasions a servicing stack update may need to be released on demand to address an issue impacting systems installing the monthly security update. Starting in November 2018 new servicing stack updates will be classified as "Security" with a severity rating of "Critical."
|
|
||||||
|
Servicing stack update are released depending on new issues or vulnerabilities. In rare occasions a servicing stack update may need to be released on demand to address an issue impacting systems installing the monthly security update. Starting in November 2018 new servicing stack updates will be classified as "Security" with a severity rating of "Critical."
|
||||||
>[!NOTE]
|
|
||||||
>You can find a list of servicing stack updates at [Latest servicing stack updates](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV990001).
|
>[!NOTE]
|
||||||
|
>You can find a list of servicing stack updates at [Latest servicing stack updates](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV990001).
|
||||||
## What's the difference between a servicing stack update and a cumulative update?
|
|
||||||
|
## What's the difference between a servicing stack update and a cumulative update?
|
||||||
Both Windows 10 and Windows Server use the cumulative update mechanism, in which many fixes to improve the quality and security of Windows are packaged into a single update. Each cumulative update includes the changes and fixes from all previous updates.
|
|
||||||
|
Both Windows 10 and Windows Server use the cumulative update mechanism, in which many fixes to improve the quality and security of Windows are packaged into a single update. Each cumulative update includes the changes and fixes from all previous updates.
|
||||||
Servicing stack updates must ship separately from the cumulative updates because they modify the component that installs Windows updates. The servicing stack is released separately because the servicing stack itself requires an update. For example, the cumulative update [KB4284880](https://support.microsoft.com/help/4284880/windows-10-update-kb4284880) requires the [May 17, 2018 servicing stack update](https://support.microsoft.com/help/4132216), which includes updates to Windows Update.
|
|
||||||
|
Servicing stack updates must ship separately from the cumulative updates because they modify the component that installs Windows updates. The servicing stack is released separately because the servicing stack itself requires an update. For example, the cumulative update [KB4284880](https://support.microsoft.com/help/4284880/windows-10-update-kb4284880) requires the [May 17, 2018 servicing stack update](https://support.microsoft.com/help/4132216), which includes updates to Windows Update.
|
||||||
|
|
||||||
## Is there any special guidance?
|
|
||||||
|
## Is there any special guidance?
|
||||||
Microsoft recommends you install the latest servicing stack updates for your operating system before installing the latest cumulative update.
|
|
||||||
|
Microsoft recommends you install the latest servicing stack updates for your operating system before installing the latest cumulative update.
|
||||||
Typically, the improvements are reliability and performance improvements that do not require any specific special guidance. If there is any significant impact, it will be present in the release notes.
|
|
||||||
|
Typically, the improvements are reliability and performance improvements that do not require any specific special guidance. If there is any significant impact, it will be present in the release notes.
|
||||||
## Installation notes
|
|
||||||
|
## Installation notes
|
||||||
* Servicing stack updates contain the full servicing stack; as a result, typically administrators only need to install the latest servicing stack update for the operating system.
|
|
||||||
* Installing servicing stack update does not require restarting the device, so installation should not be disruptive.
|
* Servicing stack updates contain the full servicing stack; as a result, typically administrators only need to install the latest servicing stack update for the operating system.
|
||||||
* Servicing stack update releases are specific to the operating system version (build number), much like quality updates.
|
* Installing servicing stack update does not require restarting the device, so installation should not be disruptive.
|
||||||
* Search to install latest available [Servicing stack update for Windows 10](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV990001).
|
* Servicing stack update releases are specific to the operating system version (build number), much like quality updates.
|
||||||
|
* Search to install latest available [Servicing stack update for Windows 10](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV990001).
|
||||||
|
|||||||
@ -1,49 +1,50 @@
|
|||||||
---
|
---
|
||||||
title: Update Compliance - Feature Update Status report
|
title: Update Compliance - Feature Update Status report
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
description: an overview of the Feature Update Status report
|
description: an overview of the Feature Update Status report
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.pagetype: deploy
|
ms.pagetype: deploy
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.author: greglin
|
author: jaimeo
|
||||||
ms.collection: M365-analytics
|
ms.author: jaimeo
|
||||||
ms.topic: article
|
ms.collection: M365-analytics
|
||||||
---
|
ms.topic: article
|
||||||
|
---
|
||||||
# Feature Update Status
|
|
||||||
|
# Feature Update Status
|
||||||
|
|
||||||
|
|
||||||
The Feature Update Status section provides information about the status of [feature updates](waas-quick-start.md#definitions) across all devices. This section tile in the [Overview Blade](update-compliance-using.md#overview-blade) gives a percentage of devices that are on the latest applicable feature update; [Servicing Channel](waas-overview.md#servicing-channels) is considered in determining applicability. Within this section are two blades; one providing a holistic view of feature updates, the other containing three **Deployment Status** tiles, each charged with tracking the deployment for a different [Servicing Channel](waas-overview.md#servicing-channels).
|
|
||||||
|
The Feature Update Status section provides information about the status of [feature updates](waas-quick-start.md#definitions) across all devices. This section tile in the [Overview Blade](update-compliance-using.md#overview-blade) gives a percentage of devices that are on the latest applicable feature update; [Servicing Channel](waas-overview.md#servicing-channels) is considered in determining applicability. Within this section are two blades; one providing a holistic view of feature updates, the other containing three **Deployment Status** tiles, each charged with tracking the deployment for a different [Servicing Channel](waas-overview.md#servicing-channels).
|
||||||
## Overall Feature Update Status
|
|
||||||
|
## Overall Feature Update Status
|
||||||
The Overall Feature Update Status blade breaks down how many devices are up-to-date or not, with a special callout for how many devices are running a build that is not supported (for a full list of feature updates, check out the [Windows 10 Release Information](https://technet.microsoft.com/windows/release-info.aspx) page). The table beneath the visualization breaks devices down by Servicing Channel and operating system version, then defining whether this combination is *up-to-date*, *not up-to-date* or *out of support*. Finally, the table provides a count of devices that fall into this category.
|
|
||||||
|
The Overall Feature Update Status blade breaks down how many devices are up-to-date or not, with a special callout for how many devices are running a build that is not supported (for a full list of feature updates, check out the [Windows 10 Release Information](https://technet.microsoft.com/windows/release-info.aspx) page). The table beneath the visualization breaks devices down by Servicing Channel and operating system version, then defining whether this combination is *up-to-date*, *not up-to-date* or *out of support*. Finally, the table provides a count of devices that fall into this category.
|
||||||
## Deployment Status by Servicing Channel
|
|
||||||
|
## Deployment Status by Servicing Channel
|
||||||
To effectively track deployment, **Deployment Status Blades** are divided into each Servicing Channel chosen for the device. This is because Deployment for each channel will happen at different periods in time and feature updates are targeted separately for each channel. Within each Deployment Status tile, devices are aggregated on their feature update distribution, and the columns list the states each device is in.
|
|
||||||
|
To effectively track deployment, **Deployment Status Blades** are divided into each Servicing Channel chosen for the device. This is because Deployment for each channel will happen at different periods in time and feature updates are targeted separately for each channel. Within each Deployment Status tile, devices are aggregated on their feature update distribution, and the columns list the states each device is in.
|
||||||
Refer to the following list for what each state means:
|
|
||||||
* **Installed** devices are devices that have completed installation for the given update.
|
Refer to the following list for what each state means:
|
||||||
* When a device is counted as **In Progress**, it has begun the feature update installation.
|
* **Installed** devices are devices that have completed installation for the given update.
|
||||||
* Devices that are **scheduled next 7 days** are all devices that were deferred from installing the Feature update using [Windows Update for Business Settings](waas-manage-updates-wufb.md) and are set to begin installation in the next 7 days.
|
* When a device is counted as **In Progress**, it has begun the feature update installation.
|
||||||
* Devices that have failed the given feature update installation are counted as **Update failed**.
|
* Devices that are **scheduled next 7 days** are all devices that were deferred from installing the Feature update using [Windows Update for Business Settings](waas-manage-updates-wufb.md) and are set to begin installation in the next 7 days.
|
||||||
* If a device should be, in some way, progressing toward this security update, but its status cannot be inferred, it will count as **Status Unknown**. Devices not using Windows Update are the most likely devices to fall into this category.
|
* Devices that have failed the given feature update installation are counted as **Update failed**.
|
||||||
|
* If a device should be, in some way, progressing toward this security update, but its status cannot be inferred, it will count as **Status Unknown**. Devices not using Windows Update are the most likely devices to fall into this category.
|
||||||
## Compatibility holds
|
|
||||||
|
## Compatibility holds
|
||||||
Microsoft uses diagnostic data to determine whether devices that use Windows Update are ready for a feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *compatibility hold* is generated to delay the device’s upgrade and safeguard the end-user experience. Holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all compatibility holds on the Windows 10 release information page for any given release.
|
|
||||||
|
Microsoft uses diagnostic data to determine whether devices that use Windows Update are ready for a feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *compatibility hold* is generated to delay the device’s upgrade and safeguard the end-user experience. Holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all compatibility holds on the Windows 10 release information page for any given release.
|
||||||
To learn how compatibility holds are reflected in the experience, see [Update compliance perspectives](update-compliance-perspectives.md#deployment-status).
|
|
||||||
|
To learn how compatibility holds are reflected in the experience, see [Update compliance perspectives](update-compliance-perspectives.md#deployment-status).
|
||||||
### Opting out of compatibility hold
|
|
||||||
|
### Opting out of compatibility hold
|
||||||
Microsoft will release a device from a compatibility hold when it has determined it can safely and smoothly install a feature update, but you are ultimately in control of your devices and can opt out if desired. To opt out, set the registry key **HKLM\Software\Microsoft\Windows NT\CurrentVersion\502505fe-762c-4e80-911e-0c3fa4c63fb0** to a name of **DataRequireGatedScanForFeatureUpdates** and a value of **0**.
|
|
||||||
|
Microsoft will release a device from a compatibility hold when it has determined it can safely and smoothly install a feature update, but you are ultimately in control of your devices and can opt out if desired. To opt out, set the registry key **HKLM\Software\Microsoft\Windows NT\CurrentVersion\502505fe-762c-4e80-911e-0c3fa4c63fb0** to a name of **DataRequireGatedScanForFeatureUpdates** and a value of **0**.
|
||||||
|
|
||||||
Setting this registry key to **0** will force the device to opt out from *all* compatibility holds. Any other value, or deleting the key, will resume compatibility protection on the device.
|
|
||||||
|
Setting this registry key to **0** will force the device to opt out from *all* compatibility holds. Any other value, or deleting the key, will resume compatibility protection on the device.
|
||||||
|
|
||||||
|
|||||||
@ -1,46 +1,47 @@
|
|||||||
---
|
---
|
||||||
title: Update Compliance - Need Attention! report
|
title: Update Compliance - Need Attention! report
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
description: an overview of the Update Compliance Need Attention! report
|
description: an overview of the Update Compliance Need Attention! report
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.pagetype: deploy
|
ms.pagetype: deploy
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.author: greglin
|
author: jaimeo
|
||||||
ms.collection: M365-analytics
|
ms.author: jaimeo
|
||||||
ms.topic: article
|
ms.collection: M365-analytics
|
||||||
---
|
ms.topic: article
|
||||||
|
---
|
||||||
# Needs attention!
|
|
||||||
|
# Needs attention!
|
||||||
|
|
||||||
The **Needs attention!** section provides a breakdown of all Windows 10 device and update issues detected by Update Compliance. The summary tile for this section counts the number of devices that have issues, while the blades within break down the issues encountered. Finally, a [list of queries](#list-of-queries) blade in this section contains queries that provide values but do not fit within any other main section.
|
|
||||||
|
The **Needs attention!** section provides a breakdown of all Windows 10 device and update issues detected by Update Compliance. The summary tile for this section counts the number of devices that have issues, while the blades within break down the issues encountered. Finally, a [list of queries](#list-of-queries) blade in this section contains queries that provide values but do not fit within any other main section.
|
||||||
>[!NOTE]
|
|
||||||
>The summary tile counts the number of devices that have issues, while the blades within the section break down the issues encountered. A single device can have more than one issue, so these numbers might not add up.
|
>[!NOTE]
|
||||||
|
>The summary tile counts the number of devices that have issues, while the blades within the section break down the issues encountered. A single device can have more than one issue, so these numbers might not add up.
|
||||||
The different issues are broken down by Device Issues and Update Issues:
|
|
||||||
|
The different issues are broken down by Device Issues and Update Issues:
|
||||||
## Device Issues
|
|
||||||
|
## Device Issues
|
||||||
* **Missing multiple security updates:** This issue occurs when a device is behind by two or more security updates. These devices might be more vulnerable and should be investigated and updated.
|
|
||||||
* **Out of support OS Version:** This issue occurs when a device has fallen out of support due to the version of Windows 10 it is running. When a device has fallen out of support, it will no longer receive important security updates, and might be vulnerable. These devices should be updated to a supported version of Windows 10.
|
* **Missing multiple security updates:** This issue occurs when a device is behind by two or more security updates. These devices might be more vulnerable and should be investigated and updated.
|
||||||
|
* **Out of support OS Version:** This issue occurs when a device has fallen out of support due to the version of Windows 10 it is running. When a device has fallen out of support, it will no longer receive important security updates, and might be vulnerable. These devices should be updated to a supported version of Windows 10.
|
||||||
## Update Issues
|
|
||||||
|
## Update Issues
|
||||||
* **Failed:** This issue occurs when an error halts the process of downloading and applying an update on a device. Some of these errors might be transient, but should be investigated further to be sure.
|
|
||||||
* **Cancelled**: This issue occurs when a user cancels the update process.
|
* **Failed:** This issue occurs when an error halts the process of downloading and applying an update on a device. Some of these errors might be transient, but should be investigated further to be sure.
|
||||||
* **Rollback**: This issue occurs when a fatal error occurs during a feature update, and the device is rolled back to the previous version.
|
* **Cancelled**: This issue occurs when a user cancels the update process.
|
||||||
* **Uninstalled**: This issue occurs when a feature update is uninstalled from a device by a user or an administrator. Note that this might not be a problem if the uninstallation was intentional, but is highlighted as it might need attention.
|
* **Rollback**: This issue occurs when a fatal error occurs during a feature update, and the device is rolled back to the previous version.
|
||||||
* **Progress stalled:** This issue occurs when an update is in progress, but has not completed over a period of 10 days.
|
* **Uninstalled**: This issue occurs when a feature update is uninstalled from a device by a user or an administrator. Note that this might not be a problem if the uninstallation was intentional, but is highlighted as it might need attention.
|
||||||
|
* **Progress stalled:** This issue occurs when an update is in progress, but has not completed over a period of 10 days.
|
||||||
Selecting any of the issues will take you to a [Log Analytics](https://docs.microsoft.com/azure/log-analytics/query-language/get-started-analytics-portal) view with all devices that have the given issue.
|
|
||||||
|
Selecting any of the issues will take you to a [Log Analytics](https://docs.microsoft.com/azure/log-analytics/query-language/get-started-analytics-portal) view with all devices that have the given issue.
|
||||||
>[!NOTE]
|
|
||||||
>This blade also has a link to the [Setup Diagnostic Tool](https://docs.microsoft.com/windows/deployment/upgrade/setupdiag), a standalone tool you can use to obtain details about why a Windows 10 feature update was unsuccessful.
|
>[!NOTE]
|
||||||
|
>This blade also has a link to the [Setup Diagnostic Tool](https://docs.microsoft.com/windows/deployment/upgrade/setupdiag), a standalone tool you can use to obtain details about why a Windows 10 feature update was unsuccessful.
|
||||||
## List of Queries
|
|
||||||
|
## List of Queries
|
||||||
The **List of Queries** blade is in the **Needs Attention** section of Update Compliance. This blade contains a list of queries with a description and a link to the query. These queries contain important meta-information that did not fit within any specific section or were listed to serve as a good starting point for modification into custom queries.
|
|
||||||
|
The **List of Queries** blade is in the **Needs Attention** section of Update Compliance. This blade contains a list of queries with a description and a link to the query. These queries contain important meta-information that did not fit within any specific section or were listed to serve as a good starting point for modification into custom queries.
|
||||||
|
|||||||
@ -1,65 +1,66 @@
|
|||||||
---
|
---
|
||||||
title: Update Compliance - Perspectives
|
title: Update Compliance - Perspectives
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
description: an overview of Update Compliance Perspectives
|
description: an overview of Update Compliance Perspectives
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.pagetype: deploy
|
ms.pagetype: deploy
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.author: greglin
|
author: jaimeo
|
||||||
ms.collection: M365-analytics
|
ms.author: jaimeo
|
||||||
ms.topic: article
|
ms.collection: M365-analytics
|
||||||
---
|
ms.topic: article
|
||||||
|
---
|
||||||
# Perspectives
|
|
||||||
|
# Perspectives
|
||||||
|
|
||||||
|
|
||||||
Perspectives are elaborations on specific queries hand-crafted by developers which data views that provide deeper insight into your data. Perspectives are loaded whenever clicking into more detailed views from both the Security Update Status section and Feature Update Status section of Update Compliance.
|
|
||||||
|
Perspectives are elaborations on specific queries hand-crafted by developers which data views that provide deeper insight into your data. Perspectives are loaded whenever clicking into more detailed views from both the Security Update Status section and Feature Update Status section of Update Compliance.
|
||||||
There is only one perspective framework; it is for **Update Deployment Status**. The same framework is utilized for both feature and quality updates.
|
|
||||||
|
There is only one perspective framework; it is for **Update Deployment Status**. The same framework is utilized for both feature and quality updates.
|
||||||
The first blade is the **Build Summary** blade. This blade summarizes the most important aspects of the given build being queried, listing the total number of devices, the total number of update failures for the build, and a breakdown of the different errors encountered.
|
|
||||||
|
The first blade is the **Build Summary** blade. This blade summarizes the most important aspects of the given build being queried, listing the total number of devices, the total number of update failures for the build, and a breakdown of the different errors encountered.
|
||||||
The second blade is the **Deferral Configurations** blade, breaking down Windows Update for Business deferral settings (if any).
|
|
||||||
|
The second blade is the **Deferral Configurations** blade, breaking down Windows Update for Business deferral settings (if any).
|
||||||
## Deployment status
|
|
||||||
|
## Deployment status
|
||||||
The third blade is the **Deployment Status** blade. This defines how many days it has been since the queried version has been released, and breaks down the various states in the update funnel each device has reported to be in. The possible states are as follows:
|
|
||||||
|
The third blade is the **Deployment Status** blade. This defines how many days it has been since the queried version has been released, and breaks down the various states in the update funnel each device has reported to be in. The possible states are as follows:
|
||||||
| State | Description |
|
|
||||||
| --- | --- |
|
| State | Description |
|
||||||
| Update Completed | When a device has finished the update process and is on the queried update, it will display here as Update completed. |
|
| --- | --- |
|
||||||
| In Progress | Devices that report they are “In Progress” are one of the various stages of installing an update; these stages are reported in the Detailed Deployment Status blade. |
|
| Update Completed | When a device has finished the update process and is on the queried update, it will display here as Update completed. |
|
||||||
| Deferred | When a device’s Windows Update for Business deferral policy dictates that the update is not yet applicable due to deferral, it will report as such in this blade. |
|
| In Progress | Devices that report they are “In Progress” are one of the various stages of installing an update; these stages are reported in the Detailed Deployment Status blade. |
|
||||||
| Progress stalled | Devices that report as “Progress stalled” have been stuck at “In progress” for more than 7 days. |
|
| Deferred | When a device’s Windows Update for Business deferral policy dictates that the update is not yet applicable due to deferral, it will report as such in this blade. |
|
||||||
| Cancelled | The update was cancelled. |
|
| Progress stalled | Devices that report as “Progress stalled” have been stuck at “In progress” for more than 7 days. |
|
||||||
| Blocked | There is a hard block on the update being completed. This could be that another update must be completed before this one, or some other task is blocking the installation of the update. |
|
| Cancelled | The update was cancelled. |
|
||||||
| Unknown | Devices that do not report detailed information on the status of their updates will report Unknown. This is most likely devices that do not use Windows Update for deployment. |
|
| Blocked | There is a hard block on the update being completed. This could be that another update must be completed before this one, or some other task is blocking the installation of the update. |
|
||||||
| Update paused | These devices have Windows Update for Business pause enabled, preventing this update from being installed. |
|
| Unknown | Devices that do not report detailed information on the status of their updates will report Unknown. This is most likely devices that do not use Windows Update for deployment. |
|
||||||
| Failed | A device is unable to install an update. This failure could be linked to a serious error in the update installation process or, in some cases, a [compatibility hold](update-compliance-feature-update-status.md#compatibility-holds). |
|
| Update paused | These devices have Windows Update for Business pause enabled, preventing this update from being installed. |
|
||||||
|
| Failed | A device is unable to install an update. This failure could be linked to a serious error in the update installation process or, in some cases, a [compatibility hold](update-compliance-feature-update-status.md#compatibility-holds). |
|
||||||
## Detailed deployment status
|
|
||||||
|
## Detailed deployment status
|
||||||
The final blade is the **Detailed Deployment Status** blade. This blade breaks down the detailed stage of deployment a device is in, beyond the generalized terms defined in Deployment Status. The following are the possible stages a device can report:
|
|
||||||
|
The final blade is the **Detailed Deployment Status** blade. This blade breaks down the detailed stage of deployment a device is in, beyond the generalized terms defined in Deployment Status. The following are the possible stages a device can report:
|
||||||
| State | Description |
|
|
||||||
| --- | --- |
|
| State | Description |
|
||||||
| Update deferred | When a device’s Windows Update for Business policy dictates the update is deferred. |
|
| --- | --- |
|
||||||
| Update paused | The device’s Windows Update for Business policy dictates the update is paused from being offered. |
|
| Update deferred | When a device’s Windows Update for Business policy dictates the update is deferred. |
|
||||||
| Update offered | The device has been offered the update, but has not begun downloading it. |
|
| Update paused | The device’s Windows Update for Business policy dictates the update is paused from being offered. |
|
||||||
| Pre-Download tasks passed | The device has finished all necessary tasks prior to downloading the update. |
|
| Update offered | The device has been offered the update, but has not begun downloading it. |
|
||||||
| Compatibility hold | The device has been placed under a *compatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared. For more information see [Feature Update Status report](update-compliance-feature-update-status.md#compatibility-holds) |
|
| Pre-Download tasks passed | The device has finished all necessary tasks prior to downloading the update. |
|
||||||
| Download Started | The update has begun downloading on the device. |
|
| Compatibility hold | The device has been placed under a *compatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared. For more information see [Feature Update Status report](update-compliance-feature-update-status.md#compatibility-holds) |
|
||||||
| Download Succeeded | The update has successfully completed downloading. |
|
| Download Started | The update has begun downloading on the device. |
|
||||||
| Pre-Install Tasks Passed | Tasks that must be completed prior to installing the update have been completed. |
|
| Download Succeeded | The update has successfully completed downloading. |
|
||||||
| Install Started | Installation of the update has begun. |
|
| Pre-Install Tasks Passed | Tasks that must be completed prior to installing the update have been completed. |
|
||||||
| Reboot Required | The device has finished installing the update, and a reboot is required before the update can be completed.
|
| Install Started | Installation of the update has begun. |
|
||||||
| Reboot Pending | The device has a scheduled reboot to apply the update. |
|
| Reboot Required | The device has finished installing the update, and a reboot is required before the update can be completed.
|
||||||
| Reboot Initiated | The scheduled reboot has been initiated. |
|
| Reboot Pending | The device has a scheduled reboot to apply the update. |
|
||||||
| Update Completed/Commit | The update has successfully installed. |
|
| Reboot Initiated | The scheduled reboot has been initiated. |
|
||||||
|
| Update Completed/Commit | The update has successfully installed. |
|
||||||
>[!NOTE]
|
|
||||||
>Interacting with any rows in the perspective view will automatically apply the given value to the query and execute it with the new parameter, narrowing the perspective to devices that satisfy that criteria. For example, clicking “Not configured (-1)” devices in Deferral Configurations will filter the query to only contain devices that do not have a deferral configuration. These filters can also be applied to queries via the filter sidebar.
|
>[!NOTE]
|
||||||
|
>Interacting with any rows in the perspective view will automatically apply the given value to the query and execute it with the new parameter, narrowing the perspective to devices that satisfy that criteria. For example, clicking “Not configured (-1)” devices in Deferral Configurations will filter the query to only contain devices that do not have a deferral configuration. These filters can also be applied to queries via the filter sidebar.
|
||||||
|
|||||||
@ -1,42 +1,43 @@
|
|||||||
---
|
---
|
||||||
title: Update Compliance - Windows Defender AV Status report
|
title: Update Compliance - Windows Defender AV Status report
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
description: an overview of the Windows Defender AV Status report
|
description: an overview of the Windows Defender AV Status report
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.pagetype: deploy
|
ms.pagetype: deploy
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.author: greglin
|
author: jaimeo
|
||||||
ms.collection: M365-analytics
|
ms.author: jaimeo
|
||||||
ms.topic: article
|
ms.collection: M365-analytics
|
||||||
---
|
ms.topic: article
|
||||||
|
---
|
||||||
# Windows Defender AV Status
|
|
||||||
|
# Windows Defender AV Status
|
||||||
|
|
||||||
|
|
||||||
The Windows Defender AV Status section deals with data concerning signature and threat status for devices that use Windows Defender Antivirus. The section tile in the [Overview Blade](update-compliance-using.md#overview-blade) provides the percentage of devices with insufficient protection – this percentage only considers devices using Windows Defender Antivirus.
|
|
||||||
|
The Windows Defender AV Status section deals with data concerning signature and threat status for devices that use Windows Defender Antivirus. The section tile in the [Overview Blade](update-compliance-using.md#overview-blade) provides the percentage of devices with insufficient protection – this percentage only considers devices using Windows Defender Antivirus.
|
||||||
>[!NOTE]
|
|
||||||
>Update Compliance's Windows Defender Antivirus status is compatible with E3, B, F1, VL Professional and below licenses. Devices with an E5 license are not shown here; devices with an E5 license can be monitored using the [Windows Defender ATP portal](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/configure-endpoints-windows-defender-advanced-threat-protection). If you'd like to learn more about Windows 10 licensing, see the [Windows 10 product licensing options](https://www.microsoft.com/Licensing/product-licensing/windows10.aspx).
|
>[!NOTE]
|
||||||
|
>Update Compliance's Windows Defender Antivirus status is compatible with E3, B, F1, VL Professional and below licenses. Devices with an E5 license are not shown here; devices with an E5 license can be monitored using the [Windows Defender ATP portal](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/configure-endpoints-windows-defender-advanced-threat-protection). If you'd like to learn more about Windows 10 licensing, see the [Windows 10 product licensing options](https://www.microsoft.com/Licensing/product-licensing/windows10.aspx).
|
||||||
# Windows Defender AV Status sections
|
|
||||||
The **Protection Status** blade gives a count for devices that have either out-of-date signatures or real-time protection turned off. Below, it gives a more detailed breakdown of the two issues. Selecting any of these statuses will navigate you to a Log Search view containing the query.
|
# Windows Defender AV Status sections
|
||||||
|
The **Protection Status** blade gives a count for devices that have either out-of-date signatures or real-time protection turned off. Below, it gives a more detailed breakdown of the two issues. Selecting any of these statuses will navigate you to a Log Search view containing the query.
|
||||||
The **Threat Status** blade shows, among devices that have encountered threats, how many were and were not remediated successfully. It also provides a detailed count. Selecting either of these will take you to the respective query in Log Search for further investigation.
|
|
||||||
|
The **Threat Status** blade shows, among devices that have encountered threats, how many were and were not remediated successfully. It also provides a detailed count. Selecting either of these will take you to the respective query in Log Search for further investigation.
|
||||||
Here are some important terms to consider when using the Windows Defender AV Status section of Update Compliance:
|
|
||||||
* **Signature out of date** devices are devices with a signature older than 14 days.
|
Here are some important terms to consider when using the Windows Defender AV Status section of Update Compliance:
|
||||||
* **No real-time protection** devices are devices that are using Windows Defender AV but have turned off real-time protection.
|
* **Signature out of date** devices are devices with a signature older than 14 days.
|
||||||
* **Recently disappeared** devices are devices that were previously seen by Windows Defender AV and are no longer seen in the past 7 days.
|
* **No real-time protection** devices are devices that are using Windows Defender AV but have turned off real-time protection.
|
||||||
* **Remediation failed** devices are devices where Windows Defender AV failed to remediate the threat. This could be due to a number of reasons, including a full disk, network error, operation aborted, etc. Manual intervention might be needed from IT team.
|
* **Recently disappeared** devices are devices that were previously seen by Windows Defender AV and are no longer seen in the past 7 days.
|
||||||
* **Not assessed** devices are devices where either a non-Microsoft AV solution is used or it has been more than 7 days since the device recently disappeared.
|
* **Remediation failed** devices are devices where Windows Defender AV failed to remediate the threat. This could be due to a number of reasons, including a full disk, network error, operation aborted, etc. Manual intervention might be needed from IT team.
|
||||||
|
* **Not assessed** devices are devices where either a non-Microsoft AV solution is used or it has been more than 7 days since the device recently disappeared.
|
||||||
## Windows Defender data latency
|
|
||||||
Because of the way Windows Defender is associated with the rest of Windows device data, Defender data for new devices might take much longer to appear than other data types. This process could take up to 28 days.
|
## Windows Defender data latency
|
||||||
|
Because of the way Windows Defender is associated with the rest of Windows device data, Defender data for new devices might take much longer to appear than other data types. This process could take up to 28 days.
|
||||||
## Related topics
|
|
||||||
|
## Related topics
|
||||||
- [Windows Defender Antivirus pre-requisites](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/troubleshoot-reporting#confirm-pre-requisites)
|
|
||||||
|
- [Windows Defender Antivirus pre-requisites](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/troubleshoot-reporting#confirm-pre-requisites)
|
||||||
|
|||||||
@ -4,9 +4,9 @@ description: Use BranchCache to optimize network bandwidth during update deploym
|
|||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
author: greg-lindsay
|
author: jaimeo
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.author: greglin
|
ms.author: jaimeo
|
||||||
ms.date: 07/27/2017
|
ms.date: 07/27/2017
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
|
|||||||
@ -8,9 +8,9 @@ ms.prod: w10
|
|||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: jaimeo
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.author: greglin
|
ms.author: jaimeo
|
||||||
ms.collection: M365-modern-desktop
|
ms.collection: M365-modern-desktop
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
---
|
---
|
||||||
|
|||||||
@ -4,9 +4,9 @@ description: Use Windows Update for Business deployments with management tools s
|
|||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
author: greg-lindsay
|
author: jaimeo
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.author: greglin
|
ms.author: jaimeo
|
||||||
ms.date: 07/27/2017
|
ms.date: 07/27/2017
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
|
|||||||
@ -1,51 +1,52 @@
|
|||||||
---
|
---
|
||||||
title: Windows as a service
|
title: Windows as a service
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.manager: elizapo
|
ms.manager: elizapo
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.author: greglin
|
author: jaimeo
|
||||||
ms.date: 12/19/2018
|
ms.author: jaimeo
|
||||||
ms.reviewer:
|
ms.date: 12/19/2018
|
||||||
manager: laurawi
|
ms.reviewer:
|
||||||
ms.localizationpriority: high
|
manager: laurawi
|
||||||
ms.topic: article
|
ms.localizationpriority: high
|
||||||
---
|
ms.topic: article
|
||||||
# Windows as a service - More news
|
---
|
||||||
|
# Windows as a service - More news
|
||||||
Here's more news about [Windows as a service](windows-as-a-service.md):
|
|
||||||
|
Here's more news about [Windows as a service](windows-as-a-service.md):
|
||||||
<ul>
|
|
||||||
<li><a href="https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency">Improving the Windows 10 update experience with control, quality and transparency</a> - April 4, 2019</li>
|
<ul>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Call-to-action-review-your-Windows-Update-for-Business-deferral/ba-p/394244">Call to action: review your Windows Update for Business deferral values</a> - April 3, 2019</li>
|
<li><a href="https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency">Improving the Windows 10 update experience with control, quality and transparency</a> - April 4, 2019</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-version-1809-designated-for-broad-deployment/ba-p/389540">Windows 10, version 1809 designated for broad deployment</a> - March 28, 2019</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Call-to-action-review-your-Windows-Update-for-Business-deferral/ba-p/394244">Call to action: review your Windows Update for Business deferral values</a> - April 3, 2019</li>
|
||||||
<li><a href="https://blogs.windows.com/windowsexperience/2019/03/06/data-insights-and-listening-to-improve-the-customer-experience">Data, insights and listening to improve the customer experience</a> - March 6, 2019</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-version-1809-designated-for-broad-deployment/ba-p/389540">Windows 10, version 1809 designated for broad deployment</a> - March 28, 2019</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Getting-to-know-the-Windows-update-history-pages/ba-p/355079">Getting to know the Windows update history pages</a> - February 21, 2019</li>
|
<li><a href="https://blogs.windows.com/windowsexperience/2019/03/06/data-insights-and-listening-to-improve-the-customer-experience">Data, insights and listening to improve the customer experience</a> - March 6, 2019</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-and-the-retirement-of-SAC-T/ba-p/339523">Windows Update for Business and the retirement of SAC-T</a> - February 14, 2019</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Getting-to-know-the-Windows-update-history-pages/ba-p/355079">Getting to know the Windows update history pages</a> - February 21, 2019</li>
|
||||||
<li><a href="https://blogs.windows.com/windowsexperience/2019/01/15/application-compatibility-in-the-windows-ecosystem/#A8urpp1QEp6DHzmP.97">Application compatibility in the Windows ecosystem</a> - January 15, 2019</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-and-the-retirement-of-SAC-T/ba-p/339523">Windows Update for Business and the retirement of SAC-T</a> - February 14, 2019</li>
|
||||||
<li><a href="https://blogs.windows.com/windowsexperience/2018/12/10/windows-monthly-security-and-quality-updates-overview/#UJJpisSpvyLokbHm.97">Windows monthly security and quality updates overview</a> - January 10, 2019</li>
|
<li><a href="https://blogs.windows.com/windowsexperience/2019/01/15/application-compatibility-in-the-windows-ecosystem/#A8urpp1QEp6DHzmP.97">Application compatibility in the Windows ecosystem</a> - January 15, 2019</li>
|
||||||
<li><a href="https://blogs.windows.com/windowsexperience/2018/12/19/driver-quality-in-the-windows-ecosystem/#ktuodfovWAMAkssM.97">Driver quality in the Windows ecosystem</a> - December 19, 2018</li>
|
<li><a href="https://blogs.windows.com/windowsexperience/2018/12/10/windows-monthly-security-and-quality-updates-overview/#UJJpisSpvyLokbHm.97">Windows monthly security and quality updates overview</a> - January 10, 2019</li>
|
||||||
<li><a href="http://m365mdp.mpsn.libsynpro.com/001-windows-10-monthly-quality-updates">Modern Desktop Podcast - Episode 001 – Windows 10 Monthly Quality Updates</a> - December 18, 2018</li>
|
<li><a href="https://blogs.windows.com/windowsexperience/2018/12/19/driver-quality-in-the-windows-ecosystem/#ktuodfovWAMAkssM.97">Driver quality in the Windows ecosystem</a> - December 19, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Measuring-Delivery-Optimization-and-its-impact-to-your-network/ba-p/301809#M409">Measuring Delivery Optimization and its impact to your network</a> - December 13, 2018</li>
|
<li><a href="http://m365mdp.mpsn.libsynpro.com/001-windows-10-monthly-quality-updates">Modern Desktop Podcast - Episode 001 – Windows 10 Monthly Quality Updates</a> - December 18, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/LTSC-What-is-it-and-when-should-it-be-used/ba-p/293181">LTSC: What is it, and when should it be used?</a> - November 29, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Measuring-Delivery-Optimization-and-its-impact-to-your-network/ba-p/301809#M409">Measuring Delivery Optimization and its impact to your network</a> - December 13, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Local-Experience-Packs-What-are-they-and-when-should-you-use/ba-p/286841">Local Experience Packs: What are they and when should you use them?</a> - November 14, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/LTSC-What-is-it-and-when-should-it-be-used/ba-p/293181">LTSC: What is it, and when should it be used?</a> - November 29, 2018</li>
|
||||||
<li><a href="https://blogs.windows.com/windowsexperience/2018/11/13/resuming-the-rollout-of-the-windows-10-october-2018-update/#amAFU5YS1igMQRoB.97">Resuming the Rollout of the Windows 10 October 2018 Update</a> - November 13, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Local-Experience-Packs-What-are-they-and-when-should-you-use/ba-p/286841">Local Experience Packs: What are they and when should you use them?</a> - November 14, 2018</li>
|
||||||
<li><a href="https://blogs.windows.com/windowsexperience/2018/11/13/windows-10-quality-approach-for-a-complex-ecosystem/#9VlPpT2qGIlPAg5a.97">Windows 10 Quality Approach for a Complex Ecosystem</a> - November 13, 2018</li>
|
<li><a href="https://blogs.windows.com/windowsexperience/2018/11/13/resuming-the-rollout-of-the-windows-10-october-2018-update/#amAFU5YS1igMQRoB.97">Resuming the Rollout of the Windows 10 October 2018 Update</a> - November 13, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Delivery-Optimization-Scenarios-and-configuration-options/ba-p/280195">Delivery Optimization: Scenarios and Configuration Options</a> - October 30, 2018</li>
|
<li><a href="https://blogs.windows.com/windowsexperience/2018/11/13/windows-10-quality-approach-for-a-complex-ecosystem/#9VlPpT2qGIlPAg5a.97">Windows 10 Quality Approach for a Complex Ecosystem</a> - November 13, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Language-pack-acquisition-and-retention-for-enterprise-devices/ba-p/275404">Language Pack Acquisition and Retention for Enterprise Devices</a> - October 18, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Delivery-Optimization-Scenarios-and-configuration-options/ba-p/280195">Delivery Optimization: Scenarios and Configuration Options</a> - October 30, 2018</li>
|
||||||
<li><a href="https://blogs.windows.com/windowsexperience/2018/10/09/updated-version-of-windows-10-october-2018-update-released-to-windows-insiders/#MDZYGkj6ZehHyF1g.97">Updated Version of Windows 10 October 2018 Update Released to Windows Insiders</a> - October 9, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Language-pack-acquisition-and-retention-for-enterprise-devices/ba-p/275404">Language Pack Acquisition and Retention for Enterprise Devices</a> - October 18, 2018</li>
|
||||||
<li><a href="https://blogs.windows.com/windowsexperience/2018/10/02/how-to-get-the-windows-10-october-2018-update/#T4LJQ3OzDkCR72em.97">How to get the Windows 10 October 2018 Update</a> - October 2, 2018</li>
|
<li><a href="https://blogs.windows.com/windowsexperience/2018/10/09/updated-version-of-windows-10-october-2018-update-released-to-windows-insiders/#MDZYGkj6ZehHyF1g.97">Updated Version of Windows 10 October 2018 Update Released to Windows Insiders</a> - October 9, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Reduced-Windows-10-package-size-downloads-for-x64-systems/ba-p/262386">Reducing Windows 10 Package Size Downloads for x64 Systems</a> - September 26, 2018</li>
|
<li><a href="https://blogs.windows.com/windowsexperience/2018/10/02/how-to-get-the-windows-10-october-2018-update/#T4LJQ3OzDkCR72em.97">How to get the Windows 10 October 2018 Update</a> - October 2, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-7-servicing-stack-updates-managing-change-and/ba-p/260434">Windows 7 Servicing Stack Updates: Managing Change and Appreciating Cumulative Updates</a> - September 21, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Reduced-Windows-10-package-size-downloads-for-x64-systems/ba-p/262386">Reducing Windows 10 Package Size Downloads for x64 Systems</a> - September 26, 2018</li>
|
||||||
<li><a href="https://www.microsoft.com/microsoft-365/blog/2018/09/06/helping-customers-shift-to-a-modern-desktop/">Helping customers shift to a modern desktop</a> - September 6, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-7-servicing-stack-updates-managing-change-and/ba-p/260434">Windows 7 Servicing Stack Updates: Managing Change and Appreciating Cumulative Updates</a> - September 21, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-amp-Windows-Analytics-a-real-world/ba-p/242417#M228">Windows Update for Business & Windows Analytics: a real-world experience</a> - September 5, 2018</li>
|
<li><a href="https://www.microsoft.com/microsoft-365/blog/2018/09/06/helping-customers-shift-to-a-modern-desktop/">Helping customers shift to a modern desktop</a> - September 6, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-next-for-Windows-10-and-Windows-Server-quality-updates/ba-p/229461">What's next for Windows 10 and Windows Server quality updates</a> - August 16, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-amp-Windows-Analytics-a-real-world/ba-p/242417#M228">Windows Update for Business & Windows Analytics: a real-world experience</a> - September 5, 2018</li>
|
||||||
<li><a href="https://www.youtube-nocookie.com/watch/BwB10v55WSk">Windows 10 monthly updates</a> - August 1, 2018 (<strong>video</strong>)</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-next-for-Windows-10-and-Windows-Server-quality-updates/ba-p/229461">What's next for Windows 10 and Windows Server quality updates</a> - August 16, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-update-servicing-cadence/ba-p/222376">Windows 10 update servicing cadence</a> - August 1, 2018</li>
|
<li><a href="https://www.youtube-nocookie.com/watch/BwB10v55WSk">Windows 10 monthly updates</a> - August 1, 2018 (<strong>video</strong>)</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-quality-updates-explained-amp-the-end-of-delta/ba-p/214426">Windows 10 quality updates explained and the end of delta updates</a> - July 11, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-update-servicing-cadence/ba-p/222376">Windows 10 update servicing cadence</a> - August 1, 2018</li>
|
||||||
<li><a href="https://blogs.windows.com/windowsexperience/2018/06/14/ai-powers-windows-10-april-2018-update-rollout/#67LrSyWdwgTyciSG.97">AI Powers Windows 10 April 2018 Update Rollout</a> - June 14, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-quality-updates-explained-amp-the-end-of-delta/ba-p/214426">Windows 10 quality updates explained and the end of delta updates</a> - July 11, 2018</li>
|
||||||
<li><a href="https://cloudblogs.microsoft.com/windowsserver/2018/06/12/windows-server-2008-sp2-servicing-changes/">Windows Server 2008 SP2 Servicing Changes</a> - June 12, 2018</li>
|
<li><a href="https://blogs.windows.com/windowsexperience/2018/06/14/ai-powers-windows-10-april-2018-update-rollout/#67LrSyWdwgTyciSG.97">AI Powers Windows 10 April 2018 Update Rollout</a> - June 14, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-Enhancements-diagnostics/ba-p/201978">Windows Update for Business - Enhancements, diagnostics, configuration</a> - June 7, 2018</li>
|
<li><a href="https://cloudblogs.microsoft.com/windowsserver/2018/06/12/windows-server-2008-sp2-servicing-changes/">Windows Server 2008 SP2 Servicing Changes</a> - June 12, 2018</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-and-the-disappearing-SAC-T/ba-p/199747">Windows 10 and the disappearing SAC-T</a> - May 31, 2018
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-Enhancements-diagnostics/ba-p/201978">Windows Update for Business - Enhancements, diagnostics, configuration</a> - June 7, 2018</li>
|
||||||
<li><a href="https://www.youtube.com/watch?v=EVzFIg_MhaE&t=5s">Manage update download size using Windows as a service</a> - March 30, 2018</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-and-the-disappearing-SAC-T/ba-p/199747">Windows 10 and the disappearing SAC-T</a> - May 31, 2018
|
||||||
</ul>
|
<li><a href="https://www.youtube.com/watch?v=EVzFIg_MhaE&t=5s">Manage update download size using Windows as a service</a> - March 30, 2018</li>
|
||||||
|
</ul>
|
||||||
|
|||||||
@ -8,10 +8,10 @@ ms.prod: w10
|
|||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: jaimeo
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.audience: itpro
|
ms.audience: itpro
|
||||||
author: greg-lindsay
|
author: jaimeo
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.collection: M365-modern-desktop
|
ms.collection: M365-modern-desktop
|
||||||
---
|
---
|
||||||
|
|||||||
@ -5,10 +5,10 @@ ms.prod: w10
|
|||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: jaimeo
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.audience: itpro
|
ms.audience: itpro
|
||||||
author: greg-lindsay
|
author: jaimeo
|
||||||
ms.date: 07/27/2017
|
ms.date: 07/27/2017
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
|
|||||||
@ -1,131 +1,133 @@
|
|||||||
---
|
---
|
||||||
title: Windows as a service
|
title: Windows as a service
|
||||||
ms.prod: windows-10
|
ms.prod: windows-10
|
||||||
layout: LandingPage
|
layout: LandingPage
|
||||||
ms.topic: landing-page
|
ms.topic: landing-page
|
||||||
ms.manager: elizapo
|
ms.manager: elizapo
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.audience: itpro
author: greg-lindsay
|
author: greg-lindsaauthor: jaimeo
|
||||||
ms.date: 01/24/2019
|
ms.audience: itpro
|
||||||
ms.reviewer:
|
author: jaimeo
|
||||||
manager: laurawi
|
ms.date: 01/24/2019
|
||||||
ms.localizationpriority: high
|
ms.reviewer:
|
||||||
ms.collection: M365-modern-desktop
|
manager: laurawi
|
||||||
---
|
ms.localizationpriority: high
|
||||||
# Windows as a service
|
ms.collection: M365-modern-desktop
|
||||||
|
---
|
||||||
Find the tools and resources you need to help deploy and support Windows as a service in your organization.
|
# Windows as a service
|
||||||
|
|
||||||
## Latest news, videos, & podcasts
|
Find the tools and resources you need to help deploy and support Windows as a service in your organization.
|
||||||
|
|
||||||
Find the latest and greatest news on Windows 10 deployment and servicing.
|
## Latest news, videos, & podcasts
|
||||||
|
|
||||||
**Discovering the Windows 10 Update history pages**
|
Find the latest and greatest news on Windows 10 deployment and servicing.
|
||||||
> [!VIDEO https://www.youtube-nocookie.com/embed/mTnAb9XjMPY]
|
|
||||||
|
**Discovering the Windows 10 Update history pages**
|
||||||
Everyone wins when transparency is a top priority. We want you to know when updates are available, as well as alert you to any potential issues you may encounter during or after you install an update. Bookmark the <a href="https://aka.ms/WindowsReleaseHealth">Windows release health dashboard</a> for near real-time information on known issues, workarounds, and resolutions--as well as the current status of the latest feature update rollout.
|
> [!VIDEO https://www.youtube-nocookie.com/embed/mTnAb9XjMPY]
|
||||||
|
|
||||||
The latest news:
|
Everyone wins when transparency is a top priority. We want you to know when updates are available, as well as alert you to any potential issues you may encounter during or after you install an update. Bookmark the <a href="https://aka.ms/WindowsReleaseHealth">Windows release health dashboard</a> for near real-time information on known issues, workarounds, and resolutions--as well as the current status of the latest feature update rollout.
|
||||||
<ul compact style="list-style: none">
|
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Upgrading-Windows-10-devices-with-installation-media-different/ba-p/746126">Upgrading Windows 10 devices with installation media different than the original OS install language</a> - July 9, 2019</li>
|
The latest news:
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Moving-to-the-next-Windows-10-feature-update-for-commercial/ba-p/732968">Moving to the next Windows 10 feature update for commercial customers</a> - July 1, 2019</li>
|
<ul compact style="list-style: none">
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Updating-Windows-10-version-1903-using-Configuration-Manager-or/ba-p/639100">Updating Windows 10, version 1903 using Configuration Manager or WSUS</a> - May 23, 2019</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Upgrading-Windows-10-devices-with-installation-media-different/ba-p/746126">Upgrading Windows 10 devices with installation media different than the original OS install language</a> - July 9, 2019</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-in-Windows-Update-for-Business-in-Windows-10-version/ba-p/622064">What’s new in Windows Update for Business in Windows 10, version 1903</a> - May 21, 2019</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Moving-to-the-next-Windows-10-feature-update-for-commercial/ba-p/732968">Moving to the next Windows 10 feature update for commercial customers</a> - July 1, 2019</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-for-IT-pros-in-Windows-10-version-1903/ba-p/622024">What’s new for IT pros in Windows 10, version 1903</a> - May 21, 2019</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Updating-Windows-10-version-1903-using-Configuration-Manager-or/ba-p/639100">Updating Windows 10, version 1903 using Configuration Manager or WSUS</a> - May 23, 2019</li>
|
||||||
<li><a href="https://blogs.windows.com/windowsexperience/2019/05/21/how-to-get-the-windows-10-may-2019-update">How to get the Windows 10 May 2019 Update</a> - May 21, 2019</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-in-Windows-Update-for-Business-in-Windows-10-version/ba-p/622064">What’s new in Windows Update for Business in Windows 10, version 1903</a> - May 21, 2019</li>
|
||||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/The-benefits-of-Windows-10-Dynamic-Update/ba-p/467847">The benefits of Windows 10 Dynamic Update</a> - April 17, 2019</li>
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-for-IT-pros-in-Windows-10-version-1903/ba-p/622024">What’s new for IT pros in Windows 10, version 1903</a> - May 21, 2019</li>
|
||||||
</ul>
|
<li><a href="https://blogs.windows.com/windowsexperience/2019/05/21/how-to-get-the-windows-10-may-2019-update">How to get the Windows 10 May 2019 Update</a> - May 21, 2019</li>
|
||||||
|
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/The-benefits-of-Windows-10-Dynamic-Update/ba-p/467847">The benefits of Windows 10 Dynamic Update</a> - April 17, 2019</li>
|
||||||
[See more news](waas-morenews.md). You can also check out the [Windows 10 blog](https://techcommunity.microsoft.com/t5/Windows-10-Blog/bg-p/Windows10Blog).
|
</ul>
|
||||||
|
|
||||||
## IT pro champs corner
|
[See more news](waas-morenews.md). You can also check out the [Windows 10 blog](https://techcommunity.microsoft.com/t5/Windows-10-Blog/bg-p/Windows10Blog).
|
||||||
Written by IT pros for IT pros, sharing real world examples and scenarios for Windows 10 deployment and servicing.
|
|
||||||
|
## IT pro champs corner
|
||||||
<img src="images/champs-2.png" alt="" width="640" height="320">
|
Written by IT pros for IT pros, sharing real world examples and scenarios for Windows 10 deployment and servicing.
|
||||||
|
|
||||||
<a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Tactical-considerations-for-creating-Windows-deployment-rings/ba-p/746979">**NEW** Tactical considerations for creating Windows deployment rings</a>
|
<img src="images/champs-2.png" alt="" width="640" height="320">
|
||||||
|
|
||||||
<a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-Enterprise-vs-Windows-10-Pro-Modern-management/ba-p/720445">**NEW** Windows 10 Enterprise vs. Windows 10 Pro: Modern management considerations for your organization</a>
|
<a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Tactical-considerations-for-creating-Windows-deployment-rings/ba-p/746979">**NEW** Tactical considerations for creating Windows deployment rings</a>
|
||||||
|
|
||||||
<a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Deployment-rings-The-hidden-strategic-gem-of-Windows-as-a/ba-p/659622">Deployment rings: The hidden [strategic] gem of Windows as a service</a>
|
<a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-Enterprise-vs-Windows-10-Pro-Modern-management/ba-p/720445">**NEW** Windows 10 Enterprise vs. Windows 10 Pro: Modern management considerations for your organization</a>
|
||||||
|
|
||||||
<a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Classifying-Windows-updates-in-common-deployment-tools/ba-p/331175">Classifying Windows updates in common deployment tools</a>
|
<a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Deployment-rings-The-hidden-strategic-gem-of-Windows-as-a/ba-p/659622">Deployment rings: The hidden [strategic] gem of Windows as a service</a>
|
||||||
|
|
||||||
<a href="https://docs.microsoft.com/windows-server/get-started/express-updates">Express updates for Windows Server 2016 re-enabled for November 2018 update
|
<a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Classifying-Windows-updates-in-common-deployment-tools/ba-p/331175">Classifying Windows updates in common deployment tools</a>
|
||||||
</a>
|
|
||||||
|
<a href="https://docs.microsoft.com/windows-server/get-started/express-updates">Express updates for Windows Server 2016 re-enabled for November 2018 update
|
||||||
<a href="https://support.microsoft.com/help/4472027/">2019 SHA-2 Code Signing Support requirement for Windows and WSUS</a>
|
</a>
|
||||||
|
|
||||||
<a href="https://go.microsoft.com/fwlink/?linkid=2005509">Deploying Windows 10 Feature Updates to 24/7 Mission Critical Devices</a>
|
<a href="https://support.microsoft.com/help/4472027/">2019 SHA-2 Code Signing Support requirement for Windows and WSUS</a>
|
||||||
|
|
||||||
## Discover
|
<a href="https://go.microsoft.com/fwlink/?linkid=2005509">Deploying Windows 10 Feature Updates to 24/7 Mission Critical Devices</a>
|
||||||
|
|
||||||
Learn more about Windows as a service and its value to your organization.
|
## Discover
|
||||||
|
|
||||||
<img src="images/discover-land.png">
|
Learn more about Windows as a service and its value to your organization.
|
||||||
|
|
||||||
<a href="waas-overview.md">Overview of Windows as a service</a>
|
<img src="images/discover-land.png">
|
||||||
|
|
||||||
<a href="waas-quick-start.md">Quick guide to Windows as a service</a>
|
<a href="waas-overview.md">Overview of Windows as a service</a>
|
||||||
|
|
||||||
<a href="windows-analytics-overview.md">Windows Analytics overview</a>
|
<a href="waas-quick-start.md">Quick guide to Windows as a service</a>
|
||||||
|
|
||||||
<a href="../deploy-whats-new.md">What's new in Windows 10 deployment</a>
|
<a href="windows-analytics-overview.md">Windows Analytics overview</a>
|
||||||
|
|
||||||
<a href="https://channel9.msdn.com/events/Ignite/2015/BRK3303">How Microsoft IT deploys Windows 10</a></font>
|
<a href="../deploy-whats-new.md">What's new in Windows 10 deployment</a>
|
||||||
|
|
||||||
## Plan
|
<a href="https://channel9.msdn.com/events/Ignite/2015/BRK3303">How Microsoft IT deploys Windows 10</a></font>
|
||||||
|
|
||||||
Prepare to implement Windows as a service effectively using the right tools, products, and strategies.
|
## Plan
|
||||||
|
|
||||||
<img src="images/plan-land.png" alt="" />
|
Prepare to implement Windows as a service effectively using the right tools, products, and strategies.
|
||||||
|
|
||||||
<a href="https://www.microsoft.com/windowsforbusiness/simplified-updates">Simplified updates</a>
|
<img src="images/plan-land.png" alt="" />
|
||||||
|
|
||||||
<a href="https://www.microsoft.com/itpro/windows-10/end-user-readiness">Windows 10 end user readiness</a>
|
<a href="https://www.microsoft.com/windowsforbusiness/simplified-updates">Simplified updates</a>
|
||||||
|
|
||||||
<a href="https://developer.microsoft.com/windows/ready-for-windows#/">Ready for Windows</a>
|
<a href="https://www.microsoft.com/itpro/windows-10/end-user-readiness">Windows 10 end user readiness</a>
|
||||||
|
|
||||||
<a href="../upgrade/manage-windows-upgrades-with-upgrade-readiness.md">Manage Windows upgrades with Upgrade Readiness</a>
|
<a href="https://developer.microsoft.com/windows/ready-for-windows#/">Ready for Windows</a>
|
||||||
|
|
||||||
<a href="https://www.microsoft.com/itshowcase/windows10deployment">Preparing your organization for a seamless Windows 10 deployment</a>
|
<a href="../upgrade/manage-windows-upgrades-with-upgrade-readiness.md">Manage Windows upgrades with Upgrade Readiness</a>
|
||||||
|
|
||||||
## Deploy
|
<a href="https://www.microsoft.com/itshowcase/windows10deployment">Preparing your organization for a seamless Windows 10 deployment</a>
|
||||||
|
|
||||||
Secure your organization's deployment investment.
|
## Deploy
|
||||||
|
|
||||||
<img src="images/deploy-land.png" alt="" />
|
Secure your organization's deployment investment.
|
||||||
|
|
||||||
<a href="index.md">Update Windows 10 in the enterprise</a>
|
<img src="images/deploy-land.png" alt="" />
|
||||||
|
|
||||||
<a href="https://www.microsoft.com/itshowcase/Article/Content/668/Deploying-Windows-10-at-Microsoft-as-an-inplace-upgrade">Deploying as an in-place upgrade</a>
|
<a href="index.md">Update Windows 10 in the enterprise</a>
|
||||||
|
|
||||||
<a href="waas-configure-wufb.md">Configure Windows Update for Business</a>
|
<a href="https://www.microsoft.com/itshowcase/Article/Content/668/Deploying-Windows-10-at-Microsoft-as-an-inplace-upgrade">Deploying as an in-place upgrade</a>
|
||||||
|
|
||||||
<a href="waas-optimize-windows-10-updates.md#express-update-delivery">Express update delivery</a>
|
<a href="waas-configure-wufb.md">Configure Windows Update for Business</a>
|
||||||
|
|
||||||
<a href="../planning/windows-10-deployment-considerations.md">Windows 10 deployment considerations</a>
|
<a href="waas-optimize-windows-10-updates.md#express-update-delivery">Express update delivery</a>
|
||||||
|
|
||||||
|
<a href="../planning/windows-10-deployment-considerations.md">Windows 10 deployment considerations</a>
|
||||||
## Microsoft Ignite 2018
|
|
||||||
<img src="images/ignite-land.jpg" alt="" width="640" height="320"/>
|
|
||||||
|
## Microsoft Ignite 2018
|
||||||
Looking to learn more? These informative session replays from Microsoft Ignite 2018 (complete with downloadable slide decks) can provide some great insights on Windows as a service.
|
<img src="images/ignite-land.jpg" alt="" width="640" height="320"/>
|
||||||
|
|
||||||
[BRK2417: What’s new in Windows Analytics: An Intro to Desktop Analytics](https://myignite.techcommunity.microsoft.com/sessions/64324#ignite-html-anchor)
|
Looking to learn more? These informative session replays from Microsoft Ignite 2018 (complete with downloadable slide decks) can provide some great insights on Windows as a service.
|
||||||
|
|
||||||
[BRK3018: Deploying Windows 10 in the enterprise using traditional and modern techniques](https://myignite.techcommunity.microsoft.com/sessions/64509#ignite-html-anchor)
|
[BRK2417: What’s new in Windows Analytics: An Intro to Desktop Analytics](https://myignite.techcommunity.microsoft.com/sessions/64324#ignite-html-anchor)
|
||||||
|
|
||||||
[BRK3019: Delivery Optimization deep dive: How to reduce internet bandwidth impact on your network](https://myignite.techcommunity.microsoft.com/sessions/64510#ignite-html-anchor)
|
[BRK3018: Deploying Windows 10 in the enterprise using traditional and modern techniques](https://myignite.techcommunity.microsoft.com/sessions/64509#ignite-html-anchor)
|
||||||
|
|
||||||
[BRK3020: Using AI to automate Windows and Office update staging with Windows Update for Business](https://myignite.techcommunity.microsoft.com/sessions/64513#ignite-html-anchor)
|
[BRK3019: Delivery Optimization deep dive: How to reduce internet bandwidth impact on your network](https://myignite.techcommunity.microsoft.com/sessions/64510#ignite-html-anchor)
|
||||||
|
|
||||||
[BRK3027: Deploying Windows 10: Making the update experience smooth and seamless](https://myignite.techcommunity.microsoft.com/sessions/64612#ignite-html-anchor)
|
[BRK3020: Using AI to automate Windows and Office update staging with Windows Update for Business](https://myignite.techcommunity.microsoft.com/sessions/64513#ignite-html-anchor)
|
||||||
|
|
||||||
[BRK3039: Windows 10 and Microsoft Office 365 ProPlus lifecycle and servicing update](https://myignite.techcommunity.microsoft.com/sessions/66763#ignite-html-anchor)
|
[BRK3027: Deploying Windows 10: Making the update experience smooth and seamless](https://myignite.techcommunity.microsoft.com/sessions/64612#ignite-html-anchor)
|
||||||
|
|
||||||
[BRK3211: Ask the Experts: Successfully deploying, servicing, managing Windows 10](https://myignite.techcommunity.microsoft.com/sessions/65963#ignite-html-anchor)
|
[BRK3039: Windows 10 and Microsoft Office 365 ProPlus lifecycle and servicing update](https://myignite.techcommunity.microsoft.com/sessions/66763#ignite-html-anchor)
|
||||||
|
|
||||||
[THR2234: Windows servicing and delivery fundamentals](https://myignite.techcommunity.microsoft.com/sessions/66741#ignite-html-anchor)
|
[BRK3211: Ask the Experts: Successfully deploying, servicing, managing Windows 10](https://myignite.techcommunity.microsoft.com/sessions/65963#ignite-html-anchor)
|
||||||
|
|
||||||
[THR3006: The pros and cons of LTSC in the enterprise](https://myignite.techcommunity.microsoft.com/sessions/64512#ignite-html-anchor)
|
[THR2234: Windows servicing and delivery fundamentals](https://myignite.techcommunity.microsoft.com/sessions/66741#ignite-html-anchor)
|
||||||
|
|
||||||
|
[THR3006: The pros and cons of LTSC in the enterprise](https://myignite.techcommunity.microsoft.com/sessions/64512#ignite-html-anchor)
|
||||||
|
|||||||
@ -1,365 +1,367 @@
|
|||||||
---
|
---
|
||||||
title: Windows Update error code list by component
|
title: Windows Update error code list by component
|
||||||
description: Reference information for Windows Update error codes
|
description: Reference information for Windows Update error codes
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl:
|
ms.mktglfcycl:
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.audience: itpro
author: greg-lindsay
|
ms.localizationprioauthor: jaimeo
|
||||||
ms.date: 09/18/2018
|
ms.audience: itpro
|
||||||
ms.reviewer:
|
author: jaimeo
|
||||||
manager: laurawi
|
ms.date: 09/18/2018
|
||||||
ms.topic: article
|
ms.reviewer:
|
||||||
---
|
manager: laurawi
|
||||||
|
ms.topic: article
|
||||||
# Windows Update error codes by component
|
---
|
||||||
|
|
||||||
>Applies to: Windows 10
|
# Windows Update error codes by component
|
||||||
|
|
||||||
|
>Applies to: Windows 10
|
||||||
This section lists the error codes for Microsoft Windows Update.
|
|
||||||
|
|
||||||
## Automatic Update Errors
|
This section lists the error codes for Microsoft Windows Update.
|
||||||
|
|
||||||
| Error code | Message | Description |
|
## Automatic Update Errors
|
||||||
|------------|-------------------------------|--------------------------------------------------------------------------------------------------------|
|
|
||||||
| 0x80243FFF | WU_E_AUCLIENT_UNEXPECTED | There was a user interface error not covered by another WU_E_AUCLIENT_\* error code. |
|
| Error code | Message | Description |
|
||||||
| 0x8024A000 | WU_E_AU_NOSERVICE | Automatic Updates was unable to service incoming requests. |
|
|------------|-------------------------------|--------------------------------------------------------------------------------------------------------|
|
||||||
| 0x8024A002 | WU_E_AU_NONLEGACYSERVER | The old version of the Automatic Updates client has stopped because the WSUS server has been upgraded. |
|
| 0x80243FFF | WU_E_AUCLIENT_UNEXPECTED | There was a user interface error not covered by another WU_E_AUCLIENT_\* error code. |
|
||||||
| 0x8024A003 | WU_E_AU_LEGACYCLIENTDISABLED | The old version of the Automatic Updates client was disabled. |
|
| 0x8024A000 | WU_E_AU_NOSERVICE | Automatic Updates was unable to service incoming requests. |
|
||||||
| 0x8024A004 | WU_E_AU_PAUSED | Automatic Updates was unable to process incoming requests because it was paused. |
|
| 0x8024A002 | WU_E_AU_NONLEGACYSERVER | The old version of the Automatic Updates client has stopped because the WSUS server has been upgraded. |
|
||||||
| 0x8024A005 | WU_E_AU_NO_REGISTERED_SERVICE | No unmanaged service is registered with AU. |
|
| 0x8024A003 | WU_E_AU_LEGACYCLIENTDISABLED | The old version of the Automatic Updates client was disabled. |
|
||||||
| 0x8024AFFF | WU_E_AU_UNEXPECTED | An Automatic Updates error not covered by another WU_E_AU \* code. |
|
| 0x8024A004 | WU_E_AU_PAUSED | Automatic Updates was unable to process incoming requests because it was paused. |
|
||||||
|
| 0x8024A005 | WU_E_AU_NO_REGISTERED_SERVICE | No unmanaged service is registered with AU. |
|
||||||
## Windows Update UI errors
|
| 0x8024AFFF | WU_E_AU_UNEXPECTED | An Automatic Updates error not covered by another WU_E_AU \* code. |
|
||||||
|
|
||||||
| Error code | Message | Description |
|
## Windows Update UI errors
|
||||||
|------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|
|
|
||||||
| 0x80243001 | WU_E_INSTALLATION_RESULTS_UNKNOWN_VERSION | The results of download and installation could not be read from the registry due to an unrecognized data format version. |
|
| Error code | Message | Description |
|
||||||
| 0x80243002 | WU_E_INSTALLATION_RESULTS_INVALID_DATA | The results of download and installation could not be read from the registry due to an invalid data format. |
|
|------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|
|
||||||
| 0x80243003 | WU_E_INSTALLATION_RESULTS_NOT_FOUND | The results of download and installation are not available; the operation may have failed to start. |
|
| 0x80243001 | WU_E_INSTALLATION_RESULTS_UNKNOWN_VERSION | The results of download and installation could not be read from the registry due to an unrecognized data format version. |
|
||||||
| 0x80243004 | WU_E_TRAYICON_FAILURE | A failure occurred when trying to create an icon in the taskbar notification area. |
|
| 0x80243002 | WU_E_INSTALLATION_RESULTS_INVALID_DATA | The results of download and installation could not be read from the registry due to an invalid data format. |
|
||||||
| 0x80243FFD | WU_E_NON_UI_MODE | Unable to show UI when in non-UI mode; WU client UI modules may not be installed. |
|
| 0x80243003 | WU_E_INSTALLATION_RESULTS_NOT_FOUND | The results of download and installation are not available; the operation may have failed to start. |
|
||||||
| 0x80243FFE | WU_E_WUCLTUI_UNSUPPORTED_VERSION | Unsupported version of WU client UI exported functions. |
|
| 0x80243004 | WU_E_TRAYICON_FAILURE | A failure occurred when trying to create an icon in the taskbar notification area. |
|
||||||
| 0x80243FFF | WU_E_AUCLIENT_UNEXPECTED | There was a user interface error not covered by another WU_E_AUCLIENT_\* error code. |
|
| 0x80243FFD | WU_E_NON_UI_MODE | Unable to show UI when in non-UI mode; WU client UI modules may not be installed. |
|
||||||
|
| 0x80243FFE | WU_E_WUCLTUI_UNSUPPORTED_VERSION | Unsupported version of WU client UI exported functions. |
|
||||||
## Inventory errors
|
| 0x80243FFF | WU_E_AUCLIENT_UNEXPECTED | There was a user interface error not covered by another WU_E_AUCLIENT_\* error code. |
|
||||||
|
|
||||||
| Error code | Message | Description |
|
## Inventory errors
|
||||||
|------------|-------------------------------------------|-------------------------------------------------------------------------------|
|
|
||||||
| 0x80249001 | WU_E_INVENTORY_PARSEFAILED | Parsing of the rule file failed. |
|
| Error code | Message | Description |
|
||||||
| 0x80249002 | WU_E_INVENTORY_GET_INVENTORY_TYPE_FAILED | Failed to get the requested inventory type from the server. |
|
|------------|-------------------------------------------|-------------------------------------------------------------------------------|
|
||||||
| 0x80249003 | WU_E_INVENTORY_RESULT_UPLOAD_FAILED | Failed to upload inventory result to the server. |
|
| 0x80249001 | WU_E_INVENTORY_PARSEFAILED | Parsing of the rule file failed. |
|
||||||
| 0x80249004 | WU_E_INVENTORY_UNEXPECTED | There was an inventory error not covered by another error code. |
|
| 0x80249002 | WU_E_INVENTORY_GET_INVENTORY_TYPE_FAILED | Failed to get the requested inventory type from the server. |
|
||||||
| 0x80249005 | WU_E_INVENTORY_WMI_ERROR | A WMI error occurred when enumerating the instances for a particular class. |
|
| 0x80249003 | WU_E_INVENTORY_RESULT_UPLOAD_FAILED | Failed to upload inventory result to the server. |
|
||||||
|
| 0x80249004 | WU_E_INVENTORY_UNEXPECTED | There was an inventory error not covered by another error code. |
|
||||||
## Expression evaluator errors
|
| 0x80249005 | WU_E_INVENTORY_WMI_ERROR | A WMI error occurred when enumerating the instances for a particular class. |
|
||||||
|
|
||||||
| Error code | Message | Description |
|
## Expression evaluator errors
|
||||||
|-------------|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------|
|
|
||||||
| 0x8024E001 | WU_E_EE_UNKNOWN_EXPRESSION | An expression evaluator operation could not be completed because an expression was unrecognized. |
|
| Error code | Message | Description |
|
||||||
| 0x8024E002 | WU_E_EE_INVALID_EXPRESSION | An expression evaluator operation could not be completed because an expression was invalid. |
|
|-------------|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------|
|
||||||
| 0x8024E003 | WU_E_EE_MISSING_METADATA | An expression evaluator operation could not be completed because an expression contains an incorrect number of metadata nodes. |
|
| 0x8024E001 | WU_E_EE_UNKNOWN_EXPRESSION | An expression evaluator operation could not be completed because an expression was unrecognized. |
|
||||||
| 0x8024E004 | WU_E_EE_INVALID_VERSION | An expression evaluator operation could not be completed because the version of the serialized expression data is invalid. |
|
| 0x8024E002 | WU_E_EE_INVALID_EXPRESSION | An expression evaluator operation could not be completed because an expression was invalid. |
|
||||||
| 0x8024E005 | WU_E_EE_NOT_INITIALIZED | The expression evaluator could not be initialized. |
|
| 0x8024E003 | WU_E_EE_MISSING_METADATA | An expression evaluator operation could not be completed because an expression contains an incorrect number of metadata nodes. |
|
||||||
| 0x8024E006 | WU_E_EE_INVALID_ATTRIBUTEDATA | An expression evaluator operation could not be completed because there was an invalid attribute. |
|
| 0x8024E004 | WU_E_EE_INVALID_VERSION | An expression evaluator operation could not be completed because the version of the serialized expression data is invalid. |
|
||||||
| 0x8024E007 | WU_E_EE_CLUSTER_ERROR | An expression evaluator operation could not be completed because the cluster state of the computer could not be determined. |
|
| 0x8024E005 | WU_E_EE_NOT_INITIALIZED | The expression evaluator could not be initialized. |
|
||||||
| 0x8024EFFF | WU_E_EE_UNEXPECTED | There was an expression evaluator error not covered by another WU_E_EE_\* error code. |
|
| 0x8024E006 | WU_E_EE_INVALID_ATTRIBUTEDATA | An expression evaluator operation could not be completed because there was an invalid attribute. |
|
||||||
|
| 0x8024E007 | WU_E_EE_CLUSTER_ERROR | An expression evaluator operation could not be completed because the cluster state of the computer could not be determined. |
|
||||||
## Reporter errors
|
| 0x8024EFFF | WU_E_EE_UNEXPECTED | There was an expression evaluator error not covered by another WU_E_EE_\* error code. |
|
||||||
|
|
||||||
| Error code | Message | Description |
|
## Reporter errors
|
||||||
|-------------|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|
|
|
||||||
| 0x80247001 | WU_E_OL_INVALID_SCANFILE | An operation could not be completed because the scan package was invalid. |
|
| Error code | Message | Description |
|
||||||
| 0x80247002 | WU_E_OL_NEWCLIENT_REQUIRED | An operation could not be completed because the scan package requires a greater version of the Windows Update Agent. |
|
|-------------|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|
|
||||||
| 0x80247FFF | WU_E_OL_UNEXPECTED | Search using the scan package failed. |
|
| 0x80247001 | WU_E_OL_INVALID_SCANFILE | An operation could not be completed because the scan package was invalid. |
|
||||||
| 0x8024F001 | WU_E_REPORTER_EVENTCACHECORRUPT | The event cache file was defective. |
|
| 0x80247002 | WU_E_OL_NEWCLIENT_REQUIRED | An operation could not be completed because the scan package requires a greater version of the Windows Update Agent. |
|
||||||
| 0x8024F002 | WU_E_REPORTER_EVENTNAMESPACEPARSEFAILED | The XML in the event namespace descriptor could not be parsed. |
|
| 0x80247FFF | WU_E_OL_UNEXPECTED | Search using the scan package failed. |
|
||||||
| 0x8024F003 | WU_E_INVALID_EVENT | The XML in the event namespace descriptor could not be parsed. |
|
| 0x8024F001 | WU_E_REPORTER_EVENTCACHECORRUPT | The event cache file was defective. |
|
||||||
| 0x8024F004 | WU_E_SERVER_BUSY | The server rejected an event because the server was too busy. |
|
| 0x8024F002 | WU_E_REPORTER_EVENTNAMESPACEPARSEFAILED | The XML in the event namespace descriptor could not be parsed. |
|
||||||
| 0x8024FFFF | WU_E_REPORTER_UNEXPECTED | There was a reporter error not covered by another error code. |
|
| 0x8024F003 | WU_E_INVALID_EVENT | The XML in the event namespace descriptor could not be parsed. |
|
||||||
|
| 0x8024F004 | WU_E_SERVER_BUSY | The server rejected an event because the server was too busy. |
|
||||||
## Redirector errors
|
| 0x8024FFFF | WU_E_REPORTER_UNEXPECTED | There was a reporter error not covered by another error code. |
|
||||||
The components that download the Wuredir.cab file and then parse the Wuredir.cab file generate the following errors.
|
|
||||||
|
## Redirector errors
|
||||||
|Error code|Message|Description |
|
The components that download the Wuredir.cab file and then parse the Wuredir.cab file generate the following errors.
|
||||||
|-|-|-|
|
|
||||||
| 0x80245001| WU_E_REDIRECTOR_LOAD_XML| The redirector XML document could not be loaded into the DOM class. |
|
|Error code|Message|Description |
|
||||||
| 0x80245002| WU_E_REDIRECTOR_S_FALSE| The redirector XML document is missing some required information. |
|
|-|-|-|
|
||||||
| 0x80245003| WU_E_REDIRECTOR_ID_SMALLER| The redirectorId in the downloaded redirector cab is less than in the cached cab. |
|
| 0x80245001| WU_E_REDIRECTOR_LOAD_XML| The redirector XML document could not be loaded into the DOM class. |
|
||||||
| 0x80245FFF| WU_E_REDIRECTOR_UNEXPECTED| The redirector failed for reasons not covered by another WU_E_REDIRECTOR_* error code. |
|
| 0x80245002| WU_E_REDIRECTOR_S_FALSE| The redirector XML document is missing some required information. |
|
||||||
|
| 0x80245003| WU_E_REDIRECTOR_ID_SMALLER| The redirectorId in the downloaded redirector cab is less than in the cached cab. |
|
||||||
## Protocol Talker errors
|
| 0x80245FFF| WU_E_REDIRECTOR_UNEXPECTED| The redirector failed for reasons not covered by another WU_E_REDIRECTOR_* error code. |
|
||||||
The following errors map to SOAPCLIENT_ERRORs through the Atlsoap.h file. These errors are obtained when the CClientWebService object calls the GetClientError() method.
|
|
||||||
|
## Protocol Talker errors
|
||||||
|
The following errors map to SOAPCLIENT_ERRORs through the Atlsoap.h file. These errors are obtained when the CClientWebService object calls the GetClientError() method.
|
||||||
| Error code | Message | Description |
|
|
||||||
|-------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------|
|
|
||||||
| 0x80244000 | WU_E_PT_SOAPCLIENT_BASE | WU_E_PT_SOAPCLIENT_\* error codes map to the SOAPCLIENT_ERROR enum of the ATL Server Library. |
|
| Error code | Message | Description |
|
||||||
| 0x80244001 | WU_E_PT_SOAPCLIENT_INITIALIZE | Same as SOAPCLIENT_INITIALIZE_ERROR - initialization of the SOAP client failed possibly because of an MSXML installation failure. |
|
|-------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------|
|
||||||
| 0x80244002 | WU_E_PT_SOAPCLIENT_OUTOFMEMORY | Same as SOAPCLIENT_OUTOFMEMORY - SOAP client failed because it ran out of memory. |
|
| 0x80244000 | WU_E_PT_SOAPCLIENT_BASE | WU_E_PT_SOAPCLIENT_\* error codes map to the SOAPCLIENT_ERROR enum of the ATL Server Library. |
|
||||||
| 0x80244003 | WU_E_PT_SOAPCLIENT_GENERATE | Same as SOAPCLIENT_GENERATE_ERROR - SOAP client failed to generate the request. |
|
| 0x80244001 | WU_E_PT_SOAPCLIENT_INITIALIZE | Same as SOAPCLIENT_INITIALIZE_ERROR - initialization of the SOAP client failed possibly because of an MSXML installation failure. |
|
||||||
| 0x80244004 | WU_E_PT_SOAPCLIENT_CONNECT | Same as SOAPCLIENT_CONNECT_ERROR - SOAP client failed to connect to the server. |
|
| 0x80244002 | WU_E_PT_SOAPCLIENT_OUTOFMEMORY | Same as SOAPCLIENT_OUTOFMEMORY - SOAP client failed because it ran out of memory. |
|
||||||
| 0x80244005 | WU_E_PT_SOAPCLIENT_SEND | Same as SOAPCLIENT_SEND_ERROR - SOAP client failed to send a message for reasons of WU_E_WINHTTP_\* error codes. |
|
| 0x80244003 | WU_E_PT_SOAPCLIENT_GENERATE | Same as SOAPCLIENT_GENERATE_ERROR - SOAP client failed to generate the request. |
|
||||||
| 0x80244006 | WU_E_PT_SOAPCLIENT_SERVER | Same as SOAPCLIENT_SERVER_ERROR - SOAP client failed because there was a server error. |
|
| 0x80244004 | WU_E_PT_SOAPCLIENT_CONNECT | Same as SOAPCLIENT_CONNECT_ERROR - SOAP client failed to connect to the server. |
|
||||||
| 0x80244007 | WU_E_PT_SOAPCLIENT_SOAPFAULT | Same as SOAPCLIENT_SOAPFAULT - SOAP client failed because there was a SOAP fault for reasons of WU_E_PT_SOAP_\* error codes. |
|
| 0x80244005 | WU_E_PT_SOAPCLIENT_SEND | Same as SOAPCLIENT_SEND_ERROR - SOAP client failed to send a message for reasons of WU_E_WINHTTP_\* error codes. |
|
||||||
| 0x80244008 | WU_E_PT_SOAPCLIENT_PARSEFAULT | Same as SOAPCLIENT_PARSEFAULT_ERROR - SOAP client failed to parse a SOAP fault. |
|
| 0x80244006 | WU_E_PT_SOAPCLIENT_SERVER | Same as SOAPCLIENT_SERVER_ERROR - SOAP client failed because there was a server error. |
|
||||||
| 0x80244009 | WU_E_PT_SOAPCLIENT_READ | Same as SOAPCLIENT_READ_ERROR - SOAP client failed while reading the response from the server. |
|
| 0x80244007 | WU_E_PT_SOAPCLIENT_SOAPFAULT | Same as SOAPCLIENT_SOAPFAULT - SOAP client failed because there was a SOAP fault for reasons of WU_E_PT_SOAP_\* error codes. |
|
||||||
| 0x8024400A | WU_E_PT_SOAPCLIENT_PARSE | Same as SOAPCLIENT_PARSE_ERROR - SOAP client failed to parse the response from the server. |
|
| 0x80244008 | WU_E_PT_SOAPCLIENT_PARSEFAULT | Same as SOAPCLIENT_PARSEFAULT_ERROR - SOAP client failed to parse a SOAP fault. |
|
||||||
|
| 0x80244009 | WU_E_PT_SOAPCLIENT_READ | Same as SOAPCLIENT_READ_ERROR - SOAP client failed while reading the response from the server. |
|
||||||
## Other Protocol Talker errors
|
| 0x8024400A | WU_E_PT_SOAPCLIENT_PARSE | Same as SOAPCLIENT_PARSE_ERROR - SOAP client failed to parse the response from the server. |
|
||||||
The following errors map to SOAP_ERROR_CODEs from the Atlsoap.h file. These errors are obtained from the m_fault.m_soapErrCode member of the CClientWebService object when GetClientError() returns SOAPCLIENT_SOAPFAULT.
|
|
||||||
|
## Other Protocol Talker errors
|
||||||
|
The following errors map to SOAP_ERROR_CODEs from the Atlsoap.h file. These errors are obtained from the m_fault.m_soapErrCode member of the CClientWebService object when GetClientError() returns SOAPCLIENT_SOAPFAULT.
|
||||||
| Error code | Message | Description |
|
|
||||||
|-------------|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
||||||
| 0x8024400B | WU_E_PT_SOAP_VERSION | Same as SOAP_E_VERSION_MISMATCH - SOAP client found an unrecognizable namespace for the SOAP envelope. |
|
| Error code | Message | Description |
|
||||||
| 0x8024400C | WU_E_PT_SOAP_MUST_UNDERSTAND | Same as SOAP_E_MUST_UNDERSTAND - SOAP client was unable to understand a header. |
|
|-------------|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||||
| 0x8024400D | WU_E_PT_SOAP_CLIENT | Same as SOAP_E_CLIENT - SOAP client found the message was malformed; fix before resending. |
|
| 0x8024400B | WU_E_PT_SOAP_VERSION | Same as SOAP_E_VERSION_MISMATCH - SOAP client found an unrecognizable namespace for the SOAP envelope. |
|
||||||
| 0x8024400E | WU_E_PT_SOAP_SERVER | Same as SOAP_E_SERVER - The SOAP message could not be processed due to a server error; resend later. |
|
| 0x8024400C | WU_E_PT_SOAP_MUST_UNDERSTAND | Same as SOAP_E_MUST_UNDERSTAND - SOAP client was unable to understand a header. |
|
||||||
| 0x8024400F | WU_E_PT_WMI_ERROR | There was an unspecified Windows Management Instrumentation (WMI) error. |
|
| 0x8024400D | WU_E_PT_SOAP_CLIENT | Same as SOAP_E_CLIENT - SOAP client found the message was malformed; fix before resending. |
|
||||||
| 0x80244010 | WU_E_PT_EXCEEDED_MAX_SERVER_TRIPS | The number of round trips to the server exceeded the maximum limit. |
|
| 0x8024400E | WU_E_PT_SOAP_SERVER | Same as SOAP_E_SERVER - The SOAP message could not be processed due to a server error; resend later. |
|
||||||
| 0x80244011 | WU_E_PT_SUS_SERVER_NOT_SET | WUServer policy value is missing in the registry. |
|
| 0x8024400F | WU_E_PT_WMI_ERROR | There was an unspecified Windows Management Instrumentation (WMI) error. |
|
||||||
| 0x80244012 | WU_E_PT_DOUBLE_INITIALIZATION | Initialization failed because the object was already initialized. |
|
| 0x80244010 | WU_E_PT_EXCEEDED_MAX_SERVER_TRIPS | The number of round trips to the server exceeded the maximum limit. |
|
||||||
| 0x80244013 | WU_E_PT_INVALID_COMPUTER_NAME | The computer name could not be determined. |
|
| 0x80244011 | WU_E_PT_SUS_SERVER_NOT_SET | WUServer policy value is missing in the registry. |
|
||||||
| 0x80244015 | WU_E_PT_REFRESH_CACHE_REQUIRED | The reply from the server indicates that the server was changed or the cookie was invalid; refresh the state of the internal cache and retry. |
|
| 0x80244012 | WU_E_PT_DOUBLE_INITIALIZATION | Initialization failed because the object was already initialized. |
|
||||||
| 0x80244016 | WU_E_PT_HTTP_STATUS_BAD_REQUEST | Same as HTTP status 400 - the server could not process the request due to invalid syntax. |
|
| 0x80244013 | WU_E_PT_INVALID_COMPUTER_NAME | The computer name could not be determined. |
|
||||||
| 0x80244017 | WU_E_PT_HTTP_STATUS_DENIED | Same as HTTP status 401 - the requested resource requires user authentication. |
|
| 0x80244015 | WU_E_PT_REFRESH_CACHE_REQUIRED | The reply from the server indicates that the server was changed or the cookie was invalid; refresh the state of the internal cache and retry. |
|
||||||
| 0x80244018 | WU_E_PT_HTTP_STATUS_FORBIDDEN | Same as HTTP status 403 - server understood the request but declined to fulfill it. |
|
| 0x80244016 | WU_E_PT_HTTP_STATUS_BAD_REQUEST | Same as HTTP status 400 - the server could not process the request due to invalid syntax. |
|
||||||
| 0x80244019 | WU_E_PT_HTTP_STATUS_NOT_FOUND | Same as HTTP status 404 - the server cannot find the requested URI (Uniform Resource Identifier). |
|
| 0x80244017 | WU_E_PT_HTTP_STATUS_DENIED | Same as HTTP status 401 - the requested resource requires user authentication. |
|
||||||
| 0x8024401A | WU_E_PT_HTTP_STATUS_BAD_METHOD | Same as HTTP status 405 - the HTTP method is not allowed. |
|
| 0x80244018 | WU_E_PT_HTTP_STATUS_FORBIDDEN | Same as HTTP status 403 - server understood the request but declined to fulfill it. |
|
||||||
| 0x8024401B | WU_E_PT_HTTP_STATUS_PROXY_AUTH_REQ | Same as HTTP status 407 - proxy authentication is required. |
|
| 0x80244019 | WU_E_PT_HTTP_STATUS_NOT_FOUND | Same as HTTP status 404 - the server cannot find the requested URI (Uniform Resource Identifier). |
|
||||||
| 0x8024401C | WU_E_PT_HTTP_STATUS_REQUEST_TIMEOUT | Same as HTTP status 408 - the server timed out waiting for the request. |
|
| 0x8024401A | WU_E_PT_HTTP_STATUS_BAD_METHOD | Same as HTTP status 405 - the HTTP method is not allowed. |
|
||||||
| 0x8024401D | WU_E_PT_HTTP_STATUS_CONFLICT | Same as HTTP status 409 - the request was not completed due to a conflict with the current state of the resource. |
|
| 0x8024401B | WU_E_PT_HTTP_STATUS_PROXY_AUTH_REQ | Same as HTTP status 407 - proxy authentication is required. |
|
||||||
| 0x8024401E | WU_E_PT_HTTP_STATUS_GONE | Same as HTTP status 410 - requested resource is no longer available at the server. |
|
| 0x8024401C | WU_E_PT_HTTP_STATUS_REQUEST_TIMEOUT | Same as HTTP status 408 - the server timed out waiting for the request. |
|
||||||
| 0x8024401F | WU_E_PT_HTTP_STATUS_SERVER_ERROR | Same as HTTP status 500 - an error internal to the server prevented fulfilling the request. |
|
| 0x8024401D | WU_E_PT_HTTP_STATUS_CONFLICT | Same as HTTP status 409 - the request was not completed due to a conflict with the current state of the resource. |
|
||||||
| 0x80244020 | WU_E_PT_HTTP_STATUS_NOT_SUPPORTED | Same as HTTP status 500 - server does not support the functionality required to fulfill the request. |
|
| 0x8024401E | WU_E_PT_HTTP_STATUS_GONE | Same as HTTP status 410 - requested resource is no longer available at the server. |
|
||||||
| 0x80244021 | WU_E_PT_HTTP_STATUS_BAD_GATEWAY | Same as HTTP status 502 - the server while acting as a gateway or a proxy received an invalid response from the upstream server it accessed in attempting to fulfil the request. |
|
| 0x8024401F | WU_E_PT_HTTP_STATUS_SERVER_ERROR | Same as HTTP status 500 - an error internal to the server prevented fulfilling the request. |
|
||||||
| 0x80244022 | WU_E_PT_HTTP_STATUS_SERVICE_UNAVAIL | Same as HTTP status 503 - the service is temporarily overloaded. |
|
| 0x80244020 | WU_E_PT_HTTP_STATUS_NOT_SUPPORTED | Same as HTTP status 500 - server does not support the functionality required to fulfill the request. |
|
||||||
| 0x80244023 | WU_E_PT_HTTP_STATUS_GATEWAY_TIMEOUT | Same as HTTP status 503 - the request was timed out waiting for a gateway. |
|
| 0x80244021 | WU_E_PT_HTTP_STATUS_BAD_GATEWAY | Same as HTTP status 502 - the server while acting as a gateway or a proxy received an invalid response from the upstream server it accessed in attempting to fulfil the request. |
|
||||||
| 0x80244024 | WU_E_PT_HTTP_STATUS_VERSION_NOT_SUP | Same as HTTP status 505 - the server does not support the HTTP protocol version used for the request. |
|
| 0x80244022 | WU_E_PT_HTTP_STATUS_SERVICE_UNAVAIL | Same as HTTP status 503 - the service is temporarily overloaded. |
|
||||||
| 0x80244025 | WU_E_PT_FILE_LOCATIONS_CHANGED | Operation failed due to a changed file location; refresh internal state and resend. |
|
| 0x80244023 | WU_E_PT_HTTP_STATUS_GATEWAY_TIMEOUT | Same as HTTP status 503 - the request was timed out waiting for a gateway. |
|
||||||
| 0x80244026 | WU_E_PT_REGISTRATION_NOT_SUPPORTED | Operation failed because Windows Update Agent does not support registration with a non-WSUS server. |
|
| 0x80244024 | WU_E_PT_HTTP_STATUS_VERSION_NOT_SUP | Same as HTTP status 505 - the server does not support the HTTP protocol version used for the request. |
|
||||||
| 0x80244027 | WU_E_PT_NO_AUTH_PLUGINS_REQUESTED | The server returned an empty authentication information list. |
|
| 0x80244025 | WU_E_PT_FILE_LOCATIONS_CHANGED | Operation failed due to a changed file location; refresh internal state and resend. |
|
||||||
| 0x80244028 | WU_E_PT_NO_AUTH_COOKIES_CREATED | Windows Update Agent was unable to create any valid authentication cookies. |
|
| 0x80244026 | WU_E_PT_REGISTRATION_NOT_SUPPORTED | Operation failed because Windows Update Agent does not support registration with a non-WSUS server. |
|
||||||
| 0x80244029 | WU_E_PT_INVALID_CONFIG_PROP | A configuration property value was wrong. |
|
| 0x80244027 | WU_E_PT_NO_AUTH_PLUGINS_REQUESTED | The server returned an empty authentication information list. |
|
||||||
| 0x8024402A | WU_E_PT_CONFIG_PROP_MISSING | A configuration property value was missing. |
|
| 0x80244028 | WU_E_PT_NO_AUTH_COOKIES_CREATED | Windows Update Agent was unable to create any valid authentication cookies. |
|
||||||
| 0x8024402B | WU_E_PT_HTTP_STATUS_NOT_MAPPED | The HTTP request could not be completed and the reason did not correspond to any of the WU_E_PT_HTTP_\* error codes. |
|
| 0x80244029 | WU_E_PT_INVALID_CONFIG_PROP | A configuration property value was wrong. |
|
||||||
| 0x8024402C | WU_E_PT_WINHTTP_NAME_NOT_RESOLVED | Same as ERROR_WINHTTP_NAME_NOT_RESOLVED - the proxy server or target server name cannot be resolved. |
|
| 0x8024402A | WU_E_PT_CONFIG_PROP_MISSING | A configuration property value was missing. |
|
||||||
| 0x8024402F | WU_E_PT_ECP_SUCCEEDED_WITH_ERRORS | External cab file processing completed with some errors. |
|
| 0x8024402B | WU_E_PT_HTTP_STATUS_NOT_MAPPED | The HTTP request could not be completed and the reason did not correspond to any of the WU_E_PT_HTTP_\* error codes. |
|
||||||
| 0x80244030 | WU_E_PT_ECP_INIT_FAILED | The external cab processor initialization did not complete. |
|
| 0x8024402C | WU_E_PT_WINHTTP_NAME_NOT_RESOLVED | Same as ERROR_WINHTTP_NAME_NOT_RESOLVED - the proxy server or target server name cannot be resolved. |
|
||||||
| 0x80244031 | WU_E_PT_ECP_INVALID_FILE_FORMAT | The format of a metadata file was invalid. |
|
| 0x8024402F | WU_E_PT_ECP_SUCCEEDED_WITH_ERRORS | External cab file processing completed with some errors. |
|
||||||
| 0x80244032 | WU_E_PT_ECP_INVALID_METADATA | External cab processor found invalid metadata. |
|
| 0x80244030 | WU_E_PT_ECP_INIT_FAILED | The external cab processor initialization did not complete. |
|
||||||
| 0x80244033 | WU_E_PT_ECP_FAILURE_TO_EXTRACT_DIGEST | The file digest could not be extracted from an external cab file. |
|
| 0x80244031 | WU_E_PT_ECP_INVALID_FILE_FORMAT | The format of a metadata file was invalid. |
|
||||||
| 0x80244034 | WU_E_PT_ECP_FAILURE_TO_DECOMPRESS_CAB_FILE | An external cab file could not be decompressed. |
|
| 0x80244032 | WU_E_PT_ECP_INVALID_METADATA | External cab processor found invalid metadata. |
|
||||||
| 0x80244035 | WU_E_PT_ECP_FILE_LOCATION_ERROR | External cab processor was unable to get file locations. |
|
| 0x80244033 | WU_E_PT_ECP_FAILURE_TO_EXTRACT_DIGEST | The file digest could not be extracted from an external cab file. |
|
||||||
| 0x80244FFF | WU_E_PT_UNEXPECTED | A communication error not covered by another WU_E_PT_\* error code. |
|
| 0x80244034 | WU_E_PT_ECP_FAILURE_TO_DECOMPRESS_CAB_FILE | An external cab file could not be decompressed. |
|
||||||
| 0x8024502D | WU_E_PT_SAME_REDIR_ID | Windows Update Agent failed to download a redirector cabinet file with a new redirectorId value from the server during the recovery. |
|
| 0x80244035 | WU_E_PT_ECP_FILE_LOCATION_ERROR | External cab processor was unable to get file locations. |
|
||||||
| 0x8024502E | WU_E_PT_NO_MANAGED_RECOVER | A redirector recovery action did not complete because the server is managed. |
|
| 0x80244FFF | WU_E_PT_UNEXPECTED | A communication error not covered by another WU_E_PT_\* error code. |
|
||||||
|
| 0x8024502D | WU_E_PT_SAME_REDIR_ID | Windows Update Agent failed to download a redirector cabinet file with a new redirectorId value from the server during the recovery. |
|
||||||
## Download Manager errors
|
| 0x8024502E | WU_E_PT_NO_MANAGED_RECOVER | A redirector recovery action did not complete because the server is managed. |
|
||||||
|
|
||||||
| Error code | Message | Description |
|
## Download Manager errors
|
||||||
|-------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
|
|
||||||
| 0x80246001 | WU_E_DM_URLNOTAVAILABLE | A download manager operation could not be completed because the requested file does not have a URL. |
|
| Error code | Message | Description |
|
||||||
| 0x80246002 | WU_E_DM_INCORRECTFILEHASH | A download manager operation could not be completed because the file digest was not recognized. |
|
|-------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
|
||||||
| 0x80246003 | WU_E_DM_UNKNOWNALGORITHM | A download manager operation could not be completed because the file metadata requested an unrecognized hash algorithm. |
|
| 0x80246001 | WU_E_DM_URLNOTAVAILABLE | A download manager operation could not be completed because the requested file does not have a URL. |
|
||||||
| 0x80246004 | WU_E_DM_NEEDDOWNLOADREQUEST | An operation could not be completed because a download request is required from the download handler. |
|
| 0x80246002 | WU_E_DM_INCORRECTFILEHASH | A download manager operation could not be completed because the file digest was not recognized. |
|
||||||
| 0x80246005 | WU_E_DM_NONETWORK | A download manager operation could not be completed because the network connection was unavailable. |
|
| 0x80246003 | WU_E_DM_UNKNOWNALGORITHM | A download manager operation could not be completed because the file metadata requested an unrecognized hash algorithm. |
|
||||||
| 0x80246006 | WU_E_DM_WRONGBITSVERSION | A download manager operation could not be completed because the version of Background Intelligent Transfer Service (BITS) is incompatible. |
|
| 0x80246004 | WU_E_DM_NEEDDOWNLOADREQUEST | An operation could not be completed because a download request is required from the download handler. |
|
||||||
| 0x80246007 | WU_E_DM_NOTDOWNLOADED | The update has not been downloaded. |
|
| 0x80246005 | WU_E_DM_NONETWORK | A download manager operation could not be completed because the network connection was unavailable. |
|
||||||
| 0x80246008 | WU_E_DM_FAILTOCONNECTTOBITS | A download manager operation failed because the download manager was unable to connect the Background Intelligent Transfer Service (BITS). |
|
| 0x80246006 | WU_E_DM_WRONGBITSVERSION | A download manager operation could not be completed because the version of Background Intelligent Transfer Service (BITS) is incompatible. |
|
||||||
| 0x80246009 | WU_E_DM_BITSTRANSFERERROR | A download manager operation failed because there was an unspecified Background Intelligent Transfer Service (BITS) transfer error. |
|
| 0x80246007 | WU_E_DM_NOTDOWNLOADED | The update has not been downloaded. |
|
||||||
| 0x8024600A | WU_E_DM_DOWNLOADLOCATIONCHANGED | A download must be restarted because the location of the source of the download has changed. |
|
| 0x80246008 | WU_E_DM_FAILTOCONNECTTOBITS | A download manager operation failed because the download manager was unable to connect the Background Intelligent Transfer Service (BITS). |
|
||||||
| 0x8024600B | WU_E_DM_CONTENTCHANGED | A download must be restarted because the update content changed in a new revision. |
|
| 0x80246009 | WU_E_DM_BITSTRANSFERERROR | A download manager operation failed because there was an unspecified Background Intelligent Transfer Service (BITS) transfer error. |
|
||||||
| 0x80246FFF | WU_E_DM_UNEXPECTED | There was a download manager error not covered by another WU_E_DM_\* error code. |
|
| 0x8024600A | WU_E_DM_DOWNLOADLOCATIONCHANGED | A download must be restarted because the location of the source of the download has changed. |
|
||||||
|
| 0x8024600B | WU_E_DM_CONTENTCHANGED | A download must be restarted because the update content changed in a new revision. |
|
||||||
## Update Handler errors
|
| 0x80246FFF | WU_E_DM_UNEXPECTED | There was a download manager error not covered by another WU_E_DM_\* error code. |
|
||||||
|
|
||||||
| Error code | Message | Description |
|
## Update Handler errors
|
||||||
|-------------|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
|
|
||||||
| 0x80242000 | WU_E_UH_REMOTEUNAVAILABLE | 9 A request for a remote update handler could not be completed because no remote process is available. |
|
| Error code | Message | Description |
|
||||||
| 0x80242001 | WU_E_UH_LOCALONLY | A request for a remote update handler could not be completed because the handler is local only. |
|
|-------------|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
|
||||||
| 0x80242002 | WU_E_UH_UNKNOWNHANDLER | A request for an update handler could not be completed because the handler could not be recognized. |
|
| 0x80242000 | WU_E_UH_REMOTEUNAVAILABLE | 9 A request for a remote update handler could not be completed because no remote process is available. |
|
||||||
| 0x80242003 | WU_E_UH_REMOTEALREADYACTIVE | A remote update handler could not be created because one already exists. |
|
| 0x80242001 | WU_E_UH_LOCALONLY | A request for a remote update handler could not be completed because the handler is local only. |
|
||||||
| 0x80242004 | WU_E_UH_DOESNOTSUPPORTACTION | A request for the handler to install (uninstall) an update could not be completed because the update does not support install (uninstall). |
|
| 0x80242002 | WU_E_UH_UNKNOWNHANDLER | A request for an update handler could not be completed because the handler could not be recognized. |
|
||||||
| 0x80242005 | WU_E_UH_WRONGHANDLER | An operation did not complete because the wrong handler was specified. |
|
| 0x80242003 | WU_E_UH_REMOTEALREADYACTIVE | A remote update handler could not be created because one already exists. |
|
||||||
| 0x80242006 | WU_E_UH_INVALIDMETADATA | A handler operation could not be completed because the update contains invalid metadata. |
|
| 0x80242004 | WU_E_UH_DOESNOTSUPPORTACTION | A request for the handler to install (uninstall) an update could not be completed because the update does not support install (uninstall). |
|
||||||
| 0x80242007 | WU_E_UH_INSTALLERHUNG | An operation could not be completed because the installer exceeded the time limit. |
|
| 0x80242005 | WU_E_UH_WRONGHANDLER | An operation did not complete because the wrong handler was specified. |
|
||||||
| 0x80242008 | WU_E_UH_OPERATIONCANCELLED | An operation being done by the update handler was cancelled. |
|
| 0x80242006 | WU_E_UH_INVALIDMETADATA | A handler operation could not be completed because the update contains invalid metadata. |
|
||||||
| 0x80242009 | WU_E_UH_BADHANDLERXML | An operation could not be completed because the handler-specific metadata is invalid. |
|
| 0x80242007 | WU_E_UH_INSTALLERHUNG | An operation could not be completed because the installer exceeded the time limit. |
|
||||||
| 0x8024200A | WU_E_UH_CANREQUIREINPUT | A request to the handler to install an update could not be completed because the update requires user input. |
|
| 0x80242008 | WU_E_UH_OPERATIONCANCELLED | An operation being done by the update handler was cancelled. |
|
||||||
| 0x8024200B | WU_E_UH_INSTALLERFAILURE | The installer failed to install (uninstall) one or more updates. |
|
| 0x80242009 | WU_E_UH_BADHANDLERXML | An operation could not be completed because the handler-specific metadata is invalid. |
|
||||||
| 0x8024200C | WU_E_UH_FALLBACKTOSELFCONTAINED | The update handler should download self-contained content rather than delta-compressed content for the update. |
|
| 0x8024200A | WU_E_UH_CANREQUIREINPUT | A request to the handler to install an update could not be completed because the update requires user input. |
|
||||||
| 0x8024200D | WU_E_UH_NEEDANOTHERDOWNLOAD | The update handler did not install the update because it needs to be downloaded again. |
|
| 0x8024200B | WU_E_UH_INSTALLERFAILURE | The installer failed to install (uninstall) one or more updates. |
|
||||||
| 0x8024200E | WU_E_UH_NOTIFYFAILURE | The update handler failed to send notification of the status of the install (uninstall) operation. |
|
| 0x8024200C | WU_E_UH_FALLBACKTOSELFCONTAINED | The update handler should download self-contained content rather than delta-compressed content for the update. |
|
||||||
| 0x8024200F | WU_E_UH_INCONSISTENT_FILE_NAMES | The file names contained in the update metadata and in the update package are inconsistent. |
|
| 0x8024200D | WU_E_UH_NEEDANOTHERDOWNLOAD | The update handler did not install the update because it needs to be downloaded again. |
|
||||||
| 0x80242010 | WU_E_UH_FALLBACKERROR | The update handler failed to fall back to the self-contained content. |
|
| 0x8024200E | WU_E_UH_NOTIFYFAILURE | The update handler failed to send notification of the status of the install (uninstall) operation. |
|
||||||
| 0x80242011 | WU_E_UH_TOOMANYDOWNLOADREQUESTS | The update handler has exceeded the maximum number of download requests. |
|
| 0x8024200F | WU_E_UH_INCONSISTENT_FILE_NAMES | The file names contained in the update metadata and in the update package are inconsistent. |
|
||||||
| 0x80242012 | WU_E_UH_UNEXPECTEDCBSRESPONSE | The update handler has received an unexpected response from CBS. |
|
| 0x80242010 | WU_E_UH_FALLBACKERROR | The update handler failed to fall back to the self-contained content. |
|
||||||
| 0x80242013 | WU_E_UH_BADCBSPACKAGEID | The update metadata contains an invalid CBS package identifier. |
|
| 0x80242011 | WU_E_UH_TOOMANYDOWNLOADREQUESTS | The update handler has exceeded the maximum number of download requests. |
|
||||||
| 0x80242014 | WU_E_UH_POSTREBOOTSTILLPENDING | The post-reboot operation for the update is still in progress. |
|
| 0x80242012 | WU_E_UH_UNEXPECTEDCBSRESPONSE | The update handler has received an unexpected response from CBS. |
|
||||||
| 0x80242015 | WU_E_UH_POSTREBOOTRESULTUNKNOWN | The result of the post-reboot operation for the update could not be determined. |
|
| 0x80242013 | WU_E_UH_BADCBSPACKAGEID | The update metadata contains an invalid CBS package identifier. |
|
||||||
| 0x80242016 | WU_E_UH_POSTREBOOTUNEXPECTEDSTATE | The state of the update after its post-reboot operation has completed is unexpected. |
|
| 0x80242014 | WU_E_UH_POSTREBOOTSTILLPENDING | The post-reboot operation for the update is still in progress. |
|
||||||
| 0x80242017 | WU_E_UH_NEW_SERVICING_STACK_REQUIRED | The OS servicing stack must be updated before this update is downloaded or installed. |
|
| 0x80242015 | WU_E_UH_POSTREBOOTRESULTUNKNOWN | The result of the post-reboot operation for the update could not be determined. |
|
||||||
| 0x80242FFF | WU_E_UH_UNEXPECTED | An update handler error not covered by another WU_E_UH_\* code. |
|
| 0x80242016 | WU_E_UH_POSTREBOOTUNEXPECTEDSTATE | The state of the update after its post-reboot operation has completed is unexpected. |
|
||||||
|
| 0x80242017 | WU_E_UH_NEW_SERVICING_STACK_REQUIRED | The OS servicing stack must be updated before this update is downloaded or installed. |
|
||||||
## Data Store errors
|
| 0x80242FFF | WU_E_UH_UNEXPECTED | An update handler error not covered by another WU_E_UH_\* code. |
|
||||||
|
|
||||||
| Error code | Message | Description |
|
## Data Store errors
|
||||||
|-------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
||||||
| 0x80248000 | WU_E_DS_SHUTDOWN | An operation failed because Windows Update Agent is shutting down. |
|
| Error code | Message | Description |
|
||||||
| 0x80248001 | WU_E_DS_INUSE | An operation failed because the data store was in use. |
|
|-------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||||
| 0x80248002 | WU_E_DS_INVALID | The current and expected states of the data store do not match. |
|
| 0x80248000 | WU_E_DS_SHUTDOWN | An operation failed because Windows Update Agent is shutting down. |
|
||||||
| 0x80248003 | WU_E_DS_TABLEMISSING | The data store is missing a table. |
|
| 0x80248001 | WU_E_DS_INUSE | An operation failed because the data store was in use. |
|
||||||
| 0x80248004 | WU_E_DS_TABLEINCORRECT | The data store contains a table with unexpected columns. |
|
| 0x80248002 | WU_E_DS_INVALID | The current and expected states of the data store do not match. |
|
||||||
| 0x80248005 | WU_E_DS_INVALIDTABLENAME | A table could not be opened because the table is not in the data store. |
|
| 0x80248003 | WU_E_DS_TABLEMISSING | The data store is missing a table. |
|
||||||
| 0x80248006 | WU_E_DS_BADVERSION | The current and expected versions of the data store do not match. |
|
| 0x80248004 | WU_E_DS_TABLEINCORRECT | The data store contains a table with unexpected columns. |
|
||||||
| 0x80248007 | WU_E_DS_NODATA | The information requested is not in the data store. |
|
| 0x80248005 | WU_E_DS_INVALIDTABLENAME | A table could not be opened because the table is not in the data store. |
|
||||||
| 0x80248008 | WU_E_DS_MISSINGDATA | The data store is missing required information or has a NULL in a table column that requires a non-null value. |
|
| 0x80248006 | WU_E_DS_BADVERSION | The current and expected versions of the data store do not match. |
|
||||||
| 0x80248009 | WU_E_DS_MISSINGREF | The data store is missing required information or has a reference to missing license terms file localized property or linked row. |
|
| 0x80248007 | WU_E_DS_NODATA | The information requested is not in the data store. |
|
||||||
| 0x8024800A | WU_E_DS_UNKNOWNHANDLER | The update was not processed because its update handler could not be recognized. |
|
| 0x80248008 | WU_E_DS_MISSINGDATA | The data store is missing required information or has a NULL in a table column that requires a non-null value. |
|
||||||
| 0x8024800B | WU_E_DS_CANTDELETE | The update was not deleted because it is still referenced by one or more services. |
|
| 0x80248009 | WU_E_DS_MISSINGREF | The data store is missing required information or has a reference to missing license terms file localized property or linked row. |
|
||||||
| 0x8024800C | WU_E_DS_LOCKTIMEOUTEXPIRED | The data store section could not be locked within the allotted time. |
|
| 0x8024800A | WU_E_DS_UNKNOWNHANDLER | The update was not processed because its update handler could not be recognized. |
|
||||||
| 0x8024800D | WU_E_DS_NOCATEGORIES | The category was not added because it contains no parent categories and is not a top-level category itself. |
|
| 0x8024800B | WU_E_DS_CANTDELETE | The update was not deleted because it is still referenced by one or more services. |
|
||||||
| 0x8024800E | WU_E_DS_ROWEXISTS | The row was not added because an existing row has the same primary key. |
|
| 0x8024800C | WU_E_DS_LOCKTIMEOUTEXPIRED | The data store section could not be locked within the allotted time. |
|
||||||
| 0x8024800F | WU_E_DS_STOREFILELOCKED | The data store could not be initialized because it was locked by another process. |
|
| 0x8024800D | WU_E_DS_NOCATEGORIES | The category was not added because it contains no parent categories and is not a top-level category itself. |
|
||||||
| 0x80248010 | WU_E_DS_CANNOTREGISTER | The data store is not allowed to be registered with COM in the current process. |
|
| 0x8024800E | WU_E_DS_ROWEXISTS | The row was not added because an existing row has the same primary key. |
|
||||||
| 0x80248011 | WU_E_DS_UNABLETOSTART | Could not create a data store object in another process. |
|
| 0x8024800F | WU_E_DS_STOREFILELOCKED | The data store could not be initialized because it was locked by another process. |
|
||||||
| 0x80248013 | WU_E_DS_DUPLICATEUPDATEID | The server sent the same update to the client with two different revision IDs. |
|
| 0x80248010 | WU_E_DS_CANNOTREGISTER | The data store is not allowed to be registered with COM in the current process. |
|
||||||
| 0x80248014 | WU_E_DS_UNKNOWNSERVICE | An operation did not complete because the service is not in the data store. |
|
| 0x80248011 | WU_E_DS_UNABLETOSTART | Could not create a data store object in another process. |
|
||||||
| 0x80248015 | WU_E_DS_SERVICEEXPIRED | An operation did not complete because the registration of the service has expired. |
|
| 0x80248013 | WU_E_DS_DUPLICATEUPDATEID | The server sent the same update to the client with two different revision IDs. |
|
||||||
| 0x80248016 | WU_E_DS_DECLINENOTALLOWED | A request to hide an update was declined because it is a mandatory update or because it was deployed with a deadline. |
|
| 0x80248014 | WU_E_DS_UNKNOWNSERVICE | An operation did not complete because the service is not in the data store. |
|
||||||
| 0x80248017 | WU_E_DS_TABLESESSIONMISMATCH | A table was not closed because it is not associated with the session. |
|
| 0x80248015 | WU_E_DS_SERVICEEXPIRED | An operation did not complete because the registration of the service has expired. |
|
||||||
| 0x80248018 | WU_E_DS_SESSIONLOCKMISMATCH | A table was not closed because it is not associated with the session. |
|
| 0x80248016 | WU_E_DS_DECLINENOTALLOWED | A request to hide an update was declined because it is a mandatory update or because it was deployed with a deadline. |
|
||||||
| 0x80248019 | WU_E_DS_NEEDWINDOWSSERVICE | A request to remove the Windows Update service or to unregister it with Automatic Updates was declined because it is a built-in service and/or Automatic Updates cannot fall back to another service. |
|
| 0x80248017 | WU_E_DS_TABLESESSIONMISMATCH | A table was not closed because it is not associated with the session. |
|
||||||
| 0x8024801A | WU_E_DS_INVALIDOPERATION | A request was declined because the operation is not allowed. |
|
| 0x80248018 | WU_E_DS_SESSIONLOCKMISMATCH | A table was not closed because it is not associated with the session. |
|
||||||
| 0x8024801B | WU_E_DS_SCHEMAMISMATCH | The schema of the current data store and the schema of a table in a backup XML document do not match. |
|
| 0x80248019 | WU_E_DS_NEEDWINDOWSSERVICE | A request to remove the Windows Update service or to unregister it with Automatic Updates was declined because it is a built-in service and/or Automatic Updates cannot fall back to another service. |
|
||||||
| 0x8024801C | WU_E_DS_RESETREQUIRED | The data store requires a session reset; release the session and retry with a new session. |
|
| 0x8024801A | WU_E_DS_INVALIDOPERATION | A request was declined because the operation is not allowed. |
|
||||||
| 0x8024801D | WU_E_DS_IMPERSONATED | A data store operation did not complete because it was requested with an impersonated identity. |
|
| 0x8024801B | WU_E_DS_SCHEMAMISMATCH | The schema of the current data store and the schema of a table in a backup XML document do not match. |
|
||||||
| 0x80248FFF | WU_E_DS_UNEXPECTED | A data store error not covered by another WU_E_DS_\* code. |
|
| 0x8024801C | WU_E_DS_RESETREQUIRED | The data store requires a session reset; release the session and retry with a new session. |
|
||||||
|
| 0x8024801D | WU_E_DS_IMPERSONATED | A data store operation did not complete because it was requested with an impersonated identity. |
|
||||||
## Driver Util errors
|
| 0x80248FFF | WU_E_DS_UNEXPECTED | A data store error not covered by another WU_E_DS_\* code. |
|
||||||
The PnP enumerated device is removed from the System Spec because one of the hardware IDs or the compatible IDs matches an installed printer driver. This is not a fatal error, and the device is merely skipped.
|
|
||||||
|
## Driver Util errors
|
||||||
|Error code|Message|Description
|
The PnP enumerated device is removed from the System Spec because one of the hardware IDs or the compatible IDs matches an installed printer driver. This is not a fatal error, and the device is merely skipped.
|
||||||
|-|-|-|
|
|
||||||
| 0x8024C001 | WU_E_DRV_PRUNED| A driver was skipped.
|
|Error code|Message|Description
|
||||||
| 0x8024C002 |WU_E_DRV_NOPROP_OR_LEGACY| A property for the driver could not be found. It may not conform with required specifications.
|
|-|-|-|
|
||||||
| 0x8024C003 | WU_E_DRV_REG_MISMATCH| The registry type read for the driver does not match the expected type.
|
| 0x8024C001 | WU_E_DRV_PRUNED| A driver was skipped.
|
||||||
| 0x8024C004 | WU_E_DRV_NO_METADATA| The driver update is missing metadata.
|
| 0x8024C002 |WU_E_DRV_NOPROP_OR_LEGACY| A property for the driver could not be found. It may not conform with required specifications.
|
||||||
| 0x8024C005 | WU_E_DRV_MISSING_ATTRIBUTE| The driver update is missing a required attribute.
|
| 0x8024C003 | WU_E_DRV_REG_MISMATCH| The registry type read for the driver does not match the expected type.
|
||||||
| 0x8024C006| WU_E_DRV_SYNC_FAILED| Driver synchronization failed.
|
| 0x8024C004 | WU_E_DRV_NO_METADATA| The driver update is missing metadata.
|
||||||
| 0x8024C007 | WU_E_DRV_NO_PRINTER_CONTENT| Information required for the synchronization of applicable printers is missing.
|
| 0x8024C005 | WU_E_DRV_MISSING_ATTRIBUTE| The driver update is missing a required attribute.
|
||||||
| 0x8024CFFF | WU_E_DRV_UNEXPECTED| A driver error not covered by another WU_E_DRV_* code.
|
| 0x8024C006| WU_E_DRV_SYNC_FAILED| Driver synchronization failed.
|
||||||
|
| 0x8024C007 | WU_E_DRV_NO_PRINTER_CONTENT| Information required for the synchronization of applicable printers is missing.
|
||||||
## Windows Update error codes
|
| 0x8024CFFF | WU_E_DRV_UNEXPECTED| A driver error not covered by another WU_E_DRV_* code.
|
||||||
|
|
||||||
|Error code|Message|Description
|
## Windows Update error codes
|
||||||
|-|-|-|
|
|
||||||
| 0x80240001 | WU_E_NO_SERVICE| Windows Update Agent was unable to provide the service.
|
|Error code|Message|Description
|
||||||
| 0x80240002 | WU_E_MAX_CAPACITY_REACHED | The maximum capacity of the service was exceeded.
|
|-|-|-|
|
||||||
| 0x80240003 | WU_E_UNKNOWN_ID| An ID cannot be found.
|
| 0x80240001 | WU_E_NO_SERVICE| Windows Update Agent was unable to provide the service.
|
||||||
| 0x80240004 | WU_E_NOT_INITIALIZED| The object could not be initialized.
|
| 0x80240002 | WU_E_MAX_CAPACITY_REACHED | The maximum capacity of the service was exceeded.
|
||||||
| 0x80240005 | WU_E_RANGEOVERLAP |The update handler requested a byte range overlapping a previously requested range.
|
| 0x80240003 | WU_E_UNKNOWN_ID| An ID cannot be found.
|
||||||
| 0x80240006 | WU_E_TOOMANYRANGES| The requested number of byte ranges exceeds the maximum number (2^31 - 1).
|
| 0x80240004 | WU_E_NOT_INITIALIZED| The object could not be initialized.
|
||||||
| 0x80240007 | WU_E_INVALIDINDEX| The index to a collection was invalid.
|
| 0x80240005 | WU_E_RANGEOVERLAP |The update handler requested a byte range overlapping a previously requested range.
|
||||||
| 0x80240008 | WU_E_ITEMNOTFOUND| The key for the item queried could not be found.
|
| 0x80240006 | WU_E_TOOMANYRANGES| The requested number of byte ranges exceeds the maximum number (2^31 - 1).
|
||||||
| 0x80240009 | WU_E_OPERATIONINPROGRESS| Another conflicting operation was in progress. Some operations such as installation cannot be performed twice simultaneously.
|
| 0x80240007 | WU_E_INVALIDINDEX| The index to a collection was invalid.
|
||||||
| 0x8024000A | WU_E_COULDNOTCANCEL| Cancellation of the operation was not allowed.
|
| 0x80240008 | WU_E_ITEMNOTFOUND| The key for the item queried could not be found.
|
||||||
| 0x8024000B | WU_E_CALL_CANCELLED| Operation was cancelled.
|
| 0x80240009 | WU_E_OPERATIONINPROGRESS| Another conflicting operation was in progress. Some operations such as installation cannot be performed twice simultaneously.
|
||||||
| 0x8024000C | WU_E_NOOP| No operation was required.
|
| 0x8024000A | WU_E_COULDNOTCANCEL| Cancellation of the operation was not allowed.
|
||||||
| 0x8024000D | WU_E_XML_MISSINGDATA| Windows Update Agent could not find required information in the update's XML data.
|
| 0x8024000B | WU_E_CALL_CANCELLED| Operation was cancelled.
|
||||||
| 0x8024000E | WU_E_XML_INVALID| Windows Update Agent found invalid information in the update's XML data.
|
| 0x8024000C | WU_E_NOOP| No operation was required.
|
||||||
| 0x8024000F | WU_E_CYCLE_DETECTED | Circular update relationships were detected in the metadata.
|
| 0x8024000D | WU_E_XML_MISSINGDATA| Windows Update Agent could not find required information in the update's XML data.
|
||||||
| 0x80240010 | WU_E_TOO_DEEP_RELATION| Update relationships too deep to evaluate were evaluated.
|
| 0x8024000E | WU_E_XML_INVALID| Windows Update Agent found invalid information in the update's XML data.
|
||||||
| 0x80240011 | WU_E_INVALID_RELATIONSHIP| An invalid update relationship was detected.
|
| 0x8024000F | WU_E_CYCLE_DETECTED | Circular update relationships were detected in the metadata.
|
||||||
| 0x80240012 | WU_E_REG_VALUE_INVALID| An invalid registry value was read.
|
| 0x80240010 | WU_E_TOO_DEEP_RELATION| Update relationships too deep to evaluate were evaluated.
|
||||||
| 0x80240013 | WU_E_DUPLICATE_ITEM| Operation tried to add a duplicate item to a list.
|
| 0x80240011 | WU_E_INVALID_RELATIONSHIP| An invalid update relationship was detected.
|
||||||
| 0x80240016 | WU_E_INSTALL_NOT_ALLOWED| Operation tried to install while another installation was in progress or the system was pending a mandatory restart.
|
| 0x80240012 | WU_E_REG_VALUE_INVALID| An invalid registry value was read.
|
||||||
| 0x80240017 | WU_E_NOT_APPLICABLE| Operation was not performed because there are no applicable updates.
|
| 0x80240013 | WU_E_DUPLICATE_ITEM| Operation tried to add a duplicate item to a list.
|
||||||
| 0x80240018 | WU_E_NO_USERTOKEN| Operation failed because a required user token is missing.
|
| 0x80240016 | WU_E_INSTALL_NOT_ALLOWED| Operation tried to install while another installation was in progress or the system was pending a mandatory restart.
|
||||||
| 0x80240019 | WU_E_EXCLUSIVE_INSTALL_CONFLICT| An exclusive update cannot be installed with other updates at the same time.
|
| 0x80240017 | WU_E_NOT_APPLICABLE| Operation was not performed because there are no applicable updates.
|
||||||
| 0x8024001A | WU_E_POLICY_NOT_SET | A policy value was not set.
|
| 0x80240018 | WU_E_NO_USERTOKEN| Operation failed because a required user token is missing.
|
||||||
| 0x8024001B | WU_E_SELFUPDATE_IN_PROGRESS| The operation could not be performed because the Windows Update Agent is self-updating.
|
| 0x80240019 | WU_E_EXCLUSIVE_INSTALL_CONFLICT| An exclusive update cannot be installed with other updates at the same time.
|
||||||
| 0x8024001D | WU_E_INVALID_UPDATE| An update contains invalid metadata.
|
| 0x8024001A | WU_E_POLICY_NOT_SET | A policy value was not set.
|
||||||
| 0x8024001E | WU_E_SERVICE_STOP| Operation did not complete because the service or system was being shut down.
|
| 0x8024001B | WU_E_SELFUPDATE_IN_PROGRESS| The operation could not be performed because the Windows Update Agent is self-updating.
|
||||||
| 0x8024001F | WU_E_NO_CONNECTION| Operation did not complete because the network connection was unavailable.
|
| 0x8024001D | WU_E_INVALID_UPDATE| An update contains invalid metadata.
|
||||||
| 0x80240020 | WU_E_NO_INTERACTIVE_USER| Operation did not complete because there is no logged-on interactive user.
|
| 0x8024001E | WU_E_SERVICE_STOP| Operation did not complete because the service or system was being shut down.
|
||||||
| 0x80240021 | WU_E_TIME_OUT| Operation did not complete because it timed out.
|
| 0x8024001F | WU_E_NO_CONNECTION| Operation did not complete because the network connection was unavailable.
|
||||||
| 0x80240022 | WU_E_ALL_UPDATES_FAILED| Operation failed for all the updates.
|
| 0x80240020 | WU_E_NO_INTERACTIVE_USER| Operation did not complete because there is no logged-on interactive user.
|
||||||
| 0x80240023 | WU_E_EULAS_DECLINED| The license terms for all updates were declined.
|
| 0x80240021 | WU_E_TIME_OUT| Operation did not complete because it timed out.
|
||||||
| 0x80240024 | WU_E_NO_UPDATE| There are no updates.
|
| 0x80240022 | WU_E_ALL_UPDATES_FAILED| Operation failed for all the updates.
|
||||||
| 0x80240025 | WU_E_USER_ACCESS_DISABLED| Group Policy settings prevented access to Windows Update.
|
| 0x80240023 | WU_E_EULAS_DECLINED| The license terms for all updates were declined.
|
||||||
| 0x80240026 | WU_E_INVALID_UPDATE_TYPE| The type of update is invalid.
|
| 0x80240024 | WU_E_NO_UPDATE| There are no updates.
|
||||||
| 0x80240027 | WU_E_URL_TOO_LONG| The URL exceeded the maximum length.
|
| 0x80240025 | WU_E_USER_ACCESS_DISABLED| Group Policy settings prevented access to Windows Update.
|
||||||
| 0x80240028 | WU_E_UNINSTALL_NOT_ALLOWED| The update could not be uninstalled because the request did not originate from a WSUS server.
|
| 0x80240026 | WU_E_INVALID_UPDATE_TYPE| The type of update is invalid.
|
||||||
| 0x80240029 | WU_E_INVALID_PRODUCT_LICENSE| Search may have missed some updates before there is an unlicensed application on the system.
|
| 0x80240027 | WU_E_URL_TOO_LONG| The URL exceeded the maximum length.
|
||||||
| 0x8024002A | WU_E_MISSING_HANDLER| A component required to detect applicable updates was missing.
|
| 0x80240028 | WU_E_UNINSTALL_NOT_ALLOWED| The update could not be uninstalled because the request did not originate from a WSUS server.
|
||||||
| 0x8024002B | WU_E_LEGACYSERVER| An operation did not complete because it requires a newer version of server.
|
| 0x80240029 | WU_E_INVALID_PRODUCT_LICENSE| Search may have missed some updates before there is an unlicensed application on the system.
|
||||||
| 0x8024002C | WU_E_BIN_SOURCE_ABSENT| A delta-compressed update could not be installed because it required the source.
|
| 0x8024002A | WU_E_MISSING_HANDLER| A component required to detect applicable updates was missing.
|
||||||
| 0x8024002D | WU_E_SOURCE_ABSENT| A full-file update could not be installed because it required the source.
|
| 0x8024002B | WU_E_LEGACYSERVER| An operation did not complete because it requires a newer version of server.
|
||||||
| 0x8024002E | WU_E_WU_DISABLED| Access to an unmanaged server is not allowed.
|
| 0x8024002C | WU_E_BIN_SOURCE_ABSENT| A delta-compressed update could not be installed because it required the source.
|
||||||
| 0x8024002F | WU_E_CALL_CANCELLED_BY_POLICY| Operation did not complete because the DisableWindowsUpdateAccess policy was set.
|
| 0x8024002D | WU_E_SOURCE_ABSENT| A full-file update could not be installed because it required the source.
|
||||||
| 0x80240030 | WU_E_INVALID_PROXY_SERVER| The format of the proxy list was invalid.
|
| 0x8024002E | WU_E_WU_DISABLED| Access to an unmanaged server is not allowed.
|
||||||
| 0x80240031 | WU_E_INVALID_FILE| The file is in the wrong format.
|
| 0x8024002F | WU_E_CALL_CANCELLED_BY_POLICY| Operation did not complete because the DisableWindowsUpdateAccess policy was set.
|
||||||
| 0x80240032 | WU_E_INVALID_CRITERIA| The search criteria string was invalid.
|
| 0x80240030 | WU_E_INVALID_PROXY_SERVER| The format of the proxy list was invalid.
|
||||||
| 0x80240033 | WU_E_EULA_UNAVAILABLE| License terms could not be downloaded.
|
| 0x80240031 | WU_E_INVALID_FILE| The file is in the wrong format.
|
||||||
| 0x80240034 | WU_E_DOWNLOAD_FAILED| Update failed to download.
|
| 0x80240032 | WU_E_INVALID_CRITERIA| The search criteria string was invalid.
|
||||||
| 0x80240035 | WU_E_UPDATE_NOT_PROCESSED| The update was not processed.
|
| 0x80240033 | WU_E_EULA_UNAVAILABLE| License terms could not be downloaded.
|
||||||
| 0x80240036 | WU_E_INVALID_OPERATION| The object's current state did not allow the operation.
|
| 0x80240034 | WU_E_DOWNLOAD_FAILED| Update failed to download.
|
||||||
| 0x80240037 | WU_E_NOT_SUPPORTED| The functionality for the operation is not supported.
|
| 0x80240035 | WU_E_UPDATE_NOT_PROCESSED| The update was not processed.
|
||||||
| 0x80240038 | WU_E_WINHTTP_INVALID_FILE| The downloaded file has an unexpected content type.
|
| 0x80240036 | WU_E_INVALID_OPERATION| The object's current state did not allow the operation.
|
||||||
| 0x80240039 | WU_E_TOO_MANY_RESYNC| Agent is asked by server to resync too many times.
|
| 0x80240037 | WU_E_NOT_SUPPORTED| The functionality for the operation is not supported.
|
||||||
| 0x80240040 | WU_E_NO_SERVER_CORE_SUPPORT| WUA API method does not run on Server Core installation.
|
| 0x80240038 | WU_E_WINHTTP_INVALID_FILE| The downloaded file has an unexpected content type.
|
||||||
| 0x80240041 | WU_E_SYSPREP_IN_PROGRESS| Service is not available while sysprep is running.
|
| 0x80240039 | WU_E_TOO_MANY_RESYNC| Agent is asked by server to resync too many times.
|
||||||
| 0x80240042 | WU_E_UNKNOWN_SERVICE| The update service is no longer registered with AU.
|
| 0x80240040 | WU_E_NO_SERVER_CORE_SUPPORT| WUA API method does not run on Server Core installation.
|
||||||
| 0x80240043 | WU_E_NO_UI_SUPPORT| There is no support for WUA UI.
|
| 0x80240041 | WU_E_SYSPREP_IN_PROGRESS| Service is not available while sysprep is running.
|
||||||
| 0x80240FFF | WU_E_UNEXPECTED| An operation failed due to reasons not covered by another error code.
|
| 0x80240042 | WU_E_UNKNOWN_SERVICE| The update service is no longer registered with AU.
|
||||||
|
| 0x80240043 | WU_E_NO_UI_SUPPORT| There is no support for WUA UI.
|
||||||
## Windows Update success codes
|
| 0x80240FFF | WU_E_UNEXPECTED| An operation failed due to reasons not covered by another error code.
|
||||||
|
|
||||||
|Error code|Message|Description
|
## Windows Update success codes
|
||||||
|-|-|-|
|
|
||||||
| 0x00240001| WU_S_SERVICE_STOP| Windows Update Agent was stopped successfully.
|
|Error code|Message|Description
|
||||||
| 0x00240002 | WU_S_SELFUPDATE| Windows Update Agent updated itself.
|
|-|-|-|
|
||||||
| 0x00240003 | WU_S_UPDATE_ERROR| Operation completed successfully but there were errors applying the updates.
|
| 0x00240001| WU_S_SERVICE_STOP| Windows Update Agent was stopped successfully.
|
||||||
| 0x00240004 | WU_S_MARKED_FOR_DISCONNECT| A callback was marked to be disconnected later because the request to disconnect the operation came while a callback was executing.
|
| 0x00240002 | WU_S_SELFUPDATE| Windows Update Agent updated itself.
|
||||||
| 0x00240005 | WU_S_REBOOT_REQUIRED| The system must be restarted to complete installation of the update.
|
| 0x00240003 | WU_S_UPDATE_ERROR| Operation completed successfully but there were errors applying the updates.
|
||||||
| 0x00240006 | WU_S_ALREADY_INSTALLED| The update to be installed is already installed on the system.
|
| 0x00240004 | WU_S_MARKED_FOR_DISCONNECT| A callback was marked to be disconnected later because the request to disconnect the operation came while a callback was executing.
|
||||||
| 0x00240007 | WU_S_ALREADY_UNINSTALLED | The update to be removed is not installed on the system.
|
| 0x00240005 | WU_S_REBOOT_REQUIRED| The system must be restarted to complete installation of the update.
|
||||||
| 0x00240008 | WU_S_ALREADY_DOWNLOADED| The update to be downloaded has already been downloaded.
|
| 0x00240006 | WU_S_ALREADY_INSTALLED| The update to be installed is already installed on the system.
|
||||||
|
| 0x00240007 | WU_S_ALREADY_UNINSTALLED | The update to be removed is not installed on the system.
|
||||||
## Windows Installer minor errors
|
| 0x00240008 | WU_S_ALREADY_DOWNLOADED| The update to be downloaded has already been downloaded.
|
||||||
The following errors are used to indicate that part of a search fails because of Windows Installer problems. Another part of the search may successfully return updates. All Windows Installer minor codes must share the same error code range so that the caller can tell that they are related to Windows Installer.
|
|
||||||
|
## Windows Installer minor errors
|
||||||
|Error code|Message|Description
|
The following errors are used to indicate that part of a search fails because of Windows Installer problems. Another part of the search may successfully return updates. All Windows Installer minor codes must share the same error code range so that the caller can tell that they are related to Windows Installer.
|
||||||
|-|-|-|
|
|
||||||
| 0x80241001 |WU_E_MSI_WRONG_VERSION| Search may have missed some updates because the Windows Installer is less than version 3.1.
|
|Error code|Message|Description
|
||||||
| 0x80241002 | WU_E_MSI_NOT_CONFIGURED| Search may have missed some updates because the Windows Installer is not configured.
|
|-|-|-|
|
||||||
| 0x80241003 | WU_E_MSP_DISABLED| Search may have missed some updates because policy has disabled Windows Installer patching.
|
| 0x80241001 |WU_E_MSI_WRONG_VERSION| Search may have missed some updates because the Windows Installer is less than version 3.1.
|
||||||
| 0x80241004 | WU_E_MSI_WRONG_APP_CONTEXT| An update could not be applied because the application is installed per-user.
|
| 0x80241002 | WU_E_MSI_NOT_CONFIGURED| Search may have missed some updates because the Windows Installer is not configured.
|
||||||
| 0x80241FFF | WU_E_MSP_UNEXPECTED| Search may have missed some updates because there was a failure of the Windows Installer.
|
| 0x80241003 | WU_E_MSP_DISABLED| Search may have missed some updates because policy has disabled Windows Installer patching.
|
||||||
|
| 0x80241004 | WU_E_MSI_WRONG_APP_CONTEXT| An update could not be applied because the application is installed per-user.
|
||||||
## Windows Update Agent update and setup errors
|
| 0x80241FFF | WU_E_MSP_UNEXPECTED| Search may have missed some updates because there was a failure of the Windows Installer.
|
||||||
|
|
||||||
|Error code|Message|Description
|
## Windows Update Agent update and setup errors
|
||||||
|-|-|-|
|
|
||||||
| 0x8024D001 | WU_E_SETUP_INVALID_INFDATA| Windows Update Agent could not be updated because an INF file contains invalid information.
|
|Error code|Message|Description
|
||||||
| 0x8024D002 | WU_E_SETUP_INVALID_IDENTDATA| Windows Update Agent could not be updated because the wuident.cab file contains invalid information.
|
|-|-|-|
|
||||||
| 0x8024D003 | WU_E_SETUP_ALREADY_INITIALIZED| Windows Update Agent could not be updated because of an internal error that caused setup initialization to be performed twice.
|
| 0x8024D001 | WU_E_SETUP_INVALID_INFDATA| Windows Update Agent could not be updated because an INF file contains invalid information.
|
||||||
| 0x8024D004 | WU_E_SETUP_NOT_INITIALIZED| Windows Update Agent could not be updated because setup initialization never completed successfully.
|
| 0x8024D002 | WU_E_SETUP_INVALID_IDENTDATA| Windows Update Agent could not be updated because the wuident.cab file contains invalid information.
|
||||||
| 0x8024D005 | WU_E_SETUP_SOURCE_VERSION_MISMATCH| Windows Update Agent could not be updated because the versions specified in the INF do not match the actual source file versions.
|
| 0x8024D003 | WU_E_SETUP_ALREADY_INITIALIZED| Windows Update Agent could not be updated because of an internal error that caused setup initialization to be performed twice.
|
||||||
| 0x8024D006 | WU_E_SETUP_TARGET_VERSION_GREATER| Windows Update Agent could not be updated because a WUA file on the target system is newer than the corresponding source file.
|
| 0x8024D004 | WU_E_SETUP_NOT_INITIALIZED| Windows Update Agent could not be updated because setup initialization never completed successfully.
|
||||||
| 0x8024D007 | WU_E_SETUP_REGISTRATION_FAILED| Windows Update Agent could not be updated because regsvr32.exe returned an error.
|
| 0x8024D005 | WU_E_SETUP_SOURCE_VERSION_MISMATCH| Windows Update Agent could not be updated because the versions specified in the INF do not match the actual source file versions.
|
||||||
| 0x8024D009 | WU_E_SETUP_SKIP_UPDATE| An update to the Windows Update Agent was skipped due to a directive in the wuident.cab file.
|
| 0x8024D006 | WU_E_SETUP_TARGET_VERSION_GREATER| Windows Update Agent could not be updated because a WUA file on the target system is newer than the corresponding source file.
|
||||||
| 0x8024D00A | WU_E_SETUP_UNSUPPORTED_CONFIGURATION| Windows Update Agent could not be updated because the current system configuration is not supported.
|
| 0x8024D007 | WU_E_SETUP_REGISTRATION_FAILED| Windows Update Agent could not be updated because regsvr32.exe returned an error.
|
||||||
| 0x8024D00B | WU_E_SETUP_BLOCKED_CONFIGURATION| Windows Update Agent could not be updated because the system is configured to block the update.
|
| 0x8024D009 | WU_E_SETUP_SKIP_UPDATE| An update to the Windows Update Agent was skipped due to a directive in the wuident.cab file.
|
||||||
| 0x8024D00C | WU_E_SETUP_REBOOT_TO_FIX| Windows Update Agent could not be updated because a restart of the system is required.
|
| 0x8024D00A | WU_E_SETUP_UNSUPPORTED_CONFIGURATION| Windows Update Agent could not be updated because the current system configuration is not supported.
|
||||||
| 0x8024D00D | WU_E_SETUP_ALREADYRUNNING| Windows Update Agent setup is already running.
|
| 0x8024D00B | WU_E_SETUP_BLOCKED_CONFIGURATION| Windows Update Agent could not be updated because the system is configured to block the update.
|
||||||
| 0x8024D00E | WU_E_SETUP_REBOOTREQUIRED| Windows Update Agent setup package requires a reboot to complete installation.
|
| 0x8024D00C | WU_E_SETUP_REBOOT_TO_FIX| Windows Update Agent could not be updated because a restart of the system is required.
|
||||||
| 0x8024D00F | WU_E_SETUP_HANDLER_EXEC_FAILURE| Windows Update Agent could not be updated because the setup handler failed during execution.
|
| 0x8024D00D | WU_E_SETUP_ALREADYRUNNING| Windows Update Agent setup is already running.
|
||||||
| 0x8024D010 | WU_E_SETUP_INVALID_REGISTRY_DATA| Windows Update Agent could not be updated because the registry contains invalid information.
|
| 0x8024D00E | WU_E_SETUP_REBOOTREQUIRED| Windows Update Agent setup package requires a reboot to complete installation.
|
||||||
| 0x8024D013 | WU_E_SETUP_WRONG_SERVER_VERSION| Windows Update Agent could not be updated because the server does not contain update information for this version.
|
| 0x8024D00F | WU_E_SETUP_HANDLER_EXEC_FAILURE| Windows Update Agent could not be updated because the setup handler failed during execution.
|
||||||
| 0x8024DFFF | WU_E_SETUP_UNEXPECTED| Windows Update Agent could not be updated because of an error not covered by another WU_E_SETUP_* error code.
|
| 0x8024D010 | WU_E_SETUP_INVALID_REGISTRY_DATA| Windows Update Agent could not be updated because the registry contains invalid information.
|
||||||
|
| 0x8024D013 | WU_E_SETUP_WRONG_SERVER_VERSION| Windows Update Agent could not be updated because the server does not contain update information for this version.
|
||||||
|
| 0x8024DFFF | WU_E_SETUP_UNEXPECTED| Windows Update Agent could not be updated because of an error not covered by another WU_E_SETUP_* error code.
|
||||||
|
|||||||
@ -1,40 +1,42 @@
|
|||||||
---
|
---
|
||||||
title: Windows Update common errors and mitigation
|
title: Windows Update common errors and mitigation
|
||||||
description: Learn about some common issues you might experience with Windows Update
|
description: Learn about some common issues you might experience with Windows Update
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl:
|
ms.mktglfcycl:
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.audience: itpro
author: greg-lindsay
|
ms.localizationprioauthor: jaimeo
|
||||||
ms.date: 09/18/2018
|
ms.audience: itpro
|
||||||
ms.reviewer:
|
author: jaimeo
|
||||||
manager: laurawi
|
ms.date: 09/18/2018
|
||||||
ms.topic: article
|
ms.reviewer:
|
||||||
---
|
manager: laurawi
|
||||||
|
ms.topic: article
|
||||||
# Windows Update common errors and mitigation
|
---
|
||||||
|
|
||||||
>Applies to: Windows 10
|
# Windows Update common errors and mitigation
|
||||||
|
|
||||||
The following table provides information about common errors you might run into with Windows Update, as well as steps to help you mitigate them.
|
>Applies to: Windows 10
|
||||||
|
|
||||||
|
The following table provides information about common errors you might run into with Windows Update, as well as steps to help you mitigate them.
|
||||||
| Error Code | Message | Description | Mitigation |
|
|
||||||
|------------------------------------------|-----------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
||||||
| 0x8024402F | WU_E_PT_ECP_SUCCEEDED_WITH_ERRORS | External cab file processing completed with some errors | One of the reasons we see this issue is due to the design of a software called Lightspeed Rocket for Web filtering. <br>The IP addresses of the computers you want to get updates successfully on, should be added to the exceptions list of Lightspeed |
|
| Error Code | Message | Description | Mitigation |
|
||||||
| 0x80242006 | WU_E_UH_INVALIDMETADATA | A handler operation could not be completed because the update contains invalid metadata. | Rename Software Redistribution Folder and attempt to download the updates again: <br>Rename the following folders to \*.BAK: <br>- %systemroot%\system32\catroot2 <br><br>To do this, type the following commands at a command prompt. Press ENTER after you type each command.<br>- Ren %systemroot%\SoftwareDistribution\DataStore \*.bak<br>- Ren %systemroot%\SoftwareDistribution\Download \*.bak<br>Ren %systemroot%\system32\catroot2 \*.bak |
|
|------------------------------------------|-----------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||||
| 0x80070BC9 | ERROR_FAIL_REBOOT_REQUIRED | The requested operation failed. A system reboot is required to roll back changes made. | Ensure that we do not have any policies that control the start behavior for the Windows Module Installer. This service should not be hardened to any start value and should be managed by the OS. |
|
| 0x8024402F | WU_E_PT_ECP_SUCCEEDED_WITH_ERRORS | External cab file processing completed with some errors | One of the reasons we see this issue is due to the design of a software called Lightspeed Rocket for Web filtering. <br>The IP addresses of the computers you want to get updates successfully on, should be added to the exceptions list of Lightspeed |
|
||||||
| 0x80200053 | BG_E_VALIDATION_FAILED | NA | Ensure that there is no Firewalls that filter downloads. The Firewall filtering may lead to invalid responses being received by the Windows Update Client.<br><br>If the issue still persists, run the [WU reset script](https://gallery.technet.microsoft.com/scriptcenter/Reset-Windows-Update-Agent-d824badc). |
|
| 0x80242006 | WU_E_UH_INVALIDMETADATA | A handler operation could not be completed because the update contains invalid metadata. | Rename Software Redistribution Folder and attempt to download the updates again: <br>Rename the following folders to \*.BAK: <br>- %systemroot%\system32\catroot2 <br><br>To do this, type the following commands at a command prompt. Press ENTER after you type each command.<br>- Ren %systemroot%\SoftwareDistribution\DataStore \*.bak<br>- Ren %systemroot%\SoftwareDistribution\Download \*.bak<br>Ren %systemroot%\system32\catroot2 \*.bak |
|
||||||
| 0x80072EE2 | WININET_E_TIMEOUT | The operation timed out | This error message can be caused if the computer isn't connected to Internet. To fix this issue, following these steps: make sure these URLs are not blocked: <br> http://<em>.update.microsoft.com<br>https://</em>.update.microsoft.com <br><http://download.windowsupdate.com> <br><br>Additionally , you can take a network trace and see what is timing out. \<Refer to Firewall Troubleshooting scenario> |
|
| 0x80070BC9 | ERROR_FAIL_REBOOT_REQUIRED | The requested operation failed. A system reboot is required to roll back changes made. | Ensure that we do not have any policies that control the start behavior for the Windows Module Installer. This service should not be hardened to any start value and should be managed by the OS. |
|
||||||
| 0x80072EFD <br>0x80072EFE <br>0x80D02002 | TIME_OUT_ERRORS | The operation timed out | Make sure there are no firewall rules or proxy to block Microsoft download URLs. <br>Take a network monitor trace to understand better. \<Refer to Firewall Troubleshooting scenario> |
|
| 0x80200053 | BG_E_VALIDATION_FAILED | NA | Ensure that there is no Firewalls that filter downloads. The Firewall filtering may lead to invalid responses being received by the Windows Update Client.<br><br>If the issue still persists, run the [WU reset script](https://gallery.technet.microsoft.com/scriptcenter/Reset-Windows-Update-Agent-d824badc). |
|
||||||
| 0X8007000D | ERROR_INVALID_DATA | Indicates invalid data downloaded or corruption occurred. | Attempt to re-download the update and initiate installation. |
|
| 0x80072EE2 | WININET_E_TIMEOUT | The operation timed out | This error message can be caused if the computer isn't connected to Internet. To fix this issue, following these steps: make sure these URLs are not blocked: <br> http://<em>.update.microsoft.com<br>https://</em>.update.microsoft.com <br><http://download.windowsupdate.com> <br><br>Additionally , you can take a network trace and see what is timing out. \<Refer to Firewall Troubleshooting scenario> |
|
||||||
| 0x8024A10A | USO_E_SERVICE_SHUTTING_DOWN | Indicates that the WU Service is shutting down. | This may happen due to a very long period of time of inactivity, a system hang leading to the service being idle and leading to the shutdown of the service. Ensure that the system remains active and the connections remain established to complete the upgrade. |
|
| 0x80072EFD <br>0x80072EFE <br>0x80D02002 | TIME_OUT_ERRORS | The operation timed out | Make sure there are no firewall rules or proxy to block Microsoft download URLs. <br>Take a network monitor trace to understand better. \<Refer to Firewall Troubleshooting scenario> |
|
||||||
| 0x80240020 | WU_E_NO_INTERACTIVE_USER | Operation did not complete because there is no logged-on interactive user. | Please login to the system to initiate the installation and allow the system to be rebooted. |
|
| 0X8007000D | ERROR_INVALID_DATA | Indicates invalid data downloaded or corruption occurred. | Attempt to re-download the update and initiate installation. |
|
||||||
| 0x80242014 | WU_E_UH_POSTREBOOTSTILLPENDING | The post-reboot operation for the update is still in progress. | Some Windows Updates require the system to be restarted. Reboot the system to complete the installation of the Updates. |
|
| 0x8024A10A | USO_E_SERVICE_SHUTTING_DOWN | Indicates that the WU Service is shutting down. | This may happen due to a very long period of time of inactivity, a system hang leading to the service being idle and leading to the shutdown of the service. Ensure that the system remains active and the connections remain established to complete the upgrade. |
|
||||||
| 0x80246017 | WU_E_DM_UNAUTHORIZED_LOCAL_USER | The download failed because the local user was denied authorization to download the content. | Ensure that the user attempting to download and install updates has been provided with sufficient privileges to install updates (Local Administrator). |
|
| 0x80240020 | WU_E_NO_INTERACTIVE_USER | Operation did not complete because there is no logged-on interactive user. | Please login to the system to initiate the installation and allow the system to be rebooted. |
|
||||||
| 0x8024000B | WU_E_CALL_CANCELLED | Operation was cancelled. | This indicates that the operation was cancelled by the user/service. You may also encounter this error when we are unable to filter the results. Run the [Decline Superseded PowerShell script](https://gallery.technet.microsoft.com/scriptcenter/Cleanup-WSUS-server-4424c9d6) to allow the filtering process to complete. |
|
| 0x80242014 | WU_E_UH_POSTREBOOTSTILLPENDING | The post-reboot operation for the update is still in progress. | Some Windows Updates require the system to be restarted. Reboot the system to complete the installation of the Updates. |
|
||||||
| 0x8024000E | WU_E_XML_INVALID | Windows Update Agent found invalid information in the update's XML data. | Certain drivers contain additional metadata information in the update.xml, which could lead Orchestrator to understand it as invalid data. Ensure that you have the latest Windows Update Agent installed on the machine. |
|
| 0x80246017 | WU_E_DM_UNAUTHORIZED_LOCAL_USER | The download failed because the local user was denied authorization to download the content. | Ensure that the user attempting to download and install updates has been provided with sufficient privileges to install updates (Local Administrator). |
|
||||||
| 0x8024D009 | WU_E_SETUP_SKIP_UPDATE | An update to the Windows Update Agent was skipped due to a directive in the wuident.cab file. | You may encounter this error when WSUS is not sending the Self-update to the clients.<br><br>Review [KB920659](https://support.microsoft.com/help/920659/the-microsoft-windows-server-update-services-wsus-selfupdate-service-d) for instructions to resolve the issue. |
|
| 0x8024000B | WU_E_CALL_CANCELLED | Operation was cancelled. | This indicates that the operation was cancelled by the user/service. You may also encounter this error when we are unable to filter the results. Run the [Decline Superseded PowerShell script](https://gallery.technet.microsoft.com/scriptcenter/Cleanup-WSUS-server-4424c9d6) to allow the filtering process to complete. |
|
||||||
| 0x80244007 | WU_E_PT_SOAPCLIENT_SOAPFAULT | SOAP client failed because there was a SOAP fault for reasons of WU_E_PT_SOAP_\* error codes. | This issue occurs because Windows cannot renew the cookies for Windows Update. <br><br>Review [KB2883975](https://support.microsoft.com/help/2883975/0x80244007-error-when-windows-tries-to-scan-for-updates-on-a-wsus-serv) for instructions to resolve the issue. |
|
| 0x8024000E | WU_E_XML_INVALID | Windows Update Agent found invalid information in the update's XML data. | Certain drivers contain additional metadata information in the update.xml, which could lead Orchestrator to understand it as invalid data. Ensure that you have the latest Windows Update Agent installed on the machine. |
|
||||||
|
| 0x8024D009 | WU_E_SETUP_SKIP_UPDATE | An update to the Windows Update Agent was skipped due to a directive in the wuident.cab file. | You may encounter this error when WSUS is not sending the Self-update to the clients.<br><br>Review [KB920659](https://support.microsoft.com/help/920659/the-microsoft-windows-server-update-services-wsus-selfupdate-service-d) for instructions to resolve the issue. |
|
||||||
|
| 0x80244007 | WU_E_PT_SOAPCLIENT_SOAPFAULT | SOAP client failed because there was a SOAP fault for reasons of WU_E_PT_SOAP_\* error codes. | This issue occurs because Windows cannot renew the cookies for Windows Update. <br><br>Review [KB2883975](https://support.microsoft.com/help/2883975/0x80244007-error-when-windows-tries-to-scan-for-updates-on-a-wsus-serv) for instructions to resolve the issue. |
|
||||||
|
|
||||||
|
|||||||
@ -1,147 +1,149 @@
|
|||||||
---
|
---
|
||||||
title: Windows Update log files
|
title: Windows Update log files
|
||||||
description: Learn about the Windows Update log files
|
description: Learn about the Windows Update log files
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl:
|
ms.mktglfcycl:
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.audience: itpro
author: greg-lindsay
|
ms.localizationprioauthor: jaimeo
|
||||||
ms.date: 09/18/2018
|
ms.audience: itpro
|
||||||
ms.reviewer:
|
author: jaimeo
|
||||||
manager: laurawi
|
ms.date: 09/18/2018
|
||||||
ms.topic: article
|
ms.reviewer:
|
||||||
---
|
manager: laurawi
|
||||||
|
ms.topic: article
|
||||||
# Windows Update log files
|
---
|
||||||
|
|
||||||
>Applies to: Windows 10
|
# Windows Update log files
|
||||||
|
|
||||||
The following table describes the log files created by Windows Update.
|
>Applies to: Windows 10
|
||||||
|
|
||||||
|
The following table describes the log files created by Windows Update.
|
||||||
|Log file|Location|Description|When to Use |
|
|
||||||
|-|-|-|-|
|
|
||||||
|windowsupdate.log|C:\Windows\Logs\WindowsUpdate|Starting in Windows 8.1 and continuing in Windows 10, Windows Update client uses Event Tracing for Windows (ETW) to generate diagnostic logs.|If you receive an error message when you run Windows Update (WU), you can use the information that is included in the Windowsupdate.log log file to troubleshoot the issue.|
|
|Log file|Location|Description|When to Use |
|
||||||
|UpdateSessionOrchestration.etl|C:\ProgramData\USOShared\Logs|Starting Windows 10, the Update Orchestrator is responsible for sequence of downloading and installing various update types from Windows Update. And the events are logged to these etl files.|When you see that the updates are available but download is not getting triggered. <br>When Updates are downloaded but installation is not triggered.<br>When Updates are installed but reboot is not triggered. |
|
|-|-|-|-|
|
||||||
|NotificationUxBroker.etl|C:\ProgramData\USOShared\Logs|Starting Windows 10, the notification toast or the banner is triggered by this NotificationUxBroker.exe . And the logs to check its working is this etl. |When you want to check whether the Notification was triggered or not for reboot or update availability etc. |
|
|windowsupdate.log|C:\Windows\Logs\WindowsUpdate|Starting in Windows 8.1 and continuing in Windows 10, Windows Update client uses Event Tracing for Windows (ETW) to generate diagnostic logs.|If you receive an error message when you run Windows Update (WU), you can use the information that is included in the Windowsupdate.log log file to troubleshoot the issue.|
|
||||||
|CBS.log|%systemroot%\Logs\CBS|This logs provides insight on the update installation part in the servicing stack.|To troubleshoot the issues related to WU installation.|
|
|UpdateSessionOrchestration.etl|C:\ProgramData\USOShared\Logs|Starting Windows 10, the Update Orchestrator is responsible for sequence of downloading and installing various update types from Windows Update. And the events are logged to these etl files.|When you see that the updates are available but download is not getting triggered. <br>When Updates are downloaded but installation is not triggered.<br>When Updates are installed but reboot is not triggered. |
|
||||||
|
|NotificationUxBroker.etl|C:\ProgramData\USOShared\Logs|Starting Windows 10, the notification toast or the banner is triggered by this NotificationUxBroker.exe . And the logs to check its working is this etl. |When you want to check whether the Notification was triggered or not for reboot or update availability etc. |
|
||||||
## Generating WindowsUpdate.log
|
|CBS.log|%systemroot%\Logs\CBS|This logs provides insight on the update installation part in the servicing stack.|To troubleshoot the issues related to WU installation.|
|
||||||
To merge and convert WU trace files (.etl files) into a single readable WindowsUpdate.log file, see [Get-WindowsUpdateLog](https://docs.microsoft.com/powershell/module/windowsupdate/get-windowsupdatelog?view=win10-ps).
|
|
||||||
|
## Generating WindowsUpdate.log
|
||||||
>[!NOTE]
|
To merge and convert WU trace files (.etl files) into a single readable WindowsUpdate.log file, see [Get-WindowsUpdateLog](https://docs.microsoft.com/powershell/module/windowsupdate/get-windowsupdatelog?view=win10-ps).
|
||||||
>When you run the **Get-WindowsUpdateLog** cmdlet, an copy of WindowsUpdate.log file is created as a static log file. It does not update as the old WindowsUpate.log unless you run **Get-WindowsUpdateLog** again.
|
|
||||||
|
>[!NOTE]
|
||||||
### Windows Update log components
|
>When you run the **Get-WindowsUpdateLog** cmdlet, an copy of WindowsUpdate.log file is created as a static log file. It does not update as the old WindowsUpate.log unless you run **Get-WindowsUpdateLog** again.
|
||||||
The WU engine has different component names. The following are some of the most common components that appear in the WindowsUpdate.log file:
|
|
||||||
|
### Windows Update log components
|
||||||
- AGENT- Windows Update agent
|
The WU engine has different component names. The following are some of the most common components that appear in the WindowsUpdate.log file:
|
||||||
- AU - Automatic Updates is performing this task
|
|
||||||
- AUCLNT- Interaction between AU and the logged-on user
|
- AGENT- Windows Update agent
|
||||||
- CDM- Device Manager
|
- AU - Automatic Updates is performing this task
|
||||||
- CMPRESS- Compression agent
|
- AUCLNT- Interaction between AU and the logged-on user
|
||||||
- COMAPI- Windows Update API
|
- CDM- Device Manager
|
||||||
- DRIVER- Device driver information
|
- CMPRESS- Compression agent
|
||||||
- DTASTOR- Handles database transactions
|
- COMAPI- Windows Update API
|
||||||
- EEHNDLER- Expression handler that's used to evaluate update applicability
|
- DRIVER- Device driver information
|
||||||
- HANDLER- Manages the update installers
|
- DTASTOR- Handles database transactions
|
||||||
- MISC- General service information
|
- EEHNDLER- Expression handler that's used to evaluate update applicability
|
||||||
- OFFLSNC- Detects available updates without network connection
|
- HANDLER- Manages the update installers
|
||||||
- PARSER- Parses expression information
|
- MISC- General service information
|
||||||
- PT- Synchronizes updates information to the local datastore
|
- OFFLSNC- Detects available updates without network connection
|
||||||
- REPORT- Collects reporting information
|
- PARSER- Parses expression information
|
||||||
- SERVICE- Startup/shutdown of the Automatic Updates service
|
- PT- Synchronizes updates information to the local datastore
|
||||||
- SETUP- Installs new versions of the Windows Update client when it is available
|
- REPORT- Collects reporting information
|
||||||
- SHUTDWN- Install at shutdown feature
|
- SERVICE- Startup/shutdown of the Automatic Updates service
|
||||||
- WUREDIR- The Windows Update redirector files
|
- SETUP- Installs new versions of the Windows Update client when it is available
|
||||||
- WUWEB- The Windows Update ActiveX control
|
- SHUTDWN- Install at shutdown feature
|
||||||
- ProtocolTalker - Client-server sync
|
- WUREDIR- The Windows Update redirector files
|
||||||
- DownloadManager - Creates and monitors payload downloads
|
- WUWEB- The Windows Update ActiveX control
|
||||||
- Handler, Setup - Installer handlers (CBS, and so on)
|
- ProtocolTalker - Client-server sync
|
||||||
- EEHandler - Evaluating update applicability rules
|
- DownloadManager - Creates and monitors payload downloads
|
||||||
- DataStore - Caching update data locally
|
- Handler, Setup - Installer handlers (CBS, and so on)
|
||||||
- IdleTimer - Tracking active calls, stopping a service
|
- EEHandler - Evaluating update applicability rules
|
||||||
|
- DataStore - Caching update data locally
|
||||||
>[!NOTE]
|
- IdleTimer - Tracking active calls, stopping a service
|
||||||
>Many component log messages are invaluable if you are looking for problems in that specific area. However, they can be useless if you don't filter to exclude irrelevant components so that you can focus on what’s important.
|
|
||||||
|
>[!NOTE]
|
||||||
### Windows Update log structure
|
>Many component log messages are invaluable if you are looking for problems in that specific area. However, they can be useless if you don't filter to exclude irrelevant components so that you can focus on what’s important.
|
||||||
The Windows update log structure is separated into four main identities:
|
|
||||||
|
### Windows Update log structure
|
||||||
- Time Stamps
|
The Windows update log structure is separated into four main identities:
|
||||||
- Process ID and Thread ID
|
|
||||||
- Component Name
|
- Time Stamps
|
||||||
- Update Identifiers
|
- Process ID and Thread ID
|
||||||
- Update ID and Revision Number
|
- Component Name
|
||||||
- Revision ID
|
- Update Identifiers
|
||||||
- Local ID
|
- Update ID and Revision Number
|
||||||
- Inconsistent terminology
|
- Revision ID
|
||||||
|
- Local ID
|
||||||
The WindowsUpdate.log structure is discussed in the following sections.
|
- Inconsistent terminology
|
||||||
|
|
||||||
#### Time stamps
|
The WindowsUpdate.log structure is discussed in the following sections.
|
||||||
The time stamp indicates the time at which the logging occurs.
|
|
||||||
- Messages are usually in chronological order, but there may be exceptions.
|
#### Time stamps
|
||||||
- A pause during a sync can indicate a network problem, even if the scan succeeds.
|
The time stamp indicates the time at which the logging occurs.
|
||||||
- A long pause near the end of a scan can indicate a supersedence chain issue.
|
- Messages are usually in chronological order, but there may be exceptions.
|
||||||
|
- A pause during a sync can indicate a network problem, even if the scan succeeds.
|
||||||
|
- A long pause near the end of a scan can indicate a supersedence chain issue.
|
||||||
|
|
||||||
#### Process ID and thread ID
|
|
||||||
The Process IDs and Thread IDs are random, and they can vary from log to log and even from service session to service session within the same log.
|
|
||||||
- The first four hex digits are the process ID.
|
#### Process ID and thread ID
|
||||||
- The next four hex digits are the thread ID.
|
The Process IDs and Thread IDs are random, and they can vary from log to log and even from service session to service session within the same log.
|
||||||
- Each component, such as the USO, WU engine, COM API callers, and WU installer handlers, has its own process ID.
|
- The first four hex digits are the process ID.
|
||||||
|
- The next four hex digits are the thread ID.
|
||||||
|
- Each component, such as the USO, WU engine, COM API callers, and WU installer handlers, has its own process ID.
|
||||||
|
|
||||||
#### Component name
|
|
||||||
Search for and identify the components that are associated with the IDs. Different parts of the WU engine have different component names. Some of them are as follows:
|
|
||||||
|
#### Component name
|
||||||
- ProtocolTalker - Client-server sync
|
Search for and identify the components that are associated with the IDs. Different parts of the WU engine have different component names. Some of them are as follows:
|
||||||
- DownloadManager - Creates and monitors payload downloads
|
|
||||||
- Handler, Setup - Installer handlers (CBS, etc.)
|
- ProtocolTalker - Client-server sync
|
||||||
- EEHandler - Evaluating update applicability rules
|
- DownloadManager - Creates and monitors payload downloads
|
||||||
- DataStore - Caching update data locally
|
- Handler, Setup - Installer handlers (CBS, etc.)
|
||||||
- IdleTimer - Tracking active calls, stopping service
|
- EEHandler - Evaluating update applicability rules
|
||||||
|
- DataStore - Caching update data locally
|
||||||
|
- IdleTimer - Tracking active calls, stopping service
|
||||||
|
|
||||||
|
|
||||||
#### Update identifiers
|
|
||||||
|
|
||||||
##### Update ID and revision number
|
#### Update identifiers
|
||||||
There are different identifiers for the same update in different contexts. It’s important to know the identifier schemes.
|
|
||||||
- Update ID: A GUID (indicated in the previous screen shot) that's assigned to a given update at publication time
|
##### Update ID and revision number
|
||||||
- Revision number: A number incremented every time that a given update (that has a given update ID) is modified and republished on a service
|
There are different identifiers for the same update in different contexts. It’s important to know the identifier schemes.
|
||||||
- Revision numbers are reused from one update to another (not a unique identifier).
|
- Update ID: A GUID (indicated in the previous screen shot) that's assigned to a given update at publication time
|
||||||
- The update ID and revision number are often shown together as "{GUID}.revision."
|
- Revision number: A number incremented every time that a given update (that has a given update ID) is modified and republished on a service
|
||||||
|
- Revision numbers are reused from one update to another (not a unique identifier).
|
||||||
|
- The update ID and revision number are often shown together as "{GUID}.revision."
|
||||||
|
|
||||||
##### Revision ID
|
|
||||||
- A Revision ID (do no confuse this with “revision number”) is a serial number that's issued when an update is initially published or revised on a given service.
|
|
||||||
- An existing update that’s revised keeps the same update ID (GUID), has its revision number incremented (for example, from 100 to 101), but gets a completely new revision ID that is not related to the previous ID.
|
##### Revision ID
|
||||||
- Revision IDs are unique on a given update source, but not across multiple sources.
|
- A Revision ID (do no confuse this with “revision number”) is a serial number that's issued when an update is initially published or revised on a given service.
|
||||||
- The same update revision may have completely different revision IDs on WU and WSUS.
|
- An existing update that’s revised keeps the same update ID (GUID), has its revision number incremented (for example, from 100 to 101), but gets a completely new revision ID that is not related to the previous ID.
|
||||||
- The same revision ID may represent different updates on WU and WSUS.
|
- Revision IDs are unique on a given update source, but not across multiple sources.
|
||||||
|
- The same update revision may have completely different revision IDs on WU and WSUS.
|
||||||
##### Local ID
|
- The same revision ID may represent different updates on WU and WSUS.
|
||||||
- Local ID is a serial number issued when an update is received from a service by a given WU client
|
|
||||||
- Usually seen in debug logs, especially involving the local cache for update info (Datastore)
|
##### Local ID
|
||||||
- Different client PCs will assign different Local IDs to the same update
|
- Local ID is a serial number issued when an update is received from a service by a given WU client
|
||||||
- You can find the local IDs that a client is using by getting the client’s %WINDIR%\SoftwareDistribution\Datastore\Datastore.edb file
|
- Usually seen in debug logs, especially involving the local cache for update info (Datastore)
|
||||||
|
- Different client PCs will assign different Local IDs to the same update
|
||||||
##### Inconsistent terminology
|
- You can find the local IDs that a client is using by getting the client’s %WINDIR%\SoftwareDistribution\Datastore\Datastore.edb file
|
||||||
- Sometimes the logs use terms inconsistently. For example, the InstalledNonLeafUpdateIDs list actually contains revision IDs, not update IDs.
|
|
||||||
- Recognize IDs by form and context:
|
##### Inconsistent terminology
|
||||||
|
- Sometimes the logs use terms inconsistently. For example, the InstalledNonLeafUpdateIDs list actually contains revision IDs, not update IDs.
|
||||||
- GUIDs are update IDs
|
- Recognize IDs by form and context:
|
||||||
- Small integers that appear alongside an update ID are revision numbers
|
|
||||||
- Large integers are typically revision IDs
|
- GUIDs are update IDs
|
||||||
- Small integers (especially in Datastore) can be local IDs
|
- Small integers that appear alongside an update ID are revision numbers
|
||||||
|
- Large integers are typically revision IDs
|
||||||
|
- Small integers (especially in Datastore) can be local IDs
|
||||||
## Windows Setup log files analysis using SetupDiag tool
|
|
||||||
SetupDiag is a diagnostic tool that can be used for analysis of logs related to installation of Windows Updates. For detailed information, see [SetupDiag](https://docs.microsoft.com/windows/deployment/upgrade/setupdiag).
|
|
||||||
|
## Windows Setup log files analysis using SetupDiag tool
|
||||||
|
SetupDiag is a diagnostic tool that can be used for analysis of logs related to installation of Windows Updates. For detailed information, see [SetupDiag](https://docs.microsoft.com/windows/deployment/upgrade/setupdiag).
|
||||||
|
|||||||
@ -1,57 +1,59 @@
|
|||||||
---
|
---
|
||||||
title: Get started with Windows Update
|
title: Get started with Windows Update
|
||||||
description: Learn how Windows Update works, including architecture and troubleshooting
|
description: Learn how Windows Update works, including architecture and troubleshooting
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl:
|
ms.mktglfcycl:
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.audience: itpro
author: greg-lindsay
|
ms.localizationprioauthor: jaimeo
|
||||||
ms.date: 09/18/2018
|
ms.audience: itpro
|
||||||
ms.reviewer:
|
author: jaimeo
|
||||||
manager: laurawi
|
ms.date: 09/18/2018
|
||||||
ms.topic: article
|
ms.reviewer:
|
||||||
---
|
manager: laurawi
|
||||||
|
ms.topic: article
|
||||||
# Get started with Windows Update
|
---
|
||||||
|
|
||||||
>Applies to: Windows 10
|
# Get started with Windows Update
|
||||||
|
|
||||||
With the release of Windows 10, we moved the update model to the Unified Update Platform. Unified Update Platform (UUP) is a single publishing, hosting, scan and download model for all types of OS updates, desktop and mobile for all Windows-based operating systems, for everything from monthly quality updates to new feature updates.
|
>Applies to: Windows 10
|
||||||
|
|
||||||
Ues the following information to get started with Windows Update:
|
With the release of Windows 10, we moved the update model to the Unified Update Platform. Unified Update Platform (UUP) is a single publishing, hosting, scan and download model for all types of OS updates, desktop and mobile for all Windows-based operating systems, for everything from monthly quality updates to new feature updates.
|
||||||
|
|
||||||
- Understand the UUP architecture
|
Ues the following information to get started with Windows Update:
|
||||||
- Understand [how Windows Update works](how-windows-update-works.md)
|
|
||||||
- Find [Windows Update log files](windows-update-logs.md)
|
- Understand the UUP architecture
|
||||||
- Learn how to [troubleshoot Windows Update](windows-update-troubleshooting.md)
|
- Understand [how Windows Update works](how-windows-update-works.md)
|
||||||
- Review [common Windows Update errors](windows-update-errors.md) and check out the [error code reference](windows-update-error-reference.md)
|
- Find [Windows Update log files](windows-update-logs.md)
|
||||||
- Review [other resources](windows-update-resources.md) to help you use Windows Update
|
- Learn how to [troubleshoot Windows Update](windows-update-troubleshooting.md)
|
||||||
|
- Review [common Windows Update errors](windows-update-errors.md) and check out the [error code reference](windows-update-error-reference.md)
|
||||||
## Unified Update Platform (UUP) architecture
|
- Review [other resources](windows-update-resources.md) to help you use Windows Update
|
||||||
To understand the changes to the Windows Update architecture that UUP introduces let's start with some new key terms.
|
|
||||||
|
## Unified Update Platform (UUP) architecture
|
||||||
|
To understand the changes to the Windows Update architecture that UUP introduces let's start with some new key terms.
|
||||||
|
|
||||||
- **Update UI** – The user interface to initiate Windows Update check and history. Available under **Settings --> Update & Security --> Windows Update**.
|
|
||||||
- **Update Session Orchestrator (USO)**- A Windows OS component that orchestrates the sequence of downloading and installing various update types from Windows Update.
|
|
||||||
|
- **Update UI** – The user interface to initiate Windows Update check and history. Available under **Settings --> Update & Security --> Windows Update**.
|
||||||
Update types-
|
- **Update Session Orchestrator (USO)**- A Windows OS component that orchestrates the sequence of downloading and installing various update types from Windows Update.
|
||||||
- OS Feature updates
|
|
||||||
- OS Security updates
|
Update types-
|
||||||
- Device drivers
|
- OS Feature updates
|
||||||
- Defender definition updates
|
- OS Security updates
|
||||||
|
- Device drivers
|
||||||
>[!NOTE]
|
- Defender definition updates
|
||||||
> Other types of updates, like Office desktop updates, are installed if the user opts into Microsoft Update.
|
|
||||||
>
|
>[!NOTE]
|
||||||
>Store apps aren't installed by USO, today they are separate.
|
> Other types of updates, like Office desktop updates, are installed if the user opts into Microsoft Update.
|
||||||
|
>
|
||||||
- **WU Client/ UpdateAgent** - The component running on your PC. It's essentially a DLL that is downloaded to the device when an update is applicable. It surfaces the APIs needed to perform an update, including those needed to generate a list of payloads to download, as well as starts stage and commit operations. It provides a unified interface that abstracts away the underlying update technologies from the caller.
|
>Store apps aren't installed by USO, today they are separate.
|
||||||
- **WU Arbiter handle**- Code that is included in the UpdateAgent binary. The arbiter gathers information about the device, and uses the CompDB(s) to output an action list. It is responsible for determining the final "composition state" of your device, and which payloads (like ESDs or packages) are needed to get your device up to date.
|
|
||||||
- **Deployment Arbiter**- A deployment manager that calls different installers. For example, CBS.
|
- **WU Client/ UpdateAgent** - The component running on your PC. It's essentially a DLL that is downloaded to the device when an update is applicable. It surfaces the APIs needed to perform an update, including those needed to generate a list of payloads to download, as well as starts stage and commit operations. It provides a unified interface that abstracts away the underlying update technologies from the caller.
|
||||||
|
- **WU Arbiter handle**- Code that is included in the UpdateAgent binary. The arbiter gathers information about the device, and uses the CompDB(s) to output an action list. It is responsible for determining the final "composition state" of your device, and which payloads (like ESDs or packages) are needed to get your device up to date.
|
||||||
Additional components include the following-
|
- **Deployment Arbiter**- A deployment manager that calls different installers. For example, CBS.
|
||||||
|
|
||||||
- **CompDB** – A generic term to refer to the XML describing information about target build composition, available diff packages, and conditional rules.
|
Additional components include the following-
|
||||||
- **Action List** – The payload and additional information needed to perform an update. The action list is consumed by the UpdateAgent, as well as other installers to determine what payload to download. It's also consumed by the "Install Agent" to determine what actions need to be taken, such as installing or removing packages.
|
|
||||||
|
- **CompDB** – A generic term to refer to the XML describing information about target build composition, available diff packages, and conditional rules.
|
||||||
|
- **Action List** – The payload and additional information needed to perform an update. The action list is consumed by the UpdateAgent, as well as other installers to determine what payload to download. It's also consumed by the "Install Agent" to determine what actions need to be taken, such as installing or removing packages.
|
||||||
|
|||||||
@ -5,10 +5,10 @@ ms.prod: w10
|
|||||||
ms.mktglfcycl:
|
ms.mktglfcycl:
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: jaimeo
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.audience: itpro
|
ms.audience: itpro
|
||||||
author: greg-lindsay
|
author: jaimeo
|
||||||
ms.date: 09/18/2018
|
ms.date: 09/18/2018
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
|
|||||||
@ -1,217 +1,219 @@
|
|||||||
---
|
---
|
||||||
title: Windows Update troubleshooting
|
title: Windows Update troubleshooting
|
||||||
description: Learn how to troubleshoot Windows Update
|
description: Learn how to troubleshoot Windows Update
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl:
|
ms.mktglfcycl:
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.audience: itpro
author: greg-lindsay
|
ms.localizationprioauthor: jaimeo
|
||||||
ms.date: 09/18/2018
|
ms.audience: itpro
|
||||||
ms.reviewer:
|
author: jaimeo
|
||||||
manager: laurawi
|
ms.date: 09/18/2018
|
||||||
ms.topic: article
|
ms.reviewer:
|
||||||
---
|
manager: laurawi
|
||||||
|
ms.topic: article
|
||||||
# Windows Update troubleshooting
|
---
|
||||||
|
|
||||||
>Applies to: Windows 10
|
# Windows Update troubleshooting
|
||||||
|
|
||||||
If you run into problems when using Windows Update, start with the following steps:
|
>Applies to: Windows 10
|
||||||
|
|
||||||
1. Run the built-in Windows Update troubleshooter to fix common issues. Navigate to **Settings > Update & Security > Troubleshoot > Windows Update**.
|
If you run into problems when using Windows Update, start with the following steps:
|
||||||
2. Install the most recent Servicing Stack Update (SSU) that matches your version of Windows from the Microsoft Update Catalog. See [Servicing stack updates](servicing-stack-updates.md) for more details on SSU.
|
|
||||||
3. Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. To verify the update status, refer to the appropriate update history for your system:
|
1. Run the built-in Windows Update troubleshooter to fix common issues. Navigate to **Settings > Update & Security > Troubleshoot > Windows Update**.
|
||||||
|
2. Install the most recent Servicing Stack Update (SSU) that matches your version of Windows from the Microsoft Update Catalog. See [Servicing stack updates](servicing-stack-updates.md) for more details on SSU.
|
||||||
- [Windows 10, version 1809 and Windows Server 2019](https://support.microsoft.com/help/4464619/windows-10-update-history)
|
3. Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. To verify the update status, refer to the appropriate update history for your system:
|
||||||
- [Windows 10, version 1803](https://support.microsoft.com/help/4099479/windows-10-update-history)
|
|
||||||
- [Windows 10, version 1709](https://support.microsoft.com/help/4043454)
|
- [Windows 10, version 1809 and Windows Server 2019](https://support.microsoft.com/help/4464619/windows-10-update-history)
|
||||||
- [Windows 10, version 1703](https://support.microsoft.com/help/4018124)
|
- [Windows 10, version 1803](https://support.microsoft.com/help/4099479/windows-10-update-history)
|
||||||
- [Windows 10 and Windows Server 2016](https://support.microsoft.com/help/4000825/windows-10-windows-server-2016-update-history)
|
- [Windows 10, version 1709](https://support.microsoft.com/help/4043454)
|
||||||
- [Windows 8.1 and Windows Server 2012 R2](https://support.microsoft.com/help/4009470/windows-8-1-windows-server-2012-r2-update-history)
|
- [Windows 10, version 1703](https://support.microsoft.com/help/4018124)
|
||||||
- [Windows Server 2012](https://support.microsoft.com/help/4009471/windows-server-2012-update-history)
|
- [Windows 10 and Windows Server 2016](https://support.microsoft.com/help/4000825/windows-10-windows-server-2016-update-history)
|
||||||
- [Windows 7 SP1 and Windows Server 2008 R2 SP1](https://support.microsoft.com/help/4009469/windows-7-sp1-windows-server-2008-r2-sp1-update-history)
|
- [Windows 8.1 and Windows Server 2012 R2](https://support.microsoft.com/help/4009470/windows-8-1-windows-server-2012-r2-update-history)
|
||||||
|
- [Windows Server 2012](https://support.microsoft.com/help/4009471/windows-server-2012-update-history)
|
||||||
Advanced users can also refer to the [log](windows-update-logs.md) generated by Windows Update for further investigation.
|
- [Windows 7 SP1 and Windows Server 2008 R2 SP1](https://support.microsoft.com/help/4009469/windows-7-sp1-windows-server-2008-r2-sp1-update-history)
|
||||||
|
|
||||||
You might encounter the following scenarios when using Windows Update.
|
Advanced users can also refer to the [log](windows-update-logs.md) generated by Windows Update for further investigation.
|
||||||
|
|
||||||
## Why am I offered an older update/upgrade?
|
You might encounter the following scenarios when using Windows Update.
|
||||||
The update that is offered to a device depends on several factors. Some of the most common attributes include the following:
|
|
||||||
|
## Why am I offered an older update/upgrade?
|
||||||
- OS Build
|
The update that is offered to a device depends on several factors. Some of the most common attributes include the following:
|
||||||
- OS Branch
|
|
||||||
- OS Locale
|
- OS Build
|
||||||
- OS Architecture
|
- OS Branch
|
||||||
- Device update management configuration
|
- OS Locale
|
||||||
|
- OS Architecture
|
||||||
If the update you're offered isn't the most current available, it might be because your device is being managed by a WSUS server, and you're being offered the updates available on that server. It's also possible, if your device is part of a Windows as a Service deployment ring, that your admin is intentionally slowing the rollout of updates. Since the WaaS rollout is slow and measured to begin with, all devices will not receive the update on the same day.
|
- Device update management configuration
|
||||||
|
|
||||||
## My machine is frozen at scan. Why?
|
If the update you're offered isn't the most current available, it might be because your device is being managed by a WSUS server, and you're being offered the updates available on that server. It's also possible, if your device is part of a Windows as a Service deployment ring, that your admin is intentionally slowing the rollout of updates. Since the WaaS rollout is slow and measured to begin with, all devices will not receive the update on the same day.
|
||||||
The Settings UI is talking to the Update Orchestrator service which in turn is talking to Windows Update service. If these services stop unexpectedly then you might see this behavior. In such cases, do the following:
|
|
||||||
1. Close the Settings app and reopen it.
|
## My machine is frozen at scan. Why?
|
||||||
2. Launch Services.msc and check if the following services are running:
|
The Settings UI is talking to the Update Orchestrator service which in turn is talking to Windows Update service. If these services stop unexpectedly then you might see this behavior. In such cases, do the following:
|
||||||
- Update State Orchestrator
|
1. Close the Settings app and reopen it.
|
||||||
- Windows Update
|
2. Launch Services.msc and check if the following services are running:
|
||||||
|
- Update State Orchestrator
|
||||||
## Feature updates are not being offered while other updates are
|
- Windows Update
|
||||||
On computers running [Windows 10 1709 or higher](#BKMK_DCAT) configured to update from Windows Update (usually WUfB scenario) servicing and definition updates are being installed successfully, but feature updates are never offered.
|
|
||||||
|
## Feature updates are not being offered while other updates are
|
||||||
Checking the WindowsUpdate.log reveals the following error:
|
On computers running [Windows 10 1709 or higher](#BKMK_DCAT) configured to update from Windows Update (usually WUfB scenario) servicing and definition updates are being installed successfully, but feature updates are never offered.
|
||||||
```
|
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent * START * Finding updates CallerId = Update;taskhostw Id = 25
|
Checking the WindowsUpdate.log reveals the following error:
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent Online = Yes; Interactive = No; AllowCachedResults = No; Ignore download priority = No
|
```
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent ServiceID = {855E8A7C-ECB4-4CA3-B045-1DFA50104289} Third party service
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent * START * Finding updates CallerId = Update;taskhostw Id = 25
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent Search Scope = {Current User}
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent Online = Yes; Interactive = No; AllowCachedResults = No; Ignore download priority = No
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent Caller SID for Applicability: S-1-12-1-2933642503-1247987907-1399130510-4207851353
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent ServiceID = {855E8A7C-ECB4-4CA3-B045-1DFA50104289} Third party service
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc Got 855E8A7C-ECB4-4CA3-B045-1DFA50104289 redir Client/Server URL: https://fe3.delivery.mp.microsoft.com/ClientWebService/client.asmx""
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent Search Scope = {Current User}
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc Token Requested with 0 category IDs.
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent Caller SID for Applicability: S-1-12-1-2933642503-1247987907-1399130510-4207851353
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc GetUserTickets: No user tickets found. Returning WU_E_NO_USERTOKEN.
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc Got 855E8A7C-ECB4-4CA3-B045-1DFA50104289 redir Client/Server URL: https://fe3.delivery.mp.microsoft.com/ClientWebService/client.asmx""
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] Method failed [AuthTicketHelper::GetDeviceTickets:570]
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc Token Requested with 0 category IDs.
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] Method failed [AuthTicketHelper::GetDeviceTickets:570]
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc GetUserTickets: No user tickets found. Returning WU_E_NO_USERTOKEN.
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] GetDeviceTickets
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] Method failed [AuthTicketHelper::GetDeviceTickets:570]
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] Method failed [AuthTicketHelper::AddTickets:1092]
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] Method failed [AuthTicketHelper::GetDeviceTickets:570]
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] Method failed [CUpdateEndpointProvider::GenerateSecurityTokenWithAuthTickets:1587]
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] GetDeviceTickets
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] GetAgentTokenFromServer
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] Method failed [AuthTicketHelper::AddTickets:1092]
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] GetAgentToken
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] Method failed [CUpdateEndpointProvider::GenerateSecurityTokenWithAuthTickets:1587]
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] EP:Call to GetEndpointToken
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] GetAgentTokenFromServer
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] Failed to obtain service 855E8A7C-ECB4-4CA3-B045-1DFA50104289 plugin Client/Server auth token of type 0x00000001
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] GetAgentToken
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID ProtocolTalker *FAILED* [80070426] Method failed [CAgentProtocolTalkerContext::DetermineServiceEndpoint:377]
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] EP:Call to GetEndpointToken
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID ProtocolTalker *FAILED* [80070426] Initialization failed for Protocol Talker Context
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Misc *FAILED* [80070426] Failed to obtain service 855E8A7C-ECB4-4CA3-B045-1DFA50104289 plugin Client/Server auth token of type 0x00000001
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent Exit code = 0x80070426
|
YYYY/MM/DD HH:mm:ss:SSS PID TID ProtocolTalker *FAILED* [80070426] Method failed [CAgentProtocolTalkerContext::DetermineServiceEndpoint:377]
|
||||||
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent * END * Finding updates CallerId = Update;taskhostw Id = 25
|
YYYY/MM/DD HH:mm:ss:SSS PID TID ProtocolTalker *FAILED* [80070426] Initialization failed for Protocol Talker Context
|
||||||
```
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent Exit code = 0x80070426
|
||||||
|
YYYY/MM/DD HH:mm:ss:SSS PID TID Agent * END * Finding updates CallerId = Update;taskhostw Id = 25
|
||||||
The 0x80070426 error code translates to:
|
```
|
||||||
```
|
|
||||||
ERROR_SERVICE_NOT_ACTIVE - # The service has not been started.
|
The 0x80070426 error code translates to:
|
||||||
```
|
```
|
||||||
|
ERROR_SERVICE_NOT_ACTIVE - # The service has not been started.
|
||||||
Microsoft Account Sign In Assistant (MSA or wlidsvc) is the service in question. The DCAT Flighting service (ServiceId: 855E8A7C-ECB4-4CA3-B045-1DFA50104289) relies on the Microsoft Account Sign In Assistant (MSA) to get the Global Device ID for the device. Without the MSA service running, the global device ID will not be generated and sent by the client and the search for feature updates never completes successfully.
|
```
|
||||||
|
|
||||||
In order to solve this issue, we need to reset the MSA service to the default StartType of manual.
|
Microsoft Account Sign In Assistant (MSA or wlidsvc) is the service in question. The DCAT Flighting service (ServiceId: 855E8A7C-ECB4-4CA3-B045-1DFA50104289) relies on the Microsoft Account Sign In Assistant (MSA) to get the Global Device ID for the device. Without the MSA service running, the global device ID will not be generated and sent by the client and the search for feature updates never completes successfully.
|
||||||
|
|
||||||
## Issues related to HTTP/Proxy
|
In order to solve this issue, we need to reset the MSA service to the default StartType of manual.
|
||||||
Windows Update uses WinHttp with Partial Range requests (RFC 7233) to download updates and applications from Windows Update servers or on-premises WSUS servers. Because of this proxy servers configured on the network must support HTTP RANGE requests. If a proxy was configured in Internet Explorer (User level) but not in WinHTTP (System level), connections to Windows Update will fail.
|
|
||||||
|
## Issues related to HTTP/Proxy
|
||||||
To fix this issue, configure a proxy in WinHTTP by using the following netsh command:
|
Windows Update uses WinHttp with Partial Range requests (RFC 7233) to download updates and applications from Windows Update servers or on-premises WSUS servers. Because of this proxy servers configured on the network must support HTTP RANGE requests. If a proxy was configured in Internet Explorer (User level) but not in WinHTTP (System level), connections to Windows Update will fail.
|
||||||
|
|
||||||
```
|
To fix this issue, configure a proxy in WinHTTP by using the following netsh command:
|
||||||
netsh winhttp set proxy ProxyServerName:PortNumber
|
|
||||||
```
|
```
|
||||||
|
netsh winhttp set proxy ProxyServerName:PortNumber
|
||||||
>[!NOTE]
|
```
|
||||||
> You can also import the proxy settings from Internet Explorer by using the following command: netsh winhttp import proxy source=ie
|
|
||||||
|
>[!NOTE]
|
||||||
If downloads through a proxy server fail with a 0x80d05001 DO_E_HTTP_BLOCKSIZE_MISMATCH error, or if you notice high CPU usage while updates are downloading, check the proxy configuration to permit HTTP RANGE requests to run.
|
> You can also import the proxy settings from Internet Explorer by using the following command: netsh winhttp import proxy source=ie
|
||||||
|
|
||||||
You may choose to apply a rule to permit HTTP RANGE requests for the following URLs:
|
If downloads through a proxy server fail with a 0x80d05001 DO_E_HTTP_BLOCKSIZE_MISMATCH error, or if you notice high CPU usage while updates are downloading, check the proxy configuration to permit HTTP RANGE requests to run.
|
||||||
|
|
||||||
*.download.windowsupdate.com
|
You may choose to apply a rule to permit HTTP RANGE requests for the following URLs:
|
||||||
*.dl.delivery.mp.microsoft.com
|
|
||||||
*.emdl.ws.microsoft.com
|
*.download.windowsupdate.com
|
||||||
|
*.dl.delivery.mp.microsoft.com
|
||||||
If you cannot permit RANGE requests, keep in mind that this means you are downloading more content than needed in updates (as delta patching will not work).
|
*.emdl.ws.microsoft.com
|
||||||
|
|
||||||
|
If you cannot permit RANGE requests, keep in mind that this means you are downloading more content than needed in updates (as delta patching will not work).
|
||||||
## The update is not applicable to your computer
|
|
||||||
The most common reasons for this error are described in the following table:
|
|
||||||
|
## The update is not applicable to your computer
|
||||||
|Cause|Explanation|Resolution|
|
The most common reasons for this error are described in the following table:
|
||||||
|-----|-----------|----------|
|
|
||||||
|Update is superseded|As updates for a component are released, the updated component will supersede an older component that is already on the system. When this occurs, the previous update is marked as superseded. If the update that you're trying to install already has a newer version of the payload on your system, you may encounter this error message.|Check that the package that you are installing contains newer versions of the binaries. Or, check that the package is superseded by another new package. |
|
|Cause|Explanation|Resolution|
|
||||||
|Update is already installed|If the update that you're trying to install was previously installed, for example, by another update that carried the same payload, you may encounter this error message.|Verify that the package that you are trying to install was not previously installed.|
|
|-----|-----------|----------|
|
||||||
|Wrong update for architecture|Updates are published by CPU architecture. If the update that you're trying to install does not match the architecture for your CPU, you may encounter this error message. |Verify that the package that you're trying to install matches the Windows version that you are using. The Windows version information can be found in the "Applies To" section of the article for each update. For example, Windows Server 2012-only updates cannot be installed on Windows Server 2012 R2-based computers. <br>Also, verify that the package that you are installing matches the processor architecture of the Windows version that you are using. For example, an x86-based update cannot be installed on x64-based installations of Windows. |
|
|Update is superseded|As updates for a component are released, the updated component will supersede an older component that is already on the system. When this occurs, the previous update is marked as superseded. If the update that you're trying to install already has a newer version of the payload on your system, you may encounter this error message.|Check that the package that you are installing contains newer versions of the binaries. Or, check that the package is superseded by another new package. |
|
||||||
|Missing prerequisite update|Some updates require a prerequisite update before they can be applied to a system. If you are missing a prerequisite update, you may encounter this error message. For example, KB 2919355 must be installed on Windows 8.1 and Windows Server 2012 R2 computers before many of the updates that were released after April 2014 can be installed.|Check the related articles about the package in the Microsoft Knowledge Base (KB) to make sure that you have the prerequisite updates installed. For example, if you encounter the error message on Windows 8.1 or Windows Server 2012 R2, you may have to install the April 2014 update 2919355 as a prerequisite and one or more pre-requisite servicing updates (KB 2919442 and KB 3173424). <br>Note: To determine if these prerequisite updates are installed, run the following PowerShell command: <br>get-hotfix KB3173424,KB2919355,KB2919442 <br>If the updates are installed, the command will return the installed date in the "InstalledOn" section of the output.
|
|Update is already installed|If the update that you're trying to install was previously installed, for example, by another update that carried the same payload, you may encounter this error message.|Verify that the package that you are trying to install was not previously installed.|
|
||||||
|
|Wrong update for architecture|Updates are published by CPU architecture. If the update that you're trying to install does not match the architecture for your CPU, you may encounter this error message. |Verify that the package that you're trying to install matches the Windows version that you are using. The Windows version information can be found in the "Applies To" section of the article for each update. For example, Windows Server 2012-only updates cannot be installed on Windows Server 2012 R2-based computers. <br>Also, verify that the package that you are installing matches the processor architecture of the Windows version that you are using. For example, an x86-based update cannot be installed on x64-based installations of Windows. |
|
||||||
## Issues related to firewall configuration
|
|Missing prerequisite update|Some updates require a prerequisite update before they can be applied to a system. If you are missing a prerequisite update, you may encounter this error message. For example, KB 2919355 must be installed on Windows 8.1 and Windows Server 2012 R2 computers before many of the updates that were released after April 2014 can be installed.|Check the related articles about the package in the Microsoft Knowledge Base (KB) to make sure that you have the prerequisite updates installed. For example, if you encounter the error message on Windows 8.1 or Windows Server 2012 R2, you may have to install the April 2014 update 2919355 as a prerequisite and one or more pre-requisite servicing updates (KB 2919442 and KB 3173424). <br>Note: To determine if these prerequisite updates are installed, run the following PowerShell command: <br>get-hotfix KB3173424,KB2919355,KB2919442 <br>If the updates are installed, the command will return the installed date in the "InstalledOn" section of the output.
|
||||||
Error that may be seen in the WU logs:
|
|
||||||
```
|
## Issues related to firewall configuration
|
||||||
DownloadManager Error 0x800706d9 occurred while downloading update; notifying dependent calls.
|
Error that may be seen in the WU logs:
|
||||||
```
|
```
|
||||||
Or
|
DownloadManager Error 0x800706d9 occurred while downloading update; notifying dependent calls.
|
||||||
```
|
```
|
||||||
[DownloadManager] BITS job {A4AC06DD-D6E6-4420-8720-7407734FDAF2} hit a transient error, updateId = {D053C08A-6250-4C43-A111-56C5198FE142}.200 <NULL>, error = 0x800706D9
|
Or
|
||||||
```
|
```
|
||||||
Or
|
[DownloadManager] BITS job {A4AC06DD-D6E6-4420-8720-7407734FDAF2} hit a transient error, updateId = {D053C08A-6250-4C43-A111-56C5198FE142}.200 <NULL>, error = 0x800706D9
|
||||||
```
|
```
|
||||||
DownloadManager [0]12F4.1FE8::09/29/2017-13:45:08.530 [agent]DO job {C6E2F6DC-5B78-4608-B6F1-0678C23614BD} hit a transient error, updateId = 5537BD35-BB74-40B2-A8C3-B696D3C97CBA.201 <NULL>, error = 0x80D0000A
|
Or
|
||||||
```
|
```
|
||||||
|
DownloadManager [0]12F4.1FE8::09/29/2017-13:45:08.530 [agent]DO job {C6E2F6DC-5B78-4608-B6F1-0678C23614BD} hit a transient error, updateId = 5537BD35-BB74-40B2-A8C3-B696D3C97CBA.201 <NULL>, error = 0x80D0000A
|
||||||
Go to Services.msc and ensure that Windows Firewall Service is enabled. Stopping the service associated with Windows Firewall with Advanced Security is not supported by Microsoft. For more information, see [I need to disable Windows Firewall](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc766337(v=ws.10)).
|
```
|
||||||
|
|
||||||
## Issues arising from configuration of conflicting policies
|
Go to Services.msc and ensure that Windows Firewall Service is enabled. Stopping the service associated with Windows Firewall with Advanced Security is not supported by Microsoft. For more information, see [I need to disable Windows Firewall](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc766337(v=ws.10)).
|
||||||
Windows Update provides a wide range configuration policies to control the behavior of WU service in a managed environment. While these policies let you configure the settings at a granular level, misconfiguration or setting conflicting polices may lead to unexpected behaviors.
|
|
||||||
|
## Issues arising from configuration of conflicting policies
|
||||||
See [How to configure automatic updates by using Group Policy or registry settings](https://support.microsoft.com/help/328010/how-to-configure-automatic-updates-by-using-group-policy-or-registry-s) for more information.
|
Windows Update provides a wide range configuration policies to control the behavior of WU service in a managed environment. While these policies let you configure the settings at a granular level, misconfiguration or setting conflicting polices may lead to unexpected behaviors.
|
||||||
|
|
||||||
|
See [How to configure automatic updates by using Group Policy or registry settings](https://support.microsoft.com/help/328010/how-to-configure-automatic-updates-by-using-group-policy-or-registry-s) for more information.
|
||||||
## Updates aren't downloading from the intranet endpoint (WSUS/SCCM)
|
|
||||||
Windows 10 devices can receive updates from a variety of sources, including Windows Update online, a Windows Server Update Services server, and others. To determine the source of Windows Updates currently being used on a device, follow these steps:
|
|
||||||
1. Start Windows PowerShell as an administrator
|
## Updates aren't downloading from the intranet endpoint (WSUS/SCCM)
|
||||||
2. Run \$MUSM = New-Object -ComObject "Microsoft.Update.ServiceManager".
|
Windows 10 devices can receive updates from a variety of sources, including Windows Update online, a Windows Server Update Services server, and others. To determine the source of Windows Updates currently being used on a device, follow these steps:
|
||||||
3. Run \$MUSM.Services.
|
1. Start Windows PowerShell as an administrator
|
||||||
|
2. Run \$MUSM = New-Object -ComObject "Microsoft.Update.ServiceManager".
|
||||||
Check the output for the Name and OffersWindowsUPdates parameters, which you can interpret according to this table.
|
3. Run \$MUSM.Services.
|
||||||
|
|
||||||
|Output|Interpretation|
|
Check the output for the Name and OffersWindowsUPdates parameters, which you can interpret according to this table.
|
||||||
|-|-|
|
|
||||||
|- Name: Microsoft Update <br>-OffersWindowsUpdates: True| - The update source is Microsoft Update, which means that updates for other Microsoft products besides the operating system could also be delivered.<br>- Indicates that the client is configured to receive updates for all Microsoft Products (Office, etc.) |
|
|Output|Interpretation|
|
||||||
|- <a name="BKMK_DCAT"></a>Name: DCat Flighting Prod <br>- OffersWindowsUpdates: True |- Starting with Windows 10 1709, feature updates are always delivered through the DCAT service.<br>- Indicates that the client is configured to receive feature updates from Windows Update. |
|
|-|-|
|
||||||
|- Name: Windows Store (DCat Prod) <br>- OffersWindowsUpdates: False |-The update source is Insider Updates for Store Apps.<br>- Indicates that the client will not receive or is not configured to receive these updates.|
|
|- Name: Microsoft Update <br>-OffersWindowsUpdates: True| - The update source is Microsoft Update, which means that updates for other Microsoft products besides the operating system could also be delivered.<br>- Indicates that the client is configured to receive updates for all Microsoft Products (Office, etc.) |
|
||||||
|- Name: Windows Server Update Service <br>- OffersWindowsUpdates: True |- The source is a Windows Server Updates Services server. <br>- The client is configured to receive updates from WSUS. |
|
|- <a name="BKMK_DCAT"></a>Name: DCat Flighting Prod <br>- OffersWindowsUpdates: True |- Starting with Windows 10 1709, feature updates are always delivered through the DCAT service.<br>- Indicates that the client is configured to receive feature updates from Windows Update. |
|
||||||
|- Name: Windows Update<br>- OffersWindowsUpdates: True|- The source is Windows Update. <br>- The client is configured to receive updates from Windows Update Online.|
|
|- Name: Windows Store (DCat Prod) <br>- OffersWindowsUpdates: False |-The update source is Insider Updates for Store Apps.<br>- Indicates that the client will not receive or is not configured to receive these updates.|
|
||||||
|
|- Name: Windows Server Update Service <br>- OffersWindowsUpdates: True |- The source is a Windows Server Updates Services server. <br>- The client is configured to receive updates from WSUS. |
|
||||||
## You have a bad setup in the environment
|
|- Name: Windows Update<br>- OffersWindowsUpdates: True|- The source is Windows Update. <br>- The client is configured to receive updates from Windows Update Online.|
|
||||||
If we look at the GPO being set through registry, the system is configured to use WSUS to download updates:
|
|
||||||
|
## You have a bad setup in the environment
|
||||||
```
|
If we look at the GPO being set through registry, the system is configured to use WSUS to download updates:
|
||||||
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
|
|
||||||
"UseWUServer"=dword:00000001 ===================================> it says use WSUS server.
|
```
|
||||||
```
|
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
|
||||||
|
"UseWUServer"=dword:00000001 ===================================> it says use WSUS server.
|
||||||
From the WU logs:
|
```
|
||||||
```
|
|
||||||
2018-08-06 09:33:31:085 480 1118 Agent ** START ** Agent: Finding updates [CallerId = OperationalInsight Id = 49]
|
From the WU logs:
|
||||||
2018-08-06 09:33:31:085 480 1118 Agent *********
|
```
|
||||||
2018-08-06 09:33:31:085 480 1118 Agent * Include potentially superseded updates
|
2018-08-06 09:33:31:085 480 1118 Agent ** START ** Agent: Finding updates [CallerId = OperationalInsight Id = 49]
|
||||||
2018-08-06 09:33:31:085 480 1118 Agent * Online = No; Ignore download priority = No
|
2018-08-06 09:33:31:085 480 1118 Agent *********
|
||||||
2018-08-06 09:33:31:085 480 1118 Agent * Criteria = "IsHidden = 0 AND DeploymentAction=*"
|
2018-08-06 09:33:31:085 480 1118 Agent * Include potentially superseded updates
|
||||||
2018-08-06 09:33:31:085 480 1118 Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
|
2018-08-06 09:33:31:085 480 1118 Agent * Online = No; Ignore download priority = No
|
||||||
2018-08-06 09:33:31:085 480 1118 Agent * Search Scope = {Machine}
|
2018-08-06 09:33:31:085 480 1118 Agent * Criteria = "IsHidden = 0 AND DeploymentAction=*"
|
||||||
2018-08-06 09:33:32:554 480 1118 Agent * Found 83 updates and 83 categories in search; evaluated appl. rules of 517 out of 1473 deployed entities
|
2018-08-06 09:33:31:085 480 1118 Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
|
||||||
2018-08-06 09:33:32:554 480 1118 Agent *********
|
2018-08-06 09:33:31:085 480 1118 Agent * Search Scope = {Machine}
|
||||||
2018-08-06 09:33:32:554 480 1118 Agent ** END ** Agent: Finding updates [CallerId = OperationalInsight Id = 49]
|
2018-08-06 09:33:32:554 480 1118 Agent * Found 83 updates and 83 categories in search; evaluated appl. rules of 517 out of 1473 deployed entities
|
||||||
```
|
2018-08-06 09:33:32:554 480 1118 Agent *********
|
||||||
|
2018-08-06 09:33:32:554 480 1118 Agent ** END ** Agent: Finding updates [CallerId = OperationalInsight Id = 49]
|
||||||
In the above log snippet, we see that the Criteria = "IsHidden = 0 AND DeploymentAction=*". "*" means there is nothing specified from the server. So, the scan happens but there is no direction to download or install to the agent. So it just scans the update and provides the results.
|
```
|
||||||
|
|
||||||
Now if you look at the below logs, the Automatic update runs the scan and finds no update approved for it. So it reports there are 0 updates to install or download. This is due to bad setup or configuration in the environment. The WSUS side should approve the patches for WU so that it fetches the updates and installs it on the specified time according to the policy. Since this scenario doesn't include SCCM, there's no way to install unapproved updates. And that is the problem you are facing. You expect that the scan should be done by the operational insight agent and automatically trigger download and install but that won’t happen here.
|
In the above log snippet, we see that the Criteria = "IsHidden = 0 AND DeploymentAction=*". "*" means there is nothing specified from the server. So, the scan happens but there is no direction to download or install to the agent. So it just scans the update and provides the results.
|
||||||
|
|
||||||
```
|
Now if you look at the below logs, the Automatic update runs the scan and finds no update approved for it. So it reports there are 0 updates to install or download. This is due to bad setup or configuration in the environment. The WSUS side should approve the patches for WU so that it fetches the updates and installs it on the specified time according to the policy. Since this scenario doesn't include SCCM, there's no way to install unapproved updates. And that is the problem you are facing. You expect that the scan should be done by the operational insight agent and automatically trigger download and install but that won’t happen here.
|
||||||
2018-08-06 10:58:45:992 480 5d8 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 57]
|
|
||||||
2018-08-06 10:58:45:992 480 5d8 Agent *********
|
```
|
||||||
2018-08-06 10:58:45:992 480 5d8 Agent * Online = Yes; Ignore download priority = No
|
2018-08-06 10:58:45:992 480 5d8 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 57]
|
||||||
2018-08-06 10:58:45:992 480 5d8 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
|
2018-08-06 10:58:45:992 480 5d8 Agent *********
|
||||||
|
2018-08-06 10:58:45:992 480 5d8 Agent * Online = Yes; Ignore download priority = No
|
||||||
2018-08-06 10:58:46:617 480 5d8 PT + SyncUpdates round trips: 2
|
2018-08-06 10:58:45:992 480 5d8 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
|
||||||
2018-08-06 10:58:47:383 480 5d8 Agent * Found 0 updates and 83 categories in search; evaluated appl. rules of 617 out of 1473 deployed entities
|
|
||||||
2018-08-06 10:58:47:383 480 5d8 Agent Reporting status event with 0 installable, 83 installed, 0 installed pending, 0 failed and 0 downloaded updates
|
2018-08-06 10:58:46:617 480 5d8 PT + SyncUpdates round trips: 2
|
||||||
2018-08-06 10:58:47:383 480 5d8 Agent *********
|
2018-08-06 10:58:47:383 480 5d8 Agent * Found 0 updates and 83 categories in search; evaluated appl. rules of 617 out of 1473 deployed entities
|
||||||
2018-08-06 10:58:47:383 480 5d8 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 57]
|
2018-08-06 10:58:47:383 480 5d8 Agent Reporting status event with 0 installable, 83 installed, 0 installed pending, 0 failed and 0 downloaded updates
|
||||||
```
|
2018-08-06 10:58:47:383 480 5d8 Agent *********
|
||||||
|
2018-08-06 10:58:47:383 480 5d8 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 57]
|
||||||
## High bandwidth usage on Windows 10 by Windows Update
|
```
|
||||||
Users may see that Windows 10 is consuming all the bandwidth in the different offices under the system context. This behavior is by design. Components that may consume bandwidth expand beyond Windows Update components.
|
|
||||||
|
## High bandwidth usage on Windows 10 by Windows Update
|
||||||
The following group policies can help mitigate this:
|
Users may see that Windows 10 is consuming all the bandwidth in the different offices under the system context. This behavior is by design. Components that may consume bandwidth expand beyond Windows Update components.
|
||||||
|
|
||||||
- Blocking access to Windows Update servers: [Policy Turn off access to all Windows Update features](http://gpsearch.azurewebsites.net/#4728) (Set to enabled)
|
The following group policies can help mitigate this:
|
||||||
- Driver search: [Policy Specify search order for device driver source locations](http://gpsearch.azurewebsites.net/#183) (Set to "Do not search Windows Update")
|
|
||||||
- Windows Store automatic update: [Policy Turn off Automatic Download and Install of updates](http://gpsearch.azurewebsites.net/#10876) (Set to enabled)
|
- Blocking access to Windows Update servers: [Policy Turn off access to all Windows Update features](http://gpsearch.azurewebsites.net/#4728) (Set to enabled)
|
||||||
|
- Driver search: [Policy Specify search order for device driver source locations](http://gpsearch.azurewebsites.net/#183) (Set to "Do not search Windows Update")
|
||||||
Other components that reach out to the internet:
|
- Windows Store automatic update: [Policy Turn off Automatic Download and Install of updates](http://gpsearch.azurewebsites.net/#10876) (Set to enabled)
|
||||||
|
|
||||||
- Windows Spotlight: [Policy Configure Windows spotlight on lock screen](http://gpsearch.azurewebsites.net/#13362) (Set to disabled)
|
Other components that reach out to the internet:
|
||||||
- Consumer experiences: [Policy Turn off Microsoft consumer experiences](http://gpsearch.azurewebsites.net/#13329) (Set to enabled)
|
|
||||||
- Background traffic from Windows apps: [Policy Let Windows apps run in the background](http://gpsearch.azurewebsites.net/#13571)
|
- Windows Spotlight: [Policy Configure Windows spotlight on lock screen](http://gpsearch.azurewebsites.net/#13362) (Set to disabled)
|
||||||
|
- Consumer experiences: [Policy Turn off Microsoft consumer experiences](http://gpsearch.azurewebsites.net/#13329) (Set to enabled)
|
||||||
|
- Background traffic from Windows apps: [Policy Let Windows apps run in the background](http://gpsearch.azurewebsites.net/#13571)
|
||||||
|
|||||||
@ -1,37 +1,39 @@
|
|||||||
---
|
---
|
||||||
title: Setting up Automatic Update in Windows Update for Business (Windows 10)
|
title: Setting up Automatic Update in Windows Update for Business (Windows 10)
|
||||||
description: Learn how to get started using Windows Update for Business.
|
description: Learn how to get started using Windows Update for Business.
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.audience: itpro
author: greg-lindsay
|
ms.localizationprioauthor: jaimeo
|
||||||
ms.date: 06/20/2018
|
ms.audience: itpro
|
||||||
ms.reviewer:
|
author: jaimeo
|
||||||
manager: laurawi
|
ms.date: 06/20/2018
|
||||||
ms.topic: article
|
ms.reviewer:
|
||||||
---
|
manager: laurawi
|
||||||
|
ms.topic: article
|
||||||
# Set up Automatic Update in Windows Update for Business with group policies
|
---
|
||||||
|
|
||||||
>Applies to: Windows 10
|
# Set up Automatic Update in Windows Update for Business with group policies
|
||||||
|
|
||||||
Use the Automatic Update group policies to manage the interaction between Windows Update and clients.
|
>Applies to: Windows 10
|
||||||
|
|
||||||
Automatic Update governs the "behind the scenes" download and installation processes. It's important to keep in mind the device limitation in your environment as the download and install process can consume processing power. The below section outlines the ideal configuration for devices with the least amount of user experience degradation.
|
Use the Automatic Update group policies to manage the interaction between Windows Update and clients.
|
||||||
|
|
||||||
|Policy|Description |
|
Automatic Update governs the "behind the scenes" download and installation processes. It's important to keep in mind the device limitation in your environment as the download and install process can consume processing power. The below section outlines the ideal configuration for devices with the least amount of user experience degradation.
|
||||||
|-|-|
|
|
||||||
|Configure Automatic Updates|Governs the installation activity that happens in the background. This allows you to configure the installation to happen during the [maintenance window](https://docs.microsoft.com/sccm/core/clients/manage/collections/use-maintenance-windows). Also, you can specify an installation time where the device will also try to install the latest packages. You can also pick a certain day and or week.|
|
|Policy|Description |
|
||||||
|Automatic Update Detection Frequency|Lets you set the scan frequency the device will use to connect to Windows Update to see if there is any available content. Default is 22 hours, but you can increase or decrease the frequency. Keep in mind a desktop computer may need to scan less frequently than laptops, which can have intermittent internet connection.|
|
|-|-|
|
||||||
|Specify Intranet Microsoft Update Service Location|Used for Windows Server Update Services or System Center Configuration Manager users who want to install custom packages that are not offered through Windows Update.|
|
|Configure Automatic Updates|Governs the installation activity that happens in the background. This allows you to configure the installation to happen during the [maintenance window](https://docs.microsoft.com/sccm/core/clients/manage/collections/use-maintenance-windows). Also, you can specify an installation time where the device will also try to install the latest packages. You can also pick a certain day and or week.|
|
||||||
|Do not connect to any Windows Update Internet locations <br>Required for Dual Scan|Prevents access to Windows Update.|
|
|Automatic Update Detection Frequency|Lets you set the scan frequency the device will use to connect to Windows Update to see if there is any available content. Default is 22 hours, but you can increase or decrease the frequency. Keep in mind a desktop computer may need to scan less frequently than laptops, which can have intermittent internet connection.|
|
||||||
|
|Specify Intranet Microsoft Update Service Location|Used for Windows Server Update Services or System Center Configuration Manager users who want to install custom packages that are not offered through Windows Update.|
|
||||||
## Suggested configuration
|
|Do not connect to any Windows Update Internet locations <br>Required for Dual Scan|Prevents access to Windows Update.|
|
||||||
|
|
||||||
|Policy|Location|Suggested configuration|
|
## Suggested configuration
|
||||||
|-|-|-|
|
|
||||||
|Configure Automatic Updates| GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates| **Attention**: If you are using this policy, don't set it/configure it to get the default behavior. If you have set this policy, delete the reg key. This ensures the device uses the default behavior. Note that this is not the same as the default setting within the policy.<br><br> **Default behavior**: Download and installation happen automatically. The device will then be in a pending reboot state. <br><br>**Pro tip**: You can configure the scan frequency to be more frequent with the policy below.|
|
|Policy|Location|Suggested configuration|
|
||||||
|Automatic Update Detection Frequency|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Automatic Updates detection frequency|State: Enabled <br>**Check for updates on the following interval (hours)**: 22|
|
|-|-|-|
|
||||||
|Do not connect to any Windows Update Internet locations (Required for Dual Scan) | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not connect to any Windows Update Internet locations |State: Disabled |
|
|Configure Automatic Updates| GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates| **Attention**: If you are using this policy, don't set it/configure it to get the default behavior. If you have set this policy, delete the reg key. This ensures the device uses the default behavior. Note that this is not the same as the default setting within the policy.<br><br> **Default behavior**: Download and installation happen automatically. The device will then be in a pending reboot state. <br><br>**Pro tip**: You can configure the scan frequency to be more frequent with the policy below.|
|
||||||
|
|Automatic Update Detection Frequency|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Automatic Updates detection frequency|State: Enabled <br>**Check for updates on the following interval (hours)**: 22|
|
||||||
|
|Do not connect to any Windows Update Internet locations (Required for Dual Scan) | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not connect to any Windows Update Internet locations |State: Disabled |
|
||||||
|
|||||||
@ -1,29 +1,31 @@
|
|||||||
---
|
---
|
||||||
title: Configure the Basic group policy for Windows Update for Business
|
title: Configure the Basic group policy for Windows Update for Business
|
||||||
description: Learn how to get started using the Basic GPO in Windows Update for Business.
|
description: Learn how to get started using the Basic GPO in Windows Update for Business.
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.audience: itpro
author: greg-lindsay
|
ms.localizationprioauthor: jaimeo
|
||||||
ms.date: 06/20/2018
|
ms.audience: itpro
|
||||||
ms.reviewer:
|
author: jaimeo
|
||||||
manager: laurawi
|
ms.date: 06/20/2018
|
||||||
ms.topic: article
|
ms.reviewer:
|
||||||
---
|
manager: laurawi
|
||||||
# Configure the Basic group policy for Windows Update for Business
|
ms.topic: article
|
||||||
|
---
|
||||||
For Windows Update for Business configurations to work, devices need to be configured with minimum [diagnostic data](https://docs.microsoft.com/windows/privacy/configure-windows-diagnostic-data-in-your-organization) level of "Basic." Additionally, compliance reporting for configured devices is obtained using [Update Compliance in Windows Analytics](https://docs.microsoft.com/windows/deployment/update/update-compliance-monitor). To view your data in Update Compliance [diagnostics data must be enabled](https://docs.microsoft.com/windows/deployment/update/windows-analytics-get-started#set-diagnostic-data-levels) and the devices must be configured with a commercial ID, a unique GUID created for an enterprise at the time of onboarding to the Windows Analytics solution.
|
# Configure the Basic group policy for Windows Update for Business
|
||||||
|
|
||||||
|Policy name|Description |
|
For Windows Update for Business configurations to work, devices need to be configured with minimum [diagnostic data](https://docs.microsoft.com/windows/privacy/configure-windows-diagnostic-data-in-your-organization) level of "Basic." Additionally, compliance reporting for configured devices is obtained using [Update Compliance in Windows Analytics](https://docs.microsoft.com/windows/deployment/update/update-compliance-monitor). To view your data in Update Compliance [diagnostics data must be enabled](https://docs.microsoft.com/windows/deployment/update/windows-analytics-get-started#set-diagnostic-data-levels) and the devices must be configured with a commercial ID, a unique GUID created for an enterprise at the time of onboarding to the Windows Analytics solution.
|
||||||
|-|-|
|
|
||||||
|Allow Telemetry|Enables Microsoft to run diagnostics on your device and troubleshoot.|
|
|Policy name|Description |
|
||||||
|Configure Commercial ID|This policy allows you to join the device to an entity.|
|
|-|-|
|
||||||
|
|Allow Telemetry|Enables Microsoft to run diagnostics on your device and troubleshoot.|
|
||||||
## Suggested configuration
|
|Configure Commercial ID|This policy allows you to join the device to an entity.|
|
||||||
|
|
||||||
|Policy|Location|Suggested configuration|
|
## Suggested configuration
|
||||||
|-|-|-|
|
|
||||||
|Allow Telemetry |GPO: Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > Allow Telemetry |State: Enabled <br>**Option**: 1-Basic|
|
|Policy|Location|Suggested configuration|
|
||||||
|Configure Commercial ID|GPO: Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > Configure Commercial ID |State: Enabled <br>**Commercial ID**: The GUID created for you at the time of onboarding to Windows Analytics|
|
|-|-|-|
|
||||||
|
|Allow Telemetry |GPO: Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > Allow Telemetry |State: Enabled <br>**Option**: 1-Basic|
|
||||||
|
|Configure Commercial ID|GPO: Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > Configure Commercial ID |State: Enabled <br>**Commercial ID**: The GUID created for you at the time of onboarding to Windows Analytics|
|
||||||
|
|||||||
@ -1,68 +1,70 @@
|
|||||||
---
|
---
|
||||||
title: Managing drivers, dual-managed environments, and Delivery Optimization with group policies in Windows Update for Business
|
title: Managing drivers, dual-managed environments, and Delivery Optimization with group policies in Windows Update for Business
|
||||||
description: Learn how to manage drivers, dual managed environments, and bandwidth (Delivery Optimization) with GPOs in Windows Update for Business.
|
description: Learn how to manage drivers, dual managed environments, and bandwidth (Delivery Optimization) with GPOs in Windows Update for Business.
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.audience: itpro
author: greg-lindsay
|
ms.localizationprioauthor: jaimeo
|
||||||
ms.date: 06/21/2018
|
ms.audience: itpro
|
||||||
ms.reviewer:
|
author: jaimeo
|
||||||
manager: laurawi
|
ms.date: 06/21/2018
|
||||||
ms.topic: article
|
ms.reviewer:
|
||||||
---
|
manager: laurawi
|
||||||
# Managing drivers, dual-managed environments, and Delivery Optimization with group policies
|
ms.topic: article
|
||||||
|
---
|
||||||
>Applies to: Windows 10
|
# Managing drivers, dual-managed environments, and Delivery Optimization with group policies
|
||||||
|
|
||||||
Use the following group policy information to manage drivers, to manage environments using both Windows Update for Business and Windows Server Update Services, and to manage the bandwidth required for updates with Delivery Optimization.
|
>Applies to: Windows 10
|
||||||
|
|
||||||
## Managing drivers
|
Use the following group policy information to manage drivers, to manage environments using both Windows Update for Business and Windows Server Update Services, and to manage the bandwidth required for updates with Delivery Optimization.
|
||||||
Windows Update for Business provides the ability to manage drivers from the Windows Update service. By default, drivers will be offered to your Windows Update-connected devices. Our guidance here is to continue to receive drivers from Windows Update. Alternatively, you can enable the following policy to stop receiving drivers from Windows Update.
|
|
||||||
|
## Managing drivers
|
||||||
### Policy overview
|
Windows Update for Business provides the ability to manage drivers from the Windows Update service. By default, drivers will be offered to your Windows Update-connected devices. Our guidance here is to continue to receive drivers from Windows Update. Alternatively, you can enable the following policy to stop receiving drivers from Windows Update.
|
||||||
|
|
||||||
|Policy| Description |
|
### Policy overview
|
||||||
|-|-|
|
|
||||||
|Do not include drivers with Windows Update |When enabled prevents Windows Update from offering drivers.|
|
|Policy| Description |
|
||||||
|
|-|-|
|
||||||
### Suggested configuration
|
|Do not include drivers with Windows Update |When enabled prevents Windows Update from offering drivers.|
|
||||||
|
|
||||||
|Policy| Location|Suggested configuration |
|
### Suggested configuration
|
||||||
|-|-|-|
|
|
||||||
|Do not include drivers with Windows Update |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not include drivers with Windows Updates|State: Disabled |
|
|Policy| Location|Suggested configuration |
|
||||||
|
|-|-|-|
|
||||||
## Dual-managed environment
|
|Do not include drivers with Windows Update |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not include drivers with Windows Updates|State: Disabled |
|
||||||
|
|
||||||
You can use an on-premises catalog, like WSUS, to deploy 3rd Party patches and use Windows Update to deploy feature and quality updates. We provide capabilities to deploy content from both Windows Update Service and from WSUS. In addition to the policies for managing drivers, apply the following configurations to your environment.
|
## Dual-managed environment
|
||||||
|
|
||||||
|Policy| Description |
|
You can use an on-premises catalog, like WSUS, to deploy 3rd Party patches and use Windows Update to deploy feature and quality updates. We provide capabilities to deploy content from both Windows Update Service and from WSUS. In addition to the policies for managing drivers, apply the following configurations to your environment.
|
||||||
|-|-|
|
|
||||||
|Specify Intranet Microsoft Update Service Location| Used for WSUS/System Center Configuration Manager customers who want to install custom packages that are not offered through Windows Update.|
|
|Policy| Description |
|
||||||
|
|-|-|
|
||||||
### Suggested configuration
|
|Specify Intranet Microsoft Update Service Location| Used for WSUS/System Center Configuration Manager customers who want to install custom packages that are not offered through Windows Update.|
|
||||||
|
|
||||||
|Policy| Location|Suggested configuration |
|
### Suggested configuration
|
||||||
|-|-|-|
|
|
||||||
|Specify Intranet Microsoft Update Service Location|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify Intranet Microsoft update service location|State: Enabled <br>**Set the Intranet Update service for detecting updates**: <br>**Set the Intranet statistics server**: <br>**Set the alternate download server**: |
|
|Policy| Location|Suggested configuration |
|
||||||
|
|-|-|-|
|
||||||
## Download Optimization - Managing your bandwidth
|
|Specify Intranet Microsoft Update Service Location|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify Intranet Microsoft update service location|State: Enabled <br>**Set the Intranet Update service for detecting updates**: <br>**Set the Intranet statistics server**: <br>**Set the alternate download server**: |
|
||||||
|
|
||||||
[Delivery Optimization](waas-delivery-optimization.md) is Windows 10's built-in downloader and peer-caching technology that can benefit CSE for network bandwidth reduction of Windows 10 servicing updates. Windows 10 clients can source content from other devices on their local network that have already downloaded the same updates in addition to downloading these updates from Microsoft. 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. To configure devices for delivery optimization, ensure the following configurations are set.
|
## Download Optimization - Managing your bandwidth
|
||||||
|
|
||||||
|Policy| Description |
|
[Delivery Optimization](waas-delivery-optimization.md) is Windows 10's built-in downloader and peer-caching technology that can benefit CSE for network bandwidth reduction of Windows 10 servicing updates. Windows 10 clients can source content from other devices on their local network that have already downloaded the same updates in addition to downloading these updates from Microsoft. 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. To configure devices for delivery optimization, ensure the following configurations are set.
|
||||||
|-|-|
|
|
||||||
|Download Mode| 2=HTTP blended with peering across a private group. Peering occurs on devices in the same Active Directory Site (if exist) or the same domain by default. When this option is selected, peering will cross NATs. To create a custom group use Group ID in combination with Mode 2|
|
|Policy| Description |
|
||||||
|Minimum Peer Caching Content File Size (in MB)|Specifies the minimum content file size in MB enabled to use peer caching. <br>Choose a size that meets your environment's constraints.|
|
|-|-|
|
||||||
|Allow uploads while the device is on battery while under set battery level (percentage)|Specify a battery level from 1-100, where the device will pause uploads once the battery level drops below that percentage. |
|
|Download Mode| 2=HTTP blended with peering across a private group. Peering occurs on devices in the same Active Directory Site (if exist) or the same domain by default. When this option is selected, peering will cross NATs. To create a custom group use Group ID in combination with Mode 2|
|
||||||
|Max Cache Age (in seconds)|Maximum number of seconds to keep data in cache.|
|
|Minimum Peer Caching Content File Size (in MB)|Specifies the minimum content file size in MB enabled to use peer caching. <br>Choose a size that meets your environment's constraints.|
|
||||||
|
|Allow uploads while the device is on battery while under set battery level (percentage)|Specify a battery level from 1-100, where the device will pause uploads once the battery level drops below that percentage. |
|
||||||
### Suggested configuration
|
|Max Cache Age (in seconds)|Maximum number of seconds to keep data in cache.|
|
||||||
|
|
||||||
|Policy| Location| Suggested configuration |
|
### Suggested configuration
|
||||||
|-|-|-|
|
|
||||||
|Download Mode|GPO: Computer Configuration > Administrative Templates > Windows Components > Delivery Optimization > Download Mode|State: Enabled <br>**Download Mode**: Group (2)|
|
|Policy| Location| Suggested configuration |
|
||||||
|Minimum Peer Caching Content File Size (in MB)|GPO: Computer Configuration > Administrative Templates > Windows Components > Delivery Optimization > Minimum Peer Caching Content File Size (in MB)|State: Enabled <br>**Minimum Peer caching content file size (in MB)**: 10 MB|
|
|-|-|-|
|
||||||
|Allow uploads while the device is on battery while under set battery level (percentage)|GPO: Computer Configuration > Administrative Templates > Windows Components > Delivery Optimization > Allow uploads while the device is on battery while under set battery level (percentage)|State: Enabled <br>**Minimum battery level (Percentage)**: 60|
|
|Download Mode|GPO: Computer Configuration > Administrative Templates > Windows Components > Delivery Optimization > Download Mode|State: Enabled <br>**Download Mode**: Group (2)|
|
||||||
|Max Cache Age (in seconds)|GPO: Computer Configuration > Administrative Templates > Windows Components > Delivery Optimization > Max Cache Age (in seconds)|State: Enabled <br>**Max Cache Age (in seconds)**: 604800 ~ 7 days|
|
|Minimum Peer Caching Content File Size (in MB)|GPO: Computer Configuration > Administrative Templates > Windows Components > Delivery Optimization > Minimum Peer Caching Content File Size (in MB)|State: Enabled <br>**Minimum Peer caching content file size (in MB)**: 10 MB|
|
||||||
|
|Allow uploads while the device is on battery while under set battery level (percentage)|GPO: Computer Configuration > Administrative Templates > Windows Components > Delivery Optimization > Allow uploads while the device is on battery while under set battery level (percentage)|State: Enabled <br>**Minimum battery level (Percentage)**: 60|
|
||||||
|
|Max Cache Age (in seconds)|GPO: Computer Configuration > Administrative Templates > Windows Components > Delivery Optimization > Max Cache Age (in seconds)|State: Enabled <br>**Max Cache Age (in seconds)**: 604800 ~ 7 days|
|
||||||
|
|||||||
@ -1,59 +1,61 @@
|
|||||||
---
|
---
|
||||||
title: Managing feature and quality updates with policies in Windows Update for Business (Windows 10)
|
title: Managing feature and quality updates with policies in Windows Update for Business (Windows 10)
|
||||||
description: Learn how to get started using Windows Update for Business.
|
description: Learn how to get started using Windows Update for Business.
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.audience: itpro
author: greg-lindsay
|
ms.localizationprioauthor: jaimeo
|
||||||
ms.date: 06/20/2018
|
ms.audience: itpro
|
||||||
ms.reviewer:
|
author: jaimeo
|
||||||
manager: laurawi
|
ms.date: 06/20/2018
|
||||||
ms.topic: article
|
ms.reviewer:
|
||||||
---
|
manager: laurawi
|
||||||
|
ms.topic: article
|
||||||
# Manage feature and quality updates with group policies
|
---
|
||||||
|
|
||||||
>Applies to: Windows 10
|
# Manage feature and quality updates with group policies
|
||||||
|
|
||||||
Windows Update for Business allows users to control when devices should receive a feature or quality update from Windows Update. Depending on the size of your organization you may want to do a wave deployment of updates. The first step in this process is to determine which Branch Readiness Level you want your organization on. For more information on which level is right for your organization review [Overview of Windows as a service](waas-overview.md).
|
>Applies to: Windows 10
|
||||||
|
|
||||||
The following policies let you configure when you want a device to see a feature and or quality update from Windows Update.
|
Windows Update for Business allows users to control when devices should receive a feature or quality update from Windows Update. Depending on the size of your organization you may want to do a wave deployment of updates. The first step in this process is to determine which Branch Readiness Level you want your organization on. For more information on which level is right for your organization review [Overview of Windows as a service](waas-overview.md).
|
||||||
|
|
||||||
## Policy overview
|
The following policies let you configure when you want a device to see a feature and or quality update from Windows Update.
|
||||||
|
|
||||||
|Policy name| Description |
|
## Policy overview
|
||||||
|-|-|
|
|
||||||
|Select when Quality Updates are received|Configures when the device should receive quality update. In this policy you can also select a date to pause receiving Quality Updates until. |
|
|Policy name| Description |
|
||||||
|Select when Preview Builds & feature Updates are received|Configures when the device should receive a feature update. You can also configure your branch readiness level. This policy also provides the ability to "pause" updates until a certain point. |
|
|-|-|
|
||||||
|Do not allow update deferral policies to cause scans against Windows Update|When enabled will not allow the deferral policies to cause scans against Windows Update.|
|
|Select when Quality Updates are received|Configures when the device should receive quality update. In this policy you can also select a date to pause receiving Quality Updates until. |
|
||||||
|
|Select when Preview Builds & feature Updates are received|Configures when the device should receive a feature update. You can also configure your branch readiness level. This policy also provides the ability to "pause" updates until a certain point. |
|
||||||
## Suggested configuration for a non-wave deployment
|
|Do not allow update deferral policies to cause scans against Windows Update|When enabled will not allow the deferral policies to cause scans against Windows Update.|
|
||||||
|
|
||||||
If you don't need a wave deployment and have a small set of devices to manage, we recommend the following configuration:
|
## Suggested configuration for a non-wave deployment
|
||||||
|
|
||||||
|Policy| Location|Suggested configuration |
|
If you don't need a wave deployment and have a small set of devices to manage, we recommend the following configuration:
|
||||||
|-|-|-|
|
|
||||||
|Select when Quality Updates are received | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Quality Updates are received|State: Enabled <br>**Defer receiving it for this many days**: 0<br>**Pause Quality Updates**: Blank <br>*Note: use this functionality to prevent the device from receiving a quality update until the time passes|
|
|Policy| Location|Suggested configuration |
|
||||||
|Select when Preview Builds & feature Updates are received |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and Feature Updates are received|State: Enabled <br>**Select Windows Readiness Level**: SAC<br>**Defer receiving for this many days**: 0-365<br>**Pause Feature Updates**: Blank <br>*Note: use this functionality to prevent the device from receiving a feature update until the time passes|
|
|-|-|-|
|
||||||
|Do not allow update deferral policies to cause scans against Windows Update|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not allow update deferral policies to cause scans against Windows Update|State: Disabled|
|
|Select when Quality Updates are received | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Quality Updates are received|State: Enabled <br>**Defer receiving it for this many days**: 0<br>**Pause Quality Updates**: Blank <br>*Note: use this functionality to prevent the device from receiving a quality update until the time passes|
|
||||||
|
|Select when Preview Builds & feature Updates are received |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and Feature Updates are received|State: Enabled <br>**Select Windows Readiness Level**: SAC<br>**Defer receiving for this many days**: 0-365<br>**Pause Feature Updates**: Blank <br>*Note: use this functionality to prevent the device from receiving a feature update until the time passes|
|
||||||
## Suggested configuration for a wave deployment
|
|Do not allow update deferral policies to cause scans against Windows Update|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not allow update deferral policies to cause scans against Windows Update|State: Disabled|
|
||||||
|
|
||||||
|
## Suggested configuration for a wave deployment
|
||||||
## Early validation and testing
|
|
||||||
Depending on your organizational size and requirements you might be able to test feature updates earlier to identify if there are impacts to Line of Business applications. Our recommendation is to enroll a set of devices that are a good representation of your device ecosystem (for example, devices with accounting software or engineering software). Learn more about [different deployment rings](https://insider.windows.com/how-to-pc/#working-with-rings).
|
|
||||||
|
## Early validation and testing
|
||||||
|Policy|Location|Suggested configuration |
|
Depending on your organizational size and requirements you might be able to test feature updates earlier to identify if there are impacts to Line of Business applications. Our recommendation is to enroll a set of devices that are a good representation of your device ecosystem (for example, devices with accounting software or engineering software). Learn more about [different deployment rings](https://insider.windows.com/how-to-pc/#working-with-rings).
|
||||||
|-|-|-|
|
|
||||||
|Select when Preview Builds & feature Updates are received |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and Feature Updates are received|State: Enabled <br>**Select Windows Readiness Level**: WIP Fast or WIP slow<br>**Defer receiving for this many days**: 0<br>**Pause Feature Updates**: Blank *Note: use this functionality to prevent the device from receiving a feature update until the time passes.|
|
|Policy|Location|Suggested configuration |
|
||||||
|Select when Quality Updates are received |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Quality Updates are received|State: Enabled <br>**Defer receiving it for this many days**: 0 <br>**Pause Quality Updates**: Blank <br>*Note: use this functionality to prevent the device from receiving a quality update until the time passes|
|
|-|-|-|
|
||||||
|
|Select when Preview Builds & feature Updates are received |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and Feature Updates are received|State: Enabled <br>**Select Windows Readiness Level**: WIP Fast or WIP slow<br>**Defer receiving for this many days**: 0<br>**Pause Feature Updates**: Blank *Note: use this functionality to prevent the device from receiving a feature update until the time passes.|
|
||||||
## Wave deployment for feature updates
|
|Select when Quality Updates are received |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Quality Updates are received|State: Enabled <br>**Defer receiving it for this many days**: 0 <br>**Pause Quality Updates**: Blank <br>*Note: use this functionality to prevent the device from receiving a quality update until the time passes|
|
||||||
|
|
||||||
If you want to deploy feature updates in waves we suggest using the following configuration. For the deferral days we recommend staging them out in 1-month increments. Manage your risk by placing critical devices later in the wave (deferrals > 30 or 60 days) while placing your low risk devices earlier in the wave (deferrals < 30 days). Using deferrals days is a great method to manage your wave deployment. Using this in combination with our suggested early validation will help you prepare your environment for the latest updates from Windows.
|
## Wave deployment for feature updates
|
||||||
|
|
||||||
|Policy|Location|Suggested configuration |
|
If you want to deploy feature updates in waves we suggest using the following configuration. For the deferral days we recommend staging them out in 1-month increments. Manage your risk by placing critical devices later in the wave (deferrals > 30 or 60 days) while placing your low risk devices earlier in the wave (deferrals < 30 days). Using deferrals days is a great method to manage your wave deployment. Using this in combination with our suggested early validation will help you prepare your environment for the latest updates from Windows.
|
||||||
|-|-|-|
|
|
||||||
|Select when Preview Builds & feature Updates are received |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and Feature Updates are received|State: Enabled <br>**Select Windows Readiness Level**: SAC<br>**Defer receiving for this many days**: 0, 30, 60, 90, 120 <br>**Pause Feature Updates**: Blank <br>*Note: use this functionality to prevent the device from receiving a feature update until the time passes
|
|Policy|Location|Suggested configuration |
|
||||||
|
|-|-|-|
|
||||||
|
|Select when Preview Builds & feature Updates are received |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and Feature Updates are received|State: Enabled <br>**Select Windows Readiness Level**: SAC<br>**Defer receiving for this many days**: 0, 30, 60, 90, 120 <br>**Pause Feature Updates**: Blank <br>*Note: use this functionality to prevent the device from receiving a feature update until the time passes
|
||||||
|
|||||||
@ -1,47 +1,49 @@
|
|||||||
---
|
---
|
||||||
title: Onboarding to Windows Update for Business (Windows 10)
|
title: Onboarding to Windows Update for Business (Windows 10)
|
||||||
description: Learn how to get started using Windows Update for Business.
|
description: Learn how to get started using Windows Update for Business.
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itproauthor: jaimeo
|
||||||
ms.localizationpriority: medium
|
author: jaimeo
|
||||||
ms.audience: itpro
author: greg-lindsay
|
ms.localizationprioauthor: jaimeo
|
||||||
ms.reviewer:
|
ms.audience: itpro
|
||||||
manager: laurawi
|
author: jaimeo
|
||||||
ms.topic: article
|
ms.reviewer:
|
||||||
---
|
manager: laurawi
|
||||||
|
ms.topic: article
|
||||||
# Onboarding to Windows Update for Business in Windows 10
|
---
|
||||||
|
|
||||||
>Applies to: Windows 10
|
# Onboarding to Windows Update for Business in Windows 10
|
||||||
|
|
||||||
Windows Update for Business is a tool that enables IT pros and power users to manage content they want to receive from Windows Update Service. Windows Update for Business can control the following:
|
>Applies to: Windows 10
|
||||||
|
|
||||||
- Interaction between the client and Windows Update service
|
Windows Update for Business is a tool that enables IT pros and power users to manage content they want to receive from Windows Update Service. Windows Update for Business can control the following:
|
||||||
- End user notification for pending updates
|
|
||||||
- Compliance deadlines for feature or quality updates
|
- Interaction between the client and Windows Update service
|
||||||
- Configure wave deployment for feature or quality updates bandwidth optimization
|
- End user notification for pending updates
|
||||||
|
- Compliance deadlines for feature or quality updates
|
||||||
We also provide additional functionality to manage your environment when risk or issues arise such as applications being blocked:
|
- Configure wave deployment for feature or quality updates bandwidth optimization
|
||||||
|
|
||||||
- Uninstall latest feature or quality update
|
We also provide additional functionality to manage your environment when risk or issues arise such as applications being blocked:
|
||||||
- Pause for a duration of time
|
|
||||||
|
- Uninstall latest feature or quality update
|
||||||
Use the following information to set up your environment using Windows Update for Business policies:
|
- Pause for a duration of time
|
||||||
|
|
||||||
- [Supported SKUs](#supported-editions)
|
Use the following information to set up your environment using Windows Update for Business policies:
|
||||||
- [Windows Update for Business basics](wufb-basics.md)
|
|
||||||
- [Setting up automatic update](wufb-autoupdate.md)
|
- [Supported SKUs](#supported-editions)
|
||||||
- [Managing feature and quality updates](wufb-manageupdate.md)
|
- [Windows Update for Business basics](wufb-basics.md)
|
||||||
- [Enforcing compliance deadlines](wufb-compliancedeadlines.md)
|
- [Setting up automatic update](wufb-autoupdate.md)
|
||||||
- [Managing drivers, environments with both Windows Update for Business and WSUS, and Download Optmization](wufb-managedrivers.md)
|
- [Managing feature and quality updates](wufb-manageupdate.md)
|
||||||
|
- [Enforcing compliance deadlines](wufb-compliancedeadlines.md)
|
||||||
## Supported editions
|
- [Managing drivers, environments with both Windows Update for Business and WSUS, and Download Optmization](wufb-managedrivers.md)
|
||||||
|
|
||||||
Windows Update for Business is supported on the following editions of Windows 10:
|
## Supported editions
|
||||||
|
|
||||||
- Windows 10 Education
|
Windows Update for Business is supported on the following editions of Windows 10:
|
||||||
- Windows 10 Enterprise
|
|
||||||
- Windows 10 Pro
|
- Windows 10 Education
|
||||||
- Windows 10 S (for Windows 10, version 1709 and earlier)
|
- Windows 10 Enterprise
|
||||||
|
- Windows 10 Pro
|
||||||
|
- Windows 10 S (for Windows 10, version 1709 and earlier)
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user