Unfortunately for us, Microsoft don't like talking about Windows internals so we end up having to figure it out for ourselves or speculate. To me that's indicative of some kind of recursive algorithms being employed, perhaps to determine superscedence or resolve dependencies. 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.
The code behind Windows Update is highly inefficient, probably due to its conceptual complexity. Windows has to maintain both GDR and LDR 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. Windows 7 64-bit has to maintain both 32-bit and 64-bit versions of each update. The code that does all this must be hellishly complex. Windows 7 uses Component-Based Servicing, 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 checking for updates part is so slow because:
0 kommentar(er)
