Windows Patch Tuesdays have recently garnered a reputation for unpredictability, often leaving users in a state of uncertainty as they encounter the familiar “Getting things ready” screen. This moment can feel like an eternity, especially when the screen offers no percentage bar or estimated time of completion. Even on high-performance machines equipped with NVMe SSDs, the animation can linger long enough to provoke frustration and curiosity about what exactly is happening behind the scenes.
“Getting things ready” is hiding more than you think
It turns out that during this seemingly idle period, Windows is engaged in a complex series of tasks that go beyond mere waiting. The Update Orchestrator is responsible for managing the download and installation of updates, which involves much more than just transferring files. Windows must assess which components of the update apply to the specific configuration of the user’s PC, prepare the necessary files, and stage them for installation. This intricate process is facilitated by the servicing stack, including Component-Based Servicing (CBS), which ensures that only the relevant parts of an update are applied.
CBS installs updates at the component level, swapping in only the small, versioned pieces an update changes transactionally.
Following this preparation, Windows undertakes the less glamorous task of organizing the components, checking dependencies, and ensuring that files and registry settings are correctly aligned. Some operations must occur in a specific order, and files currently in use may need to wait until the next reboot to be replaced. Thus, while the screen may appear stagnant, Windows is meticulously orchestrating changes to the operating system.
My hardware was never the bottleneck while Windows works
Even the fastest PCIe 4.0 NVMe SSDs, capable of impressive benchmark speeds, cannot escape the intricacies of Windows servicing. The update process is not a straightforward file transfer; it involves a series of applicability checks, package handling, staging, installation, and finalization, each managed by different components. This means that despite the appearance of inactivity, Windows is effectively renovating the system while the user continues to work.
The variability in the duration of the “Getting things ready” screen can be attributed to the unique configurations of each PC. Factors such as installed components, optional features, drivers, and the current state of the Windows component store all influence the time spent waiting. Although the update package may be the same across devices, the installations they modify are anything but identical.
The wait makes sense now, but Windows could explain it better
Understanding the underlying processes has shed light on why Microsoft refrains from providing a precise percentage or countdown during updates. The workload can fluctuate significantly based on the hardware and the specific update, making it challenging to predict completion times accurately. However, a simple message indicating the current task—such as “Preparing components,” “Applying updates,” or “Finalizing installation”—would offer users a clearer picture of what is happening, alleviating some of the frustration associated with the wait.
I still don’t enjoy waiting, but at least now I know what I’m waiting for.
The absence of information can blur the line between a system performing necessary updates and one that is genuinely stuck, amplifying the perception of time spent waiting. This realization transforms the experience, allowing users to appreciate the complexity of the process rather than merely enduring the delay.
While the “Getting things ready” screen may never be a welcome sight, it is comforting to know that beneath its surface lies a carefully managed system working diligently to ensure a smooth and effective update process. A touch more transparency from Microsoft could enhance this experience, allowing users to feel more in control during these moments of waiting.
