The Big Picture: A Delivery Service for Your Computer
Think of a magazine subscription. A publisher prints new issues, a delivery service brings them to your door, and you (or a helper) put them on the shelf. Windows Update works the same way. Microsoft publishes fixes, a client on your PC checks for new "issues", download helpers carry them in, and an installer puts them in the right place.
Why do updates exist at all? Windows has tens of millions of lines of code. Nobody writes that much code without mistakes. Updates fix them over time.
| Reason | What an update does | Example |
|---|---|---|
| Security fixes | Close holes that attackers could use | A flaw that lets a web page run code |
| Bug fixes | Correct crashes and wrong behavior | A printer that stops after sleep |
| New features | Add or improve parts of Windows | A new Settings page |
| Drivers | Newer driver files for hardware (Chapter 13) | A better Wi-Fi driver |
| Definitions | Fresh "known malware" lists for Microsoft Defender (Chapter 26) | Several small updates per day |
1.1 Windows Update Service Role
What it is: The Windows Update client is the part of Windows that asks Microsoft what is new, then fetches and installs it. It is not one program. It is a team of services (Chapter 12) that work together.
| Piece | Typical name on your PC | Its job (plain English) |
|---|---|---|
| Windows Update service | wuauserv ("Windows Update") | The classic client: scans for updates, tracks what is needed |
| Update Orchestrator | UsoSvc ("Update Orchestrator Service") | The scheduler on Windows 10/11: decides when to scan, download and install, and when to ask for a restart |
| BITS | BITS ("Background Intelligent Transfer Service") | Downloads files quietly in the background, pauses when you need the network, resumes later |
| Delivery Optimization | DoSvc ("Delivery Optimization") | Also downloads, and can share pieces with other PCs (see 1.3) |
| Windows Modules Installer | TrustedInstaller | Does the actual installing (Section 4) |
Exact service names and which one does what can differ between Windows versions. Treat the table as a map, not a law. You can see the real ones on your PC with
Get-Service wuauserv,UsoSvc,BITS,TrustedInstaller,DoSvc.
Analogy: UsoSvc is the manager with the calendar. wuauserv is the clerk who checks the catalog. BITS and DoSvc are the delivery vans. TrustedInstaller is the builder who puts things on the shelves.
Most of these are set to Manual or Automatic (Trigger Start). They wake up when needed and go back to sleep. That is why you often see them Stopped when you look. That is normal (Chapter 12).
YOUR PC MICROSOFT
+------------------------------+ +-------------------------------+
| UsoSvc: "time to check" | | Windows Update / Microsoft |
| | | | Update servers |
| v | ask | (update catalog + metadata) |
| wuauserv: "what is new" -----+------->| |
| ^ | list | |
| +--------------------------+<-------+ |
| BITS / DoSvc: download <-----+--------+ content servers (the files) |
| | | | |
| v | +-------------------------------+
| TrustedInstaller: install |
+------------------------------+
Figure 35.1 — The PC asks Microsoft which updates apply, receives a list, downloads the files with BITS or Delivery Optimization, and hands them to the installer.
Two names, one idea. You may see Windows Update and Microsoft Update. Windows Update covers Windows itself. Microsoft Update also covers other Microsoft products such as Office. In modern Settings you can switch on "Receive updates for other Microsoft products".
1.2 Update Sources (Microsoft servers, WSUS, Windows Update for Business)
What it is: The place your PC gets its updates from. At home it is almost always Microsoft directly. Companies often put a middle layer in between so they can test and control updates.
| Source | Who uses it | How it works |
|---|---|---|
| Microsoft servers (Windows Update / Microsoft Update) | Home users, small offices | The PC talks straight to Microsoft over the internet |
| WSUS (Windows Server Update Services) | Companies with their own servers | A server inside the company downloads updates from Microsoft, the IT team approves them, and the PCs fetch them from that server |
| Windows Update for Business | Companies, often without a server | Settings (or Intune, a cloud management tool) tell PCs when to update: for example "wait 7 days after release" |
Why do companies bother? One bad update on 5,000 PCs is a disaster. IT teams test on a few PCs first, then roll out in waves. A company PC may therefore show "Some settings are managed by your organization" in Windows Update. That message means a policy is in charge (policies are stored in the registry, see Chapter 17 — Windows Registry).
How does Microsoft decide what your PC needs? Each update is published with metadata: a small description that says which Windows versions it applies to, what it replaces, and which files it changes. During a scan, your PC sends facts about itself (Windows version and build, installed updates, hardware and driver IDs) and the service answers: "These apply to you." You will see this step in Section 3.
1.3 Downloading: BITS and Delivery Optimization
What BITS does. BITS is a polite downloader. It uses spare network capacity, slows down when you stream a video, and resumes after a disconnect or restart. That is why a big update can pause and continue without starting over.
What Delivery Optimization does. Big updates are large (hundreds of megabytes or more). Instead of every PC pulling every byte from Microsoft, Delivery Optimization (DO) lets PCs share pieces of an already-downloaded update with each other, like neighbors who split a bulk order.
| DO mode | Meaning |
|---|---|
| Off | Your PC downloads only from Microsoft (and does not share) |
| PCs on my local network | Shares only with other PCs in your home or office |
| PCs on the local network and the internet | Also shares with other people's PCs, and gets pieces from them |
You find it in Settings → Windows Update → Advanced options → Delivery Optimization. The switch "Allow downloads from other PCs" can be turned off if you do not want sharing, for example on a slow upload line. The pieces are checked (Section 3.2), so another PC cannot hand you a tampered update.
Metered connections. If you mark a network as metered (Settings → Network & internet → Wi-Fi → your network), Windows downloads fewer updates automatically. This protects a small mobile-data plan. Networking basics are in Chapter 28 — Windows Networking Internals.
1.4 The Whole Picture in One Table
| Question | Answer |
|---|---|
| Who makes updates? | Microsoft (and hardware makers, for drivers) |
| Who decides when to look? | The update orchestrator (UsoSvc) and your policies |
| Who downloads? | BITS and Delivery Optimization |
| Who installs? | TrustedInstaller / TiWorker.exe (Section 4) |
| Where do files go first? | C:\Windows\SoftwareDistribution\Download (a "waiting room") |
| Where do they end up? | The component store, C:\Windows\WinSxS (Section 5) |
| What happens at the end? | A restart "finishes" the job (Section 3.4) |
Services were covered in Chapter 12 — Windows Services. Section 2 shows what an update actually looks like as a package.
Summary
| Term | Plain meaning |
|---|---|
| Windows Update client | Team of services that find, fetch and install updates |
wuauserv | The classic Windows Update service (the "clerk") |
UsoSvc | Update Orchestrator: the scheduler (the "manager") |
| BITS | Quiet background downloader that can pause and resume |
| Delivery Optimization | Lets PCs share update pieces; can be turned off |
| WSUS | A company's own server that approves and hands out updates |
| Windows Update for Business | Policy-based timing control, often via Intune |
| Metadata | The description that tells a PC whether an update applies |