This is a partial, not full, update replacement. Update Revisions: When changes are made to a previously released update, it's called an Update Revision, where some pieces of the download are changed. Let us look at these points more in detail.Īfter an update is released, it can enter into three additional different phases over time: Revisions, Supersedence, and Expiration. Microsoft's WU servers are sometimes over-burdened.Which is in general an exponential algorithm, resulting in a brute-force Microsoft has not been able to optimize enough the update mechanism,.Then fixes of fixes and so on to the n'th generation Security problems, which resulted in very many hectic fixes, The last years, Microsoft was under a great pressure to fix numerous.Windows 7 is an older system, and SP2 is overdue and will probably never arrive, which makes for very many updates.WU needs to apply the updates in the correct order.WU needs to support an incalculable number of hardware and software combinations.Which unfortunately also means complicated Microsoft Windows Update mechanism is extremely sophisticated,.Without repeating what has already been said: I will try to tie them together by listing the causes in a general manner, Several facets of the problem were treated in the existing answers. 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:
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |