This update installs ucrtbase.dll and api-ms-win-crt-*-l1-1-0.dll v10.0.9920.0 libraries VC redist already have v10.0.9924.0 of those, but they are ment for XP only (Condition= (VersionNT = 501) OR (VersionNT = 502)) i wonder why they didn't make the condition for all and spared us the extra msu updates
Maybe the XP files aren't compatible with the Windows 7/8.1/10 files. Windows XP, really? I would have at least thought Windows 7/Server 2008. The only reasonable explanation is Server 2003. It would be interesting to know whether the 9924 files are actually just the exact same files but later versions (by exact same, I mean for the same systems). It could be a minor stuff-up by Microsoft, like the minor issues I discussed with you (abbodi) via pm earlier today. These minor issues don't affect the operation of the files or anything, they're just minor programming oversights that I can't imagine being deliberate.
Is there any way how to update to PowerShell v4-0 in W8-0-0? Windows Management Framework v4-0 doesn't install there I have heard. :/
This will probably be around the time Windows 10 goes gold, by which point releasing it on Windows 7 and 8.1 is kind of redundant . The reason for it not being redundant is because of Server 2008/2012 R2, and therefore by extension, 7/8.1., but that's hardly a point worthy of consideration. If you're on Windows 7 and 8.1, you'd be silly not to take advantage of the free upgrade to Windows 10. This is especially true of the hotfix repository, since its purpose is to maintain a high level of 'updatedness', the 7 and 8.1 repositories will be truly redundant and Windows 10 superlative.
Seeing as Microsoft are pushing Windows 10 quite heavily, especially as a 'free upgrade' to Windows 7/8.1, it's unlikely that Microsoft will maintain Windows 7 and 8.1 to any respectable extent. Why would they? Windows 10 is essentially a make-or-break for Microsoft, if it becomes redundant then Windows 7 and 8.1 will also be redundant and you might as well use an Android tablet or a Mac. Yes, those dirty three letters when placed in that order. The funny thing is, on that platform the same change would have been applauded, and anyone dare using an older version should be ashamed of themselves .
2015/03/04 Code: Added: 3038562 Moved: 3023562 / Security -> WU.Satisfy Could be a temporary status, but these WU.Satisfy updates no longer requested by WU: Code: KB2955164 KB2958262 KB2965142 KB2965500 KB2971203 KB2975719 KB2980654 KB2984006 KB2993100 KB2995004 KB2995388 KB2998174 KB3023562 i guess KB3000850 has fulfilled its statement at last
Updates are categorized based on there release type, not distribution channel most hotfixes that have (releaseType="Update") gets released later as general updates yes i know there are some update which break this rule for different reasons, but it's still the main rule take KB3006137 as an example, it's a general update, but because it's released as hotfix first i mistakenly put it in hotfix section and i don't see it worth the trouble to move it .NET 4.5.2 hotfix rollups are present in General section, because they represent the .NET 4.5.2 package itself even though monthly adobe flash package is an update, but it goes in security section because it's released as Security Update at the end, and for projects like WHD and KUC, the updates in all the 3 main sections have the same level of importance