Pourquoi checking Windows Mise à jour so lent?
Pourquoi checking Windows Mise à jour so lent?
J'ai Windows 7 PCs that have automatic update turned off. I do updates in batch once a month or so. But each time "check for update" takes 15 to 30 minutes. Je ne comprends pas why checking for updates can be so slow? J'ai to wonder what is happening in the background. Is it computing hash? Are my PCs with automatic updates enabled suffer the same fate every time it boots up (only that I wasn't aware)?
Re: Pourquoi checking Windows Mise à jour so lent?
The *checking for updates* part is so slow because:
-
Windows 7 uses [Component-Based Servicing](https://web.archive.org/web/20130527043402/http://technet.microsoft.com/en-us/library/cc756291(v=ws.10).aspx), which means Windows Update has to work ridiculously hard to determine file and component dependencies/inter-dependencies, maintain side-by-side versions of older files/components, while still making it possible to uninstall individual updates/components but without breaking any other updates/components, all the while taking into account supercedence and god knows what else. The code that does all this must be hellishly complex.
-
Windows 7 64-bit has to maintain both 32-bit and 64-bit versions of each update.
-
Windows has to maintain both [GDR and LDR](https://web.archive.org/web/20141218171018/http://blogs.technet.com/b/mrsnrub/archive/2009/05/14/gdr-qfe-ldr-wth.aspx) versions of each update, which means on Windows 7 64-bit you get 32-bit GDR, 32-bit LDR, 64-bit GDR, 64-bit LDR for each update.
-
The code behind Windows Update is highly inefficient, probably due to its conceptual complexity. My observations over the last few years are that, as the total number of released updates has increased, update check time has increased in an almost exponential way. To me that's indicative of some kind of recursive algorithms being employed, perhaps to determine superscedence or resolve dependencies.
Unfortunately for us, Microsoft don't like talking about Windows internals so we end up having to figure it out for ourselves or speculate.
-
Windows 7 uses [Component-Based Servicing](https://web.archive.org/web/20130527043402/http://technet.microsoft.com/en-us/library/cc756291(v=ws.10).aspx), which means Windows Update has to work ridiculously hard to determine file and component dependencies/inter-dependencies, maintain side-by-side versions of older files/components, while still making it possible to uninstall individual updates/components but without breaking any other updates/components, all the while taking into account supercedence and god knows what else. The code that does all this must be hellishly complex.
-
Windows 7 64-bit has to maintain both 32-bit and 64-bit versions of each update.
-
Windows has to maintain both [GDR and LDR](https://web.archive.org/web/20141218171018/http://blogs.technet.com/b/mrsnrub/archive/2009/05/14/gdr-qfe-ldr-wth.aspx) versions of each update, which means on Windows 7 64-bit you get 32-bit GDR, 32-bit LDR, 64-bit GDR, 64-bit LDR for each update.
-
The code behind Windows Update is highly inefficient, probably due to its conceptual complexity. My observations over the last few years are that, as the total number of released updates has increased, update check time has increased in an almost exponential way. To me that's indicative of some kind of recursive algorithms being employed, perhaps to determine superscedence or resolve dependencies.
Unfortunately for us, Microsoft don't like talking about Windows internals so we end up having to figure it out for ourselves or speculate.