A variant of this approach seems to have improved but not completely corrected my situation. When I looked at @Devib/bosson's post, I was able to use the "services" UI to check these services. On my system, the wuausrv had been set to "Manual", possibly
by a script run by a remote support session I had with Microsoft which "fixed things" only long enough for another update to come out. My system now tells me it is "up to date" and does not try to reboot itself. However, the "update history" includes multiple
entries for the same updates some with "awaiting reboot" notations eve though other instances are listed as "installed."
I also tried using the "image checker" tools listed under solutions for "performance issues" and ran an hour long internet script that produced an unintelligible log file, and "Fixed" a problem I have had with the appearance of the "Network Name" assigned
to my internet connection in the "Settings" display since the days of Windows 7 (x64) on this system made in 2010. I have had the same router configuration all these years, although the hardware has been changed. When I first set this system up, it was connected
to Ethernet but would not update Windows 7 (X64) until I set up the wireless radio to talk to the wireless connection to the same router that provided Ethernet. It downloaded and was rebooted three days straight back then before it stopped applying updates
and started working as a useful computer! The name of that wireless connection always appeared on the "Network" settings screen of Windows 10 until yesterday when I ran the image checker!
I still see three instances of the update that prompted this thread in my "Update History" one showing installed, another a day later showing the same update as installed and one with the coded error message 0x80070bc2
appearing. I believe my "problems" actually started with these files as released earlier in November of 2017 and then updated by Microsoft.
| File name |
File version |
File size |
Date |
Time |
Platform |
| Activex.vch |
Not applicable |
163,646 |
06-Feb-2018 |
02:49 |
Not applicable |
| Flash.ocx |
28.0.0.161 |
28,874,224 |
06-Feb-2018 |
02:49 |
x64 |
| Flashutil_activex.dll |
28.0.0.161 |
708,600 |
06-Feb-2018 |
02:49 |
x64 |
| Flashutil_activex.exe |
28.0.0.161 |
990,200 |
06-Feb-2018 |
02:49 |
x64 |
| Activex.vch |
Not applicable |
754,642 |
06-Feb-2018 |
02:49 |
Not applicable |
| Flash.ocx |
28.0.0.161 |
22,319,088 |
06-Feb-2018 |
02:49 |
x86 |
| Flashplayerapp.exe |
28.0.0.161 |
835,576 |
06-Feb-2018 |
02:49 |
x86 |
| Flashplayercplapp.cpl |
28.0.0.161 |
177,648 |
06-Feb-2018 |
02:49 |
Not applicable |
| Flashutil_activex.dll |
28.0.0.161 |
624,624 |
06-Feb-2018 |
02:49 |
x86 |
| Flashutil_activex.exe |
28.0.0.161 |
1,424,376 |
06-Feb-2018 |
02:49 |
x86 |
I got these installed using the downloadable installer, but the log screen under Windows Update on my system still shows the installation as "pending restart" even though the script
that checks for updates says I do not need any and am "Up to Date" as of February 9th.