Volume Z

Yes, it will. The file used to be available online at a Microsoft URL. It used to get retrieved to the user profile automatically when activating the gadget and then updated regularly. The Microsoft online template went out of service soon after mainstream support ended.

No. On Dec. 1 your Config.xml turned unmodified for at least 72 hours. It is the date last modified that makes or breaks the gadget.

You started out with and then introduced the July 2016 one for no obvious reason.

When they retired all Windows-signed SHA-1 content last year, nothing actually changed in Windows 7 SP1 against their own claim. Them now claiming "We expect the SHA-1 certificate expiration to be uneventful" I guess means less than nothing will change.

Do you understand that the July 2016 update rollup and the Convenience Rollup is two different rollups? V4 of KB3125574 has been around since day one.

V4 is the first one. "Last updated: 5/16/2016". https://www.catalog.update.microsoft.com/search.aspx?q=kb3125574

"Update for Windows 7 for x64-based Systems (KB3125574) is not working at all." Sounds like good advertising to me.

Fix 80072EFF by installing the March 2016 Windows Update Client. Windows Update Client for Windows 7 and Windows Server 2008 R2: March 2016

Nein.

Is it KB976932?

What is the exact content of Update History?

MS has created additional inconvenience lately. They broke selfupdate of the Windows Update Client. The good news is there is no need to mess with version 7.6.7600.320 anymore. Give KB3138612 a shot. https://www.catalog.update.microsoft.com/Search.aspx?q=KB3138612 Regards, VZ

That would be a disadvantage of UEFI compared to BIOS I'm outright denying. UEFI launches the one Windows Boot Manager, which might as well be a Windows 7 one including an 8.1 entry. Regards, VZ

The Windows 7 boot manager won't hurt Windows 8.1 in any way, shape or form. In theory you could install anything down to Windows Vista alongside anything up to Windows 10 without causing any damage. Regards, VZ

And Windows 7 RTM, for that matter, but no bearing of KB4474419 and KB4490628 on that one either.

Works as not advertised. No bearing of KB4474419 and KB4490628 on the August 2020 SHA-1 endpoint retirement, and no bearing of the August 2020 SHA-1 endpoint retirement on Windows 7 SP1.

Thank you. You know, I couldn't for the life of me make sense of replies like "The update is not applicable to your computer". https://answers.microsoft.com/en-us/windows/forum/all/windows-7-update-error-80244019/c220c4eb-115a-4703-b580-70b36f2c2b0e An answer in perfect accordance to article 4569557 was given, but no success??? So I tried to break Windows Update by removing KB4474419. Nothing happened. Ran Windows Update on a fresh virtual installation of Windows 7 SP1 - found updates without making any preparations... I know that both updates become indispensable going further, but Microsoft's claim of "Will be impacted" regarding Windows 7 SP1 is just plain incorrect. Windows 7 SP1 has experienced no change at all by the 2020 SHA-1 endpoint discontinuation. Also note that it just makes no sense advising to fix Windows 7 RTM and SP1 the same way. https://support.microsoft.com/en-us/help/4569557/windows-update-sha-1-based-endpoints-discontinued Regards, VZ

Not at all. In full contrast to Microsoft's announcement at help article 4569557, Windows 7 SP1 remains unaffected whatsoever by the August 2020 discontinuation of SHA-1 based endpoints. Regards, VZ