Via IUpdateServiceManager::AddScanPackageServiceĬommon update failure is caused due to network issues. It's totally controlled by responses from the Service Locator Service. No assumption should be made of which server a serviceId is pointing to. ServiceId here identifies a client abstraction, not any specific service in the cloud. The Windows Update engine treats every service as a separate entity, even though multiple services may contain the same updates. Service IDs indicate which update source is being scanned. 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. "Agent" messages: queueing the scan, then actually starting the work:.The caller (Microsoft Defender Antivirus) tells the Windows Update engine to scan for updates. The scan first generates a “ComApi” message.When users start scanning in Windows Update through the Settings panel, the following occurs:
Windows Update does the following actions when it runs a scan.
This sync is optional and runs after the software sync.Ī 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.
Part of the scan that checks driver updates only. Part of the scan that only checks for software updates (both the apps and the operating system). Only useful if online scan has been performed before.Ĭategory scan where caller can specify a categoryId to get updates published under that categoryId.Ĭategory scan where caller can specify an AppCategoryId to get apps published under that appCategoryId. Scan that doesn't use the network and instead checks the local datastore. Scan that uses the network and to check an update server. Scan with updates from previous scan already cached in datastore. Used for grouping updates and to allow the device to filter updates. Used for prereq evaluation.Ī special "detectoid" that has an IsInstalled rule that is always true. Leaf update that's bundled by another update contains payload.Ī special "update" that contains "IsInstalled" applicability rule only and no payload. We use this term to mean several different things, but in this context it's the actual updated code or change.Īn update that contains 1-N child updates doesn't contain payload itself. Make sure you're familiar with the following terminology related to Windows Update scan: Term It uses 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 device. 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 randomization ensures that the Windows Update server isn't overloaded with requests all at the same time. The Windows Update Orchestrator on your PC checks the Microsoft Update server or your WSUS endpoint for new updates at random intervals. It does these actions automatically, according to your settings, and silently so that doesn't disrupt your computer usage.
The arbiter finalizes before the restart.ĭuring the updating process, the Windows Update Orchestrator operates in the background to scan, download, and install updates.The arbiter calls the installer to install the package.The arbiter stages the downloaded files.Windows Update client downloads files in a temporary folder.The arbiter evaluates the manifest and tells the Windows Update client to download files.Windows Update downloads manifest files and provides them to the arbiter.Orchestrator verifies admin approvals and policies for download.The Windows Update workflow has four core areas of functionality: Scan