![]() Since that machine has an Asus motherboard the optional update KB3133977 was skipped at the time (as several optional updates are), but changes were made to UEFI to clear the way. That's the one which caused boot problems for computers with Asus motherboards and a bit of a headache for users. However, even if the machine had those two updates (and in one case an older version), it lacked a third optional non-security update, the KB3133977 from the spring 2016. If that's a requisite, then they shouldn't be offered together. ![]() It would then seem MSFT wanted the more recent version (of the SHA-2 code signing support) to be installed before the big one, the monthly rollup. ![]() It also had an earlier version of KB4474419, the SHA-2 code signing support, also from this spring. It already had the servicing stack update from this spring, KB4490628. ![]() I had one machine fall over on this one (I'm not running WU on auto.). SHA-2 code signing support is a requirement since this summer on Windows 7, what MSFT calls "legacy Windows versions" I think it has been released and updated in stages.) (The SHA-2 code signing support has been updated again some days ago, being part of September month's updates, but that's another story. It's a monthly rollup update for August it came with another update for Windows 7 SP1, the update to the SHA-2 code signing support, KB4474419, mentioned by Hans, which was installed on your machine 14 August according to your screenshot. Though that documentation mentions a bit more than has already been mentioned above. Dave Davison wrote:Looking at the updates history I see that there is one that constantly fails, any suggestions as to what this update is and why the constant failure to install?Ĭould have replied but was away for a second or two and then Hans had replied, not much to add in this case, it's documented.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |