Not complaining really -- If I wanted to complain it would be about the 10th, when we were without power [& heat] for 1/2 the day [during a cold snap no less] -- but reporting my experience with Windows Update in case anyone else had similar...
It actually reminded me of problems with XP in the months before Microsoft turned off XP support -- since then, after doing the registry hack to report my XP Mode VM as a POS device, haven't had a lick of update problems, including on the 9th. At any rate, out of 4 win7 installations, 3 had problems, 1 especially severe. Starting at about 2 PM Eastern, ran Windows Update for over an hour without anything happening in each of 2 VMs, one win7 64, 1 win7 32, with one scvhost process reported by Task Mgr. as consuming 50% CPU -- FWIW the Performance tab & the figure at the bottom of Task Mgr. both reported varying values, from 20% to 80%, but that 50% figure for svchost never wavered. Restarting Windows & restarting the Windows Update service had no effect, while not starting Windows Update at all only meant that the same svchost process would consume the same 50% CPU as Windows ran Windows Update itself.
Windows Update for the 32 bit win7 VM worked the evening of the 9th after running Microsoft Fixit 50202.msi *Without* having aggressive mode checked. I had to use the same Fixit With aggressive checked in the 64 bit win7 VM, had to restart win7 after it found updates but would not download them, had to restart win7 again when it wouldn't install them, & had to run the Fixit again without aggressive checked when update failed on 2 updates. I wound up having to run the same Fixit twice more to tease a total of 4 more updates out of Windows Update [including the 2 that initially failed]. A copy of win7 64 installed to a real PC wouldn't run Windows Update at all until I ran that Fixit *Without* having aggressive checked, but afterwards seemed to be OK. And the 4th copy of win7 [also installed to a real PC], worked as it was supposed to -- since it was getting pretty late [near midnight] by then, I'm uncertain whether it didn't work just because it was so late & people had stopped trying to update Windows.
In the week leading up to Windows Update Tuesday all 4 of those copies of win7 had been fully updated & backed up anticipating Update Tuesday, so Windows Update had been working fine, in one case less than 24 hours before it started failing. 7 win10 & 1 XP update went normally. No win7 updates mentioning win10 in their online description at microsoft.com were installed on any of the 4 win7 installations.
