Folks,
BTW, after rebooting my system, the service I thought I disabled went back to manual and enabled. Also, the weird suffix as mentioned, changes to another group of alphanumerics on the same services as before.
The only way to really take this on if one is crazy and maybe dangerous, is to copy those parts of the new entry with the weird extension into the original and then physically delete the weird suffixed version.
BTW, ALL of the weird suffixed services are a Type=0x0000000e0 (224) whereas the original was Type=0x00000060 (96). Both the weird and original Service entries have the same Startup Type whatever that was. Is this useful in explaining what has happened
here?
Another interesting fact is that all of the weird Service entries do not have a "DependOnService" entry as the original Service does.
It is possible that Microsoft is changing all of those Windows Services with the weird suffixes and need the old entries for now, but will eventually in one the future updates, eliminate one or both of the Service entries as they see fit.
Another thing I noticed about these Service entries: I think they are pretty new, i.e., I do not remember seeing these categories in earlier versions of either Windows 7 or Windows 10 prior to the May 2020 update.
You can start and stop any of these services, but you cannot change their Startup or Type entries either in the Services dialog or Registry. Once you reboot, everything goes back to where it was originally.
Finally, there are 19 weird Service entry categories that get this added suffix. I originally had thought there were around 10, but I counted them in the MSCONFIG application under Services.
Chris