How Windows Update works
- Windows 10
- Windows 11
The Windows Update workflow has four core areas of functionality:
- Orchestrator schedules the scan.
- Orchestrator verifies admin approvals and policies for download.
- Orchestrator starts downloads.
- Windows Update downloads manifest files and provides them to the arbiter.
- The arbiter evaluates the manifest and tells the Windows Update client to download files.
- Windows Update client downloads files in a temporary folder.
- The arbiter stages the downloaded files.
- Orchestrator starts the installation.
- The arbiter calls the installer to install the package.
- Orchestrator starts a restart.
- 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 these actions automatically, according to your settings, and silently so that doesn't disrupt your computer usage.
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 device. It uses 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:
|Update||We use this term to mean several different things, but in this context it's the actual updated code or change.|
|Bundle update||An update that contains 1-N child updates; doesn't contain payload itself.|
|Child update||Leaf update that's bundled by another update; contains payload.|
|Detector update||A special "update" that contains "IsInstalled" applicability rule only and no payload. Used for prereq evaluation.|
|Category update||A special "detectoid" that has an IsInstalled rule that is always true. Used for grouping updates and to allow the device to filter updates.|
|Full scan||Scan with empty datastore.|
|Delta scan||Scan with updates from previous scan already cached in datastore.|
|Online scan||Scan that uses the network and to check an update server.|
|Offline scan||Scan that doesn't use the network and instead checks the local datastore. Only useful if online scan has been performed before.|
|CatScan||Category scan where caller can specify a categoryId to get updates published under that categoryId.|
|AppCatScan||Category scan where caller can specify an AppCategoryId to get apps published under that appCategoryId.|
|Software sync||Part of the scan that only checks for software updates (both the apps and the operating system).|
|Driver sync||Part of the scan that checks driver updates only. This sync is optional and runs after the software sync.|
|ProductSync||A sync based on attributes, in which the client provides a list of device, product, and caller attributes ahead of time to allow service to check applicability in the cloud.|
How Windows Update scanning works
Windows Update does the following 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:
- The scan first generates a “ComApi” message. The caller (Microsoft Defender Antivirus) tells the Windows Update engine to scan for updates.
- "Agent" messages: queueing the scan, then actually starting the work:
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
Service IDs indicate which update source is being scanned.
The Windows Update engine treats every service as a separate entity, even though multiple services may contain the same updates.
Common service IDs
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 responses from the Service Locator Service.
|Unspecified / Default||WU, MU, or WSUS
|WSUS or Configuration Manager||Via ServerSelection::ssManagedServer
|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:
Look for "ProtocolTalker" messages to see client-server sync network traffic.
"SOAP faults" can be either client- or server-side issues; read the message.
The Windows Update client uses the Service Locator Service to discover the configurations and endpoints of Microsoft network update sources: Windows update, Microsoft Update, or Flighting.
If the search is against WSUS or Configuration Manager, you can ignore warning messages for the Service Locator Service.
On sites that only use WSUS or Configuration Manager, the Service Locator Service might be blocked at the firewall. In this case the request will fail, and though the service can’t scan against Windows Update or Microsoft Update, it can still scan against WSUS or Configuration Manager, since it’s locally configured.
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 operation in the background without interrupting your normal use of the device.
To ensure that your other downloads aren't affected or slowed down because updates are downloading, Windows Update uses Delivery Optimization, which downloads updates and reduces bandwidth consumption.
For more information, see Configure Delivery Optimization for Windows 10 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".
The action list describes all the files needed from Windows Update, and what the installation agent (such as CBS or Setup) should do with them. The action list is provided to the installation agent along with the payload to begin the installation.
When the option to automatically install updates is configured, the Windows Update Orchestrator, in most cases, automatically restarts the device for you after installing the updates. It has to restart the device because it might be insecure, or not fully updated, until it restarts. 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.