It does. A few years ago, I decided to chase down what Windows Update does, so I ran regmon to see what configuration keys it builds in for tracing. Turns out i

It does. A few years ago, I decided to chase down what Windows Update does, so I ran regmon to see what configuration keys it builds in for tracing. Turns out it has a LOT of trace parameters in Windows 7 (and I assume for Windows 10 as well). It basically has tracing for each component.[1] But one component in particular takes a long time - and that component seems to be the one that determines the package dependencies. Honestly, if Microsoft would fix this one thing, I suspect they could speed up their update process by a factor of 2 or 3, possibly higher. As an aside, the Windows Update datastore and the Windows AD datastore must be seriously some of the very last things to use the ESENT. Dunno if Exchange still uses it. Awful way of doing things though. Windows Update is overly complicated and utterly unweildy. My perspective is that it was rather bolted together in the years when Microsoft decided to make the filesystem a database. They now have an inelegant mess that they cannot easily get rid of. I would hate to be someone who had to work on Windows Update code! 1. https://docs.microsoft.com/en-us/windows/deployment/update/windows-update-logs https://docs.microsoft.com/en-us/windows/deployment/update/w...