Brian, I saw that same article (and several more) last night, all referring to the system32 issue. No good.
For the first one, it's just allowing changing the DisableAntivirus parameter (and another for file protection) for Defender in the registry. It seems like many people have installed other malware protection, and even though they attempt to get rid of it, there are remnants left. Many times, these two parameters are left at 1 in the registry as a result. So people want to change them to 0 in order to get Defender back. But this was never my problem. I did not have the values set to 1 ever...until I installed Avast, and then that is the correct behavior. When I uninstalled Avast, they went back to 0.
For the second suggestion, that command did not work for me because it said the service was already started, which was accurate. Again, other people's problem is that they can't get Defender to start, but that was never my problem. But I had still stopped and restarted the service by other means earlier, still with the same errors in action center.
I've reinstalled Avast and am going with that for a while, maybe until I go to Windows 10! Thank you.