Should be easy feature to add, just needs to detect if you are on Win8 and execute the dism command to /StartComponentCleanup
download using windowsdownloader and after installing them all these were offered via windows update... KB2780342 KB2771744 - Included within KB2770917 KB2778171 - Included within KB2770917 KB2780523 - Included within KB2770917 KB2800033 so these must be missing from the repository
Right- KB2770917 is a "rollup"; it contains all those individual updates in one. You won't see those four individual updates in the repo since they are all contained in KB2770917. If Windows Update is showing all those individual updates, just hide them and install KB2770917 since it contains all of them.
i injected all updates downloaded and windows update offered the listed ones and if i check which updates are installed the ones listed are missing... and if you manually downloaded them from ms website they are all individual...
NICK@NUMBER11 (and everyone else), I wanted to go into more detail why many of the updates offered through Windows Update are not available in the repo. I'll use the four individual updates that you listed as being offered by WU as examples of why they're unneeded and just add clutter. All updates/hotfixes contain particular versions of various components to be updated. Some updates are small and only patch one or two components. Others, like the large cumulative ones, patch many components. The large ones are nice since they update a lot of components all at once. But the downside is that they end up creating clutter if subsequent updates don't supersede (contain newer versions) of every single component contained within them. Ideally, each update would patch just one component. That way, it would be simple to entirely remove old, superseded updates. But, instead of having one large cumulative update, there'd be hundreds of small updates to accomplish the same thing. So some of the older cumulative updates are still needed even though most of their components are now superseded. That results in multiple versions of the same components being installed and taking up space in the Windows\WinSxS\Manifests folder. And only the latest version of these components is active. That's why it doesn't make sense to install some of the old, superseded updates that are suggested by Windows Update. WU may stop complaining that the update is not installed, but it does nothing unless it is the latest version. Only the latest version is active. So it's just a waste of space to install old, superseded ones. I listed all the components that are updated by the four individual updates that you said were suggested by WU. On the first line is the version of the components contained in that update. On the following lines are the components contained in the updates and all the later versions of them that you will have installed on your system if you've installed all the other updates available from the repo. As you can see, every component in all four updates has been superseded by at least one version, and in some cases by five versions, of newer component updates. KB2780342 contains version .20553 (or .16449 GDR) of: windows-smb20-minirdr (.20555, .20625, .20667) windows-smbminirdr (.20555, .20625) windows-taskhost (.20555, .20569, .20652) windows-u..roundprocessmanager (.20555, .20569, .20652) windows-w..ames-wellknown-keys (not installed) windows-w..client-ui.resources (.20555, .20569, .20652) windows-w..ient-core.resources (.20555, .20569, .20652) windows-w..lient-aux.resources (.20555, .20569, .20652) windows-w..owsupdateclient-aux (.20555, .20569, .20652) windows-w..pdateclient-activex (.20555, .20569, .20652) windows-w..wsupdateclient-core (.20555, .20569, .20652) windows-windowsupdateclient-ui (.20555, .20569, .20652) KB2771744 contains version .20540 (or .16438 GDR) of: windows-a..on-authui-component (.20555, .20569, .20652, .20654, .20683) windows-activexproxy (.20555, .20569, .20652, .20654, .20683) windows-pdc (.20555, .20569, .20652, .20654, .20683) windows-twinui (.20555, .20569, .20652, .20654, .20683) KB2778171 contains version .20548 (or .16444 GDR) of: windows-audio-audiocore (.20555, .20683) windows-mfcore (.20555) KB2780523 contains version .20553 (or .16449 GDR) of: windows-store-client-ui (.20555, .20557, .20569, .20683)
Once Windows 8.1 comes out, I'll most likely remove Windows 8 support from the Installer for Windows Updates and the Old Update Remover. The reason for this is that Windows 8.1 is essentially a service pack for Windows 8, is a free update for people with Windows 8, and there is no need for people to stick to running Windows 8. The post Windows 8.1 support for Windows 8 is likely to be very minimal from Microsoft, since Windows 8.1 isn't a new OS, it is merely a very large update.
Burf, I agree. Just like when SP1 came out for Win7, the repo contents were based on the assumption that it was installed. Win8.1 will become the new baseline.
Yes, but I'd recommend to fully drop support for Windows 8 only after 8.1 RTMs. While the preview will be offered in June 26th, most likely not everyone will install that version. So it may be needed to support both in these several months after (there surely going to be fixes out for the preview, before it's RTM will be signed off).
That's the plan, I won't be removing Windows 8 support until Windows 8.1 it RTM'd. I probably won't even install 8.1 until the RTM becomes available, due to support for things like Classicshell (and others), and theme patching.
I will be dropping support for Windows 8 RTM on my update lists, but not straight away. I'll support the RTM version for 3 months, after the final release of Windows 8.1 (SP1)!